Related
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)
Been a bit confused on this. When I initially got this phone i317 (rogers), I rooted no problem, got TWRP running no problem and first thing did a nandroid. Flashed the older stable version of paranoid android 2.54 (i believe) which is based on 4.1.2. No issue what so ever.
As well before i go on, I've been rooting phones a while. Never bricked anything and definitely know the concept of the search button.
After running PA for a day or so and not seeing too many people having issues flashing roms on this phone i flashed another ROM (unfortunately I cant remember which one, but it was one of the popular ones on xda) TWRP had no issues flashing.
When the rom booted and android itself loaded i then had three FC errors and android rebooted. Ok thought it was a bit odd. Said screw it and recovered a backup. However any backup i flashed the error continued. Tried flashing the original PA rom again, the issue continued. Eventually had to reflash in odin the original rooted stock rom.
As you have read this issue has been resolved. My question is what happened? Is this a common problem with this device? Is it perhaps an issue going between 4.1.2 and 4.1.1? Is this just an issue with the devices internal memory? I have yet to read anyone having similar issues, however am not on xda as much as i used to be.
I am really just making sure that i am not missing something obvious or if this was simply an isolated issue before i sample some other ROMS floating around this site.
Any input is appreciated.
Sent from my SGH-I317 using Tapatalk
Did you happen to wipe data before you flashed the new Rom? I have never experienced any force closes while flashing roms.
This is what I usually do when going in between roms.
1. Wipe data/cache twice
2. Flash rom
3. Usually start to hate the Rom after the first minute.
4. GO into recovery
5. Wipe data twice
6. Restore from CWM recovery.
7. Fix permissions (just in case there was a mixup (usually helps resolve force closes)
Hope this helps. If you do happen to wipe data then I am as lost as you are . Maybe try fixing permissions? I am fairly new to android but I have been picking up modding it pretty quick.
______________________________________
Phones: iPhone 4 - > iPhone 5 - > Note 2 (Always on AT&T)
ROM: International N7105XXDMA6 by miscom
LINK: http://forum.xda-developers.com/showthread.php?t=2016575
Kernal: Perseus alpha32.1
A lot of bloatware removed.
Screen on time after normal charge: 7-8 hours always.
I don't think this is a process thing.
I always full wipe before a new rom, clear dalvic and such. This was something different.
Have been stuck in many a bootloop, but never one that caused rebooting when a recovery is flashed or a different rom for that matter.
Sent from my SGH-I317 using Tapatalk 2
Some ROMs require a factory reset wipe on top of the cache and dalvik wipe. I've used PA, and when I did the standard cache and dalvik wipe to PA from JellyBeer, I had repeated FCs, which namely was System UI. Even a nandroid restore after a cache and dalvik wipe had no effect. I was still getting the same FCs. I ended up using all four wipes with TWRP and a clean flash of JellyBeer, then a nandroid restore, to get rid of the FCs. Of course, several of my settings got wiped, including DPIs. Some ROMs just don't play well with other ROMs without a factory reset after the cache and dalvik wipe, which gets rid of your settings for a clean flash.
The other possibility is you're going between 4.1 and 4.2 ROMs. 4.2 ROMs create a new directory that puts all your files into due to multi-user login capabilities. Switching to a 4.1 ROM would certainly cause confusion within the phone without transfer the files back outside of the new directory.
Thank you. That was exactly what I needed to know. Was a scary issue the day after I purchased this phone outright lol. Not an issue I've experienced before with any other device.
Cheers.
Sent from my GT-N7105 using Tapatalk 2
So I've been flashing a couple of different roms this week like Carbon (based on AOSP), PACMAN (Don't know what it's based on), Rootbox (based on AOKP) and Slimbean (AOSP) the method I've been using to flash is wiping data/factory reset, wiping cache/dalvic cache, flashing ROM & gapps, flashing NexusLouder mod, flashing custom kernel, advance restoring data only then rebooting. I think this could be the cause of the boot loops. Or... it could be the function implemented in Carbon which doesn't require you to constantly flash gapps anymore since it backs everything in /system/apps. Anyone know what the cause of the boot loops are for sure?
Extra details - I started using this method ever since I was on AOKP which was my first custom rom. Then a few months ago, I moved to Rootbox, then Carbon, then I tried out PACMAN for a while then reverted back and just today I went back to Rootbox for a while, then I tried out SlimBean and ever since today, I've been getting random bootloops when I restart my phone. It doesn't happen every time I reboot my phone but when it does, clearing the cache solves the problem temporarly and I also had to do a full restore of my nandroid a couple of times today.
Also, I use this method because I have over 75 songs on my playlist which I spent hours creating and I don't want to start all over again. I also don't want to set all my rom settings again either.
Reduce any OC
Undo any Voltage mods
Disable any apps that alter how the system behaves
Disable all apps and enable one by one until you have an issue
You get the idea.
Definitely want to avoid restoring data from another rom and flashing audio mod. If after flashing a new rom you still get the random reboot then you can narrow down the problem.
Sent from my Galaxy Nexus
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
I always do that :thumbup:
Sent from my Galaxy Nexus using xda premium
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
Thanks for the tip
[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.)
Just like the title says. It's been a while since I've flashed a different ROM so I may be missing something simple. I'm currently using stock nexOgen 1.7 ROM, I was trying to flash one of two different CM ROMs and each time I had the same thing happen no data, the three buttons on the front wouldn't work and the keyboard wouldn't show up, it kept promoting a android keyboard force close. Each time I flash I'm wiping system, dalvik, cache, and data. I did not flash a different kernel just ROM and gapps. Let me know if I'm missing something.
Thanks guys
kazerak2 said:
Just like the title says. It's been a while since I've flashed a different ROM so I may be missing something simple. I'm currently using stock nexOgen 1.7 ROM, I was trying to flash one of two different CM ROMs and each time I had the same thing happen no data, the three buttons on the front wouldn't work and the keyboard wouldn't show up, it kept promoting a android keyboard force close. Each time I flash I'm wiping system, dalvik, cache, and data. I did not flash a different kernel just ROM and gapps. Let me know if I'm missing something.
Thanks guys
Click to expand...
Click to collapse
Maybe try going into recovery and wipe cache and davlik and fix permissions see if that straightens out the rom