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)
Related
I do not know the reason for the following Situation.
I once had Fresh 3.2 installed, for no reason the phone one day stayed at the boot screen after a restart.
I tried Installing CYANOGEn but never could o I installed NONSENSE, this is all usong RA recovery.
I tried installing the latest Fresh and Myns and no luck, I decided to go Closckwork, I was finally able to istall the new FRESH. YAY SO HAPPY... NOT I cant install anythig from the market or any apks. it reboots to bootscreen saying FRESHHHHH. AHHHHH, so I tryed reinstallyng, nothing then tried Myns, wont install in closckwork.
AHHH
then I go and reinstall RAs recovery, Im able to install Myn Ota supersonic, the rom runs perfectly I can install apps on the market, it wont reboot. so Now I install Myns warm twopointtwo. and yess it installs YAY, lets go install an app.. NOOOOOOO it restarts phone to boot screen.
WHY?????????????????
is there a problem witth my phone?
Did you wipe before flashing? If you dont, it might cause the problem you are describing.
i heard psoting in the right forum helps fixs problems too (see Q&A)
You're not wiping. If you are, you're doing it wrong. If you wipe wrong, it leaves sh*t behind. Same rule applies to the men's room.
Sent cuz I like boobies
Not sure if you are doing complete wipes and disregard my answer if you are, but I used Amon RA and wipe EVERYTHING twice whenever I install a new ROM or do a nandroid restore. I wipe data, cache, dalvik cache, ext, battery, and rotation twice. I have never had a problem flashing ROMs. It might be overkill, but it works.
I have done everything
I have Wiped EVERYTHING even changed the SD card,
now Im able to Flash Fresh and Warms rom but
now I cant install any apps from the market or SD
everytime I try to install something it reboots.
Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn
Hey..
I downloaded Super Wipe for Desire HD, so I can install newer ROM, but after running it, it tells me that everything was a success, but when I restart my phone, nothing have been deleted, all my programs, rom, system files and everything else is still there.
Any ideas why's that?
ps. My phone is ****ed up, Sense not working, everything is crashing every second and so on.. I even have to restart it every 30 minutes so it works.. And 50% chance that It will not turn on, it will just vibrate 7-8 times and will stuck at HTC logo. That's why I want to re-install it.
EDIT: I just tried to delete some applications (swiftkey and others). I deleted them succesfully. I also changed wallpaper. But when I restarted my phone, all those applications were installed again and I had old wallpaper.. Maybe my phone memory is read-only?
lauris3722 said:
Hey..
I downloaded Super Wipe for Desire HD, so I can install newer ROM, but after running it, it tells me that everything was a success, but when I restart my phone, nothing have been deleted, all my programs, rom, system files and everything else is still there.
Any ideas why's that?
ps. My phone is ****ed up, Sense not working, everything is crashing every second and so on.. I even have to restart it every 30 minutes so it works.. And 50% chance that It will not turn on, it will just vibrate 7-8 times and will stuck at HTC logo. That's why I want to re-install it.
EDIT: I just tried to delete some applications (swiftkey and others). I deleted them succesfully. I also changed wallpaper. But when I restarted my phone, all those applications were installed again and I had old wallpaper.. Maybe my phone memory is read-only?
Click to expand...
Click to collapse
have u flashed superwipe before flash the new ROM?
I'm not really good in this, all I did was upload the both, super wipe and rom to SD. I ran the Super Wipe thru recovery and it told me that everything have been wiped and phone restarted back in recovery. I saw in recovery that free space on phone memory haven't changed, so I tried to boot the phone normally and it worked.. I tried to wipe the phone about 5 times..
lauris3722 said:
I'm not really good in this, all I did was upload the both, super wipe and rom to SD. I ran the Super Wipe thru recovery and it told me that everything have been wiped and phone restarted back in recovery. I saw in recovery that free space on phone memory haven't changed, so I tried to boot the phone normally and it worked.. I tried to wipe the phone about 5 times..
Click to expand...
Click to collapse
Maybe u can try
1.reboot to recovery
2.flash superwipe
3.flash the rom
4.reboot
Sent from my HTC Desire HD using Tapatalk 2
Did as you said, flashed the new rom, gave me message that everything was succesful and the new rom is ready.. However, after I restarted my phone, I saw no changes.. Old ROM, everything still crashing and applications/configuration werent deleted.
SUPERWIPE?
lauris3722 said:
Did as you said, flashed the new rom, gave me message that everything was succesful and the new rom is ready.. However, after I restarted my phone, I saw no changes.. Old ROM, everything still crashing and applications/configuration werent deleted.
Click to expand...
Click to collapse
Did you get superwipe from here? http://goo.gl/hWSCt
Just in case you should redownload superwipe. Also download and install a different ROM like Blackout ICS: http://tinyurl.com/9rltovs
If you decide to install the Blackout-- you must use the AROMA installer to wipe and format. Also do NOT select the "FINISH" button at the end of the installation-- but hit your back button and select reboot from recovery.
In Gingerbread-- I like the CoreDroid v9.4 ROM as well: http://forum.xda-developers.com/showthread.php?t=965207&highlight=coredroid
You say you flashed superwipe, did you actually go into recovery and select install zip file? Superwipe will take about 3-5 mins to wipe everything out. Again, sorry if I'm being parochial, but I just want to be clear.
If that doesnt work do it manually.
http://forum.xda-developers.com/showthread.php?p=30007255
Post#7
Sent from a dream.
1shukla said:
Did you get superwipe from here? http://goo.gl/hWSCt
Just in case you should redownload superwipe. Also download and install a different ROM like Blackout ICS: http://tinyurl.com/9rltovs
If you decide to install the Blackout-- you must use the AROMA installer to wipe and format. Also do NOT select the "FINISH" button at the end of the installation-- but hit your back button and select reboot from recovery.
In Gingerbread-- I like the CoreDroid v9.4 ROM as well: http://forum.xda-developers.com/showthread.php?t=965207&highlight=coredroid
You say you flashed superwipe, did you actually go into recovery and select install zip file? Superwipe will take about 3-5 mins to wipe everything out. Again, sorry if I'm being parochial, but I just want to be clear.
Click to expand...
Click to collapse
Superwipe took about 20 seconds to delete everything (well.. to tell that it deleted, but did not really). And yes, I downloaded it from there. And yes, I installed from recovery by choosing Install zip file.
...
download revolution hd superwipe.It will help you. and change the sensor. IT's not expensive. :good:
I tried everything.. Starting from Superwipe and Recovery built-in wipe and ending with Factory reset.. Nothing can be deleted, settings doesn't save, everything is crashing, USB doesn't work (can't connect to PC to upgrade the firmware), its hard to turn on phone and so on..
I'm really starting to give up.
[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.)
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.