Hello people!
Since I had this Galaxy Nexus I always clean flashed my ROM whenever even a major version (4.1 -> 4.2) update was done. Dirty flashed Nightlies. When I clean flashed, I wiped everything except /sdcard/ and everything went fine. However, lately some AOKP things started giving trouble so I restored, wiped and flashed a lot of times. Now this is what happened:
Flash kernel, AOKP 4.3 stopped booting.
Restore from backup, AOKP 4.3 still not booting.
Forget to wipe, install XP + PA 4.4 Gapps (it's a 4.4 CM based ROM), boot. Everything works! All my apps work, even SuperUser works, which normally asks for permissions after a new flash.
Don't like XP, install CM11 + PA 4.4 Gapps. It works fine!
So what's the matter with no dirty flashing? I just flashed a 4.4 ROM over a 4.3 ROM based on completely different things and it still works great, then I flashed another ROM on top of that and no issues have occurred yet. All works fine - E-mail accounts, Google accounts, YouTube, even my alarms are still kept in one place. The custom toggles I set in XP still are there and everything is just dandy.
Do you guys always clean flash, or did you also decide to say "who gives a hell, let's go dirty"? Did any dirty flashing result in bad things for you?
tl;dr
Why exactly is dirty flashing bad? I dirty flashed AOKP 4.3.1 -> CM11 (4.4) and all's fine.
RainbowSwag said:
Hello people!
Since I had this Galaxy Nexus I always clean flashed my ROM whenever even a major version (4.1 -> 4.2) update was done. Dirty flashed Nightlies. When I clean flashed, I wiped everything except /sdcard/ and everything went fine. However, lately some AOKP things started giving trouble so I restored, wiped and flashed a lot of times. Now this is what happened:
Flash kernel, AOKP 4.3 stopped booting.
Restore from backup, AOKP 4.3 still not booting.
Forget to wipe, install XP + PA 4.4 Gapps (it's a 4.4 CM based ROM), boot. Everything works! All my apps work, even SuperUser works, which normally asks for permissions after a new flash.
Don't like XP, install CM11 + PA 4.4 Gapps. It works fine!
So what's the matter with no dirty flashing? I just flashed a 4.4 ROM over a 4.3 ROM based on completely different things and it still works great, then I flashed another ROM on top of that and no issues have occurred yet. All works fine - E-mail accounts, Google accounts, YouTube, even my alarms are still kept in one place. The custom toggles I set in XP still are there and everything is just dandy.
Do you guys always clean flash, or did you also decide to say "who gives a hell, let's go dirty"? Did any dirty flashing result in bad things for you?
tl;dr
Why exactly is dirty flashing bad? I dirty flashed AOKP 4.3.1 -> CM11 (4.4) and all's fine.
Click to expand...
Click to collapse
This is because roms dont always format the proper partitions and can cause corruption and data loss. This can also lead to ghost issues. I personally set my script to clean flash my roms. This way I dont have to do it manually and when I was releasing it prevented ghost issues and the normal questions about clean or dirty flashing.
Related
Hey guys,
I (was) on jokers CM9 (before recent update). I backed up and then attempted to install the new version... So here's the problem, I can't install Gapps PERIOD. It failed for jokers CM9, as well as MIUI v4. I'm not new to installing ROMs, I know I did all the wipes properly etc and fixed permissions just in case. I have tried the last 3 releases of Gapps as well. The ROM is good, boots fine and all (MIUI and CM9) but no Gapps in any situation. The only time I've been able to get it to stick is using the Options Chooser MIUI Installer, worked great. Ive downloaded the files mutiple times with no problems... no idea what I could be missing! Anyone else had this problem/fix?
did you update your CWM recovery to 6.0.x.x? That's what i did before flashing jokers CM10 alpha build and it wouldn't let me install GAPPS either. I just reverted back to an earlier version and it worked fine.
R2DeeTard said:
did you update your CWM recovery to 6.0.x.x? That's what i did before flashing jokers CM10 alpha build and it wouldn't let me install GAPPS either. I just reverted back to an earlier version and it worked fine.
Click to expand...
Click to collapse
Yes! I actually did right before I started flashing the new stuff... thanks!
Still having trouble ... downgraded back to 5.x. (joker v3). Now it seems like data/cache arent wiping. When trying to flash clean, after doing all wipes I still end up with the same install.
fabe0334 said:
Still having trouble ... downgraded back to 5.x. (joker v3). Now it seems like data/cache arent wiping. When trying to flash clean, after doing all wipes I still end up with the same install.
Click to expand...
Click to collapse
I use photon3 recovery. Works great. Be sure to flash twice if gapps don't show up. If still nothing then you must have a bad download of gapps.
If this works let me know.
Sent from my SGH-I777 using XDA
Ok, I got a question what to do now.
The following happened.
I updated the nightly CM10.1 from the settings menu. Normally this works fine. I forgot to make a backup (DUMB). When CM10.1 restarted it never came further than the boot screen (Samsung logo). After waiting for more than 30 minutes I decided to restart the device (get rid of battery). Now CM10.1 won't start again.
Luckily I had a backup, but it was from CM9 (at least I can call). I already tried to install CM10.1 again, but whit no result (bootlooping again).
How to install CM10.1 again? From CM9. What did I forget?
Hope someone can help.
Cm10.1 is no good. Unreliable I think. Try aokp milestone 2 for a solid Rom. If you really want it
Mounts and storage
Format
Data
system
Cache
Wipe dalv cache in advanced
Flash Rom
flash gapps
wipe cache
wipe dalv
Reboot
Enjoy.
or read op first post on first page
I've only just installed CM10.1 on my S2 today. I encountered the same problem with cm-10.1-20130722-NIGHTLY-i9100
However, 0723 worked fine for me. Give that (the latest at time of writing) a go perhaps?
andrewwright said:
Cm10.1 is no good. Unreliable I think. Try aokp milestone 2 for a solid Rom. If you really want it
Click to expand...
Click to collapse
I did, and it works now, luckaly I made a backup on my google account so all apps are downloaded
Thanks for your solution!
ps. Is there an overview what the big differences are between CM10.1 and aokp m2?
baszer said:
I did, and it works now, luckaly I made a backup on my google account so all apps are downloaded
Thanks for your solution!
ps. Is there an overview what the big differences are between CM10.1 and aokp m2?
Click to expand...
Click to collapse
Easy way to put it is cm 10.1 unstable aokp milestone 2 stable. Simple as that. Also more changeable things in aokp. Cm fanboys wont like what I put but they no its the truth :thumbup: glad you sorted your problem :thumbup:
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
So I am very new to rooting, but after reading through the XDA threads for about a year, I finally took the leap. Last week, I rooted my device using Framaroot. I flashed my device with Omnirom 4.4 nightly (20131203-i777-NIGHTLY) and PA-Gapps 20131215. Everything was working very well except for some battery drain. I decided to flash the newest Omnirom nightly in the hope that some of my issues would be addressed. Flashed Omnirom 20131230-i777-NIGHTLY via an OTA. That flash worked very well, except Google Play services was not working aka it would not allow me to sign into any of my google apps. I tried flashing the newest PA Gapps, that didn't fix the issues. Tried reflashing Omnirom and Gapps, that didn't work. Tried wiping my device and then restoring the ROM to a previous backup. Restoring to any of my previous backups failed continually, so I tried reflashing earlier builds of Omnirom. Several times that did not work, until now. Right now, I was able to flash Omnirom 20131203 with Gapps 20131215. My device will boot and google apps are running, but now I have no home screens...at all.
I'm hoping I might just be able to sideload the google experience launcher and that would fix this issue. I've been messing with my phone all day and decided to ask the experts on this sight for help before I did any further damage.
Thanks for you help and forgive my lack of knowledge...Thanks!
...and now
senuod said:
So I am very new to rooting, but after reading through the XDA threads for about a year, I finally took the leap. Last week, I rooted my device using Framaroot. I flashed my device with Omnirom 4.4 nightly (20131203-i777-NIGHTLY) and PA-Gapps 20131215. Everything was working very well except for some battery drain. I decided to flash the newest Omnirom nightly in the hope that some of my issues would be addressed. Flashed Omnirom 20131230-i777-NIGHTLY via an OTA. That flash worked very well, except Google Play services was not working aka it would not allow me to sign into any of my google apps. I tried flashing the newest PA Gapps, that didn't fix the issues. Tried reflashing Omnirom and Gapps, that didn't work. Tried wiping my device and then restoring the ROM to a previous backup. Restoring to any of my previous backups failed continually, so I tried reflashing earlier builds of Omnirom. Several times that did not work, until now. Right now, I was able to flash Omnirom 20131203 with Gapps 20131215. My device will boot and google apps are running, but now I have no home screens...at all.
I'm hoping I might just be able to sideload the google experience launcher and that would fix this issue. I've been messing with my phone all day and decided to ask the experts on this sight for help before I did any further damage.
Thanks for you help and forgive my lack of knowledge...Thanks!
Click to expand...
Click to collapse
Now, after wiping/factory reset and re-flashing the rom, gapps, and supersu....still getting no homescreens AND not able to connect to google play services.
Any help would be greatly appreciated!!
You're very close, but I'm not sure that it's worth trying to treat the symptoms (sideloading, reflashing, etc). It's easier to start clean. Once you are assured that you are using a compatible kernel/recovery, please follow all of the steps under the "initial installation" header of the OmniRom OP. The installation is easy and very straight forward.
if you prefer to avoid using mr-cook's script, then you can substitute it by wiping:
both caches
/data
/system
/preload
edit: Wiping /system is necessary. A factoy reset is NOT enough to guarantee a clean start.
Survival scripts are stored at /system/addon.d, which are honored by the omnirom install script. The only way to truly start clean is to wipe /system.
senuod said:
So I am very new to rooting, but after reading through the XDA threads for about a year, I finally took the leap. Last week, I rooted my device using Framaroot. I flashed my device with Omnirom 4.4 nightly (20131203-i777-NIGHTLY) and PA-Gapps 20131215. Everything was working very well except for some battery drain. I decided to flash the newest Omnirom nightly in the hope that some of my issues would be addressed. Flashed Omnirom 20131230-i777-NIGHTLY via an OTA. That flash worked very well, except Google Play services was not working aka it would not allow me to sign into any of my google apps. I tried flashing the newest PA Gapps, that didn't fix the issues. Tried reflashing Omnirom and Gapps, that didn't work. Tried wiping my device and then restoring the ROM to a previous backup. Restoring to any of my previous backups failed continually, so I tried reflashing earlier builds of Omnirom. Several times that did not work, until now. Right now, I was able to flash Omnirom 20131203 with Gapps 20131215. My device will boot and google apps are running, but now I have no home screens...at all.
I'm hoping I might just be able to sideload the google experience launcher and that would fix this issue. I've been messing with my phone all day and decided to ask the experts on this sight for help before I did any further damage.
Thanks for you help and forgive my lack of knowledge...Thanks!
Click to expand...
Click to collapse
cyril279 said:
You're very close, but I'm not sure that it's worth trying to treat the symptoms (sideloading, reflashing, etc). It's easier to start clean. Once you are assured that you are using a compatible kernel/recovery, please follow all of the steps under the "initial installation" header of the OmniRom OP. The installation is easy and very straight forward.
if you prefer to avoid using mr-cook's script, then you can substitute it by wiping:
both caches
/data
/system
/preload
edit: Wiping /system is necessary. A factoy reset is NOT enough to guarantee a clean start.
Survival scripts are stored at /system/addon.d, which are honored by the omnirom install script. The only way to truly start clean is to wipe /system.
Click to expand...
Click to collapse
I was able to restore my phone to a point before I flashed any ROMS using CWM recovery. Only issue with that is storage has been eaten up and some apps that were on my sd card aren't working well. I'll take those steps to properly flash OmniRom again in 2014.
Thanks cyril
looks like things may actually be working. thanks again!
cyril279 said:
You're very close, but I'm not sure that it's worth trying to treat the symptoms (sideloading, reflashing, etc). It's easier to start clean. Once you are assured that you are using a compatible kernel/recovery, please follow all of the steps under the "initial installation" header of the OmniRom OP. The installation is easy and very straight forward.
if you prefer to avoid using mr-cook's script, then you can substitute it by wiping:
both caches
/data
/system
/preload
edit: Wiping /system is necessary. A factoy reset is NOT enough to guarantee a clean start.
Survival scripts are stored at /system/addon.d, which are honored by the omnirom install script. The only way to truly start clean is to wipe /system.
Click to expand...
Click to collapse
I've run into a problem flashing the VANIR & COMMOTIO rom for the e970. I was originally on slimkat beta 3.0, then I went to TWRP and wiped data, system, chache, and dalvik. Then I flashed B64-Commotio-geeb (the latest nightly) and finally I flashed standard Banks gapps 4.4.2. Now I rebooted, and my phone has been stuck on the bootup screen saying "COMMOTIO" for the last 2 hours.
I am pretty sure everything I did was right, but I'd appreciate it if someone pointed out a mistake or fix. I don't want to restore from nandroid if I don't have to.
1. commotio has had issues since 20th nightly
2. Use up to 22nd for vanir
3. Try march 01 of vanir without the kernel b64. Then try the kernel afterwards
Sent from my LG-E970
Solved
bokilenator said:
I've run into a problem flashing the VANIR & COMMOTIO rom for the e970. I was originally on slimkat beta 3.0, then I went to TWRP and wiped data, system, chache, and dalvik. Then I flashed B64-Commotio-geeb (the latest nightly) and finally I flashed standard Banks gapps 4.4.2. Now I rebooted, and my phone has been stuck on the bootup screen saying "COMMOTIO" for the last 2 hours.
I am pretty sure everything I did was right, but I'd appreciate it if someone pointed out a mistake or fix. I don't want to restore from nandroid if I don't have to.
Click to expand...
Click to collapse
I ended up having to restore via Nandroid, then download an older nightly and flashing that. It worked, and now I can flash the new nightly with no problems. Weird that the newest nightly was unable to boot up alone.
Off topic, how was ur experience with SlimKat?
awesome
CarvellW said:
Off topic, how was ur experience with SlimKat?
Click to expand...
Click to collapse
Very good. Barely any bugs and the customization was awesome. However battery sometimes felt short, theres no theme support and no halo.