I searched the forum for something similar to no avail, so if I missed it, I apologize. So I had been running CM 6 stable for a month and everything was great. Hadn't upgraded kernels, or any other modifications. Turned my phone off for the night last night, and when it came back on, stuck in bootloop for no good reason why. So, oh well, I'll just flash a new ROM, no big deal, then tried CM7RC, it boots, I use titanium backup to restore everything, it all works well, until I reboot the phone again, and bam, right back to bootloop, but this time with CM7. I'm completely out of ideas, any help would be appreciated. I've wiped davlik, cache, did factory reset, everything I can think of.
Thanks ahead of time.
Try fixing permissions in recovery, if that fails then try wiping ALL data and installing CM again. If that doesn't work, try a Sense ROM, it might be an AOSP problem
so here's an update to my problem so far. What I had left out earlier was that I could install a new ROM, and I could reboot my phone and it would work fine. Not until I used Titanium Backup and restored all of my apps and settings did I run into a problem. With that said, I did as PGleo86 said. This time, it worked just as it had before. Phone was fine, until I restored data. So I thought about what I had installed last. So the last time I wiped everything and installed CM7, I used Titanium Backup, but this time I omitted a few programs and settings, namely, Amazon App Store and Angry Birds Rio. This time when I rebooted, it worked fine. So I am slowly going to restore the settings, apps, and data I omitted one at a time and reboot my phone to see if any of them put me into boot loop. Has anyone heard of anything like this before? Particularly with Amazon App Store or Angry Birds Rio? (I did recently upgrade my version of Swype as well)
jprakes said:
so here's an update to my problem so far. What I had left out earlier was that I could install a new ROM, and I could reboot my phone and it would work fine. Not until I used Titanium Backup and restored all of my apps and settings did I run into a problem. With that said, I did as PGleo86 said. This time, it worked just as it had before. Phone was fine, until I restored data. So I thought about what I had installed last. So the last time I wiped everything and installed CM7, I used Titanium Backup, but this time I omitted a few programs and settings, namely, Amazon App Store and Angry Birds Rio. This time when I rebooted, it worked fine. So I am slowly going to restore the settings, apps, and data I omitted one at a time and reboot my phone to see if any of them put me into boot loop. Has anyone heard of anything like this before? Particularly with Amazon App Store or Angry Birds Rio? (I did recently upgrade my version of Swype as well)
Click to expand...
Click to collapse
From what I understand, its restoring the data that is killin it. You can restore all the apps you like, but when you start restoring data, it seriously screws with alot of roms. You will keep having the issue as long as your restoring data. Good luck dude
This may take a while but try reloading a few apps at a time to see which on in particular is causing the issue. I saw a post like this somewhere on this massive forum, but the person found out it was one app that was killing the boot process.
Different roms store data in different places. So titanium is writing data to somewhere it shouldn't be.
Related
OK so today my wifi went out.... Just completely went out. I tried wiping the settings and reconnecting to the Wifi point and all it does is try and authenticate, then it drops. So with a few prior bugs like this in the past, I decided to do a combo Temp Files wipe with 4.3 Smelkus MOD recovery.
EVERYTHING GOT WIPED; Go launcher is non existent, Play Store is gone, apps just magically vanished. Going into App Settings, the Symlinks are there, but the app is missing from drawer. Even all the aroma options I turned on are gone. It's basic android with no gapps. This happened to me on first install and I had to wipe my memory card and reformat. I refuse to do this again. So I am going to try and nandroid back to before the wipe.
What caused this?
In my excitement, and retardedness, I forgot to nandroid after a successful install. So it likes like I have no other choice to set EVERYTHING back up again. I'm just thankful I'm smart enough to have recurring TB backups every other day. D
Naturesretard said:
OK so today my wifi went out.... Just completely went out. I tried wiping the settings and reconnecting to the Wifi point and all it does is try and authenticate, then it drops. So with a few prior bugs like this in the past, I decided to do a combo Temp Files wipe with 4.3 Smelkus MOD recovery.
EVERYTHING GOT WIPED; Go launcher is non existent, Play Store is gone, apps just magically vanished. Going into App Settings, the Symlinks are there, but the app is missing from drawer. Even all the aroma options I turned on are gone. It's basic android with no gapps. This happened to me on first install and I had to wipe my memory card and reformat. I refuse to do this again. So I am going to try and nandroid back to before the wipe.
What caused this?
Click to expand...
Click to collapse
Im pretty sure I know what caused this. First...did you install a2sd?
Sent from my PC36100 using Tapatalk 2
Yesterday my phone was acting weird - Poweramp was starting at boot, Poweramp told me it couldn't verify my license, I had no media volume (but system volume was ok), my lock screen was being bypassed on boot, S-voice was starting whenever I put headphones in, no sound from bluetooth, etc. Weird stuff.
After troubleshooting and coming up empty, I took a backup with Clockworkmod, then restored to a backup I took on the 4th. When I rebooted, apps started crashing non-stop. Not only gapps, but also twitter, dropbox, etc. Every 1-3 seconds I'd get a couple of crashes. I also get a lot of notifications (not in crash windows) that it "cannot open database". These appear across the bottom of the screen, like when I'm notified that an app has received superuser access. It happens so often I can't even shut the phone off - I have to pull the battery.
I restored to a backup I took on January 10th and got the same thing. I restored back to the backup I'd just taken, same thing. I wiped the cache and the dalvik cache, same thing. I reflashed my gapps, but that didn't fix anything. I tried to remove my google account, but I can't get into the menu because the phone's crashing too fast.
So far, the only way I can get a usable phone is by performing a factory reset and setting up my phone again.
Does anyone have any suggestions on how I can get my data back? I have an app backup from January some time using My Backup Pro, but I don't want to lose a month's worth of data if at all possible.
I'm running a rooted Galaxy S3 (AT&T) on Stock 4.3. I've been messing with Xposed for the past couple days, but disabled almost all of the modules while trying to troubleshoot the issue (and it seemed stable before it started acting weird while I was shoveling snow). Also, only the most recent backup has Xposed installed.
Thanks in advance.
UPDATE: I was able to remove my Google account and this initially stopped the Google apps from constantly crashing, but other apps continued to crash. After a minute or so, the Google apps started crashing again.
I was able to restore a much older backup (4.0) and this seemed to work ok for the few minutes I tested it.
I did a factory reset on 4.3, which seemed ok, but when I started restoring my apps through My Backup Pro, android.process.acore started crashing every second or so. I cleared the cache, but it didn't fix the problem (in fact, it started crashing on the lock screen, which hadn't happened before.)
I'm starting to wonder if I need to flash a new ROM because something not backed up by Clockworkmod is FUBAR.
As far as I can tell, the causes of my issues were:
I think my CWM was messed up. When I flashed CM11 to get a working ROM, I saw there was an update pending. I installed that and it seemed to fix the problem with making new backups. I don't think I'll be able to recover the backups from before, but at least I can make new backups now.
I think the android.process.acore issue was the result of the My Backup Pro backup being from CM10.1 when I was trying to restore to Stock 4.3. I think there was some system data in there that wasn't compatible with stock. Selecting only the 3rd party apps that I "needed" to install seemed to resolve this.
I don't know about the original sound issue. I got a ticket response from Poweramp saying it was a Google account mismatch issue. I hadn't made any changes, so my guess is that somehow the account was corrupted. I don't know if removing/adding the account would have made a difference, since the whole thing blew up before I could try. It's also possible that something else got corrupted that caused the volume issue. Volume works fine now that I have a new ROM, so it was definitely not a hardware issue with the headphone jack. I backup restore or factory reset might have fixed the problem, but I don't know for sure.
Today I wanted to upload the new P5210 OEM Rom P5210UEUANB2. So I set up ODIN and loaded without issues. I then installed TWRP and rooted. After all that was done, I started setting the system up to the way I like it by using NoBloat to remove apps. I must have removed one that was associated with my Play Store app. This app opens and then closes just as fast.
So the next thing I did was to restore to my last save which was yesterday. I restored and the problem followed. It should be noted that when I restored, the system went back to the previous version. I am guessing that it was something in one of the caches that did not clear. So I wiped all the caches and restored again. Same thing, Play Store opened and closed just as fast.
Next I loaded the OEM Rom of the version P5210UEUAMK1. Now I get to the setup wizard and it FC's in the middle of me answering questions.
I would like to completely clean this things clock and start fresh with the AMK1 rom. How would I do that in TWRP? Would I wipe both caches, data, system and internal storage? Or would I Format Data? I guess I could try, there has to be a very basic boot level eprom in the system to at least get it into download mode.
Waiting for some advise and appreciate any you can give. Thanks.
Brian D said:
Today I wanted to upload the new P5210 OEM Rom P5210UEUANB2. So I set up ODIN and loaded without issues. I then installed TWRP and rooted. After all that was done, I started setting the system up to the way I like it by using NoBloat to remove apps. I must have removed one that was associated with my Play Store app. This app opens and then closes just as fast.
So the next thing I did was to restore to my last save which was yesterday. I restored and the problem followed. It should be noted that when I restored, the system went back to the previous version. I am guessing that it was something in one of the caches that did not clear. So I wiped all the caches and restored again. Same thing, Play Store opened and closed just as fast.
Next I loaded the OEM Rom of the version P5210UEUAMK1. Now I get to the setup wizard and it FC's in the middle of me answering questions.
I would like to completely clean this things clock and start fresh with the AMK1 rom. How would I do that in TWRP? Would I wipe both caches, data, system and internal storage? Or would I Format Data? I guess I could try, there has to be a very basic boot level eprom in the system to at least get it into download mode.
Waiting for some advise and appreciate any you can give. Thanks.
Click to expand...
Click to collapse
I think I found the problem. It was not anything I did last night, it was what I did a few days ago and saved as part of my backup. It would appear that I broke the Play Store but did not realize it until now. I restored the next oldest backup and everything is working as it should. I knew I should test certain apps before I do a backup. LOL
I posted something similar in the general questions subforum but of course there was no response.
I'm on stock rooted 4.3. If it matters, I ALWAYS get a message about gapps crashing.
Basically, I'm sick of ****Wiz and its continuous bulkiness and slowness. Tried a few ROMs, settled on PacMan. Trouble is there just seems to be NO way to restore my apps.
Titanium is no good because it breaks push notifications for any app that uses them - unacceptable.
The Play Store just refuses to act right. At first it wouldn't restore anything at all, then on one of my million flashes, I started restoring from Titanium one-by-one, then got even MORE frustrated and stopped. Now that list of about six apps is what the Play Store tries to "restore".
I've flashed and Nandroided back so many times because of this. And no matter HOW many times I manually sync, or how long I leave my phone on Wi-Fi to do it itself, when I flash it's those same six apps restoring.
Today I thought to make an update.zip in Titanium before flashing. Flashed the ROM, then Gapps. Tried the update.zip and it wouldn't work. Booted, then tried it. It worked, but didn't "reboot in 5 seconds"... had to battery pull after 10 minutes. Then the apps didn't have data. Titanium restored them and recommended a reboot. When I did that, the menu button no longer worked. At all.
I'm really ****ing sick of this. What am I supposed to do? If I have to stay on TouchWiz I'm getting rid of this phone. It's counterproductive at this point.
Are the custom ROMs based on the stock Samsung kernel? If not, that may be why your apps are crashing after being restored.
audit13 said:
Are the custom ROMs based on the stock Samsung kernel? If not, that may be why your apps are crashing after being restored.
Click to expand...
Click to collapse
Well, they're not crashing. When I restore them with Titanium, everything works fine about them except push notifications and that just can't happen.
And the ROM I've chosen for now is PacMan. I don't think it is?
I've used sultanxda's cm 13 rom since it's inception and only stayed there because of xposed. Since the official xposed was released, I decided to upgrade and have had nothing but problems.
To start with, I upgraded with TWRP by wiping (system/cache), flashing new fw by sultan, flashing the new sultanxda cm14 rom, flashed gapps, flashed magisk, wiped cache, and booted. After it booted it up, a lot of FC and apps staying on their splash window and closing.
So I tried RR and they fared well, but after a while it started doing the same. I could be not using my phone for a few hours, load whats app, and it would FC.
Backed up data (using TB), did a full wipe (system/data/cache), flashed fw, flashed rom, flashed gapp, magisk, xposed, and flashed the update.zip I created with TB. After boot and restore it did the same thing.
Thinking maybe it's the data, I did the above, but this time I didn't restore the data by TB's update.zip. I did a clean install, booted, waited for google play to restore by downloading all apps, then restored only the data using TB. This seemed to be having the best result and I used it all day with minor issues like whatsapp would not update until I launched it. So if people were sending me messages, I didn't know until I launched whatsapp.
Went to bed and woke up, same deal as the original problems. Lots of apps: Whatsapp, Web video broadcaster, whisper, signal, ring, sc, firetv app, and many more would either give FC or not launch. Only way I figured to fix it is restore the app only using TB.
I even tried reflashing the FW and Open beta FW again, but that did not help.
What is about my phone and nougat that's causing me to have these problems? I had no issue using MM with all of these apps. If they were not compatible, google would have not downloaded them after a clean install.
Anyone else having these issues or know what might be going on? I'm very tempted to go back to my MM backup and update the data for all apps if I cant fix this.
ahb83 said:
I've used sultanxda's cm 13 rom since it's inception and only stayed there because of xposed. Since the official xposed was released, I decided to upgrade and have had nothing but problems.
To start with, I upgraded with TWRP by wiping (system/cache), flashing new fw by sultan, flashing the new sultanxda cm14 rom, flashed gapps, flashed magisk, wiped cache, and booted. After it booted it up, a lot of FC and apps staying on their splash window and closing.
So I tried RR and they fared well, but after a while it started doing the same. I could be not using my phone for a few hours, load whats app, and it would FC.
Backed up data (using TB), did a full wipe (system/data/cache), flashed fw, flashed rom, flashed gapp, magisk, xposed, and flashed the update.zip I created with TB. After boot and restore it did the same thing.
Thinking maybe it's the data, I did the above, but this time I didn't restore the data by TB's update.zip. I did a clean install, booted, waited for google play to restore by downloading all apps, then restored only the data using TB. This seemed to be having the best result and I used it all day with minor issues like whatsapp would not update until I launched it. So if people were sending me messages, I didn't know until I launched whatsapp.
Went to bed and woke up, same deal as the original problems. Lots of apps: Whatsapp, Web video broadcaster, whisper, signal, ring, sc, firetv app, and many more would either give FC or not launch. Only way I figured to fix it is restore the app only using TB.
I even tried reflashing the FW and Open beta FW again, but that did not help.
What is about my phone and nougat that's causing me to have these problems? I had no issue using MM with all of these apps. If they were not compatible, google would have not downloaded them after a clean install.
Anyone else having these issues or know what might be going on? I'm very tempted to go back to my MM backup and update the data for all apps if I cant fix this.
Click to expand...
Click to collapse
/using TB is known to brek google push messaging service. Alos when going from something that was on android m to android n, always do a clean flash (formatting both caches, system and data) When backing up, make sure to only back up and restore user data. Not a single piece of system info should ever be restored.
zelendel said:
/using TB is known to brek google push messaging service. Alos when going from something that was on android m to android n, always do a clean flash (formatting both caches, system and data) When backing up, make sure to only back up and restore user data. Not a single piece of system info should ever be restored.
Click to expand...
Click to collapse
right, that's what I did this last time I reflashed everything. backed up all important apps, flashed everything, let google restore the apps, and restore only the data to the non-system apps.
would that have an effect of every other app though? I could not use web video caster even thought it was a fresh install, no restored data, because it would just FC.
ahb83 said:
right, that's what I did this last time I reflashed everything. backed up all important apps, flashed everything, let google restore the apps, and restore only the data to the non-system apps.
would that have an effect of every other app though? I could not use web video caster even thought it was a fresh install, no restored data, because it would just FC.
Click to expand...
Click to collapse
The best thing you can do is grab matlog from the play store and run a logcat. The post it in the roms thread.