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.
Related
Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo
OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
bobstone said:
Just froze a couple.
Click to expand...
Click to collapse
There's your problem...
Sorry mate, but I can't help myself - attention everyone, here comes a rant:
I cannot believe how many people do not backup the data on their tablets! This is the second time in as many days that I read: "Something unexpected went wrong and I cannot loose my data".
If you did not back it up the question is not if you loose it, the question is WHEN!
This is a portable device! Pre-destined to be lost, stolen, dropped, submerged, spilled upon, run over by trucks - and those are everyday scenarios which are LIKELY. Don't even want to get into freak accidents... It's so easy to protect your data now-a-days! There's Dropbox in conjunction with Dropsync, there's Google Drive and a host of other solutions. There is no excuse for having only one copy of important data...... End of rant
To your problem. Before you apply a stock update you have to replace/unfreeze all stock apps. Usually the update just fails if you have frozen system apps - I do not know what went wrong in your case.
How did you update? OTA or manually?
It sounds as if your data partition is corrupted since the stock apps (installed in /system) work, but your user apps (installed in /data) do not. But that your system apps work is the good news! At least you didn't brick your tablet.
One of the stock apps is the file browser. See if you can copy your precious data to a microSD. And I'm only talking about data like pictures, files, video, projects. Don't worry about your apps.
If the file browser cannot see your data you're gonna have to get into the area of data recovery tools - lots of research ahead of you there.....
Another possibility may be - if you can access your tablet from your PC through USB - to ADB pull files off your tablet, check if your computer recognizes your tablet.
Once you have your data safe (or given up on it) you can perform a factory reset and possibly have to reflash the firmware.
BTW, if you did not protect root with Voodoo Rootkeeper before the update or if you flashed the full firmware (as opposed to doing an OTA update) you also lost root. And Asus plugged the hole Motochopper used in the latest firmware version. At this point 10.6.1.14.10 is not rootable without unlocking.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
bobstone said:
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
Click to expand...
Click to collapse
I would just wipe and start over, even if you get it functional again you could end up with problems.
Hmmm - I too think you are going to lose your data here as I can't see how you can recover without wiping if everything is force closing now.
BTW don't worry about the kernel version being cancer that is Asus naming convention. They have been using planets and have now run out so they are now using astrology instead of astronomy which is rather odd but there you go.
Previously we had mercury, venus, jupiter, uranus etc now we have aquarius and cancer......
What don't make sense and I can't accept, I've updated this device 4 times now total and never had a problem like this. Also, I've updated a few devices with frozen apps and had no problems. Are frozen apps really the cause? I can't see it.
And if I do have to wipe, and I really don't want to, will I still be rooted after wiping and is there a way to back up things since I can't use 3rd party apps? (Also, I used voodoo)
It just seems like something went wrong with the update, say something initializing or cache problem, and im sure there's an easy fix.
Please, keep the ideas coming...
I guess, I just need to clerify , stock bootloader, stock ROM, but rooted??
Sent from my [email protected]
Sorry all was reading it on the app wow that really is not good lol
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
bobstone said:
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
Click to expand...
Click to collapse
I think you will have to wipe mate as said. Painful but can't see any other way around it.
bobstone said:
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Click to expand...
Click to collapse
Yea, wipe, and no you won't keep root on a stock rom wipe. As I said previously even if you managed to "fix" the problem you would be creating potential for lockups/forced reboots. Your also not the first to have issues when upgrading with sys apps frozen, look around the forum, its been discussed before. Sucks, but there it is.
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
boy, i can't believe how close i was to actually going forward with this OTA when it "pooped" up in the notification area. good thing i had just been reading xda forums and i saw a couple posts bout ppl losing root and whatnot with said update.
now i am a happy camper on Cromi-x =D
best bet as a few already said is to try to extract your data from the thingy, and wipe it out, if you wanna take a n00b advice, if you're close to the end of your warranty period, go ahead and unlock it then proceed to cromi-x it. i was of the same position as you back when i bought it, not interested in custom roms and whatnot, just root...... but since my warranty was expiring next month anyways, and it had grown considerably sloppy and laggy, i figured out, why not? and i gotta tell you, it was the right thing to do.
hands down
anyways, good luck on your recovery.
I wiped and downgraded to .8 and will happily stay there for now. Maybe until I unlock the bootloader in the future.
vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
If you don't have it download Titanium Backup, hit Menu and wipe Dalvic cache. Reboot. The reboot will take a while because the Dalvic has to be rebuild - so don't panic
If that doesn't do it, I'm fresh out of ideas.
I tried to wipe via the stock recovery, but all the FC's was still there, and what's worse was that because of the FC's I couldn't finish (or quit) the "Set up your tablet" thingie. I always crashed on setting up a gmail account. Didn't matter if I was connected to the internet or not, or if I declined setting it up. So I had to do everything from the stock recovery.
Downloaded the .8 firwmare, unpacked the first .zip file, renamed the second .zip (to EP201_768_SDUPDATE.zip) and put it on an empty micro SD, made sure the SD-card was FAT32, booted to recovery (Power Vol down for 5 sec) and installed it via RCK, Android stock recovery.
Thanks for the tip, though. It might have worked. I don't know.
Hey, I just installed my first ROM, and I cannot seem to get the dialer to work. Whenever I try to open it, it force closes, and "android.process.acore has stopped" keeps appearing. Any help? I wiped everything as shown in the thread, and I tried to restore my contacts using Titanium Backup, and I think that may have been the problem. No one else on the thread reports this problem, it seems. Everything else seems to work.
What Android version did you come from before HellKat? I think there's sometimes issues restoring things from previous versions of Android.
It may also be another app... I did a quick Google search and things like Facebook and Hotmail came up, removed and all was well again.
I came from stock 4.1.2 rooted, I'm guessing this means I can't restore JellyBean system data/apps, only from other KitKat ROMs?
nossmeet said:
I came from stock 4.1.2 rooted, I'm guessing this means I can't restore JellyBean system data/apps, only from other KitKat ROMs?
Click to expand...
Click to collapse
Before I continue, disclaimer, I'm not a dev or anything. I'm just trying to help with what I've picked up over my time here.
Hopefully you followed the nandroid step. Go back to your stock ROM and have Google backup your contacts. It's never let me down in restoring my contacts on a new ROM.
Sorry for the confusion, but yeah, it's a bad idea backing up system apps, especially with the changes to the dialer (among other things) in Kitkat. Games and other apps should be fine, though.
asimowalk said:
Before I continue, disclaimer, I'm not a dev or anything. I'm just trying to help with what I've picked up over my time here.
Hopefully you followed the nandroid step. Go back to your stock ROM and have Google backup your contacts. It's never let me down in restoring my contacts on a new ROM.
Sorry for the confusion, but yeah, it's a bad idea backing up system apps, especially with the changes to the dialer (among other things) in Kitkat. Games and other apps should be fine, though.
Click to expand...
Click to collapse
Yeah, I made a backup, so now I'm back to stock rooted. Thanks for the help, I'll keep that in mind when flashing back to HellKat.
What recovery are you using and what gapps package?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
In an attempt to collect more data for this: http://forum.xda-developers.com/showpost.php?p=50666286&postcount=192, I made a new backup, and began restoring previous backups to identify when I had good WiFi speeds. I restored my stock ROM backup, and before I could even run any speed tests, AT&T jammed an update down my throat. No way to abort/postpone. Needless to say, I'm stuck in recovery. No matter which backup I restore, I can't get anywhere. My thoughts are that the update file is still somewhere on the phone, which is why nothing will get me past recovery. Does anybody know what the file is called and where it would be located? I'd like to exhaust every option before resorting to completely wiping everything.
Other thoughts: Is it possible to flash the stock recovery by itself? This would at least allow the update to happen.
Thanks.
What recovery are you using? This might help if you're using TWRP.
cron912 said:
What recovery are you using? This might help if you're using TWRP.
Click to expand...
Click to collapse
Perfect. Thank You.
Glad you got it working I don't know why carriers and lg find it okay to push updates to our device really without asking I've heard where people say no to the update and it installs it anyway I think its a bad business practice
Sent from my LG-VS980 using Tapatalk
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...