Related
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Eric_Eric_Eric said:
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Click to expand...
Click to collapse
There may have been a corruption in your data backup. Just delete that backup and make a new one.
Nope, I tried all three of my backups and had the same problem with all three. Plus, I can't simply make a new backup. I tried restoring to the backup and lost my stuff because it didn't finish restoring my data.
I'm having some issues with cwm too. Sometimes when I'm trying toi recover, it says "md5 mismatch", maybe its a linked problem?
Sent from my GT-S5830 using XDA
rommanager
Install rommanager.apk premium and, to me is to solve the problem
So, I think I figured it out. Apparently, I only get this error when my backup contains more than a certain number of apps (or possibly the /data is over a certain size). Granted, I do have over 350 apps, but why is CWM Recovery messing up while trying to restore a big backup? It really should not affect it, but it seems to. So, I will be backing up with Titanium for my apps, and making nandroid backups only when I have under about 350 apps installed. If anybody else has any insight, please share it with me. Thanks.
The Answer (I am pretty sure...)
Okay, I think I finally figured it out. The reason it was not restoring properly was because I had about 350 user apps installed. My guess is that, while restoring, the recovery (CWM recovery in my case) puts the /data onto the RAM, and the RAM is not large enough to hold that much at once. I deleted a lot of apps, backed up in CWM recovery, and restored back to the backup, and everything worked flawlessly. I am surprised that no one has ever had this problem. So, in the future, I am making Titanium backups of all my apps, batch uninstalling a bunch of them from within Titanium (so that I have under 300 at the most), and then making a backup. Then, I can flash a new ROM, recover, or whatever and finally use Titanium to put all my apps and data back. I just thought I would post this in case anyone else ever finds this problem. It was really frustrating for me, but the insufficient RAM theory seems to explain it. Post your thoughts on the matter.
Eric_Eric_Eric said:
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Click to expand...
Click to collapse
its better to use titanium backup application for you.user friendly and worthy..
So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
intelligentduck said:
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
Click to expand...
Click to collapse
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Trozzul said:
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Click to expand...
Click to collapse
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
intelligentduck said:
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
Click to expand...
Click to collapse
might want to try flashing a stock rom via odin cause it sounds like you have stock recovery now, i dont know if anyone will pick you up in the q&a section, since yours is us cellular i dont think they have a forum for that specific contractor just only t-mobile at&t and verizon would have one. you can ask them in their q&a but tell them your situation and that your on us cellular. good luck mate. if ya have any questions just ask right here.
So guys, yesterday I updated twrp (cwm) on my i9505 and everything worked fine.
this afternoon i suddenly couldnt use my phone anymore because i got systemui fc's messages every 3 seconds.
i reflashed the rom, cleaned cache +dalvik but it still wouldnt work.
so i thought: hey, you did a complete backup yesterday, why not use that.
well, seems that this didnt work out so well.
its always telling me failed when trying to restore either /system or /data (boot and efs works fine).
i dont exactly know whether i made the backup before or after the update, but either way i do think that it SHOULD NOT be a problem (im looking at you, devs)
do you guys have any idea on how i can possibly use my old backups? i downgraded again but it still says failed everytime
any help will be greatly appreciated.
oh and yes, i did use the search, but all suggestions that help didnt with me
hi.
i'm not a pro/dev, but by flashing rom or restoring backup i think you are missing a point.
i think, you need stock recovery too to have phone fully reset. in case you flash Stock rom i think it also flashes stock recovery too. but incase not, the old recovery and changes you made to custom recovery are still there. so you maybe is facing that problem.
as i mentioned above that i'm not pro/dev, so again just trying to find the exact problem/point maybe you are missing or i could be wrong too. all i mean is that updated recovery is still there. see in case you can flash stock recovery and stock/custom rom again. i hope you get the point/idea what i mean to say. try it and i think you'll not get the error.
but do not do anything in case you are not sure/aware about what you are doing.
i hope it help.
no, i dont need the stock recovery to fully reset it. trwp can do that too.
actually my point was that it denies to restore that backup and i have no goddman clue why.
(so nothing about roms or so, all that works perfectly fine)
ok i fixed it, it seems like the last backup i made was faulty so i just took an older backup. never had an issue like this before
Thread closed - OP request!
I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?
kanjigirl said:
I don't know if I missed a step or not, but every app and settings screen now takes about 20-30 seconds to open, booting takes 3-5 minutes. The phone is set up with the same ROM, kernel, apps, etc. as a few weeks ago when it was running super-fast.
I reflashed this version of CM 11 which had worked perfectly for me for about a month (this is a Samsung Galaxy Blaze S 4G):
cm-11-20150119-NIGHTLY-t769.zip
I was downgrading back to that after trying a nightly that made staticky lines all over my phone and made it lock up constantly...
When I reflashed, here's what I did (after backing up with TiBu):
In recovery I wiped to factory
Cleared the cache and Dalvik cache
Formatted /system and /data
Flashed the zip of CM 11 from my external SD
Flashed the zip of GaPPs from the external SD
Rebooted
Rebooted fine, I installed TiBu and Link2SD and started restoring apps/moving to 2nd SD card partition.
The phone is much much slower than stock. I don't know what the difference is... can someone please give me a checklist to try or tell me what I might have done wrong in the re-flashing process?
Click to expand...
Click to collapse
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.
LS.xD said:
Hi
There are newer versions of CM11 t769 up already.
You should wipe cache and dalvik after restoring your apps. If it doesn't help, make a clean installation of cm and try if the speed is better. Restoring apps via Titanium Backup while using Link2SD can easily cause errors. May be you have reinstall apps without restore. Also new partitioning of your sd card could help.
Click to expand...
Click to collapse
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).
kanjigirl said:
How do I choose a version of CM to use?? This is new to me, just rooted for the first time last month. I don't know how to choose... I was using that one I mentioned above for a month with zero issues, then upgraded to a new nightly, but had to downgrade back due to problems and that was where my issue here started...
I did wipe cache and Dalvik after restoring my apps, and I did repartition my SD card as Link2SD wasn't working for me after reflashing (I got a new beta version of Link2SD from the developer that worked perfectly).
Click to expand...
Click to collapse
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.
LS.xD said:
The CM11 builds are sorted by date. Newest build CLICK HERE are always on the top. Latest is 02/23. Keep in mind that CM is still under develpoment and may not run stable.
Click to expand...
Click to collapse
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).
kanjigirl said:
Should I pick the newest build then, and reflash with that? I see there's a stable one for CM 10 for my phone, but it's from 2012...
Should I go with something other than CM? I'm just confused at this point. I like Kitkat and would like to stay with that if feasible (my stock phone was ICS).
Click to expand...
Click to collapse
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time
LS.xD said:
I haven't tested the builds as i don't have the phone, its usefull to read the CM11 thread for your phone to check out bugs. You can try newer builds, but theres no guarantee that everything works. All in all you should go for newer versions from time to time
Click to expand...
Click to collapse
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?
kanjigirl said:
Hmm. My build was stable, I upgraded to a new one, and my phone stopped working. Going back isn't working either.
CM 10.0 is listed as a stable release, I'm wondering if that would be better (i.e. less time spent wiping and reflashing repeatedly) than a new nightly for CM 11?
Click to expand...
Click to collapse
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.
LS.xD said:
CM10 = Android 4.1.2
CM10.1 = Android 4.2.2
CM10.2 = Android 4.3.1
CM11 = Android 4.4.4
CM12 = Android 5.0.2
CM10 means you have NO bugs, everything runs stable at the cost that you have a really old rom. If you don't like maintain your phone continuisly its a good choice. I really like trying new stuff, so i flash nearly every new build of used roms / kernels for my phones. So I would stay at CM11. But thats just my personal opinion. By the way you don't need to create backups with Titanium Backup all the time. Just make a backup with your recovery. After installing a new rom, use Titanium Backup with the option "Extract from nandroid backup" to restore your apps. On previous phones I also used tools like Link2SD or Int2Ext, but after some time it always caused problems and never ran 100% stable and fast, so think about if you really need it.
Click to expand...
Click to collapse
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.
kanjigirl said:
Ack. Well... I like Kitkat a lot. I might get the latest CM11 nightly and new GAPPS and try that first.
I have so little memory, kept running out of space and that's why I use Link2SD. But thanks for the advice on TiBu, I did make a Nandroid backup last night from CWM.
Click to expand...
Click to collapse
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.
LS.xD said:
PA GApps are quite good and still up-to-date. Use "PICO" to save some space.
Click to expand...
Click to collapse
That looks great, thanks very much!
I'll post back here once I get my phone straightened out in the next couple of days to say what happened, in case it helps someone later.
Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?
kanjigirl said:
Possibly stupid question - do I need to do anything with the kernel or pit if I'm just installing a new ROM? That was only for rooting, right?
Click to expand...
Click to collapse
Kernel is always included in the new "rom". So everytime you flash a rom, you automatically flash the kernel with it. PIT is the partition table of the phones partition. As long its not clearly necessary, DON'T ever change it!
Got it, thank you for your help!
So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.
kanjigirl said:
So last night I wiped the phone and flashed the latest CM 11 (from yesterday) and the Pico package from PA-GApps. The phone is now super-fast again. I restored a few key apps to try out for the next day or so before restoring the rest, but so far so good, everything is back to normal. Thank you so much for the help.
Click to expand...
Click to collapse
Sounds great
Quick question - if this thread is still open. The phone's been fine since I flashed CM 11 and Pico GApps, until this morning, when it now does 'Android is Upgrading' every time I boot and every user app crashes as soon as it's opened. I have all auto-syncs and auto-updates disabled, and haven't added any user apps to the phone since Wednesday.
Do I need to flash again, and then have to go through the restore process all over? Or could it be an app causing this? I'm not sure where to look for a source of the problem.