First off all, credit for this guide goes to steal25 and lowetaxes for the original guide
It was just revised for the Shift
A special thanks also goes to strapped365 for his help revising this guide
READ ALL THE INSTRUCTIONS ALL THE WAY THROUGH FIRST BEFORE DOING ANYTHING
I do not reccomend "just flashing over a ROM"
1. REREAD THE INSTRUCTIONS (If your seeing this for the second time, proceed)
2. Make a Nandroid backup of your present set up.
3. Boot into Recovery
4. WIPE EVERYTHING!!! I CANNOT STRESS THIS ENOUGH
•Wipe in this order:
DALVIK CACHE
CACHE PARTITION
FORMAT SYSTEM
FORMAT SD:EXT
FORMAT DATA
FORMAT CACHE
THEN WIPE ALL USER DATA/FACTORY RESET
Do all of these 3Xs . Some do it only once. Some do it as much as 4Xs . 3Xs is Recommended
WIPE EVERYTHING EXCEPT THE SD CARD
5. Flash ROM (of your choosing)
6. Reboot (first Boot may take a while ) this is NOT a Bootloop.
7. Before you do anything, let the ROM settle in for about 10 mins. After about 10 mins, unlock the lockscreen.
8. Skip through Initial set up. DO NOT set up any accounts yet. Check and make sure everything installed.
9. IF NOT ON A SENSE ROM go ahead and install google apps
10. Now go ahead and sign into all your accounts. Set up Google and all that good stuff.
11. Open market, and install apps. If you use Titanium Backup DO NOT RESTORE System Apps or Data. Try not to restore Data for any app. If you restore an app like games and such, just restore the app.
THESE ARE THE SAME INSTRUCTIONS I FOLLOW. THE RESULT IS A BETTER FLASH THAN JUST DOING A REGULAR WIPE.
THIS PROCESS WILL ENSURE THE SYSTEM IS WIPED PROPERLY. RESULT, LESS OF A CHANCE FOR ISSUES TO ARISE!
The Original THREAD for the Guide
***I am not responsible for any damage that may occur to your device. If it BLOWS UP - MELTS - STEALS YOUR CAR - OR EATS YOUR GOLDFIISH IT'S ON YOU. This is only a recommendation of what you should do to Properly Wipe your device. If you cannot follow instructions that is on you.
You forgot google apps and google apps new talk which should be flashed right after the rom.
He's a sense guy probably why.
Sent from my Rooted Thrive
VICODAN said:
You forgot google apps and google apps new talk which should be flashed right after the rom.
Click to expand...
Click to collapse
Yea these instructions were orignally posted (by him) on themikmik.com which is soley a sense rom development site, and he just reposted them on XDA because there are alot of people who don't read themikmik (i hardly do) lol.
Btw nice idea posting it here too Prboy1969
Sent from my Epicly Blue Shift!
VICODAN said:
You forgot google apps and google apps new talk which should be flashed right after the rom.
Click to expand...
Click to collapse
Didn't forget . But just for you, updated OP .
prboy1969 said:
Didn't forget . But just for you, updated OP .
Click to expand...
Click to collapse
I'd give you a thanks but I'm limited to 5 per day.
Thanks very much for the detailed step-by-step instructions. Great tips... and I've successfully flashed MikShifted G Executive Edition onto my Evo Shift. It's *gorgeous*!!
Your very welcome. Glad I could help .
9. Boot into recovery, and wipe CACHE and DALVIK-CACHE. Then Reboot phone.
is wipe cache the same as format cache ?
Yes and no. It's a deeper clean allegedly.
This is the one I meant
Here we go again . I meant this one .
Can we get this stickied please?
is there anyway to write a script that can be run from recovery to do all that stuff automatically?
I'm sure it can be accomplished. I just don't know how :'(
TEAM MiK
Mik Roms Since 3/13/11
prboy1969 said:
Can we get this stickied please?
Click to expand...
Click to collapse
I'd second that but I don't agree with the instructions regarding Titanium. Of course, one should only restore system data at their own risk with the expectation that it'll mess things up but I've never had any trouble restoring data for nonsystem apps. For me being able to restore an app's data after a wipe or reset is one of the main benefits of having root access. I would never flash different ROMs if I thought I was gonna lose all my app data.
raydawg said:
is there anyway to write a script that can be run from recovery to do all that stuff automatically?
Click to expand...
Click to collapse
Yes. My Linuxfu is weak though, so I'm not gonna be writing it but I think it's a fairly easy task. Maybe check the Evo forums, I've seen a lot of them mention a full wipe zip. I wanna say it's Myn's but wouldn't place money on it.
jesusice said:
I'd second that but I don't agree with the instructions regarding Titanium. Of course, one should only restore system data at their own risk with the expectation that it'll mess things up but I've never had any trouble restoring data for nonsystem apps. For me being able to restore an app's data after a wipe or reset is one of the main benefits of having root access. I would never flash different ROMs if I thought I was gonna lose all my app data.
Yes. My Linuxfu is weak though, so I'm not gonna be writing it but I think it's a fairly easy task. Maybe check the Evo forums, I've seen a lot of them mention a full wipe zip. I wanna say it's Myn's but wouldn't place money on it.
Click to expand...
Click to collapse
There is a " Format ALL " for the OG EVO made by Calkulin. It's on his thread HERE. But it's only for 2.1 / 2.2 . As for my opinion on TB, well it comes from a LOT of Flahing ( read FLASHAHOLIC ). That's why I'm always flashing devices for other people. Just so I can get that rush of installing a new Rom on a device . Yes I know it's a sickness . But I figure it's safer to instruct people not to restore any data. Because we are who we are, and if you say some is ok. Then what is likely to happen is it will almost all be restored . Most always causing all kinds of weird issues. Yes you can restore some app data, but you have to use common sense ( no pun intended ) .
Mod can you please sticky this for us. Thank you
good guide noticed a big improvment! thanks. +1 for sticky!
No problem. Glad it helped you .
I’m new to this forum and to the Android world, so please bear with me.
I have just purchased the Samsung Galaxy Tab2 10.1 GT-P5113, and the 1st thing I did was to root the device.
I have since been searching for the perfect ROM in order to get both smoothness/performance and the ability to over clock up to 1400. I have tried a couple of ROM’s and flashing ROM’s became pretty straight forward for me, but I was just not happy with the ones I have tried and the only over clocking one only allowed me overclock up to 1200.
Now I just restored it back to factory settings, but I now have an issue…
The available space on the internal sdcard is less than 500Mb!!!! I followed all the procedures of wipe data/factory reset, wipe cache, wipe dalvik. And still, something is getting stored on the sdcard and I’m not sure what or where that is.
I also have the issue, that I’m not able to update the OS, but that I would guess it’s because, and correct me if I’m wrong.. the devise is Rooted..
So all in all, those are my issues and I would like to get them fixed. Any help would be gladly appreciated.
1- The sdcard space causes me headaches and I don’t know how to resolve it.
2- What ROM would you suggest based on what you read
3- Why can’t I update?
1-Their is option in cwm to format emmc use with extreme caution
2- use aokp or cm10 from www.teamhacksung.org and it has update feature inside it
Sent from my GT-I9300 using xda app-developers app
If you did Soft-Brick your new Nexus 7 2013 and you cannot access your Nexus 7 from your computer or a Factory Reset does not help please follow this guide. :crying:
(This is way different than the 0 Internal Storage bug. Go here: http://forum.xda-developers.com/showthread.php?t=2380913 )
Step 1: Download and install Wugs toolkit from here: http://www.wugfresh.com/nrt/
Step 2: Let it download the files it needs and choose what device your have EXACTLY what you have.
Step 3: Install the universal drivers by finding the Initial Setup part which is the big bar at the top. Go to the Step 2 tab and install the Universal Drivers and then let that install. It installs ADB so you can access ADB even in recovery if you could not before.
Step 4: Launch the Advanced Utilities in the bottom left and you will need a new ROM. Go here to get one: http://forum.xda-developers.com/forumdisplay.php?f=2411
gApps: http://goo.im/gapps
Step 5: Once you have those two things go to Flash Zips at the top right and tell it that the file is on the computer. Go to add files and add the ROM then GAPPS and enable to the left that it is a ROM but disable the nandroid backup because you really don't need it at the moment. Also have Wipe Dalvik, Cache, and Data on at the bottom.
Step 6: Confirm it and let it flash. Done! It will take about 5 minutes. Go eat or do something while waiting. It might take less but if you want to be on the safe side just let it run until your device powers on. :victory:
I AM NOT RESPONSIBLE FOR ANYTHING THAT YOU DO WRONG.
If you have any questions or comments please leave some.:good:
So, use a toolkit to install a ROM. How is this some magical fix?
khaytsus said:
So, use a toolkit to install a ROM. How is this some magical fix?
Click to expand...
Click to collapse
I never meant for it to be a "magical" fix. It is just a fix for a soft-bricked Nexus which had a rogue ROM and a Factory Reset would not fix nor was ADB working. Maybe someone has this happen and if you have a Backup from lets say Titanium Backup you kind of don't want to Format Data. So if you could just appreciate if I made a tutorial for the less fortunate in Android I am sorry. Skip the thread next time please
WeRSpecialPeople said:
Also have Wipe Dalvik, Cache, and Data on at the bottom.
Click to expand...
Click to collapse
You say here to wipe data.
WeRSpecialPeople said:
Maybe someone has this happen and if you have a Backup from lets say Titanium Backup you kind of don't want to Format Data.
Click to expand...
Click to collapse
And here not to format data. Though wipe and format are not the same, the end result to the user is still that the data is gone. So I'm not sure whether you mean for the data gone or not.
WeRSpecialPeople said:
If you have any questions or comments please leave some.:good:
Click to expand...
Click to collapse
1. Usually, the better option is to find the most similar ROM to the one that the data partition was populated with, so there will be a smaller likelihood of problems. For example, an older working nightly of the same ROM. Dirty flashing a random ROM is less likely to be problem-free.
2. Out of curiosity, why a toolkit, especially when flashing a ROM zip from recovery (not even ADB or fastboot) would work just as well?
bananagranola said:
You say here to wipe data.
And here not to format data. Though wipe and format are not the same, the end result to the user is still that the data is gone. So I'm not sure whether you mean for the data gone or not.
1. Usually, the better option is to find the most similar ROM to the one that the data partition was populated with, so there will be a smaller likelihood of problems. For example, an older working nightly of the same ROM. Dirty flashing a random ROM is less likely to be problem-free.
2. Out of curiosity, why a toolkit, especially when flashing a ROM zip from recovery (not even ADB or fastboot) would work just as well?
Click to expand...
Click to collapse
Alright Formatting Data wipes the whole device usually. Wiping the data gets rid of the users apps. Lets say you have a backup in storage/emulated/legacy. It will still be there after you wipe the data.
1. Yes but that is the users choice. I couldn't find a definite stock ROM to the device so I will just let them pick.
2. If you want me too I could make a tutorial using ADB if you really want me too. This was just a 5 minute tutorial on a toolkit and I understand that most people here do not like toolkits but it is a really easy way. Just tell me if you do want me to add ADB tutorial as well and I will. :silly:
WeRSpecialPeople said:
Alright Formatting Data wipes the whole device usually. Wiping the data gets rid of the users apps. Lets say you have a backup in storage/emulated/legacy. It will still be there after you wipe the data.
...
Just tell me if you do want me to add ADB tutorial as well and I will. :silly:
Click to expand...
Click to collapse
I don't think formatting data wipes the whole device...just the data partition. Same as wiping data. The kernel and ROM in the boot and system partitions respectively stay. Wiping data wipes all user data as well, not just apps. In either case, I don't think sdcard gets wiped.
Since I won't be using it, I personally don't mind what you do with the toolkit, but users need to be aware that it's not the most problem-free method.
bananagranola said:
I don't think formatting data wipes the whole device...just the data partition. Same as wiping data. The kernel and ROM in the boot and system partitions respectively stay. Wiping data wipes all user data as well, not just apps. In either case, I don't think sdcard gets wiped.
Since I won't be using it, I personally don't mind what you do with the toolkit, but users need to be aware that it's not the most problem-free method.
Click to expand...
Click to collapse
Sdcard is on /data so if you wipe data (including factory reset) the sdcard is 'formatted'.
khaytsus said:
Sdcard is on /data so if you wipe data (including factory reset) the sdcard is 'formatted'.
Click to expand...
Click to collapse
Does it now...how odd. Has it always worked like that on every device? On my Galaxy Nexus, TWRP specifically ignores the sdcard mount point.
EDIT: okay, I think I understand the confusion. I meant that wiping data/factory resetting from recovery doesn't wipe sdcard. I know that doing so from Android does.
Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Any information you guys can offer would be great. Thank you so much for your time !
Downloaded7 said:
Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
A backup in CWM is the same as a nandroid backup. It basically take a "snapshot" of your ROM and restore it exactly as it was when backing up.
Titanium Backup is an app that backup your apps and app's data. It's recommend you only restore user's apps and data. Let Google restore any system app's data.
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
Wiping data/factory reset only wipe the data. Wiping system will wipe your ROM (system partition) Of course you don't want to wipe all the files such as the ROM you're going to flash.
There's an option to format internal sd, that will wipe EVERYTHING so unless you know how to ADB push files or sideload a ROM, DO NOT touch that.
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
No, just flash kernel. Some recommend wipe cache and dalvik cache after kernel flash before reboot.
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Different app that does the same thing. Usually go with what is recommend by the ROM's dev. I ususally just leave what's included with the ROM.
Any information you guys can offer would be great. Thank you so much for your time !
Click to expand...
Click to collapse
Hope that answer some of your questions. I'm sure I left out some stuffs so hopefully someone else can add to it.:good:
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?