Database Info

Replaced battery now FC galore.

When i picked up my charge i also got the desk cradle with the extra battery. Yesterday at work i was listening to music and drained the battery pretty quickly so i swapped in the extra battery. Once i rebooted i started getting a bunch of FC's. I'm getting ones for Google Services Framework, messaging, android.processes.acore and one or two others i can't remember. I reflashed GC and still get the errors. Anyone have any idea why this would happen after swapping batteries and how to fix this?
Sent from my SCH-I510 using XDA App

It just happens sometimes. Ill have to do this once every 3 months or so. Hope you made a backup...If you have the EXT4 formatter saved then just mount all in CWM, wipe all user data, dalvik, cache, etc. Then run EXT4 formatter, then flash GC. If you don't have it, you have to restock with the EE4 Odin and PIT, then reflash GC.
Sent from my Droid Charge running GummyFroyo 1.9.1

Happened to me a week or so ago, huge pain because I hadn't backed up in a while but it took me about a day or two to get all my apps back in order. In all honesty though it was one of the most annoying things that could happen. Had to redownload a ton of my apps and all the apps I had backed up were outdated(like ColorNote, I lost like 4 notes because it was an old backup). Happened totally out of the blue, I just rebooted the phone because apps weren't installing and I got spammed with FCloses. Not even a factory reset/cache/Dalvcache worked I had to flash the .pit/ee4factory.md5 to get my phone working again. PAIN IN TEH ASH.

Well son of a batch of cookies. That was my last resort but i suppose i will give that a shot this evening and report back to ya.
Sent from my SCH-I510 using XDA App

I finally got around to restoring my phone using the EE4 ODIN. I had no idea it was going to take over an hour to do, lol. Anyway, the flash completed and passed so I unplugged the USB cable, pulled the battery, but now I can't get the phone to turn on. Is there something else that I screwed up?

Lockett said:
I finally got around to restoring my phone using the EE4 ODIN. I had no idea it was going to take over an hour to do, lol. Anyway, the flash completed and passed so I unplugged the USB cable, pulled the battery, but now I can't get the phone to turn on. Is there something else that I screwed up?
Click to expand...
Click to collapse
It should have not taken an hour. If you flashed without the battery try flashing again with the battery in.
Also make sure you are using the PDA button.. not phone. Flash will show pass if you use phone but it will not boot.
Sent from my SCH-I510 using XDA App

Yep that was the mistake i made. I was in a rush to get my phone back up and running before i went to sleep that i accidently used the phone option. I reflashed using PDA and all is well. Now i just have to reroot.
Sent from my SCH-I510 using XDA App

I dont know if you were rooted and on a rom already but for future ref., when this happened to me I just went into CWR, fixed permissions, wiped cache and dalvik, rebooted and bam the FClosing stopped. my wifes phone on the other hand I had to just go into CWR and flash the rom over again and it cleared the problem rather than going through ODIN.

jrock7885 said:
I dont know if you were rooted and on a rom already but for future ref., when this happened to me I just went into CWR, fixed permissions, wiped cache and dalvik, rebooted and bam the FClosing stopped. my wifes phone on the other hand I had to just go into CWR and flash the rom over again and it cleared the problem rather than going through ODIN.
Click to expand...
Click to collapse
I was rooted and running GC 1.9.1. I went into CWR and tried wiping just the cache and dalvik as well as flashing the rom again and I couldn't get the FC's to stop. Thanks for the info, I'll keep this in mind next time this happens.

I was on GC 1.9 when my mega galore of FC's started happening too, my end result was a replacement phone from Verizon... I really don't know what happened or why. It just randomly happened under normal use.

Wow, that kinda sucks. They didn't say anything about the phone being rooted? They gave me hell for trading my rooted D2G for my charge.

Lockett said:
Wow, that kinda sucks. They didn't say anything about the phone being rooted? They gave me hell for trading my rooted D2G for my charge.
Click to expand...
Click to collapse
No because I flashed a bone stock ED1 with no root and nothing at all on the phone, I even had a blank 2GB SD Card in it.

Same happened to me. Yesterday I just clicked on camera and got a force close, then froze. Pulled battery, then everything was force closing. Only thing that would function was browser. Flashed everything, wiped data, you name it. Nothing has worked for me.

Happy! said:
Same happened to me. Yesterday I just clicked on camera and got a force close, then froze. Pulled battery, then everything was force closing. Only thing that would function was browser. Flashed everything, wiped data, you name it. Nothing has worked for me.
Click to expand...
Click to collapse
Just do what I said.
Sent from my Droid Charge running GummyFroyo 1.9.1

Did the rom you were running have journaling turned off by default?? If so, any improper shutdown will result in data corruption.
Sent from my SPH-D700 using xda premium

And I second clearing the cache and dalvik.
Sent from my SPH-D700 using xda premium

nismology said:
And I second clearing the cache and dalvik.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
When I had this problem clearing cache and dalvik didn't help at all.
Sent from my Droid Charge running GummyFroyo 1.9.1

kvswim said:
When I had this problem clearing cache and dalvik didn't help at all.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
It depends on the level of data corruption I suppose. As an aside, roms should really be released with journaling enable or at least have that option. The slight speed increase is not worth the hassle IMO.
Sent from my SPH-D700 using xda premium

When it happened to me one the first things I tried was wiping cache and nothing worked. If you follow kv's advice and that doesn't work then the only other method would be to odin back to stock and start fresh. I did have one fc for android.processes.acore but I can't remember what I did to cause or replicate it. The only thing I'm having trouble with now that I rerooted the phone is that I cannot get back into CWR. I flashed the latest version and was able to get in to flash gc and everything else but now when I try to get in it locks up on the samsung logo.
EDIT: I wasn't able to get past the Samsung logo no matter what I tried. I ended up having to odin back and start fresh....again.
Sent from my SCH-I510 using XDA App

nismology said:
It depends on the level of data corruption I suppose. As an aside, roms should really be released with journaling enable or at least have that option. The slight speed increase is not worth the hassle IMO.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Is there any way to re-enable it?

[Q] 4.2 to 4.3 Saving App Data

I have a possibly simple yes or no question in the case there is no alternative. So, I am currently running 4.2.2 PAC-Man Rom and I want to update to the 4.3 version of it. Technically, speaking, I have no issues in updating the ROM itself. The problem is when I try to keep my app data moving from 4.2.2 to 4.3. Whenever I try to restore data via Titanium Backup, the phone will allow it, but upon the next shutdown, will not boot again. Likewise, I have also tried to flash 4.3 and then do an advanced restore via CWM and only restore data. This has the same results as the previous option in that I can boot the phone, but if I shut it off, it won't restart. Basically, I can keep and install the original app apks, but the moment I try to restore any form of app data from the previous iteration of the ROM, my phone will refuse to restart. This predicament is met on any 4.3 ROM I have tried. I have never had this problem before, as I have been able to move from 4.1.2 to 4.2.1 to 4.2.2 (I suppose 4.3 is different?). This brings me to my question, is it possible to keep app data moving from 4.2 to 4.3? I fear I already know the answer. In any case, thank you for your time.
Tl;DR
When moving to 4.3, restoring app data from previous rom (PAC-man 4.2.2) causes the phone to lose the inability to boot. Is there any way to keep app data, or is it a lost cause? Thank you for your time.

One thing that comes to mind is are you restoring any system data? That causes problems.
Other than that I would download and install all my apps through the app store and reboot.
Then make a restore image to fall back on so you don't have to repeat these steps.
Now start restoring you app data SELECTIVELY. And restore app data ONLY. And do it one by one and reboot. This is the only way I know that can pin point the problem or the one restore data piece causing you problem.
Identifying it is the hardest part, any better ideas are welcomed.
Once identified just avoid that one app as your migration casualty.
Good luck,
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

verissimus said:
I have a possibly simple yes or no question in the case there is no alternative. So, I am currently running 4.2.2 PAC-Man Rom and I want to update to the 4.3 version of it. Technically, speaking, I have no issues in updating the ROM itself. The problem is when I try to keep my app data moving from 4.2.2 to 4.3. Whenever I try to restore data via Titanium Backup, the phone will allow it, but upon the next shutdown, will not boot again. Likewise, I have also tried to flash 4.3 and then do an advanced restore via CWM and only restore data. This has the same results as the previous option in that I can boot the phone, but if I shut it off, it won't restart. Basically, I can keep and install the original app apks, but the moment I try to restore any form of app data from the previous iteration of the ROM, my phone will refuse to restart. This predicament is met on any 4.3 ROM I have tried. I have never had this problem before, as I have been able to move from 4.1.2 to 4.2.1 to 4.2.2 (I suppose 4.3 is different?). This brings me to my question, is it possible to keep app data moving from 4.2 to 4.3? I fear I already know the answer. In any case, thank you for your time.
Tl;DR
When moving to 4.3, restoring app data from previous rom (PAC-man 4.2.2) causes the phone to lose the inability to boot. Is there any way to keep app data, or is it a lost cause? Thank you for your time.
Click to expand...
Click to collapse
What recovery are you using? If it's not TWRP 2.6.0.3 or newer, or the custom CWM provided by Team Chopsticks, you will continue to have this problem. Also, it has absolutely nothing to do with restoring data.

Fixed XD
Okay, so I have been doing nandroid backups the whole time, so I haven't really lost anything. I did try to install apps using Google Play and it would cause the same problem that restoring data only via cwm would. That said, I got bored and just left the phone boot looping and slept for 5 hours. Interestingly enough, upon checking on it later, it had in fact booted and it did function. Naturally, I reverted back to 4.2 and tried to upgrade again, this time timing it. Over all, it took about 1 hour for the phone to stop bootlooping and actually boot up. I don't really know what is wrong, but hey, it works. Nevertheless, I would like to thank you guys for your input. Sorry that my problem wasn't actually what I thought it was. :/ Good day.

verissimus said:
Okay, so I have been doing nandroid backups the whole time, so I haven't really lost anything. I did try to install apps using Google Play and it would cause the same problem that restoring data only via cwm would. That said, I got bored and just left the phone boot looping and slept for 5 hours. Interestingly enough, upon checking on it later, it had in fact booted and it did function. Naturally, I reverted back to 4.2 and tried to upgrade again, this time timing it. Over all, it took about 1 hour for the phone to stop bootlooping and actually boot up. I don't really know what is wrong, but hey, it works. Nevertheless, I would like to thank you guys for your input. Sorry that my problem wasn't actually what I thought it was. :/ Good day.
Click to expand...
Click to collapse
This is due to the recovery version you are on as the guy before your last post indicated. It has nothing to do with your restoration of data, but rather the recovery used to flash the rom and the way it's handling the partitions.
Long story short, update your recovery to one of the ones indicated two posts above mine and you should be good to go.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

bps119 said:
This is due to the recovery version you are on as the guy before your last post indicated. It has nothing to do with your restoration of data, but rather the recovery used to flash the rom and the way it's handling the partitions.
Long story short, update your recovery to one of the ones indicated two posts above mine and you should be good to go.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ah, okay, that makes a great deal of sense. Thank you for elucidating, I shall do just that.

[Q] Stuck on bootloader after battery drained

Last night I was out and my battery drained and phone shut off. When I got to the car and put it to charge the phone got stuck in the loading screen for a long time. I power cycled and nothing. I booted up to TWRP and wiped cache and the phone booted and got to the updating apps part and at the end it got stuck in the starting app part and never finished booting.
I'm on stock 4.4.2 and rooted. I was using faux's mainline kernel and had been running the latest version for a few days already.
I've tried a few things to try to get it working. I flashed the stock kernel back again and that didn't work. I also flashed the stock system image but nothing. I've been searching al morning for a fix. If possible, I would like to fix it without having to lose all my data.
Here is a logcat as well. http://pastebin.com/UYn9Z3Ja

This might sound too simple, but have you tried holding the power button for 30 seconds and letting it boot
Sent from my Nexus 5

Yea. I've power cycled it a few times and just let it sit there for long periods of time to see if it boots and it doesn't go past the boot animation. Only time it goes past it is when I wipe cache and after that it get stuck on starting apps.

I'm afraid your going to have to factory reset it. This is kind of a pita, but in recovery adb pull your /sdcard to your pc. Then afterwards adb push it back. That'll save your data. You'll probably have to flash the factory image and then reinstall twrp too.
Sent from my Nexus 5

I was afraid that it may come to that. In regards to my data. I made a TWRP backup earlier. Can I restore any of it after I do the factory reset?,

JayBachatero said:
I was afraid that it may come to that. In regards to my data. I made a TWRP backup earlier. Can I restore any of it after I do the factory reset?,
Click to expand...
Click to collapse
Sure but only users apps and data, no system apps.

JayBachatero said:
I was afraid that it may come to that. In regards to my data. I made a TWRP backup earlier. Can I restore any of it after I do the factory reset?,
Click to expand...
Click to collapse
You can but maybe the cause of the ''not booting issue'' will be in that already

JayBachatero said:
I was afraid that it may come to that. In regards to my data. I made a TWRP backup earlier. Can I restore any of it after I do the factory reset?,
Click to expand...
Click to collapse
You can restore one of your nandroids afterwards no problem
Sent from my SAMSUNG-SGH-I727

Thanks for the responses. I'll give this a try and report back later.

JayBachatero said:
Thanks for the responses. I'll give this a try and report back later.
Click to expand...
Click to collapse
Pulling and pushing the sd card will take along time. Probably 30 minutes each way or longer depending on how much stuff you have on it
Sent from my SAMSUNG-SGH-I727

Oh that I know. Part of the reason why I was avoiding the full wipe. I have the about 24gigs to pull/push

JayBachatero said:
Oh that I know. Part of the reason why I was avoiding the full wipe. I have the about 24gigs to pull/push
Click to expand...
Click to collapse
Grab a beer and get comfortable
Sent from my SAMSUNG-SGH-I727

[Q] Restoring Issue

So I created a backup with TWRP and now am trying to restore from said back up. It's been running for nearly an hour and its still on restoring data. Just wondering if this is normal. The progress bar is still spinning, but hasn't made any progress really since it started on the data partition. Just wondering what I should do in this kind of case.
Edit: Coming up on two hours, I'm scared to let my phone die. Really not sure what to do with it tho at this point.

p4ranoid4ndroid said:
So I created a backup with TWRP and now am trying to restore from said back up. It's been running for nearly an hour and its still on restoring data. Just wondering if this is normal. The progress bar is still spinning, but hasn't made any progress really since it started on the data partition. Just wondering what I should do in this kind of case.
Edit: Coming up on two hours, I'm scared to let my phone die. Really not sure what to do with it tho at this point.
Click to expand...
Click to collapse
If you still want to continue the restore, you can always plug it in the charger..... It'll charge while in recovery. One of the perks when using TWRP.
Sent from my Nexus 5 using xda app-developers app

Mojar7070 said:
If you still want to continue the restore, you can always plug it in the charger..... It'll charge while in recovery. One of the perks when using TWRP.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
what will happen if I let it die? its been going for hours now and I just have a feeling it got stuck

p4ranoid4ndroid said:
what will happen if I let it die? its been going for hours now and I just have a feeling it got stuck
Click to expand...
Click to collapse
I wouldn't recommend letting it die... Just in case, you don't want to end up with a bigger problem.
I would power off the device before letting it die and reboot to recovery and try restoring the backup again.
If it still doesn't restore your backup, you could try re-flashing TWRP again and then try restoring the backup.
Also did you make your backup with an older version of TWRP and then updated to a newer version? If so reflash the version of TWRP you used to make the backup with and then restore your backup.

[Q] Need Help after rooting implosion

UPDATE: 07-04-14 5:25pm EST:
I was able to get all my data off using a mac. I re-flashed Purity ROM after doing a full wipe. I have now re-installed all most of my apps and have begun normal use. For now this is resolved hopefully I have no further issues. Thanks for the response @Kreateablaze Much appreciated.
So here is a brief history about what I did and what I am experiencing. I am pretty much a newb here so please be gentle and excuse my ignorance.
Just in case you don't want to read my book below:
TLDR: rooted phone, Installed TWRP, installed Purity Rom, system failed hardcore, cant get data off my phone because explorer crashes. I just want to get my data off so I can re-install a ROM or just flash back to stock and re-lock the bootloader.....
-Unlocked bootloader, rooted, and installed TWRP using "Wug's Nexus Root Toolkit"
(just want to give props to any one involved in that tool, it is an amazing tool and worked flawlessly!)
-After running the toolkit, I was successfully rooted and running TWRP.
-I ran a back up using TWRP. Is that what is referred to as a "Nandroid" back up?
-After running this back up I installed "Purity ROM"
-For the first 24 hours everything was fine.
-I had to reboot my N5 due to an app that was acting up and a reboot usually cleared up the issue if force stopping didn't. (an app I used before rooting and I knew how to fix the issue I was having, I don't think this is related to my issue.)
-After rebooting the phone, I was faced with a pop up stating something along the lines of android UI has stopped working. I clicked okay, unlocked the phone it flashed black with my home screen icons and everything went back to normal. I rebooted the phone again just to make sure that was a one time fluke. This time The phone was in an endless crash cycle. Every process I could think of was crashing non stop the phone was unusable. I did some research and found something that said to go into TWRP and run a permissions repair.
-After running permissions repair my phone booted back up and was working relatively okay.
-After the repair rebooting my N5 results in that same UI crash I got the first time. BUT the phone is usable, and that process never crashes again unless I reboot.
-After running that permissions repair some of my apps disappeared. Trying to re-install them results in a -24 error. I got a few of them to re-install by clearing related data in data/data folder. A few of my apps refuse to re-install even though there is no trace of the data in the data/data folder.
-Another issue I am having after all of this is that I can NOT pull any data off of the phone. I plug it in, Windows recognizes the phone but it takes about 10-15 minutes to load the folder structure. I am then unable to copy any of the data off of the phone. Explorer crashes and I cant get the data off. UPDATE: I was able to get the data of the phone by using a friends Mac. I will post an update with some more info.
-I need to get my data off the phone before I can continue but am unable to. Any help would here would be greatly appreciated.
-Also if any one knows a more stable ROM with a similar feature set to Purity that is fast, has good battery life and isn't packed to the gills with features tht may one day cause more issues that they are worth. Please let me know.
Thanks in advance for any help you guys may be able to offer me.

Well I'm not too sure what your issue could be, but purity is one of the most stable roms on here... Have you looked in the purity thread for posts saying the same thing happened? I highly doubt it is the rom.
Sent from my Nexus 5 using xda app-developers app

Kreateablaze said:
Well I'm not too sure what your issue could be, but purity is one of the most stable roms on here... Have you looked in the purity thread for posts saying the same thing happened? I highly doubt it is the rom.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I would definitely agree that something went wrong rather than the ROM being unstable..... Any idea about how to get my data off the phone. at this point that is my main concern so I can re-flash purity....

basik17 said:
I would definitely agree that something went wrong rather than the ROM being unstable..... Any idea about how to get my data off the phone. at this point that is my main concern so I can re-flash purity....
Click to expand...
Click to collapse
I'm not too sure, I never had to get the data off my phone using a computer, always just used titanium backup. Maybe try reflashing purity, just wipe cache not any data.
Sent from my Nexus 5 using xda app-developers app

Kreateablaze said:
I'm not too sure, I never had to get the data off my phone using a computer, always just used titanium backup. Maybe try reflashing purity, just wipe cache not any data.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response. I was able to get my data off using a friends Mac... I am going to reflash Purity and see how things go. If they dont go well I may go back to stock. I never seem to have good luck with these things...