Nandroid Restore Errors - com.google.process.gapps has Stopped - T-Mobile Samsung Galaxy S 4

Hi Everyone,
Trying to see if there is a simple fix for this without having to wipe the device to factory.
Working with 4.4.4 on an insurance replacement (old power button went bad). Ran a Nandroid backup on my faulty device using CWM, and when restoring to the new device (after flashing the 4.4.4 deodexed rom, permissive kernel and modems) I am getting a looping error on process.gapps and Google Play services.
Looks like something got hosed post-restore and need some assistance wrangling this without having to do a hard reset.
I've tried:
- Clearing Cache
- Clearing Dalvik Cache
- Clearing cache on Google Play Services
Unfortunately, none of these options have been successful. Does anyone have a hammer and nails approach I can use here to stabilize the device? I have no problem with reinstalling Google Play Services or GApps, but in this state the device is challenging to navigate (popup after popup).
Thank you in advance for your feedback.

Did you wipe everything and then restore your nandroid?

serio22 said:
Did you wipe everything and then restore your nandroid?
Click to expand...
Click to collapse
Yes, wiped cache, dalvik cache and data/system.

Worked around CWM by installing TWRP and converting a spare MicroSD card to Fat32. From there was able to run a TWRP System/Data backup and image the new phone.
I've experienced this issue before with CWM, so assuming it's a defect in the System and or Data backup process.
Glad to be back up.

oblivion0 said:
Worked around CWM by installing TWRP and converting a spare MicroSD card to Fat32. From there was able to run a TWRP System/Data backup and image the new phone.
I've experienced this issue before with CWM, so assuming it's a defect in the System and or Data backup process.
Glad to be back up.
Click to expand...
Click to collapse
Good to know, thanks for the update

Related

Help with CM7 boot looping

H'okay. So. I had Myn's 2.2 and I wanted to try out something different so I decided on CM7 RC2.
I do a nandroid backup (ofcourse) and then proceed to wipe my cache/factory reset. I then flash CM7 and then do a partial restore of my data for my apps/contacts.
I then proceed to the boot screen and it just loops, over and over again. Without loading my data, CM7 boots just fine... so what in my data is preventing me from being able to boot into CM7?
Thanks in advance!
Boot into recovery, wipe dalvik cache, reboot system.
Try not restoring the data part of the applications. I've heard sometimes issues can arise from that.
r916 said:
Boot into recovery, wipe dalvik cache, reboot system.
Click to expand...
Click to collapse
I have tried this.
totalanonymity said:
Try not restoring the data part of the applications. I've heard sometimes issues can arise from that.
Click to expand...
Click to collapse
What am I supposed to restore to get apps/contacts back then? :3
What you should do is backup your apps with titanium, backup your rom, then wipe factory/data, cache, dalvik cache, flash the rom. on the first boot, it may take an extra couple of minutes. After you sign in, blah blah, open titanium backup, then restore apps with data, NOT system settings.
What you have to do is flash Calkulin's Format All zip. This will delete everything except for the SD card. While still in recovery reflash CM7 and then while STILL in recovery flash the proper Gaaps. You follow these tlstwps I guarantee it will work without a problem. FYI, in terms of restoring your apps with data more than likely it wont work. I have always had trouble restoring AP data when going from Sense to AOSP (CM) Hope this helped.

Q: stuck in cyanogen boot animation - Flashed back to Cm6

So I got Cm7 running using rom manager, used titanium backup to restore apps + system data, then fixed permissions. For the last 10 minutes it's been stuck in the CM7 screen....
What should I do? Can I pull the battery without harm? Does it take that long to boot after fixing permissions?
Edit: pulled the batter and am trying to boot into recovery...going to wipe the dalvik/cache again.
Edit2: same thing for the last 6 minutes....dang. I guess I'll just nandroid in 5 minutes if it doesn't' get out of it.
Edit3: going to nandroid back. I might try it again later flashing from a Zip instead of using rom manager. I probably won't restore system data either next time. If anyone has any suggestions though please post them.
Edit4: not good...phone is bootlooping cyangen screen after nandroid.
Edit5: Cleared factordata, cache, and when I go to clear dalvik I'm getting
e unknown volume for path sd-ext
Any ideas here?
Edit6: I'm reflashing 6.1.2....okay...got through the boot and now I'm setting up the phone.
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
housry23 said:
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
Click to expand...
Click to collapse
Will do....I know I had been installing apps to the SD card using CM6 and when I first got CM7 up it said my phone memory was low. I thought it would say on the SD card.
I'll probably try tomorrow again if I get the courage and I most definitely will DL Calkun's tools.
Thanks!
I'm going to guess the nandroid didn't work either because of the phone memory low issue?
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
teh roxxorz said:
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
Click to expand...
Click to collapse
Wiped manually, installed from zip, and didn't restore system data. CM7 has been running for about an hour now.
Thanks everyone!
Glad that you got it working man.
Is ANY system data safe to restore from Titanium?
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
phsteve said:
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
Click to expand...
Click to collapse
You should never restore system settings.
For contacts, open accounts and sync, tap your google account, then sync contacts, and that'll be done.
For texts, people highly recommend sms backup or my backup. Then backup apps and data, then restore only apps and data, and you'll be set.

[Q] Frozen Bootscreen - attempted change from LeeDrOiD V3.0.2 GB to RCMix S v1.3

Hi all,
Would really appreciate your help! I'm a nOOb and may have bricked my phone. I rooted and installed a LeeDroid Froyo Rom last year, updated this recently to LeeDrOiD V3.0.2 GB. I got brave today and attempted to change this to RCMix S v1.3 (Sense 2.1+3.0mix) but now my phone is stuck on the HTC Bootscreen.
The process I followed was the same as when installing LeeDroids ROMs:
I backed up my apps
Re-partioned my SD card - 512md using ROM Manager
Used ROM Manager to boot to recovery
Factory re-set
Re-installed ROM Manager
Copied the new ROM zip file to the SD Card
Used ROM Manager to boot to recovery
Installed the new ROM which installed correctly ("Congrats, successful installation, re-boot and enjoy ..." or similar word to that effect)
Re-booted
But now it's frozen on a permanent HTC logo bootscreen.
I would greatly appreciate any help you can offer, or a link to the solution if there is one that may have been requested and solved before, I've spent an age searching the forums but can not find a solution.
Thanks in advance,
Karl
sounds like you didnt wipe the dalvik cache.
I would drop the battery out, replace and boot into recover, wipe data factory reset, wipe dalvik and go for another install.
Can you confirm if you did the above?
edit: oh and i dont know if its made a differance but when i install a new rom, i transfer to the SD card then, wipedata, wipe cache and then install as opposed to booting the phone after wiping data
Before flashing you always have to do a full wipe.
Your systemdata and apps can backed up by Titanium Backup. The backup don't get deleted by the wipe. After flashing the new rom (and eventually re-downloading/re-installing Titanium Backup you can restore all systemdata and apps by "Menu>Batch>Restore missing systemdata and apps".
First tip for the future: Always make a complete nandroid before every flash. If there are problems with your new system, you a running system anyway.
Second: When go from sense-rom to a non-sense-rom (or reversed), you must not restore system data, only the apps. Otherwise there can be heavy problems with your system.
vis-tec said:
sounds like you didnt wipe the dalvik cache.
I would drop the battery out, replace and boot into recover, wipe data factory reset, wipe dalvik and go for another install.
Can you confirm if you did the above?
edit: oh and i dont know if its made a differance but when i install a new rom, i transfer to the SD card then, wipedata, wipe cache and then install as opposed to booting the phone after wiping data
Click to expand...
Click to collapse
Cheers Vis-tec,
Yeah, it was the dalvik cache, I did exactly what you suggested and it worked perfectly. Never heard of dalvik cache before but wiping it did the job.
Thanks again,
Karl
MatDrOiD said:
Before flashing you always have to do a full wipe.
Your systemdata and apps can backed up by Titanium Backup. The backup don't get deleted by the wipe. After flashing the new rom (and eventually re-downloading/re-installing Titanium Backup you can restore all systemdata and apps by "Menu>Batch>Restore missing systemdata and apps".
First tip for the future: Always make a complete nandroid before every flash. If there are problems with your new system, you a running system anyway.
Second: When go from sense-rom to a non-sense-rom (or reversed), you must not restore system data, only the apps. Otherwise there can be heavy problems with your system.
Click to expand...
Click to collapse
Thanks MatDroid,
Good tip about the system data when moving between sense and non-sense roms - I would have found that out the hard way for sure!
I know nothing about nandroid so I'll start reading up on it!
Thanks again,
Karl
Yekrallum said:
Thanks MatDroid,
Good tip about the system data when moving between sense and non-sense roms - I would have found that out the hard way for sure!
I know nothing about nandroid so I'll start reading up on it!
Thanks again,
Karl
Click to expand...
Click to collapse
This thread might help to understand the technical definitions:
http://forum.xda-developers.com/showthread.php?t=805247
MatDrOiD said:
Before flashing you always have to do a full wipe.
Your systemdata and apps can backed up by Titanium Backup. The backup don't get deleted by the wipe.
Click to expand...
Click to collapse
Another good tip, I assumed that the wipe would delete the back-up, or to be more precise, I was unsure where it backed up the data/apps to. So I uploaded to Dropbox using the Dropbox feature in Titanium Backup ... this takes an age so it's good to know that the backup doesn't get deleted by the wipe for future rom changes!
Thanks again,
Karl
Try using RaRecovery http://forum.xda-developers.com/showthread.php?t=839621
It's the recommended recovery for RCMix S. I got stuck in splash because of CWM.

[Q] How to upgrade rom without data wipe

Hello,
I have an Amazon Kindle Fire with gedeROM v1.7. I love the updates because it makes my device better and better.
But can i update my device without data wipe so i don't have to reinstall and reconfigure the entire device every time. And if I can can someone please tell me how.
My usual procedure is download file, data wipe, clear davlik and cache, flash, wipe cache restart and wonderfull a better device. But all the data and apps go with the wipe so any help would be awesome!
Thnx for all the help!!
Moaely said:
My usual procedure is download file, data wipe, clear davlik and cache, flash, wipe cache restart and wonderfull a better device.
Click to expand...
Click to collapse
If you're not switching to a different ROM (ie, from CM7 to CM9, or from hashcode to energy...) then you can optionally skip the data wipe (factory reset), which will retain your data and applications...
Alternatively, you may want to take a look at Titanium Backup.
Thnx for the info.
I have been hearing a lot about Titanium Backup, can you give more info about the program.
With TB you can back up any apps on your device. Then when you update a rom just download TB again and then you can restore your apps that you backed up. I love TB and use it on every device that I have rooted. It is a lifesaver!! Ok maybe a time saver anyway!! LOL!!!!
I had a REALLY bad experience from not wiping everything completely. I'd definitely do a backup, like Titanium or MyBackupPro, and wipe it all just to be safe. To many goofy things can happen if you don't.
It really depends on what ROM your flashing. There are rare occasions you can cross flash without issue. Not recommended. Just updating the same ROM so wipe is necessary, unless mentioned by the dev.
If you do wipe than BUYING titanium backup is the way to go. The free version doesn't auto install apps, each needs confirmation.
I can get any ROM on the kf or my gnex but up and running in less than 15 minutes.
this is what I have been doing and I am not sure if it's bad to do or not. I make a backup of just my data using twrp, then I wipe the caches and do a factory reset. Then I install the rom, and then restore my data using twrp
chris_m128 said:
this is what I have been doing and I am not sure if it's bad to do or not. I make a backup of just my data using twrp, then I wipe the caches and do a factory reset. Then I install the rom, and then restore my data using twrp
Click to expand...
Click to collapse
Restoring your backed up data is akin to not having done "factory reset" in the first place.
You shouldn't encounter any major issues so long as you're flashing newer versions of the same ROM and there hasn't been a large change (for example, switching to linaro).

stuck at galaxy s4 screen please help

Yesterday I tried installing Danvh's 4.4.2 Google Edition ROM and I guess it must have went wrong. I backed up my current ROM and data before the installation. I did a full wipe (davick / data / cache etc.) and I also did a format of internal SD. I installed Danvh's ROM fine but when I rebooted after the installation it will not get past Galaxy S4 screen. So I figured there was something wrong with the ROM so I flashed back to my back up but when I restart my phone it will still be stuck at the S4 screen so I have to keep flashing back to the backup file. I used TWRP 2.6.1.0 for recovery and I also fixed the permissions with TWRP. Any ideas? What should I do? If my phone ever crashes I will have to restore to my only back up.
re: stuck
ragingazn628 said:
Yesterday I tried installing Danvh's 4.4.2 Google Edition ROM and I guess it must have went wrong. I backed up my current ROM and data before the installation. I did a full wipe (davick / data / cache etc.) and I also did a format of internal SD. I installed Danvh's ROM fine but when I rebooted after the installation it will not get past Galaxy S4 screen. So I figured there was something wrong with the ROM so I flashed back to my back up but when I restart my phone it will still be stuck at the S4 screen so I have to keep flashing back to the backup file. I used TWRP 2.6.1.0 for recovery and I also fixed the permissions with TWRP. Any ideas? What should I do? If my phone ever crashes I will have to restore to my only back up.
Click to expand...
Click to collapse
You forgot to do a "factory reset" in twrp before restoring your Nandroid backup.
Most likely after doing that the phone will fully boot.
Be sure to wipe data, system, cache, dalvik cache and
do a factory reset before restoring your backup.
Good luck!
Good luck!
Nope I did do factory reset as well...

Categories

Resources