Develop Bugs

How can I fix this

It keeps happening on my evo and im using the newest fresh rom and the current radio http://tweetphoto.com/33676911

jxb25 said:
It keeps happening on my evo and im using the newest fresh rom and the current radio http://tweetphoto.com/33676911
Click to expand...
Click to collapse
that's called a Force Close (FC). It usually happens with an unstable ROM/unstable app but more often it happens when you don't wipe (Cache/Dalvik) before installing a custom ROM.
Backup any important data that's not already on your sdcard, go back into recovery, wiple your cache and dalvik, and flash the ROM again. see if that helps you

initial said:
that's called a Force Close (FC). It usually happens with an unstable ROM/unstable app but more often it happens when you don't wipe (Cache/Dalvik) before installing a custom ROM.
Backup any important data that's not already on your sdcard, go back into recovery, wiple your cache and dalvik, and flash the ROM again. see if that helps you
Click to expand...
Click to collapse
even if im coming from the old fresh to the new fresh i still have to wipe

I'm not familiar with Fresh's ROMs, if you read his threads carefully I'm sure he'll tell you which version upgrades require a wipe and which don't. Usually a drastic upgrade will require a wipe. In your case a wipe will most likely fix these FCs

With the learning curve for the EVO still growing, its usually a good idea to wipe data/cache/dalvik when flashing new roms. Even updates. I haven't seen too many "No Wipe Necessary" around this forum. As long as you've got Titanium or MyBackup, wiping isnt as big of a headache as it used to be. Hope you get things figured out. Screwing with these phones can get frustrating. Dont know how many times I wished I hadnt messed with anything.

well i just wiped and reloaded fresh so hopefully this will fix everything

[Q] MAJOR Problems, Error occurred while attempting to run privileged commands

Alrighty....seems as if I have some MAJOR problems here.
Background, I have a DInc 1, rooted using Unrevoked, and the only ROM I put on it was Cyanogen Mod 7. S-off is all set up, and there is the Superuser features have worked fine 75% of the time. Everything was up and running quite well for some time. Then this weekend, I installed a few different DWLauncher themes, and things still seemed to be ok. Sunday night, I installed Words with Friends, and that is when all hell broke lose.
Now, I really can't run anything. Apps are force closing all over the place, Google framework stuff is force closing and when I even try to report a problem, even that force closes. So, I uninstalled the Words with Friends App, and changed themes, thinking those were the culprits, but seems like the damage has been done. Nothing really works and everything is force closing.
Went into the ROM Manager (premium) and did a fix permissions and it gave me the "error occurred while attempting to run privileged commands" error. I ran it a handful of times, and it worked once last night. I thought it would have cleared a bunch of stuff up, but it didn't really help at all. Kept the phone off all night, and when I got to work this morning, I started working on it. Fine, time to ditch everything and start from scratch. So, downloaded a different ROM (Cyanogen MOD nightly), and also tried a few others, which it let me download, but when I click to install, no matter what options I click from wiping cache, wiping Dalvik, backing up or anything, it always gave me the same error. So, back to ROM manager, trying to boot in recovery, error, boot into CM recovery, error.
Edit, as I finished typing this, I tried to install the nightly one more time, but did not click wipe Dalvik, and it is installing things. As soon as everything installed, it was more of the same, apps crashing all over the place. I was able to go into ROM manager and boot into CM recovery, which is now allowing me to fix problems. So, it seems as if was working properly, for the first couple of hours, but around 10 pm, roughly 12 hours after the install, app crash-o-rama again. Also, from ROM Manager, when I try to flash ClockworkMod Recovery, it force closes.
So, I am kinda stuck. No matter what ROM I download, it gives me the same error. At this point, I don't care what ROM is on there (I do have preferences), but I just want the phone working again. Is there anyway to force a wipe and install?
Thanks in advance

You can, instead of installing the ROM through ROM Manager, just download the ROM zip file, put it on your SD card, do the full wipe/factory reset/dalvik in Recovery, then flash the ROM zip from there.
I've had issues trying to install a ROM that's downloaded from ROM Manager.
Here's what I do before flashing the ROM zip file:
Wipe user data/factory reset
Wipe dalvik (under the Advanced menu in Recovery)
Wipe /boot, /system, /data, /cache (under Mounts and Storage in Recovery)
THEN flash the ROM zip file.
Hope this helps!

Thanks for the reply. It has been a long day of working on this phone. I have to pull my battery so many times, almost as many times as my blackberry.
I have installed about 4 different ROM versions until it would allow me to clean everything up, Dalvik and system cache, but as of now, everything is back up and running.....for now. Let's hope it stays that way.
If it doesn't, it seem like I will go the way of skipping the ROM Manager and just boot straight into recovery and do it all that way.
Thanks again

ROM manager isn't exactly reliable software. Most devs recommend a clockwork flash rather than ROM manager. Don't know why there are so many issues with it, but its pretty much not worth using to flash ROMs. It's fix permission feature is exactly the same routine that clockwork uses though. Updating the superuser might be something to try too.

ROM manager only wipes once and cwm3 doesn't wipe properly.... I've always read that you should wipe data cache and dalvik 3 times each before installing a new ROM wich is why you should use cwm.
Sent from my Synergy Rom using XDA App

:facepalm:
Re: multiple wipes
http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache

k_nivesout said:
:facepalm:
Re: multiple wipes
http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
Click to expand...
Click to collapse
Awesome link!

That you all for the info. I tried a few things, installed a few ROMS, wiped them each time, and back to the CM7 nightlies and it all seems to be working fine now. Let's hope it stays that way.
Next time I have problems, I will have to do everything out side of ROM Manager and see if it has a better result..
Thanks again

Actually this has happened to me, usually happens when installing or Uninstalling certain hardware.
After reinstalling my roms to get it to work right when it did it few hours later to infuriate me. The only thing that did work was booting into Recovery and install my rom again but with what the guy said.
Wipe all data, everything, factory reset.
Then install your rom, then make sure you don't install or Uninstall certain hardware.
Sent from my HTC Droid Incredible -CyanogenMod- 157#build/Chads IncrediKernel ("Using" XDA Forums App)

three major problems

ok so heres the deal...
i downloaded htcclay supercm7 (latest version) from ROM manager premuim... flashed it and rebooted my phone... after 3 seconds i noticed three major problems:
1- where is the status bar? oh wait... "status bar not responding" oh... force close issue :S
2- i'll try fixing the status bar issue by rebooting... WHAT?? i can't turn off my phone... it reboots direcly into "google" splash screen!!
3- lockscreen gone!!
any ideas on how to fix these??
thank you!

PROBLEMS UPDATE:
just got to cyanogenmod settings, system, update nofication... when i click it... the settings force closes
its frustrating!!

Wipe. In either hboot or recovery. Whichever one you can get into. Flash something more reliable. A stable cm build. I'd say the latest nightly, but I don't want to sound like a broken record.
Never again load something from rom manager's list
Sent from my HTC Vision using XDA Premium App

LOL... ok
i reflashed the latest ILWT CM7 and everything went back to normal...
just one last question: i usually wipe dalvik cache and flash a ROM...
should i wipe data if i flash a new ROM?
and should i wipe data if i update a ROM?

Riro Zizo said:
LOL... ok
i reflashed the latest ILWT CM7 and everything went back to normal...
just one last question: i usually wipe dalvik cache and flash a ROM...
should i wipe data if i flash a new ROM?
and should i wipe data if i update a ROM?
Click to expand...
Click to collapse
General rule of thumb:
- when switching to an entirely different rom (or if you switch to a rom by a different developer, e.g. bulletproof miui to osimod miui) it's best (in many cases necessary) to do a full data/cache wipe
- when updating a rom one can generally assume to get by fine if only cache and dalvik are wiped, in this case extensive wiping should only be necessary if you encounter problems or the OP specifically tells you to do so.

[Q] ROM with Settings Profiles besides CM9?

I am currently using CM9 on my GNex because it has a built-in Profiles management application in Settings.
Is this feature exclusive to CM? Do other ROMs have this feature? I have tried various market apps to replicate this functionality, but none of them seem to work the way the CM9 one does.
I thought I had seen someone using AOKP and it had this in his Settings, but when I tried to Flash that ROM, I got a ton of errors on reboot and didn't find Profiles in the Settings section either.
Also, as I am relatively new to Android (this is my first Android device), should I do a complete wipe data before installing a totally different ROM to avoid process errors? I am using Clockwork Mod recovery to flash ROMs and just performing the default "wipe Dalvik cache" before installing a new ROM. So far, the only ROM I am able to install/update is CM9. AOKP and Codename Android just gave me a ton of process errors after booting and were just unusable. As such, i am currently stuck using CM9, but have really bad wifi performance with it.
TIA!

bryanus said:
Also, as I am relatively new to Android (this is my first Android device), should I do a complete wipe data before installing a totally different ROM to avoid process errors? I am using Clockwork Mod recovery to flash ROMs and just performing the default "wipe Dalvik cache" before installing a new ROM. So far, the only ROM I am able to install/update is CM9. AOKP and Codename Android just gave me a ton of process errors after booting and were just unusable. As such, i am currently stuck using CM9, but have really bad wifi performance with it.
TIA!
Click to expand...
Click to collapse
Yes. Yes Yes Yes Yes. ALWAYS do a full data wipe when moving from one ROM to another ROM. You can sometimes get away with not wiping if you are simply upgrading to a newer version of the same ROM, but anytime that you run into issues after installing a new ROM please do make sure that you wiped data before posting/complaining about issues.

Thank you for your clarification. The next time I try a completely different ROM I will do a full data wipe. I assume flashing new Nightlies of the ROM I am already running doesn't require a full data wipe?
But can you or anyone else tell me if AOKP or any other ROMs have the "Profiles" feature in Settings, like CM9 does? Or is this exclusive to the CM9 ROM?
Thanks again.

bryanus said:
Thank you for your clarification. The next time I try a completely different ROM I will do a full data wipe. I assume flashing new Nightlies of the ROM I am already running doesn't require a full data wipe?
But can you or anyone else tell me if AOKP or any other ROMs have the "Profiles" feature in Settings, like CM9 does? Or is this exclusive to the CM9 ROM?
Thanks again.
Click to expand...
Click to collapse
I haven't seen it anywhere else, though AOKP does offer a Quiet Hours option.

THANK YOU!
Using your suggestion to do a wipe data when flashing a rom, I downloaded the latest CM9 nightly, and just installed it wiping both the data and cache.
After my initial setup and installing the speedtest app, my ping is back to normal at ~25ms and 15mb down and 2 up!
Do you always (or recommend) wipe the data even if you are just updating the current ROM?
Hopefully one of my other apps wasn't the cause of this issue, but I'll soon find out once I have re-installed everything.
Thanks again.

bryanus said:
Using your suggestion to do a wipe data when flashing a rom, I downloaded the latest CM9 nightly, and just installed it wiping both the data and cache.
After my initial setup and installing the speedtest app, my ping is back to normal at ~25ms and 15mb down and 2 up!
Do you always (or recommend) wipe the data even if you are just updating the current ROM?
Hopefully one of my other apps wasn't the cause of this issue, but I'll soon find out once I have re-installed everything.
Thanks again.
Click to expand...
Click to collapse
The ROM developer will usually state in the changelog / release notes if a wipe is required/recommended for an upgrade. Rule of thumb though:
1) Updating ROM to newer version, same Android release (ex: 4.0.3 -> 4.0.3) ==> No wipe
2) Updating ROM to newer version, different Android release (ex: 4.0.3 -> 4.0.4) ==> WIPE
3) Changing from one ROM to another ROM (CM9 -> AOKP) ==> WIPE

Interesting. After reinstalling my apps one by one, I've been running speedtest and found that Airsync/Doubletwist is the cause of my slowness. Uninstalling and rebooting fixes the speed/ping issue right away. Glad I bought this app. Not.

[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"

[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?

nwjimmy said:
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
Click to expand...
Click to collapse
Are you wiping system and data before flashing? This is most likely your issue.

zelendel said:
Are you wiping system and data before flashing? This is most likely your issue.
Click to expand...
Click to collapse
yes, cache and dalvik, and a factory reset.

nwjimmy said:
yes, cache and dalvik, and a factory reset.
Click to expand...
Click to collapse
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.

zelendel said:
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
Click to expand...
Click to collapse
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.

nwjimmy said:
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
Click to expand...
Click to collapse
No wiping the system doesnt format the data partition. Wipe system then format the data and then wipe the caches and then flash the rom.

Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
matt_schieman said:
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Agreed.
Double check your gapps and make sure uts the right version
sent from my 1920 overclocked note 2 running jedi xp12

What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

nwjimmy said:
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Most rom threads have a download link to the gapps that work with the version of android that specific rom is on. Look in the rom thread for the one you're currently running. There are different gapps for each android version (4, 4.1, 4.2)

I have that same problem too
I was trying to install new roms for my phone i tried liquid smooth and avatar and CM 10. I also tried install a new kernel and also different recoveries but nothing seems to work. I never "dirty" flashed and i use the right gapps. Someone please help me here i hate stock roms!

No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't work.

xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse

fig03 said:
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
That's a good point. You should be on TWRP 2.7.0.0 that's the latest version of that recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, but it constantly froze, tried to reset, stuck with the same issue. Never used TWRP, so if someone could actually point me in the right direction, that'd actually be helpful.

xantechie said:
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, though...it doesn't really look the way I remember it last it worked, but it's had the issue so long, I forget what it actually looked like before.
Click to expand...
Click to collapse
I have no idea how to use TWRP...it only lists a .img file and no instructions on how to use it. zip files can be used from the bootloader or recovery. WTF am I supposed to do with an .img file. And it can't be to use the terminal emulator because to do that I would have to be able to get passed the Setup Wizard...which is the issue.

I finally figured it out with CWM. Thankfully. The phone would've went flying otherwise.
If anyone else stumbles upon this thread (so they can find the answer for CWM also), you have to format the device from the CWM Recovery to get rid of the crap that is blocking it. I did the following:
Once in CWM Recovery, Remove your SD card to avoid formatting it by accident.
Use the Volume Key to scroll to "mounts and storage".
Format all existing options (this is why the SD needed to be removed); this will blank out the phone's system which was causing the Setup issue to begin with.
Put your SD card with the ROM to be installed back into the phone.
Follow the guide as normal after this (install ROM, then reboot, then KK_gapps, then wipe the two caches, then reboot.)