Related
OK, the CM7 ROM for the Samsung Galaxy S i9000 has now hit the CM7 Mainstream and has matured in leaps and bounds over the last few weeks. The installation method has therefore ALSO matured by leaps and bounds.
However, there has been a downside to all that advancement...namely that there are lots and lots of incorrect install procedures floating around out there and even more misunderstandings as to what/how/when/why you install CM7 on your SGS i9000.
Therefore, this is intended to be the definitive guide about how to install CyanogenMod 7 (or CyanogenMod 7.1 if you are a stickler for such things since that is the most recent stable version but for the purposes of this guide it is STILL CM7) on the i9000 right here, right NOW. As things change, the first post of this thread will be updated.
If you have any questions/comments about the CM7 install procedure, post them here.
If you have any questions/comments about CM7's features, capabilities, battery life or anything OTHER THAN installing it...look HERE or HERE.
Before we do anything....make sure of the following:
* Your phone is fully charged.
* You have confirmed you can get into download/recovery with the three button method.
* You have used Titanium Backup to backup your apps (yes, there may be some factory defaulting happening soon).
* You have taken a Nandroid backup via Clockwork Mod, just in case the early steps go south.
* You have used a third party program to back up your SMS messages (if so desired)
* You have made your peace with your loved ones and said all your goodbyes...maybe left a nice note or something.
Remember, this will be one of the most harrowing, horrific experiences of your life. Grown men have been known to gnaw off their own legs during this procedure, unable to face the deepening horror their feeble minds cannot hope to comprehend.
Are you SURE you want to install CM7?
Very, VERY SURE?
OK, its your funeral, I am just here for the open bar.
OK, here we go....
FIRST STEP!!!!! THE PRE-INSTALLATION TANGO!!!!
Boy are you lucky to be doing this now. Recently CM7 was improved so that it works just fine with either Froyo or Gingerbread Bootloaders. It used to be that when you installed CM7 with Gingerbread bootloaders, a puppy died in agony. Now, the cuddly little puppies are safe thanks to the hard work of the CM7 Devs.
However, if for some strange reason you have still have Eclair installed currently, smash your head repeatedly against a wall for being such a stinking Luddite. Once you wake up, update to Froyo or Gingerbread and then come back and start this again. Plenty of threads on XDA will help you do that. Go read one and flash froyo or gingerbread via ODIN, we'll wait right here with the car running.
Don't know how to use ODIN? Not sure about all those little checkboxes? Befuddled by those driver thingies? Unsure how to click on the links above while using a Commodore64? Well, we won't wait in the car THAT long. If this is the case then you absolutely shouldn't be flashing CM7 yet my poor lost child, educate yourself for awhile and then come back, or just buy a used iPhone.
OK, still with me? ONWARDS.
SECOND STEP!!!!! THE NITTY GRITTY DETAILS, AKA THE CALM BEFORE THE STORM!!!!!
Here is the point where you need to do all sorts of things that you may have already done.
If you have already done them, GOOD, you are very, very clever and ahead of the game. Give yourself a gold star.
If you don't know how to do any of these things, then you shouldn't be here yet. Go search for things you don't understand in the general and Q&A forums for the i9000 and when you feel you are better grounded in the arcane mysteries of flashing custom ROMS, come back and we will have a joyous reunion and try this again.
OK, so what do you do in STEP TWO?
* Doublecheck that you can indeed get into Download Mode using Vol Down+PWR+Home, and into Recovery with Vol Up+PWR+Home. If not, go away and search XDA for a way to fix that.
* Root your phone.
* Confirm you have Clockwork Mod recovery running. If not, use Odin to flash this Speedmod kernel if you are on Froyo. If you are on Gingerbread flash the TalonDev kernel using the v2.2 tar (yes I know the TalonDev kernel has lagfix automatically enabled, but as your file system will be grabbed and ripped out still beating and then replaced with a better one by the CM7 Installer, it really doesn't matter). There are two different versions of the v2.2 tar available but don't panic. Use TalonDEV-0.2.2R2-I9000-1200-JVP.tar first...if that doesn't work for you, try TalonDEV-0.2.2R2-I9000-JVP.tar. One of the two should work for you. (Thanks to chan1628 for testing them the hard way)
* Install ROM Manager (I STRONGLY suggest you buy the Premium version if possible to make flashing Nightlies easier. It is quite cheap with a lot of great features and is one of the core apps you will use on your phone from here on in...plus Koush deserves your support).
* Take another nandroid backup (even if you took one already) and confirm your Titanium Backup is up to date (and includes a backup of ROM Manager).
* Confirm that you are rooted.
* Backup your contacts to either Exchange, Gmail or your SIM card.
* Write down your correct APNs and your IMEI, just in case.
* Take a backup of your efs folder and save it somewhere.
* Post a note on your monitor reminding yourself to breathe.
* Say goodbye to your Samsung apps like Snap2Go and Daily Briefing, they won't work with CM7.
* Pour yourself a stiff drink
Confused? Not sure how to root your phone or worried about voiding your warranty? Really curious about what these APN things and where can you find them? Hoping to sync your phone with iTunes once CM7 is installed? Then go away, do some searching, get up to speed and I will see you later. I mean it...avaunt ye. Scram. Exeunt with all due alacrity. Happy reading.
Also, if you are getting errors concerning CWM, or cannot get into CWM3 Recovery, then search XDA (or the comments to this thread) for a solution. I cannot help you. I am not an expert on Clockwork Mod, I am just here to get CM7 running for you, or kill you and steal your girlfriend in the attempt. Clockwork Mod is YOUR lookout.
Still here? Did all that? CWM Recovery working properly? Crossed all your i's and dotted your t's? Forward then. Things get REALLY BAD from here on in. Whatever happens next, I am truly, truly sorry.
THIRD STEP!!!!!! THE COMPLEX, AGONIZING EXPERIENCE OF FLASHING THE ROM ITSELF!!!
Are you sure you are ready for this? Are you quite, QUITE sure?
It is not too late to turn back....and if you do no one will think less of you. I promise.
Positive you are where you want to be?
Brave, brave darling. Take my hand and lets do this then....there are two possible methods to use now that you are at the Third Step..Method the First uses the ROM Manager and is by far the simpler of the two. However if the ROM Manager doesn't work for you or if you have a sudden premonition of flaming disaster about it....don't cry. Man up and go to the manual method listed after Method the First, known quite coincidentally as Method the Second.
Method the First!
Open ROM Manager from your App Drawer.
Select Flash ClockworkMod Recovery.
When it asks you what phone you are using, scroll down until you find Galaxy S MTD and select it (Galaxy S is what CM7 calls the i9000 series...CM7 is weird that way).
When it asks what version to use, select CMW3.
By the way, if ROM Manager tries to argue with you during this process, or tells you your phone may not be supported, ignore it and click OK or Continue or whatever it takes. It just worries over what you may be about to do to yourself.
Confirm that under Flash ClockworkMod Recovery it now reads Current Recovery: ClockworkMod 3.x.x.x. This means that now you should be able to see CyanogenMod zips and nightlies (if you have ROM Manager Premium) in ROM Manager. Hoorah!
Now, the moment of truth arrives...select Download ROM.
Next close your little eyes tightly and select CyanogenMod or CyanogenMod Nightlies (if you see that one). Either one will do.
Down the road, you will use the CyanogenMod Nightlies files to update...assuming you survive the next 15 minutes. However when installing you can use the single file in the CyanogenMod folder (there for Free users) or the latest Nightly in the CyanogenMod Nightlies folder...same difference.
So click the file of your choice and stand back...well, not too far back because there is more stuff you have to do.
If/when you are asked if you wish to reinstall Google Apps, it is highly recommended that you do so, so check the little box. This saves many headaches and potential fc's down the line.
When you are asked what you wish to do to prepare for the new ROM, you can choose to do another Nandroid Backup, Clear Data and Cache (wiping the device) and/or Clear the Data Cache. No need for another Nandroid backup, but select the other two and hit OK.
Now let the ROM Manager make some magic. It will take a couple minutes but likely not nearly as long as you expect, so go out and make tea or paint the Sistine Chapel or something.
While you are gone your device will do all the wiping and installing, back up your efs folder and apply the new file system you will need. You will NOT need to apply any lagfix or mess about with tweaks or whatnot....CM7 does it all for you and no other options are possible....so don't ask.
Method the Second!
If for whatever reason you are having trouble working with ROM Manager in the previous method and are therefore stuck, you can do the following to flash CM7 manually.....but if you have a weak heart or tend to get squeamish...I implore you to look away.
Download this most recent version of CM7 from http://download.cyanogenmod.com/?type=nightly&device=galaxysmtd
Then download the most recent set of Google Apps from http://goo-inside.me/gapps
Place both on your SD card.
Go into Recovery using the handy-dandy Three Button Skidoo (NOT by using the command "Reboot to Recovery" found in ROM Manager...you have been warned).
Do a Factory Reset (wiping data so if you forgot to backup your apps before....whoops)
Wipe the Dalvik and Cache (just in case).
Select Install Zip from SD Card and flash first the CM7 zip, and then the gapps zip. No need to reboot in between. Finally fix permissions.
NOTE: If you are one of those people who have done some research and have also downloaded one of the CM7 custom kernels which you wish to flash as part of your install (if you haven't don't worry about it, I don't recommend using a custom kernel before you have spent some time with the stock kernel, but some people think they are 1337)...make certain you flash the Nightly BEFORE the custom kernel, otherwise you will totally confuse the installer and very bad things will happen which will require you to flash back to a Samsung ROM using ODIN and start all over again.
Once everything has completed, THEN reboot into CM7 (HOO-RAH) and continue to the Fourth Step. Hurry, hurry, scroll back up....
GO!!!
Oh, WAIT A MINUTE....When you have done all the stuff in the Fourth Step, do this too...go to ROM Manager, and select Flash ClockworkMod Recovery. ID your phone as Galaxy S MTD when it asks and select CWM3...it will tell you that your phone is not supported or some such but have it install it anyway. What the heck does it know. Doing so will ensure you can find your the Nightly updates using ROM Manager Premium in the future.
OK, now go on to the Fourth Step...really this time...
GO! GO!
FOURTH STEP!!!!! STEP OUT INTO THE LIGHT AND BREATHE THE FREE AIR
That's it, you are done. Throw back that drink now...or if you don't want it, I'll take it.
Your phone will show the CM7 SGS splash screen for a bit, then the CM7 boot animation for a while longer (spin, spin, spin)...and then you will be in CyanogenMod 7.
If you find that the boot animation never seems to end, or keeps restarting...DON'T PANIC. This happens to some people when flashing CM7 for the first time. Just go to recovery and flash the Nightly again, you should be fine. If you used ROM Manager the first time, the nightly will be in the ROM Manager folder on your SD card.
Where is all the pain, the agony, the brain bending complexity reducing scholars to madness that I warned you about?
OK, I lied...but I had to make sure you were serious.
Now restore your apps (remember that is best to do fresh from the Market, but if you use TB then be sure to reinstall just the APP, not APP + DATA, and NO SYSTEM APPS) and put all your contacts and email addresses back and so on.
Also, remember that your external SD card is now located in the /emmc directory. Why? Because that is how it is in CM7, so cope. It really is NOT that tough to get used to. However, if you want to have some kicks, go into the CM7 Dev thread and ask where your external_sd card has gone a few times to watch people go berzerk yelling at you. Fun, fun, fun.
From here on in, you can install nightly updates to stay on the bleeding edge of CyanogenMod, as well as to allow yourself to experience the terror of waiting for that boot animation to stop again and again and again. You can look at the Nightly Wiki for instructions on different flashing strategies.
You may also install custom kernels and alternate modems via Recovery if you wish, but be sure that they are CM7 compatible. The ones you used back on Samsung ROMs won't work for you any more.
Carry on, and enjoy your new ROM.
As always, if this procedure bricked anything or gave your dog syphilis, it isn't my fault. By God, I WARNED you. If you liked it, or it worked out well for you, feel free to click Thanks and heap praise in the comments.
Finally, all due honour and thanks to the incredible Devs and Maintainers of TeamHacksung and the SGSTEAM listed below. Find their profiles and donate to them, they have earned it.
* codeworkx - http://twitter.com/codeworkx
* atinm - http://twitter.com/atinm
* coolya - http://twitter.com/coolya
Great guide, just want to make a quick addition...
rschenck said:
OK, so what do you do in STEP TWO?
* Root your phone.
* Confirm you have Clockwork Mod recovery running. If not, flash the Speedmod kernel.
Click to expand...
Click to collapse
I couldn't complete this step during my exciting first install of CM7
If anyone has trouble getting Clockworkmod Recovery running, and you can't manage to flash a new kernel using Odin/heimdall please read:
[RECOVERY] 3e Recovery Modded w/ No Verification
I just skimmed through it but wouldn't this require you to buy rom manager premium?
runedrune said:
I just skimmed through it but wouldn't this require you to buy rom manager premium?
Click to expand...
Click to collapse
No. The premium version is only required to download nightlies directly through the app. Download them manually, then point rom manager at the zip on your sdcard & install.
Yay! First thanker! Nice guide too.
runedrune said:
I just skimmed through it but wouldn't this require you to buy rom manager premium?
Click to expand...
Click to collapse
Not the install, that is free as far as I know. Installing nightlies via ROM Manager needs Premium. Plus I suggested people buy Premium anyway.
sambwel said:
No. The premium version is only required to download nightlies directly through the app. Download them manually, then point rom manager at the zip on your sdcard & install.
Click to expand...
Click to collapse
Exactly. The instructions tell you to use rom manager to download CM7. Just thinking that http://download.cyanogenmod.com/?device=galaxysmtd should be included too for those that can't buy rom manager.
But anyway great guide rschenck. Hopefully it'll save us from unnecessary questions.
runedrune said:
I just skimmed through it but wouldn't this require you to buy rom manager premium?
Click to expand...
Click to collapse
Yepp true story!
IF you want to download roms and stuff from Rom manager you do have to have premium.
I have no plans to install yet (still waiting for the stable release) but really this guide has no boring part. Very informative and easy to follow. Just wanna say thanks for this guide. KUDOS!
Nice tutorial man. I want to instal cm7 and this tutorial is very helpfull. Hope this topic get sticky :d
upgrading to latest
just to clarify, I'm (thanks to you!) on v11 due to some people suggesting me that version over v14. After reading some I would like to flash the new experimental build (v15?) in order to do so I:
1) charge it up
2) do a nandroid backup /done
3) wipe data/factory reset + wipe cache in CMW /not sure about this, I've read some diferent post about what to wipe. Some said that when upgrading only cache + dalvik will do just fine. This is the main issue.
4) flash the v15 (update-cm-7-05282011-NIGHTLY-GalaxyS-signed.zip) through CMW
+ all that other stuff like preparing myself for long agonizing experience and stuff
thanks in advance!
James.q said:
just to clarify, I'm (thanks to you!) on v11 due to some people suggesting me that version over v14. After reading some I would like to flash the new experimental build (v15?) in order to do so I:
1) charge it up
2) do a nandroid backup /done
3) wipe data/factory reset + wipe cache in CMW /not sure about this, I've read some diferent post about what to wipe. Some said that when upgrading only cache + dalvik will do just fine. This is the main issue.
4) flash the v15 (update-cm-7-05282011-NIGHTLY-GalaxyS-signed.zip) through CMW
+ all that other stuff like preparing myself for long agonizing experience and stuff
thanks in advance!
Click to expand...
Click to collapse
You are quite correct...when upgrading all you need to do is wipe dalvik cache. You can also take a nandroid backup if you wish to be extra careful but there is no need to wipe data for an upgrade.
Sent from my GT-I9000 using XDA Premium App
rschenck said:
You are quite correct...when upgrading all you need to do is wipe dalvik cache. You can also take a nandroid backup if you wish to be extra careful but there is no need to wipe data for an upgrade.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
thanks! .. so is it just wipe cache or both wipe cache + wipe dalvik cache in advanced menu? I get confused with that
James.q said:
thanks! .. so is it just wipe cache or both wipe cache + wipe dalvik cache in advanced menu? I get confused with that
Click to expand...
Click to collapse
Wipe cache is in the main cwm menu, wipe dalvik is in advanced...and you can wipe them both.
Sent from my GT-I9000 using XDA Premium App
Thanks mate, you made my day! I haven't laughed so hard in a while ...
James.q said:
thanks! .. so is it just wipe cache or both wipe cache + wipe dalvik cache in advanced menu? I get confused with that
Click to expand...
Click to collapse
Yes, you should do both
A few small edits and clarifications added...
Good job on this guide.
You kids gave it easy. Back in my day, we had to flash our phones in Morse code.
Sent via XDA Premium app on my GT-I9000 running CM7 (GB 2.3.4)
bump...and if anyone who has used this guide has feedback or suggestions, please comment with them.
How come when i go to download rom i cannot see cyanogen mod there?
I did buy the rom manager
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 .
So, I'm new to the world of tablets - the only interaction with them being some light use on my mom's tablet (including rooting it via Iconia Root and installing Acer Recovery Installer v2.54) I was curious about updating via ARI (since she's rooted and being plagued by OTA popups). Back when she first got the tablet, she tried to update and it would stop mid-download, giving no error, and just sit there until she cancelled it (this was before the root). So, basically, my question is: Is it possible to run a stock update (Ie "Stock 3.1 4.010.42_EMEA_GEN3") without having to wipe during install? I have a backup via ARI and also Titanium backup installed but I'd really like to not have to re-install all the apps/set up the homescreen (she's on stock) and stuff. I know on my OG droid that when I installed CM7 I had to do a wipe for it to even get past the boot screen but I figure with this being a stock update maybe it's different...
If not is there some way that I can install an update while keeping the root/system data?
AliceInUnderland said:
So, I'm new to the world of tablets - the only interaction with them being some light use on my mom's tablet (including rooting it via Iconia Root and installing Acer Recovery Installer v2.54) I was curious about updating via ARI (since she's rooted and being plagued by OTA popups). Back when she first got the tablet, she tried to update and it would stop mid-download, giving no error, and just sit there until she cancelled it (this was before the root). So, basically, my question is: Is it possible to run a stock update (Ie "Stock 3.1 4.010.42_EMEA_GEN3") without having to wipe during install? I have a backup via ARI and also Titanium backup installed but I'd really like to not have to re-install all the apps/set up the homescreen (she's on stock) and stuff. I know on my OG droid that when I installed CM7 I had to do a wipe for it to even get past the boot screen but I figure with this being a stock update maybe it's different...
If not is there some way that I can install an update while keeping the root/system data?
Click to expand...
Click to collapse
No. If you run the OTA, you WILL lose root. Not to mention I don't have a lot of faith in any device OTA updates. Prior experience, and hanging around various forums, well, you can read the horror stories.
I would advise, if you want to upgrade her OS and get rid of the "pesky" update notifications, is to flash one of the Stock rooted roms available. Or maybe a stripped down version of a Stock rom.
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
get and flash one of the honeylicious rom from the dev area .. good rom very basic apps.. but has a update to get the acer apps back.. and bunch of other cool mods.. the dev is also . kinda trustworthy..
Giggles.. ok he is kewl for a guy yukeeee guys smell..
good luck .. read read read read before you flash anything and of course back up and back up your backups .. then back them up again
cruise350 said:
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
Click to expand...
Click to collapse
Well... if the person was going to do an update to the exact same rom (different version) I would say ok.
But... if you are going to go to a totally different Rom, you NEED to wipe User Data.
Or, does anybody want to tell me you never have to?
3 Wipes. Mandatory when switching between roms, unless you are a dev and know exactly what you are doing.
Or.... you can forget about the safe side of things, and just flash away, and hope luck is with you.
The Market, SHOULD, allow you to re-download apps based on the market version you previously used. If not, it's a good time to clean house of the useless apps.
Moscow Desire said:
No. If you run the OTA, you WILL lose root. Not to mention I don't have a lot of faith in any device OTA updates. Prior experience, and hanging around various forums, well, you can read the horror stories.
I would advise, if you want to upgrade her OS and get rid of the "pesky" update notifications, is to flash one of the Stock rooted roms available. Or maybe a stripped down version of a Stock rom.
Click to expand...
Click to collapse
I wasn't talking about an OTA, I was talking about the stock 'rom' updates via recovery. I've had experiences with phones that have been rooted and accidentally updated via OTA, it's not fun. My phone was actually put into something I like to refer to as the Root limbo lol, bricked it for a small period of time - that was fun fixing it. I didn't have a nandroid at the time so I had to start from scratch...
cruise350 said:
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
Click to expand...
Click to collapse
So if I find a rooted version of stock OTA I can install it and only wipe Dalvik? I won't get stuck in a bootloop if I don't wipe data?
AliceInUnderland said:
So if I find a rooted version of stock OTA I can install it and only wipe Dalvik? I won't get stuck in a bootloop if I don't wipe data?
Click to expand...
Click to collapse
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------
erica_renee said:
get and flash one of the honeylicious rom from the dev area .. good rom very basic apps.. but has a update to get the acer apps back.. and bunch of other cool mods.. the dev is also . kinda trustworthy..
Giggles.. ok he is kewl for a guy yukeeee guys smell..
good luck .. read read read read before you flash anything and of course back up and back up your backups .. then back them up again
Click to expand...
Click to collapse
Hey I resemble....or is it resent that remark! lol
kjy2010 said:
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
I can't seem to find any pre-rooted stock Roms on the Developers forum. Links? I know I'm probably being a pain in the ass but I really don't want to get something by mistake and start with scratch on my mom's tablet - if it were mine I wouldn't care. lol
Click to expand...
Click to collapse
The link in the post above yours in this thread. Is a link to the rom scroll up one post
Giggles
AliceInUnderland said:
kjy2010 said:
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
I can't seem to find any pre-rooted stock Roms on the Developers forum. Links? I know I'm probably being a pain in the ass but I really don't want to get something by mistake and start with scratch on my mom's tablet - if it were mine I wouldn't care. lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
Oh my god you rock, thanks so much!
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Oh my god you rock, thanks so much!
Click to expand...
Click to collapse
Yw
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
Okay, this sent her into a bootloop so I had to nandroid. I wiped dalvik cache before installing this. Put it in the root of my SD card and installed via CWM in recovery. what am I doing wrong?
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Okay, this sent her into a bootloop so I had to nandroid. I wiped dalvik cache before installing this. Put it in the root of my SD card and installed via CWM in recovery. what am I doing wrong?
Click to expand...
Click to collapse
I've never heard of the A500 going into a bootloop simply from flashing one rooted stock ROM to another, but then again most people do all the necessary wipes when they do. Did you wipe dalvik and battery stats? That's about as minimal as you're going to get. If that doesn't work, you'll just have to flash the proper way. Instructions here complete with a video tutorial on how to flash by yours truly:
http://forum.xda-developers.com/showthread.php?t=1390860
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
I've never heard of the A500 going into a bootloop simply from flashing one rooted stock ROM to another, but then again most people do all the necessary wipes when they do. Did you wipe dalvik and battery stats? That's about as minimal as you're going to get. If that doesn't work, you'll just have to flash the proper way. Instructions here complete with a video tutorial on how to flash by yours truly:
http://forum.xda-developers.com/showthread.php?t=1390860
Click to expand...
Click to collapse
Nevermind, I fixed it XD I wiped dalvik and battery/partition and it worked fine lol.
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Nevermind, I fixed it XD I wiped dalvik and battery/partition and it worked fine lol.
Click to expand...
Click to collapse
Uh huh....you're welcome!
Click to expand...
Click to collapse
Hello,
So out of nowhere, everytime I open a LG app, such as the dailer,quickremote,launcher and even the gallery, it syas "App updates has stopped".
Also, when I opened Whatsapp, it said that my messasging files where damaged, luckily I could restore them...
Whats is happening and how can I solve this problem??
I'm to afraid to reboot my device, because I'm scared that It will end up in a bootloop...
If you're using an original stock ROM, than copy all your important files to your PC, and factory wipe.
If you're on a custom ROM, copy all your important files to your PC, than get a copy of your custom ROM zip file and Gapps onto your phone, than do the following (using TWRP, I don't use CWM):
1) Go to Advanced Wipe, and wipe everything except for Internal Storage.
2) Install ROM and Gaps.
3) Wipe Cache, Dalvik Cache, and Internal Storage.
4) Reboot.
palaczu said:
If you're using an original stock ROM, than copy all your important files to your PC, and factory wipe.
If you're on a custom ROM, copy all your important files to your PC, than get a copy of your custom ROM zip file and Gapps onto your phone, than do the following (using TWRP, I don't use CWM):
1) Go to Advanced Wipe, and wipe everything except for Internal Storage.
2) Install ROM and Gaps.
3) Wipe Cache, Dalvik Cache, and Internal Storage.
4) Reboot.
Click to expand...
Click to collapse
Okay, so I'm on the stocks ROM, but rooted, with x posed and TWRP.... What do I have to do??
pottemans said:
Okay, so I'm on the stocks ROM, but rooted, with x posed and TWRP.... What do I have to do??[/QUOTE
Go to the post where you got your KDZ file, and ask the DEV quoting my second method, if using it will require re-rooting or re-flashing SuperUser again.
I don't think it does, but, better to be safe than sorry.
I personally always use plain stock (d80220a currently), or I use an AOSP, CM, or PA, and using the above methods during installation of a custom ROM, always prevented system ui or other FCs, which did sometimes happen when I didn't wipe cache, dalvik, and internal.
Just double check with the dev of your ROMs OP.
Click to expand...
Click to collapse
palaczu said:
pottemans said:
Okay, so I'm on the stocks ROM, but rooted, with x posed and TWRP.... What do I have to do??[/QUOTE
Go to the post where you got your KDZ file, and ask the DEV quoting my second method, if using it will require re-rooting or re-flashing SuperUser again.
I don't think it does, but, better to be safe than sorry.
I personally always use plain stock (d80220a currently), or I use an AOSP, CM, or PA, and using the above methods during installation of a custom ROM, always prevented system ui or other FCs, which did sometimes happen when I didn't wipe cache, dalvik, and internal.
Just double check with the dev of your ROMs OP.
Click to expand...
Click to collapse
Ok thanks.... But the weird thing is, is that it just appears out of nowhere! I'm using the stock rom, with root and Xposed since I got my LG and never had a problem with it! Don't you think a simple reboot will fix this?
Click to expand...
Click to collapse
I assumed you've already rebooted your phone and cleared data and cache for the affected apps, and it hasn't solved your problem, that's why I provided the solutions above.
palaczu said:
I assumed you've already rebooted your phone and cleared data and cache for the affected apps, and it hasn't solved your problem, that's why I provided the solutions above.
Click to expand...
Click to collapse
Thanks! What I'll do tomorrow is I'll backup my files with MyBackup, Backup my foto's and move those files to my computer... After I've done that, I'll try to reboot, but I'm just too afraid that I will get in a bootloop.... But I'll wait for tomorrow, since it's Kingsday were i live (The Netherlands)
palaczu said:
I assumed you've already rebooted your phone and cleared data and cache for the affected apps, and it hasn't solved your problem, that's why I provided the solutions above.
Click to expand...
Click to collapse
Welp, I just noticed vibration is not working either....
Yeah, I tried a few various ROMs, like CM, PA, Mahdi, SlimKat, PAC, etc, and because of all the bugs, I always endup going back to stock.
The only thing I don't like in the stock ROM, is the way the calling and massaging apps UI look. Other than that, I'm satisfied.
I used Sony phones before, and they didn't have so many bugs in the custom ROMs.
LG G2 ROMs seem to plagued by bugs, which is evident from all the beta releases, and hardly any STABLE versions. Even the so called stable releases are plagued by bugs. I think all the good devs are gone. They probably got real jobs, and don't have time to tinker with all these ROMs, especially that the LG G2 has so many variants.
Personally, I'd go back to Sony, especially that the Z2 has 3GBs of RAM, but, it's just so much bigger than the G2, and the performance vs price, compared to the G2, is just not worth it.
Anyway. Good luck with your problem.
palaczu said:
Yeah, I tried a few various ROMs, like CM, PA, Mahdi, SlimKat, PAC, etc, and because of all the bugs, I always endup going back to stock.
The only thing I don't like in the stock ROM, is the way the calling and massaging apps UI look. Other than that, I'm satisfied.
I used Sony phones before, and they didn't have so many bugs in the custom ROMs.
LG G2 ROMs seem to plagued by bugs, which is evident from all the beta releases, and hardly any STABLE versions. Even the so called stable releases are plagued by bugs. I think all the good devs are gone. They probably got real jobs, and don't have time to tinker with all these ROMs, especially that the LG G2 has so many variants.
Personally, I'd go back to Sony, especially that the Z2 has 3GBs of RAM, but, it's just so much bigger than the G2, and the performance vs price, compared to the G2, is just not worth it.
Anyway. Good luck with your problem.
Click to expand...
Click to collapse
Thanks! Yesterday Quickremote and Apps-update radomly started to work again, so basically everything is fine now.... Only 2 things are still doing weird....
1) Notification LED not working. It's working with Knock-On though, not with Lightflow....
2) Vibration isn't working at all... not in system apps, games and/or vibrate mode....
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?