Related
Since I have seen alot of individuals within ROM threads stating things such as, "Your ROM bricked my phone." or "I can't get your new ROM to install." decided to make this guide. Hopefully it will solve this issue and help educate people.
What not flasing correctly can do:
1. Cause your phone not to boot
2. Cause Force closes and issues
3. POSSIBLY Brick your phone (though I have not seen an Eris Brick yet)
We must also remember that:
1. The devs of these ROMs are NOT responsible for any damage to your phone
2. The devs spend alot of time with testing to make sure the ROM works.
3. A ROM will NOT always flash over a previous ROM
OK.. So onto the main topic..
assuming you are rooted and using AMON's Recovery. I suggest AMON's because Clockwork has had recent issues. Big thanks to AMON for this!
How to install a ROM properly:
1. Boot into recovery ( with either reboot to recovery option or powerdown and then holding volume up and power )
2. Goto Backup/Restore and do a NAND Back-Up
3. Do a data/factory wipe ( NOTE: if the dev says you can flash over an old version you dont NEED to do this, but if you don't do this and the ROM is not booting then I suggest you restart this process [minus the back-up] and do a data/factory wipe)
4. Do a Dalvik Wipe... 3 times (ALWAYS ALWAYS ALWAYS do this)
5. Flash ROM
6. Reboot and Wait ( after a Dalvik wipe and flashing ROMs first boot can take 3+ minutes to load... BE PATIENT )
More to Come...
If you could, please explain what a Dalvik flash does. Thanks in adavnce, and thanks for this thread. I've never had any issues flashing, but it's nice to see someone explain the basics....
MOS95B said:
If you could, please explain what a Dalvik flash does. Thanks in adavnce, and thanks for this thread. I've never had any issues flashing, but it's nice to see someone explain the basics....
Click to expand...
Click to collapse
"Dalvik cache is a program cache area for the program Dalvik. Dalvik is a java based virtual machine that is the bases for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the Dalvik-cache is the result of Dalvik doing a optimization of the running program." - Taken From Android forums
Basically it analyzes the phone before it boots. Then it sees what apps you have and will use and assigns cache to them. This way they will load quickly and properly.
When you flash a new ROM apps can change, or if you do a data/factory reset those apps are gone. SO wiping the Dalvik allows it to rebuild itself for what YOU are using.
This is also good to do after cleaning out or removing many unused apps from the phone. I usually do it once a week AT LEAST.
With the exception of a 2.1 ROM running apps2sd on an ext partition, is there really any point to wipe Dalvik if you have just done a wipe data/factory reset (which also wipes Dalvik cache)? And what exactly is the point of wiping Dalvik three times - why is once not enough? Is there something wrong with Amon Recovery which prevents a full Dalvik wipe unless you do it more than once?
It certainly doesn't hurt to wipe Dalvik after a wipe data/factory reset, but it should be already wiped.
I'm still fairly new, but I've flashed quite a bit. I didn't know to wipe dalvik x3. that's an interesting bit of info. Any reason why? Thanks
lp4261 said:
I'm still fairly new, but I've flashed quite a bit. I didn't know to wipe dalvik x3. that's an interesting bit of info. Any reason why? Thanks
Click to expand...
Click to collapse
Safety reasons... personally I do factory then dalvik 3x then factory again and dalvik 3x again.
Sent from my ERIS using XDA App
I tried this and now I have a paper weight lol j/k
tazzpatriot said:
I tried this and now I have a paper weight lol j/k
Click to expand...
Click to collapse
My plan worked
Sent from my ERIS using XDA App
I believe the reason is that sometimes even after a wipe people have reported residual data in the cache, I personally don't do it three times but I do a wipe, dalvik, dalvik, wipe.
Its not going to hurt anything and it gives me piece of mind.
Delvaris said:
I believe the reason is that sometimes even after a wipe people have reported residual data in the cache, I personally don't do it three times but I do a wipe, dalvik, dalvik, wipe.
Its not going to hurt anything and it gives me piece of mind.
Click to expand...
Click to collapse
cool. Thanks for the good info.
x3? I do once before and once after. Frankly once before has been enough for me... though I suppose being safe has never hurt.
If the dalvik cache still won't clear after 3 times you can piss on your phone. That seems to really help.
in most cases once is enough but like I said, it's not likely to hurt anything to give it a couple of wipes to make sure all the junk data is cleared.
Let me put it this way...
I wont use a public toilet just by seeing it is clean... ill clean it like twice ...
This is why I dalvik 3 times lol
Sent from my ERIS using XDA App
icbeer said:
If the dalvik cache still won't clear after 3 times you can piss on your phone. That seems to really help.
Click to expand...
Click to collapse
I tried that today.. now my phone wont turn on... any fix?...
Jk
Sent from my ERIS using XDA App
It would be interesting for someone like Amon to comment on the need to wipe data or recovery more than one time. In my opinion, once is enough. I'm 100% confident than wipes #2, #3, and so on are wiping blank space...
hallstevenson said:
It would be interesting for someone like Amon to comment on the need to wipe data or recovery more than one time. In my opinion, once is enough. I'm 100% confident than wipes #2, #3, and so on are wiping blank space...
Click to expand...
Click to collapse
I personally and others have experienced residual data... so is three too much... maybe... but its safe... two might be a better choice... this guide was made to make sure you have no issues... therefore I said three times for safety... if you want to just do it once... be my guest
Sent from my ERIS using XDA App
At the risk sounding like an idiot, I must ask this:
You mention wiping the Dalvik once a week. When you do this wipe, do you replace it (flash) something over it? Or can you simply wipe then reboot.
Sent from my FroyoEris using XDA App
J&M said:
At the risk sounding like an idiot, I must ask this:
You mention wiping the Dalvik once a week. When you do this wipe, do you replace it (flash) something over it? Or can you simply wipe then reboot.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Yep, just wipe and boot. After wiping dalvik, it will redo your app tree or configuration if you will, just clears all the current info and rebuilds it fresh.
Great thread, people still need it I guess
workshed said:
Yep, just wipe and boot. After wiping dalvik, it will redo your app tree or configuration if you will, just clears all the current info and rebuilds it fresh.
Great thread, people still need it I guess
Click to expand...
Click to collapse
Lol thanks buddy!
Sent from my ERIS using XDA App
Gentlemen,
I am having great difficult when I wipe prior to installing a new ROM. I obviously am doing to much and on both occasions that I have done this on my N7 have lost everything including my backups and operating system. I am left with just TWRP which worked great for me on my KF so I am not blaming it.
Would someone please be kind enough to tell me exactly which areas to wipe because I like to experiment with different ROMs but can't stand the stress involved of wiping out the complete device again. I am 70 years old and my heart can't take it!
Thanks in advance.
wipe data, factory reset. thats all. dont wipe anything on the sd. you only need to wipe data when flashing 2 different roms, not when updating your current rom.
damn, youre older than me. and i though that i was the old man here. guess not :silly:
simms22 said:
wipe data, factory reset. thats all. dont wipe anything on the sd. you only need to wipe data when flashing 2 different roms, not when updating your current rom.
damn, youre older than me. and i though that i was the old man here. guess not :silly:
Click to expand...
Click to collapse
Thanks for the help. Should have started this when I was younger I guess hahaha
Always wipe north/south, then follow up with a wet wipe. Helps.
Sent from my SPH-D710 using xda app-developers app
Hi, I was just wondering if I need to go through the whole process when updating a rom in Clockwork? I am running Paranoid and I have received many updates and its getting frustrating having to set up my phone like it was brand new after each update. I just installed PA Updater but at the end of the download it brings me to Clockwork anyway. For an update to a rom I usually wipe data/ factory reset / wipe cache partition / perform a backup and wipe dalvik cache. Are these steps only necessary when installing a new rom? I am new to this and love the benefits that unlocked bootloaders / custom roms and root give me but I am sick and tired of setting up my phone once a week. I imagine flashing a new rom means I am guaranteed to go through the set up process as if it were a brand new phone ??? Is there an easier way to do this???
Thanks
Yeah sure ask the dev to build a rom already set up according to your settings
Sent from my Nexus 4 using xda premium
djp1313 said:
Hi, I was just wondering if I need to go through the whole process when updating a rom in Clockwork? I am running Paranoid and I have received many updates and its getting frustrating having to set up my phone like it was brand new after each update. I just installed PA Updater but at the end of the download it brings me to Clockwork anyway. For an update to a rom I usually wipe data/ factory reset / wipe cache partition / perform a backup and wipe dalvik cache. Are these steps only necessary when installing a new rom? I am new to this and love the benefits that unlocked bootloaders / custom roms and root give me but I am sick and tired of setting up my phone once a week. I imagine flashing a new rom means I am guaranteed to go through the set up process as if it were a brand new phone ??? Is there an easier way to do this???
Thanks
Click to expand...
Click to collapse
no need to wipe anything when updating a rom, just flash it over what you already have(dirty flash). if the rom needs gapps, flash them as well. you wont lose any data. you do need to wipe data when flashing to a different rom.
I don't get where people get the idea of wiping literally everything when flashing an update. Just flash over the old one, wipe cache/dalvik and you're good to go.
Nigeldg said:
I don't get where people get the idea of wiping literally everything when flashing an update. Just flash over the old one, wipe cache/dalvik and you're good to go.
Click to expand...
Click to collapse
Wiping data when flashing a new rom is a bit like reinstalling Windows. It helps to eliminate potential problems. However, because of the amount of time and effort it takes, wiping your phone every single time you update is plain stupidity, especially if you are on cyanogenmod nightly updates. Unfortunately, some people (including developers) have decided to encourage people to wipe with every single update in order to deal with less bug reports due to, admittedly, user errors.
This a simple guide I made for the note 3. Seeing these 2 questions being asked alot here so posting it here. Will need to edit it a bit so currently it's a WIP.
NOTE- First thing you should do before flashing roms/kernels for the first time is backup EFS.
How to flash CLEAN flash roms -*This is how I flash roms(even updates of the same rom) and the method i recommend to users. It is better to take 10 mins to set your phone again rahter than wasting more time to fix issues that could have been avoided by a clean flash.
NOTE- This is a MUST when changing roms.
1. Make a nandroid backup in recovery
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash kernel(optional)
10. Reboot
11. Wait 10 mins, then do another reboot
12. Enjoy
How to DIRTY flash roms -*This method is used by users when flashing a update of the same rom.*
NOTE- Some users follow this and some just flash the rom without wiping anything.
Note- If you flash rom that has aroma installer you will need to edit the updater script to make sure the aroma doesn't wipe system before flashing rom.
1. Make a nandroid backup in recovery
3. Wipe cache
4. Wipe dalvik
5. Flash ROM
6. Flash gapps
7. Flash AK kernel(optional)
8. Reboot
9. Wait 10 mins, then do another reboot
10. Enjoy
How to SUPER CLEAN flash roms -*This is the method that I recommend to your that have weird issues, even after clean flashing.
Will be adding this method. Need to edit it a bit.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
How to flash flash kernels -*Many users say to wipe cache/dalvik but it's useless as neither if their partitions are affected when flashing a kernel.
1. Boot into recovery*
2. Flash kernel*
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
@Khizar welcome back man, good to see you're writing guides again. Get that RC title again!
Sent from my OnePlus One using Tapatalk VIP
nicholaschum said:
@Khizar welcome back man, good to see you're writing guides again. Get that RC title again!
Sent from my OnePlus One using Tapatalk VIP
Click to expand...
Click to collapse
Yeah let's hope ppl actually read and my time editing see stuff to make it for OPO isn't wasted.. These forums seem to be worse than the note 3 ones.. Man saw this guy today who apparently couldn't find the link to gapps that was posted in the OP.. SMH
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
This a simple guide I made for the note 3. Seeing these 2 questions being asked alot here so posting it here.
Click to expand...
Click to collapse
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
CafeKampuchia said:
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Click to expand...
Click to collapse
I've seen that thread, it's pretty useful bit I wouldn't say "the information is out there already. If you read the thread his instructions are just telling users how to wipe and flash roms.
The point of my thread was, or still is, to list all the different ways to flash roms. Clean, dirty, super clean. Most new users don't know the difference.
With that being said I am not saying anything negative about the guide nor am I comparing the 2 guides. Think that I should add that, on the Internet things are usually misinterpreted.
I am simply making a bit know detailed and specify guide just for flashing roms.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Amazing as usual! You're a treasure, my friend! So happy to see you back on xda!
Plus... do you really want me to tell you how we "dirty flashers" flash roms? love you man, you're perfect!
NOTE- This is a MUST when changing roms.
1. Backup EFS -Not necessary every time you flash a ROM.
2. Make a nandroid backup in recovery -Not necessary every time you flash a ROM.
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash AK kernel(optional) -There are many kernels available for our device, not just AK.
10. Reboot
11. Wait 10 mins, then do another reboot -Not necessary.
12. Enjoy
Transmitted via Bacon
daxgirl said:
Amazing as usual! You're a treasure, my friend! So happy to see you back on xda!
Plus... do you really want me to tell you how we "dirty flashers" flash roms? love you man, you're perfect!
Click to expand...
Click to collapse
Haha no comments... ?
timmaaa said:
NOTE- This is a MUST when changing roms.
1. Backup EFS -Not necessary every time you flash a ROM.
2. Make a nandroid backup in recovery -Not necessary every time you flash a ROM.
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash AK kernel(optional) -There are many kernels available for our device, not just AK.
10. Reboot
11. Wait 10 mins, then do another reboot -Not necessary.
12. Enjoy
Transmitted via Bacon
Click to expand...
Click to collapse
Did you read the first few sentence of the OP? Like I said it's a WIP and I need to edit stuff.
But after seeing your edits, the only thing I agree I need to edit out is doing an EFS backup every time you flash a rom. Nandroid is a must IMO, you never know when you'll be unlucky.
As for the "there are many kernels avaliable".. It says optional next to it for a reason.
And about waiting 10 after a rom/kernel and rebooting not being necessary, from my experience it helps let the rom/kernel settle. There was a time when devs used to recommend that. I still do that and recommend it.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
Haha no comments... ?
Did you read the first few sentence of the OP? Like I said it's a WIP and I need to edit stuff.
But after seeing your edits, the only thing I agree I need to edit out is doing an EFS backup every time you flash a rom. Nandroid is a must IMO, you never know when you'll be unlucky.
As for the "there are many men kernels avaliable".. It says optional next to it for a reason.
And about waiting 10 after a rom/kernel and rebooting not being necessary, from my experience it helps let the rom/kernel settle. There was a time when devs used to recommend that. I still do that and recommend.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Yeah I did read it and that's why I was putting forth my constructive criticism. The nandroid isn't an absolute must every time you flash though, if you have at least one nandroid on your phone at all times you have insurance against the unknown, whether or not you do that with every flash is purely optional (as opposed to describing it as essential, because it just isn't).
There's a reason devs don't recommend to reboot a second time after a ROM flash anymore, because it isn't essential either.
I only mentioned the kernel because it might seen as favouritism, and it's always best to remain objective in a guide thread.
I'm detecting animosity in your reply. Don't get me wrong, I'm all for having resources, I'm about to add your thread to my index thread so folks can find it easier. I'm just pointing out things that aren't actually essential every time a ROM is flashed, trying to save the user unnecessary time and effort.
Transmitted via Bacon
---------- Post added at 07:45 PM ---------- Previous post was at 07:38 PM ----------
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
timmaaa said:
Yeah I did read it and that's why I was putting forth my constructive criticism. The nandroid isn't an absolute must every time you flash though, if you have at least one nandroid on your phone at all times you have insurance against the unknown, whether or not you do that with every flash is purely optional (as opposed to describing it as essential, because it just isn't).
OK. I agree with this, I'll change it to optional and have a bold warning that you should have atleast one nandroid just in case at all times.
There's a reason devs don't recommend to reboot a second time after a ROM flash anymore, because it isn't essential either.
OK this one I am kinda biased about, have had the same discussion with many others. I've always experienced that if I use a rom/kernel right after I flash everything is a bit laggy. If I wait 10 mins and reboot, everything is a lot smoother.
I only mentioned the kernel because it might seen as favouritism, and it's always best to remain objective in a guide thread.
Hmm.. You do have a point, I'll edit that bit.
I'm detecting animosity in your reply. Don't get me wrong, I'm all for having resources, I'm about to add your thread to my index thread so folks can find it easier. I'm just pointing out things that aren't actually essential every time a ROM is flashed, trying to save the user unnecessary time and effort.
Feedback is always welcome. I appreciate you taking the time and commenting here.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks for adding the thread to the index. :good:
Khizar said:
Thanks for adding the thread to the index. :good:
Click to expand...
Click to collapse
No worries mate. All good, and well done on the thread!
Transmitted via Bacon
Khizar said:
Yeah let's hope ppl actually read and my time editing see stuff to make it for OPO isn't wasted.. These forums seem to be worse than the note 3 ones.. Man saw this guy today who apparently couldn't find the link to gapps that was posted in the OP.. SMH
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
CafeKampuchia said:
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Click to expand...
Click to collapse
Nice job and I agree it was getting a little crazy in here as well with the how do I flash this rom crap. I thought this was self explanatory but it seems to be a lot of first timers in here.
I know you said your instructions are a WIP but simply remember when you are ready to put out the finished product you must think as they do the super duper noobs and try and make it as flashing for dummies as possible. They will hold on to your every letter.
I agree that a recent nandroid is needed and honestly I keep 2 at least on my phone because I have been burnt with a corrupted backup before. Also who wants to restore a rom from 2 months ago.... :good:
Nice work
If I may I would like to make some suggestions ??? may I? And no... not as a dirty flasher... if is OK with you, I will...
playya said:
Nice job and I agree it was getting a little crazy in here as well with the how do I flash this rom crap. I thought this was self explanatory but it seems to be a lot of first timers in here.
I know you said your instructions are a WIP but simply remember when you are ready to put out the finished product you must think as they do the super duper noobs and try and make it as flashing for dummies as possible. They will hold on to your every letter.
I agree that a recent nandroid is needed and honestly I keep 2 at least on my phone because I have been burnt with a corrupted backup before. Also who wants to restore a rom from 2 months ago.... :good:
Nice work
Click to expand...
Click to collapse
Yes I think I'll try to make it simpler and more easier for new users to understand, a dummy proof version as you said. Thanks for your feedback.
daxgirl said:
If I may I would like to make some suggestions ??? may I? And no... not as a dirty flasher... if is OK with you, I will...
Click to expand...
Click to collapse
Since when have you needed to ask for permission Anna..? Anyways all suggestions are welcome.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
Yes I think I'll try to make it simpler and more easier for new users to understand, a dummy proof version as you said. Thanks for your feedback.
Since when have you needed to ask for permission Anna..? Anyways all suggestions are welcome.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Well we already know that I am a polite non xda material
Sooooooo here we go...
1. When you wipe data in any recovery, it includes AT LEAST 3 things: a. Format data partition b. Eliminate dalvik exec files along with that (since dalvik cache sits on data partition) c. Format cache
So after wiping data, there is not reason to wipe cache and dalvik cache, since they have already been cleaned as a whistle.
2. During rom installation, new framework jars are being pushed over /system/framework. It's enough for just android.policy.jar to be replaced, the android will rebuild all dalvik upon boot (hence the "Android is upgrading. Optimizing xx app out of xxx"). All the major jars upon replacement will wipe dalvik and rebuild it. It's enough to have 1 byte of difference.
So I guess that summorizes the need for wiping dalvik cache.
3. As for wiping system. Well things are a bit more controversial here. Since any normal rom updater script has as first command "mount /system" and as second command "delete recursive /system", it seems like there is no need as well. BUT!!!
There seems to be a discussion whether formatting system (which is done when it's unmounted) the way recovery does it in "mounts and storage " is more "thorough and effective" then recursively deleting it (when it's mounted) by the updater script.
So I can see the point in formatting system! Well, a little...
Hey, don't get me wrong, I admire this guide and I think it's super helpful! I just always feel the need to set things straight with this "triple wipe" that everyone keeps recommending.
Imo, wipe data is simply enough that is IF you're not a dirty flasher. ..
Now to the last part! You guys all have pretty uh the same sqlite vs in all those aosp/cm/aokp roms.
All I am saying: sometimes you can try to flash without wipe, if there is a problem, which in most cases there won't be, some individual data/data databases can be deleted and rebuilt. Maybe we should write a guide on dirty flashing I am certainly good at THAT
daxgirl said:
Well we already know that I am a polite non xda material
Sooooooo here we go...
1. When you wipe data in any recovery, it includes AT LEAST 3 things: a. Format data partition b. Eliminate dalvik exec files along with that (since dalvik cache sits on data partition) c. Format cache
So after wiping data, there is not reason to wipe cache and dalvik cache, since they have already been cleaned as a whistle.
2. During rom installation, new framework jars are being pushed over /system/framework. It's enough for just android.policy.jar to be replaced, the android will rebuild all dalvik upon boot (hence the "Android is upgrading. Optimizing xx app out of xxx"). All the major jars upon replacement will wipe dalvik and rebuild it. It's enough to have 1 byte of difference.
So I guess that summorizes the need for wiping dalvik cache.
3. As for wiping system. Well things are a bit more controversial here. Since any normal rom updater script has as first command "mount /system" and as second command "delete recursive /system", it seems like there is no need as well. BUT!!!
There seems to be a discussion whether formatting system (which is done when it's unmounted) the way recovery does it in "mounts and storage " is more "thorough and effective" then recursively deleting it (when it's mounted) by the updater script.
So I can see the point in formatting system! Well, a little...
Hey, don't get me wrong, I admire this guide and I think it's super helpful! I just always feel the need to set things straight with this "triple wipe" that everyone keeps recommending.
Imo, wipe data is simply enough that is IF you're not a dirty flasher. ..
Now to the last part! You guys all have pretty uh the same sqlite vs in all those aosp/cm/aokp roms.
All I am saying: sometimes you can try to flash without wipe, if there is a problem, which in most cases there won't be, some individual data/data databases can be deleted and rebuilt. Maybe we should write a guide on dirty flashing I am certainly good at THAT
Click to expand...
Click to collapse
1. I get what you're saying with the wiping being a little excessive, again this comes down to experience. My guide is made from what I have personally experienced.
Factory reset does wipe cache and dalvik but I am a believer in "better safe than sorry". Same thing with wiping system even though, like you said, most updater scripts wipe system. Also the bigger reason WHY I am firm in saying atleast wipe data and system is cuz I have noticed in sometimes that when I wipe system as opposed to only wiping data, the experience is better so I have come to the conclusion that the recoveries manual wiping options are to be trusted more.
2. You're right about the dirty flashing, you'll be happy to hear I've been flashing dirty since I got the phone. Now dirty flashing different roms is a bit tricky but I have had success, however even if it gets messy I always have a backup.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
9. Wait 10 mins, then do another reboot
Click to expand...
Click to collapse
I can not understand this step? After the first reboot the new OS booted UP, you must set in and installing the Google APPS update if it available. After the first bootup, why should the users rebooting the device?
Criton30 said:
I can not understand this step? After the first reboot the new OS booted UP, you must set in and installing the Google APPS update if it available. After the first bootup, why should the users rebooting the device?
Click to expand...
Click to collapse
After the first boot up, Java has to create it's working areas for the OS to function well, and it configures the kernel and miscellaneous trash handling (if dirty flashed). Rebooting will clear the supposedly terminates "completed services" after they were used to configure Android on first boot, hence things like kernel will be set on next boot, and on the next boot, you will have a clean Daily Driver configuration.
Also, it's like "why do you reboot your computer after a new install of a big program?", well, for it to settle, and to reinitiate the program. In this case, Android was setting up all your working directories on your internal storage, clearing out junk it may have had, and also rebuilding of the VM. That's a lot of work. Why not reboot to make sure everything that has been sitting on idle after making all these folders, would be terminated completely so just to make sure everything goes right.
nicholaschum said:
After the first boot up, Java has to create it's working areas for the OS to function well, and it configures the kernel and miscellaneous trash handling (if dirty flashed). Rebooting will clear the supposedly terminates "completed services" after they were used to configure Android on first boot, hence things like kernel will be set on next boot, and on the next boot, you will have a clean Daily Driver configuration.
Also, it's like "why do you reboot your computer after a new install of a big program?", well, for it to settle, and to reinitiate the program. In this case, Android was setting up all your working directories on your internal storage, clearing out junk it may have had, and also rebuilding of the VM. That's a lot of work. Why not reboot to make sure everything that has been sitting on idle after making all these folders, would be terminated completely so just to make sure everything goes right.
Click to expand...
Click to collapse
so if I understand you correctyl, after the first bootup after the OS installation I must reboot the phone before setting up the google account and soo on?
I flashed my Moto G4 Play with Lineage OS. Everything was working fine until I unlocked my phone and a linked opened automatically in Chrome. This happens everytime I unlock my phone. I also get other kind of ads. When I press the activity button to see which app is responsible, the ad disappears.
What should I do to fix this?
I was thinking about flashing crDroid but noticed "DO A DATA WIPE " in the instructions. What does this mean? How can one do this? And what are dirty and clean flashes?
Not sure exactly about what is causing your ads, but clean flashing either another rom or the same one should fix it. To answer your question, this is what you wipe in recovery mode before flashing a rom for the first time (usually in TWRP):
data, cache, dalvik, system
This is what is called a clean flash, because you also wipe the data partition (which is where all your apps and their respective data is stored); if you were to do a dirty flash, common for updating roms, this is what you would wipe before flashing:
cache, dalvik, system (I wipe system because old habits die hard, I believe most - if not all - roms do this from the zip already).
So, dirty flashing (the same or a newer/older build of the rom you're in, otherwise you're just asking for trouble) would most likely not fix your issue as it is probably caused by an app you need to get rid of. Either clean flash the same rom, or go for another one. crDroid is nice, I'm using it with the heliox kernel. It has adaway built in so even if your ads issue does come back you might still be able to get rid of it natively.
Hope I helped!
fretboard_squatter said:
I flashed my Moto G4 Play with Lineage OS. Everything was working fine until I unlocked my phone and a linked opened automatically in Chrome. This happens everytime I unlock my phone. I also get other kind of ads. When I press the activity button to see which app is responsible, the ad disappears.
What should I do to fix this?
I was thinking about flashing crDroid but noticed "DO A DATA WIPE " in the instructions. What does this mean? How can one do this? And what are dirty and clean flashes?
Click to expand...
Click to collapse
Usually the cause of this kind of ads is some app you installed, and not the rom itself.
I would uninstall apps to find out the culprit.
rafaelrgi said:
Usually the cause of this kind of ads is some app you installed, and not the rom itself.
I would uninstall apps to find out the culprit.
Click to expand...
Click to collapse
Turned out to be Adblock Plus. The irony.
I have some torrents downloading on the internal storage. As soon as they are downloaded I will do a clean flash as the problem has resurfaced. Except android device manager, apps like greenify have their administrator access revoked. However, the ads still come.
anerik said:
Not sure exactly about what is causing your ads, but clean flashing either another rom or the same one should fix it. To answer your question, this is what you wipe in recovery mode before flashing a rom for the first time (usually in TWRP):
data, cache, dalvik, system
This is what is called a clean flash, because you also wipe the data partition (which is where all your apps and their respective data is stored); if you were to do a dirty flash, common for updating roms, this is what you would wipe before flashing:
cache, dalvik, system (I wipe system because old habits die hard, I believe most - if not all - roms do this from the zip already).
So, dirty flashing (the same or a newer/older build of the rom you're in, otherwise you're just asking for trouble) would most likely not fix your issue as it is probably caused by an app you need to get rid of. Either clean flash the same rom, or go for another one. crDroid is nice, I'm using it with the heliox kernel. It has adaway built in so even if your ads issue does come back you might still be able to get rid of it natively.
Hope I helped!
Click to expand...
Click to collapse
How do I flash a kernel? Is it safe for a noob like me? Does the kernel have adaway or the ROM? Because if the ROM has adaway I would prefer not to mess with the kernel.
Thanks a lot for explaining what a clean and dirty flash is and how they are different!
fretboard_squatter said:
How do I flash a kernel? Is it safe for a noob like me? Does the kernel have adaway or the ROM? Because if the ROM has adaway I would prefer not to mess with the kernel.
Thanks a lot for explaining what a clean and dirty flash is and how they are different!
Click to expand...
Click to collapse
Kernel flashing is similar to rom flashing; I think the best way to flash a kernel is to flash it right after clean installing the rom (this is, do all the wipes, flash the rom, the gapps, whatever addon, and the kernel); though I wouldn't call it safe (since none of this potentially is, if you don't pay attention), I wouldn't advise against it. It's part of the whole experience, and kernels can really improve your phone. In this case, adaway's included in the rom, not the kernel. So you should be fine without Heliox. But you should try it someday! Just remember to keep a backup of your data in case anything goes sideways. Good luck!
I took no backup of the kernel (my bad), flashed it after wiping the data and then I installed wiped everything and then I flashed the kernel again, the ROM (crDroid) and gapps. Working like a charm. Thanks!