Related
So, I have been having some major problems with my phone. Tons of force closes, major lag times and things like that. I have tried a handful of different ROMs, including CM7, the nightlys, Miui and a few others. I hear great stories about people and rooting and I want to be one of them. I am tired of all the hassles. So, when talking to someone in the office who has had no issues with his Droid 2, he suggested, and said he has read, the best thing to do is go back to stock, unroot, as they will remove all possible conflicting files that could be causing problems. Then, re-root, and install whatever.
Any thoughts on that? Generally, my process for installing a new ROM, I boot into recovery manually, clean cache, clean Dalvik, then install ROM. Then, I restore apps and data from Titanium and restore the Nandroid from Rom Manager. The past couple times, I have done the factory reset, but eventually, a day or 2, it goes back to the same problems. Maybe, I should just try it without the restoring the Nandroid (even though it is a backup from when there was no problems) and the app data from Titanium. I assume, you know what happens when you assume, that both the Nandroid and Titanium backups are clean as I backed up when I was having no issues.
So, any thoughts here? Unroot, then re-root or is there something else I should try to wipe everything clean to solve the problems? Currently, on the original Droid Incredible (got it on the release day, so the first screen), running 2.2 when I rooted, currently on Miui 1.9.16, but just installed it 10 minutes ago and was running the Cyanogen nightly's before hand..
Thanks in advance
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Try not restoring apps and data from Titanium, as restoring the app is okay, but restoring data can cause unwanted things to happen more times than not.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that...
If you flash the RUU to return to stock and re-root, make sure you use the 2.2 RUU. If you use the 2.3, you need to be s-off to get rooted again. If you use the 2.3 RUU and you're s-on, no root for you...come back one year.
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
Click to expand...
Click to collapse
Thanks for the correction, I forgot to put system in there...restoring system data is not good.
+1 on ROM Manager issues, always get a zip file of the ROM, and flash through recovery.
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that....
Click to expand...
Click to collapse
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
Click to expand...
Click to collapse
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
MikeDaub said:
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
Click to expand...
Click to collapse
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
loonatik78 said:
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
Click to expand...
Click to collapse
I am fine with not restoring it, I just thought "that is what you should do".
I don't venture too far from the regular settings, so it isn't a pain to do, just thought I should...
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Click to expand...
Click to collapse
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
MikeDaub said:
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
Click to expand...
Click to collapse
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
loonatik78 said:
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
Click to expand...
Click to collapse
That's kinda what I figured, but I thought it was worth asking so I don't completely wipe the whole thing every time I install an update. The nightly I am on now seems to be working, so the new plan is keep whats working until it doesn't work anymore, or some major update comes along..
Thanks again for the help. I really appreciate it.
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
jackbtha1 said:
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
Click to expand...
Click to collapse
Certainly worth a thought. The card that is in it now came from a different phone. I am pretty sure I formatted it when I first plugged it in, but it can't hurt to try...
Thanks
Hi everyone,
I got a question. Is it a must to wipe before flashing a rom? For example, I'm on a rom and i want to flash another rom. Why is it a must to wipe it? What happens if I don't wipe it and flash a new rom?
Kind regards,
Semih
Its not a must but its highly recommended if you don't sometimes you'll get bootloops, sometimes you'll get random crashes and apps not working or you could get very lucky and everything might work fine. You should at least wipe the /cache partition, you won't lose any data.
semihsikier said:
Hi everyone,
I got a question. Is it a must to wipe before flashing a rom? For example, I'm on a rom and i want to flash another rom. Why is it a must to wipe it? What happens if I don't wipe it and flash a new rom?
Kind regards,
Semih
Click to expand...
Click to collapse
if you are on the same rom and the dev updates then most of the times no it is no need to update. if you are trying different roms though then yeah best to do is wipe. if you go into ARHD thread in the first page there is a script called superwipe. download that and flash it before you flash a new rom and that will do all the wipes for you. or just do it the old fashion way in recovery and reason why to wipe sometimes so you do not have old system data from previous roms
NoobTerminator said:
if you are on the same rom and the dev updates then most of the times no it is no need to update. if you are trying different roms though then yeah best to do is wipe. if you go into ARHD thread in the first page there is a script called superwipe. download that and flash it before you flash a new rom and that will do all the wipes for you. or just do it the old fashion way in recovery and reason why to wipe sometimes so you do not have old system data from previous roms
Click to expand...
Click to collapse
Also make sure 100% you have your Rom on your sd as you can't mount sd in recovery and after running there is no system.
Sent from my HTC One X using xda premium
treebill said:
Also make sure 100% you have your Rom on your sd as you can't mount sd in recovery and after running there is no system.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
And also a backup..that is the most important thing...went through a lot of threads that i read and most of the people on some threads ask on how to restore using RUU cause they do not have a backup of their stock rom..So please always make a backup my friend
It's not. They call that a "dirty flash". I've never done it but I've heard that it's not advised.
I want to flash a new rom, but i don't want to use titanium backup to restore my apps, thats to much time. And if I wipe it, my settings will lost. So, i don't want to do it. But it seems that I have to do it, otherwise i'll get some errors and bootloops etc. I thank you all for your fast reply. I'll wipe my phone
A nandroid backup. If I do it while on the old rom, can I restore it on the new rom? not an updated rom, just another rom of another developer..
semihsikier said:
I want to flash a new rom, but i don't want to use titanium backup to restore my apps, thats to much time. And if I wipe it, my settings will lost. So, i don't want to do it. But it seems that I have to do it, otherwise i'll get some errors and bootloops etc. I thank you all for your fast reply. I'll wipe my phone
Click to expand...
Click to collapse
contacts you can save them if you have a google account my friend. regarding backing up apps with Titanium backup if you have the Pro version it is all a matter on a few clicks. so my advise would be get it if you do not have the Pro version
semihsikier said:
A nandroid backup. If I do it while on the old rom, can I restore it on the new rom? not an updated rom, just another rom of another developer..
Click to expand...
Click to collapse
Yeah thats fine, I usually flash the old rom first then restore the backup when coming from cm9 or miui to stock to avoid bootloops etc.
NoobTerminator said:
contacts you can save them if you have a google account my friend. regarding backing up apps with Titanium backup if you have the Pro version it is all a matter on a few clicks. so my advise would be get it if you do not have the Pro version
Click to expand...
Click to collapse
Yes, I have the pro version, thats not a problem. Ok, I'm going to wipe it for the safety. Thanks a lot
semihsikier said:
Yes, I have the pro version, thats not a problem. Ok, I'm going to wipe it for the safety. Thanks a lot
Click to expand...
Click to collapse
no problem mate
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
dal320driver said:
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
Click to expand...
Click to collapse
dal320driver said:
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Click to expand...
Click to collapse
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
kmok said:
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
Click to expand...
Click to collapse
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
dal320driver said:
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
Click to expand...
Click to collapse
Okay, I was just making sure something wasn't forgotten when you were going back to JB this time around. I figured you were able to get the different ROMs working since you were able to make a backup of the JB ROM you were using. AFAIK the different versions of CWM (5 vs 6) shouldn't matter in this situation. Hopefully someone else has had the same problem and will be able to chime in.
CWM6 creates backups differently than CWM5 or most other recoveries. Instead of putting the entire backup in one folder, it has a separate Blobs folder that contains a lot of the data. If the folders get separated, the backup won't get restored correctly. Did you by any chance move the main folder or delete the blobs folder?
This is my first custom flash off stock. I have actually had some experience flashing due to accidently flashing from LH9 to LG1, which doesn't work. So I had to install TWRP, do a factory reset, root it, and install LH9 from there.
But I plan on trying out CM10 and I have a few question.
A) Can I just flash CM10 in ROM Manager since it is built in?
B) How can I keep my apps, app data, account data, folders,settings...etc? I have both CWM Pro and Titanium Backup Pro installed.
C) Is there anything that is worse in CM10 than Touchwiz?
D) If I don't like CM10, I can go into CWM ROM Manager and just restore my Backup, correct?
To be honest you need to flash it and give a shot and see what you think, everybody loves something different.
Download from the cm10 build from the link in the xda thread and also get the 10/12 gapps.
Boot to recovery and make a NANDROID BACKUP!
When you install, you will need to do a full wipe.(Wipe Data/Wipe Cache/Wipe Dalvik/Format System in that order to be safe
Flash the cm10 rom and the flash the 10/12 gapps.
Then Reboot!
And enjoy the goodness!
I love CM10 or AOKP much better than TW, just my opinion.
Hope this helps!:cyclops:
GilaMonster1 said:
This is my first custom flash off stock. I have actually had some experience flashing due to accidently flashing from LH9 to LG1, which doesn't work. So I had to install TWRP, do a factory reset, root it, and install LH9 from there.
But I plan on trying out CM10 and I have a few question.
A) Can I just flash CM10 in ROM Manager since it is built in?
B) How can I keep my apps, app data, account data, folders,settings...etc? I have both CWM Pro and Titanium Backup Pro installed.
C) Is there anything that is worse in CM10 than Touchwiz?
D) If I don't like CM10, I can go into CWM ROM Manager and just restore my Backup, correct?
Click to expand...
Click to collapse
QnA bud. Good to see you're starting to flash tho.
I've tried many, many ROMs on my S3 but I keep going back to CM10. Even though it's not a stable release for my model it's still awesome
Couldn't I just use ROM Manager since CM10 in on there and wipe data and cache?
Isn't the CWM ROM Manager backup a Nandroid?
How could I keep my apps and most my data...etc?
I appreciate your help, but I was knew how to do it in that way
Use Titanium to backup all your apps & data, boot to CWM recovery take a backup and install CM10 then restore your apps from Titanium, should be that easy!
Yeah, perhaps you guys don't use it, but my question remains. I've backed up using ROM Manager and transferred that image to my PC for an external copy. Couldn't I just install CM10 using ROM Manger as it is supported? Isn't that backup a NANdroid?
Or is it just not preferable?
Thanks for any help guys/
Can someone please answer my questions?
rom manager simply boots into recovery for you and makes the backup itself, etc. however, if you want to do more (wipe /system, etc) you need to go into recovery manually and do it.
sent from my I747
cehf said:
rom manager simply boots into recovery for you and makes the backup itself, etc. however, if you want to do more (wipe /system, etc) you need to go into recovery manually and do it.
sent from my I747
Click to expand...
Click to collapse
So basically I should can ROM Manager to upgrade CM10 or restore, but not flash new ROMS?
GilaMonster1 said:
So basically I should can ROM Manager to upgrade CM10 or restore, but not flash new ROMS?
Click to expand...
Click to collapse
i'm confused by your wording, sorry. rom manager would be suitable to your needs. it can install a rom for you, but it will only wipe data/factory reset. it will not wipe /system or dalvik cache like so many installation instructions say to do. rom manager can backup your rom and restore your backup.
so yes, you can use it if you choose to, but learning to use cwm would probably be easier in the long run than needing to rely on an app.
sent from my I747
How would I keep photo or music that are on my phone's memory? Aren't they in a SD parition?
GilaMonster1 said:
How would I keep photo or music that are on my phone's memory? Aren't they in a SD parition?
Click to expand...
Click to collapse
they are either on the internal sd card or one that you inserted into your phone. you won't lose any data on those.
GilaMonster1 said:
Can someone please answer my questions?
Click to expand...
Click to collapse
You should really do some reading over in the development section. They're full of information that can answer all these questions you have.
Sent from my Nexus 7 using xda app-developers app
I've got my mind set on jellybomb and would like to flash that coming from stock. Will dirty flash work? First time flashing a custom rom on this phone. Will I be able to backup and restore my apps and data using titanium backup? Going to probably use mybackup to backup everything else. Also what is your experience with jellybomb? Will there be future updates? Still new to this forum and this phone.
Kenny301 said:
I've got my mind set on jellybomb and would like to flash that coming from stock. Will dirty flash work? First time flashing a custom rom on this phone. Will I be able to backup and restore my apps and data using titanium backup? Going to probably use mybackup to backup everything else. Also what is your experience with jellybomb? Will there be future updates? Still new to this forum and this phone.
Click to expand...
Click to collapse
I've flashed a bunch of ROMs on my phone and I gotta say dirty flashing is trouble. Yes, when reading through the posts, you can always find someone who has dirty-flashed without any problems, but there is a reason why the first debugging recommendation is always "do a clean (fresh) flash." I've heard of many problems with dirty flashing, and if you plan on going from 4.1.2 to 4.2.1 or 4.2.2, dirty flashing is completely out of the question.
As far as Titanium Backup and the other options... I always use Titanium Backup to do all of the dirty work for me (including SMS/MMS messages, phone logs, wifi access points, etc.). My only recommendation would be to not restore the system files (RED in Titanium Backup), as different ROMs might deal with system apps in different ways.
Hope this helps!