Hey all, never posted on here before because I've had good luck with ROMS in the past but here goes.
Haven't rooted since the 4.3 update. Rooted the other day with cfautoroot. Everything went fine. Decided to try slimrom, so I installed TWRP 2.7.0, made a backup, ect. Went to install the ROM and it gave me errors. So I restored my backup. I had a hell of a time getting past the at&t screen but I finally got it to boot. The minute I unlocked, I was bombarded by "com.processes.gapps has unexpectedly quit" among every other app telling me it failed. So I got to the backup and restore and did a factory restore. Everything seemed to be normal. So I looked online for some information on the errors. Found a forum that indicated I was using a TWRP version that was too new. So I installed 2.6.1. Because I apparently enjoy being aggravated, I did the whole process over again. The same result happened. After more research I discovered that TWRP may have been the culprit along with ROM manager. So I installed Clockwork and did the whole process AGAIN! I got slimrom to install without problems. I was able to make a backup of slimrom as well. Just to be sure, I went and did a wipe in clockwork and tried to restore the backup I made of stock. Restarted, same error messages. Every second. Did a factory restore and everything was fine. So then I did a backup again and restored my backup of slimrom. It works fine! If I try to restore the backup of stock, I get errors. What's going on here!?
What I tried:
Clearing caches and data of the apps that were throwing errors
Stopping download manager and restarting it.
Clearing cache and delvik cache in CWM
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Related
I just flashed the Quick Settings for Official GB OTA (4.06.605.2).
http://forum.xda-developers.com/showthread.php?t=1239820
Now I'm getting the following error every couple seconds. "The process android.process.acore has stopped unexpectedly." I have cleared the cache and the dalvik cache. Is there anything I can do short of factory reset or restoring a backup to get rid of this error?
Not likely since you flashed something over top of your rom set up. Just bite the bullet and revert to a backup or reflash the rom.
I flashed this earlier today and I haven't had that FC issue. Any other mods installed?
Sent from my ADR6300 using XDA Premium App
I backed up everything with Titanium and did a factory reset. That seemed to fix the problem but after I restored my apps I started to get FCs again. I just wiped everything and flashed McSense v1.2 and the Quick Settings on top of that. Rebooted and everything works good. I'm going to re install everything from market rather than restore from backup.
Also, it helps to backup only user apps and some data. Avoid system days if you were restoring any.
Hello,
I was flashing the latest version of AOKP using TWRP, and the update failed. I verified the MD5 hash before attempting the flash, but figured I'd the file had gotten corrupt somehow. So I went to reboot my phone, and it hung on the boot loader screen. I Pulled the battery and tired again, but same result. So I booted back into TWRP, restored from the backup I took just prior to attempting the flash, and upon booting my phone went directly to the Setup Wizard. I rebooted, tried the restore again, but same result. I went through the wizard, and confirmed my phone had factory reset (Note, I didn't manually wipe anything).
Does anyone know what might cause this, and if I have any way to restore the backup I have? I was going from AOKP JB Builld 3 to 4, so I didn't take a Titanium Backup first. I've been using CWM since I got my GNex in January and have never had an issue (I've switched ROMs several times, and done many backup.restores with CWM. So i'd like to think I know what I'm doing ). This is the first time I've tried out TWRP, and everything seemed to go smoothly (Except for the failed flash).
Any help would be greatly appreciated. I've been searching around and haven't found anyone else reporting this.
Not sure why it factory reset but if you still have cwm back ups flash cwm and restore one of those. Factory reset isn't a bad thing though staying fresh is the best way to start a new ROM. I don't recommend restoring anything.
Sent from my Galaxy Nexus using xda premium
Ok so here is my situation. I was running RootBox and decided to restore my backup of JediX. After running JediX for a bit I missed RootBox so I decided to go back and as I was restoring my back-up of RootBox TWRP said that the restore failed. So I tried booting back into the OS only to be stuck in a bootloop. So I wiped system, data, cache and dalvik and did a clean flash of RootBox and Gapps. Much to my surprise when it booted up all my apps that I had on my RootBox Nandroid were there but the system configurations were gone. Confused about my apps still being here because I know I wiped data I decided to go to the playstore and realised that even tho the play store app is there I actually do not have any Google services for example I can not even add my google account. So I thought that the RootBox nandroid must have messed something up I decided to tried restoring the previous JediX nandroid that worked ealier and yet again I was confronted by a Restore Failed message. And no matter how many times I wipe and flash I can not get any google services to stick and nor can I get a clean wipe of my device.
So after that long rant has this happened to anyone or does anyone know of any solution?
Update: Ok so Flashing TWRP 2.4.4 via Odin allowed me to flash rootbox and gapps and have the google services working properly (so far...) but still even after doing a factory reset and a fresh install once i booted up all my apps were already installed all 150+ of them... When I get back from work tomorrow I will back up everything on my PC and attempt a full wipe including internal storage
Hello
last night I tried installing the carbon rom for my Note 2 N7100. (v1.8 Release stable build)
Everything wen't fine but I used titanium backup to backup my files and I also have a backup with CWM. I cleared all data/factory reset and wipe cache plus I installed the 4.2.2 gapps. The OS worked completely fine but when I used titanium backup to restore all apps and system data, It asks to restart which I did and when I restarted my phone the startup time took 25 minutes+ so I knew something wen't wrong. I rebooted into recovery and wiped cache and data reset again but I'm still having issues. I forgot to mention I tried using titanium backup and just restoring system data and not the apps.
I decided to do a restore completely using the CWM backup then I flashed 4.3 gapps to get it back up to date. However, when I tried to startup my phone, gapps isn't working properly and keeps popping up com.process.gapps or something like that has stopped. Usually this means the wrong version of gapps is installed but I've tried reflashing it incase I had a bad flash but that didn't work either.
I'm now using carbon rom without any of my previous system data or apps.
What can I do?
Thanks
I'm trying to restore a backup, and every time I try TWRP successfully restores it, I reboot system, and then about 3 seconds into the boot animation the phone reboots into recovery and asks for my security pattern. When I unlock it, it says "running openrecovery script" and wipes /data/, then says "/cache/twrp/openrecoveryscript not found" and reboots to system. When Android boots, I have the setup screen and can't get out of it.
I arrived in this situation by trying to update to the july security updates, and finding that I flashed the wrong build of a ROM, then trying to go back to my previous state. After the first restore attempt, I wiped cache & dalvik, which I now assume was bad.
Is there something I can do to prevent TWRP from running that script? Can I edit it? Or should I just accept my fate and spend hours reinstalling everything
Running Dirty Unicorns 11.4, TWRP RC2.
Thanks.
Holy smokes, I am having the same issue..
I went ahead and wiped.. yay.. time to start again.
Same happened to me. Had to start over from factory reset status ?
Sent from my Pixel XL using XDA-Developers Legacy app
I recall reading on some thread (too many to remember which) that RC1 was more reliable for backups and RC2 for flashing zips.
I found this to be true. I never could successfully restore a backup with RC2, so I went back to RC1.
This is a well known issue with RC2. You can keep RC2 installed, but fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img for backups and restores.