Related
So, I'm kinda new at this, as I was told by the forums when trying to post this question in the official gsb thread
I got an eris a few weeks ago for free, and its my first android device. I used it for a while, then rooted it and installed GSB.v2.0-CM7.0.0_RC2_STABLE
I've got it all customized and got some cool apps installed and am loving it. My question is, can I just go into recovery and install GSB.v2.6-CM7.0.0_RC4_STABLE and be good to go, or do I have to back up all my apps and settings and start fresh? I have most of my apps moved to sd. Will they be okay? Also, I went into system and changed my bootscreen, lock and unlock sounds, and added a boot script. I will have to back those up and redo them if anything, right?
skot85 said:
So, I'm kinda new at this, as I was told by the forums when trying to post this question in the official gsb thread
I got an eris a few weeks ago for free, and its my first android device. I used it for a while, then rooted it and installed GSB.v2.0-CM7.0.0_RC2_STABLE
I've got it all customized and got some cool apps installed and am loving it. My question is, can I just go into recovery and install GSB.v2.6-CM7.0.0_RC4_STABLE and be good to go, or do I have to back up all my apps and settings and start fresh? I have most of my apps moved to sd. Will they be okay? Also, I went into system and changed my bootscreen, lock and unlock sounds, and added a boot script. I will have to back those up and redo them if anything, right?
Click to expand...
Click to collapse
You will lose your bootscreen during any ROM flash, plus whatever your boot script is I assume it's somewhere where it would get lost, too.
This may not work for your apps and system settings, but it's safe to try, then you'll know for sure if it'll work.
1. Go to your recovery and create a Nandroid backup of everything just the way it is.
2. Wipe Dalvik cache ONLY, do NOT Factory Reset/Wipe Data.
3. Flash GSB v2.6 and immediately after flash the GAPPs package, just like before.
4. If you had flashed the Cache2Cache script before you have to do that again as well, right after flashing the GAPPs.
5. Reboot and test everything to see if everything works to your satisfaction.
If it's doesn't then you have the Nandroid backup that you can restore. I can provide instructions that I use, and at least one other person has recently used and reported good about which uses Titanium Backup, but you'd really probably want to buy it off the market for it to be easier to do Batch backups and Restores (choose Menu/Batch from TB's main screen).
1. First, make sure the option is checked in TB's preferences to "Force to same location". FYI I do NOT use the checkbox for "Migrate system data". At THIS time (you can change it later), I suggest changing the Compression method to No Compression. This'll make sense in step 6.
2. From Menu/Batch, choose "Backup all user apps + system data".
3. Boot into recovery, do a COMPLETE wipe (Factory Reset/Data/Dalvik cache), flash your ROM and then your GAPPs (it's recommended at this time to NOT flash C2C just yet).
4. Reboot, SKIP setup of your Google account, go into Preferences/CyanogenMod settings/Application and check the box for "Allow application moving". I also change "Install location" to External, but that's up to you; this is just what works for me.
5. Boot back into recovery and flash C2C and reboot the ROM again.
6. Use File Manager, which comes with GSB and navigate to the TitaniumBackup folder (not TitaniumBackup-system). Find the Titanium Backup apk app installer file and reinstall it from here.
7. In TB, under Menu/Batch, choose "Restore all apps with data".
After this is done, reboot. If this works for you and you want to do this again in the future, you can make a copy of the Titanium Backup apk file to some other folder, that way you can re-enable compression in TB's preferences for future backups. I recommend LZ0.
I've been using this second method for the last 3-4 new versions of GSB, don't know how it would work with such a big jump in versions. If neither of these work for you, let me know if you still need help.
You will lose your bootanimation and any scripts you have but your apps will be fine. Like WRT said above just make sure you do a nandroid back up in recovery then wipe cache only. Once that's done flash 2.6 and gapps. Enjoy!
DINC|CM7|SLAYHER#27
Awesome. I had done a nandroid and ti backup to prepare, but I never saw the option in ti for force same location. I know how to backup and reinstall my lockscreen sounds and bootani, so I've got that down. Now that I look there's a 2.7 release which integrates the sdcard speed fix, so I won't need my init script now
Thanks for clearing that up for me, I'll post back when its done and tested if there's any issues.
Update: Well everything worked great! Thanks for all the help guys
Just an idea to restore large data.
An idea is coming to my mind where we can use recovery instead of titanium backup to restore large amount of data.
The idea is to backup only data, android.secure folder and ext via amonRa recovery.
Now, if you are changing roms, you can try to do this thing.
After installation of the rom, restore this backup via recovery.
(If you have ext, flash dt apps2sd first and then restore.)
Don't wipe anything after restore and reboot.
See how it goes.
If all goes well, this may be a good alternative to titanium where a whole bunch of data is required to be restored.
I will also attempt this shortly.
Another important thing.
Just two hours back I flashed cm 6.6.1, flashed gapps, flashed Franco kernel 40, flashed dt apps2sd in that order without rebooting and everything went well after first reboot. I had rom, gapps, kernel and ext everything working fine. So I think there is no need to reboot in between in this case.
Sent from my LG-P500 using Tapatalk
Nice trick, but you can only restore all apps or none. You cant select which apps you would like to restore and if any of the data gets corrupt you will lose all apps.
Hows 6.6.1 treating you ? I am using 6.5.7 which is great in terms of performance and battery.
mansirawat said:
Nice trick, but you can only restore all apps or none. You cant select which apps you would like to restore and if any of the data gets corrupt you will lose all apps.
Hows 6.6.1 treating you ? I am using 6.5.7 which is great in terms of performance and battery.
Click to expand...
Click to collapse
Often, while changing roms, we think of having our current apps on the new rom.
As for 6.6.1, its going very fine. Previously I had uninstalled it due to wifi problem, but I hadn't checked it with Franco kernel.
With Franco gb kernel its all fine.
Sent from my LG-P500 using Tapatalk
Did you try with app2sd script ?
I've once tried this but with data2sd, it didn't work. (or maybe the script doesnt succeeded at first place).
Anyway, thanks for reminding this
i believe this may also work with cwm (make a backup, wipe the usual stuff, flash the new rom, restore data.img in advanced restore). please confirm this
I think it should work. We will have to select all three data/android secure /ext one by one.
Sent from my LG-P500 using Tapatalk
It works!
Just used this method to upgrade from mike's os beta6.5.6 to beta6.5.8 with Darktremor's A2SD.
-Booted in the cwm recovery and did a compleat backup
-Wiped everything, data/cache/dalvkin..everything
-Flashed os (didny reboot as recomended)
-Flashed new kernel
-Rebooted to check if the OS was loading (think you can skip this)
-Back to custom recovery-> backup and restore -> advance restore -> restor data and sd-ext
-Rebooted to check if the os was loading (think you can skip this)
-Back to custom recovery -> flash darktremor 2.7.5.3 Beta 04 reboot (realy took long 5min+ to load)
Tryd this a couple of times ( hence the many reboots to check if everything was ok) at the end didnt manage to make it boot with darktremor's 2.7.5.2-1 had to go with the relative new beta.
just my 2cents
Yes it works fine - with Advanced Restore
Hello,
To Switch ROMS
I have tried this twice - 1st do a nandroid backup
Wipe data/ Factory reset/ wipe cahe/ Dalvik Cache
Flash new ROM - Reboot for assurance really
Advanced Restore/choose backup/ restore data then restore cache/ reboot X 2
I find this easier than Ti Backup/ and more comprehensive.
I do not recommend ROM Manager for anything other than flashing recoveries
Thanks for reading this far
MAJOR UPDATE 2/22/12: While the process hasn't changed too much, the key files have all been replaced for greater flexibility, and they are NOT compatible with the old method using rookie1's prep-dualboot zip. See this post for an update path from the old method to the current one.
This guide details how to repartition your internal storage and install two operating systems, or ROMs, side by side. If you're looking for a SD install that leaves the Nook's main storage untouched, you're in the wrong place (see my sig).
This guide takes advantage of the multiboot functionality built-in to CM7.1 nightlies since about #140. As such, it is not compatible with CM7.0.x builds or with earlier boot menus.
What you'll get: Whatever two ROMs you install, each will have a nearly 2GB /data partition for apps and they will share a nearly 2GB /media partition for storage, and both will have access to the SD card for more storage. At startup you will see either a small green bar labeled "CyanogenMod," or the word "cyanoboot" in blue. Both boot menus work the same:
Do nothing, and your primary system will boot
Hold down both volume buttons, and your alternate system will boot
Hold down 'n' for a more detailed boot menu
Hold 'n'+power and recovery will boot (if you installed CWM internally).
All of these actions must be taken in the first couple seconds, before a "loading" message appears below the logo. Once you see a confirmation message, you can release all buttons.
DISCLAIMER: As usual, YOU are responsible for changes YOU make to YOUR device. This process is intermediate difficulty level. It probably shouldn't be the first thing you've ever done with ClockworkMod Recovery, and you probably shouldn't just follow the steps if you don't understand them. If you don't know how your NC is currently partitioned, turn back now. If you want to preserve your warranty, turn back now. Here be serpents; be so warned.
Following the guide as-is with all default options gets you a stock 1.4.1* install on secondary and a CM7 install on primary. I hope you can figure out what to substitute where for different results.
*I don't have access to a CWM-flashable 1.4.2 zip right now, but there are instructions for making one here.
The Guide
Prerequisites:
CWM on either SD or internal recovery (internal recommended)
Wi-Fi access
Materials:
repartitionDual2GBdata
BNpri2alt
reformatData
1.4.1-keep-CWM (IF you're not starting with an up-to-date stock install)
CM7.1+ OR MiRaGe's CM7.2 OR unofficial CM9 nightlies (w/ compatible gapps)
CM7 gapps(look near the bottom of the page)
Steps:
Put all materials in your SD card's root directory (DO NOT UNZIP).
Boot into CWM.
From CWM main menu, "backup and restore" and "backup."
From CWM main menu, "install zip from sdcard," and "choose zip from sdcard."
Choose the repartitionDual2GB file.
Reboot recovery. If you have internal CWM and no boot menu, you may need to use the rhythm method:
verygreen said:
hold nook N key and then press and hold power until the {first} message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the {first} message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long
Click to expand...
Click to collapse
Repeat step 4 and choose reformatData
If your backup in step 3 was stock, you can "backup and restore" then "restore" and skip to step 13.
Otherwise, repeat step 4 and choose 1.4.1-keep-CWM.
When it finishes, hold the power button to shut down, remove your CWM card (if applicable), and power back on.
Complete B&N registration process¹
Power off and boot back into CWM (may require rhythm method above).
Repeat step 4 and choose BNpri2alt.
From CWM main menu, in "mounts and storage," format system, data, and cache.
From CWM main menu, choose "Advanced" and "Wipe dalvik cache."
Repeat step 4 and choose CM7 update zip.²
Reboot into main partition and set up Wi-Fi.
Reboot into alt partition (hit both volume buttons at once on "CyanogenMod" loading screen) to make sure it's working.
optional: install gapps, keysmod, etc from CWM.
¹Any mods you want to make to stock, do it now: update to a newer version, root with Manual Nooter (if rooting 1.4.x firmware, follow the linked instructions but use MN 5.12.20), flash keysmod, overclock kernels, or anything else CWM-flashable.
²If you backed up an existing CM7/9 install in step 3, then after step 16 just install gapps, install keysmod if you want it, then from CWM's main menu, Backup & restore > Advanced Restore, and restore data only from your most recent backup. When you boot into CM7 (not tested with CM9), it will be just like you left it.³
³Steps 17 and 18 may look unnecessary, but several users experienced force closes in their CM7 installs when they didn't take these steps.
Other Resources:
CMpri2alt: Moves a CyanogenMod install from the primary partition set to the alternate partition set
BNalt2pri: Moves a stock install from the alternate partition set to the primary partition set
CMalt2pri: Moves a CyanogenMod install from the alternate partition set to the primary partition set
Revert dual boot: deletes the alternate partition set and alternate boot files. Does not restore stock partition sizes, but must be run prior to partitioning back to stock.
1.4.1 full restore: removes CWM from internal recovery, does not affect partitioning
1.4.1-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Steps to back up and/or update both partitions
Instructions to rename boot files created with j4mm3r's old multiboot
Possible fix for rooted stock boot-looping at 'n' screen on secondary
Credits:
repartitionDual2GB and reformatData provided by DeanGibson
1.4.1 zips provided by rajendra82
possible boot-loop fix provided by sryan1983
BNpri2alt, BNalt2pri, CMpri2alt and CMalt2pri are minor alterations of DeanGibson's files
revert-dualboot is a minor alteration of rookie1's remove-dualboot
Racks11479 provided key info for the above alterations
________________________________________________________
Old Resources (Do Not Use with Current Method):
prep-dualboot
froyo-to-dualboot
Remove dual boot: returns partitioning altered with prep-dualboot to stock (1GB/5GB, non-blue-dot)
1.2 full restore: removes CWM from internal recovery, does not affect partitioning
1.3-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Video documenting setup for a CM9 (Ice Cream Sandwich Alpha) dual boot with Nook Color stock 1.4.1
Old Credits:
1.2 full restore provided by nemith: thank here
prep dual boot and remove dual boot by rookie1: thank here
froyo-to-dualboot from jasoraso: thank here
1.4-to-alt from jasoraso: thank here
You can thank me with the button below, or if you feel real strongly about it, you can make a donation at my blog.
UPDATE 5/25/12: Removed the prerequisite for 1GB/5GB partitioning. A little bird named jicama confirmed that the newer partitioning script doesn't care if you start with a blue dot NC. Prep-dualboot would carve the alt partitions out of /media, which doesn't work if /media's not big enough. RepartitionDual just deletes the last three partitions (/system, /data and /media) and makes new partitions from the now-unallocated space, so as long as you have the right number of partitions, it doesn't matter how big they are.
Added to my Subscribed list !! ...Thank you
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
oppy said:
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
Click to expand...
Click to collapse
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7? Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Taosaur said:
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7?
Click to expand...
Click to collapse
Yes.
Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Click to expand...
Click to collapse
Okay, I'll do that and post results. Thanks.
EDIT: Looks like that did it. Seems to work fine, other than some app FCs, which, from what I've read, are fairly common. Thanks for the assist!
I worked that info into the OP. I've done this process twice now without taking those steps and without getting FCs, but you're not the first to report them.
I was a bit confused about the backup and restore part also. Seeing as my Nook was stock to start, I probably didn't need to do that step, and might have actually caused a problem or two by restoring data that didn't exist to start.
Still working great. The only FCs I've had so far were while trying to run Facebook.
Excellent guide! Thanks for all the work on this, it works great.
This is an awesome guide. Thanks for the help. I've been wanting to do this for a while.
Thanks man.
I appreciate you putting all the tools in one place, and I especially appreciate you posting that us blue dot people needed to repartition to 1gb data before doing this; I should've figured that, but I didn't for some reason.
Moving 1.3 to the dual boot partition as I type
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
SCrid2000 said:
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
Click to expand...
Click to collapse
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Taosaur said:
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Click to expand...
Click to collapse
Thanks man. That's what I figured.
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
This is the best thing EVER. I got sick of the nook app on my CM7 build, so this worked flawlessly.
I am running the CM7.1.0 RC1 build, and everything runs smooth as silk
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3. You would have to use j4mm3r's multiboot and the matching stock-to-secondary file found in this thread: http://forum.xda-developers.com/showthread.php?t=1156909
Nevermind, dumb question.
Updated with a link to CM7.1 stable
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
TomMelee said:
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
Click to expand...
Click to collapse
I'll just leave these here:
Taosaur said:
this guide is not compatible with CM 7.0.x sta(b)le releases, nor branch ROMs based on those builds
Click to expand...
Click to collapse
Taosaur said:
Phiremod 7+
Click to expand...
Click to collapse
Taosaur said:
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3.
Click to expand...
Click to collapse
Try installing regular CM 7.1.
rabi347 said:
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
Click to expand...
Click to collapse
Sounds like you got close. I would say start over at step 5.
Howdy All !
I have the Classicnerd ICS v3 ROM installed on my TP, would like to switch to CM A2 ROM to check out their HD video stuff along with netflix. So what do i need to do. Can someone put some steps for newb's like me on how to switch back n forth between these lovely pieces of work.
Thanks
ncube2 said:
Howdy All !
I have the Classicnerd ICS v3 ROM installed on my TP, would like to switch to CM A2 ROM to check out their HD video stuff along with netflix. So what do i need to do. Can someone put some steps for newb's like me on how to switch back n forth between these lovely pieces of work.
Thanks
Click to expand...
Click to collapse
I don't think you can simply switch but you can experiment fairly easily using Nandroid backups
1) ReBoot into recovery
2) Backup current ROM (e.g. CN)
3) Install CM A2
a) format system, cache, wipe Dalvik
b) Flash new ROM (e.g. alpha2)
c) Flash Gapps
4) Reboot system and set up Alpha2, your apps and basic set up should still be OK from CN
5) Reboot into recovery again
6) Backup new ROM (e.g. alpha2)
To switch between then reboot to recovery and Restore chosen ROM and reboot. Note that will fully restore so any updates to data partition e.g. new apps downloaded will get lost unless you take a new back up.
The other things to consider is the space in the boot partition and the moboot default. There should be enough space in boot to accomodate both the uImage files but if not then you need to clean out the CN one before making the alpha2 install. A CN install will have created a moboot.default to try to start CN. An Alpha2 install will not touch moboot.default. If you leave it on alpha2 and want it to default boot into that then you will need to create a new moboot.default file.
hi,
this ROM works very nice for me, thanks all the deveopers!
i have few questions:
(1) since this ROM has OTA updater (it seems, from the changelog), next time when the new version is realeased, can i just update the ROM via OTA updater?
(2) i dont really understand what “Wipe cache/dalvik” and “Wipe data / factory reset” really do. my guess is that “Wipe data / factory reset” repartitions the internal flash memory of the original memory, so we can use all the memory for our purpose. (not like original Nook Tablet, in which they dedicate only 1GB for personal usage)
if i understand all these correctly, this means next time if i flash the new ROM and want to keep the old data, i should not do "Wipe data / factory reset", but only need to do "Wipe cache/dalvik"? is this correct?
thanks so much,
Jun
junkoi said:
hi,
this ROM works very nice for me, thanks all the deveopers!
i have few questions:
(1) since this ROM has OTA updater (it seems, from the changelog), next time when the new version is realeased, can i just update the ROM via OTA updater?
(2) i dont really understand what “Wipe cache/dalvik” and “Wipe data / factory reset” really do. my guess is that “Wipe data / factory reset” repartitions the internal flash memory of the original memory, so we can use all the memory for our purpose. (not like original Nook Tablet, in which they dedicate only 1GB for personal usage)
if i understand all these correctly, this means next time if i flash the new ROM and want to keep the old data, i should not do "Wipe data / factory reset", but only need to do "Wipe cache/dalvik"? is this correct?
thanks so much,
Jun
Click to expand...
Click to collapse
Wipe data/factory reset is an option in CWM Recovery. Really all it does (from the screen messages) is format both /data and /cache.
Assuming you have CWM Recovery (though I imagine that there are similar entries in TWRP, I've just never used it), to wipe both of the caches you will first need to go to the entry "Wipe Cache Partition", which I believe is directly below Wipe Data/Factory Reset. Do that 3x (that's always been the recommendation, anyway) then go to Advanced and click on Wipe Dalvik Cache (again, 3x).
Again, assuming CWM Recovery, when you're in the recovery Vol Up/Down goes up and down in the list, the 'n' key is for Enter, and the Pwr button goes back.
I don't know about the OTA Updater. I always download and install ROMs (on both my phone and my NT) via Recovery.
Since this is a CM10 based rom you probably don't want to do the ota updater since that is a Cyanogenmod feature. This rom is optimized for the Nook from the CM10 Source I would presume. I personally tried the ota uldater since i get the notifications all the time but i get an error message something like "can't verify the source with a string of numbers". Stick to the recovery based flash installation.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 10:48 AM ---------- Previous post was at 10:10 AM ----------
I agree with liquidzoo that you should probably do the wipe cache, wipe dalvik cache and factory reset 3times seems like overkill but you can never be too safe. Also i use twrp recovery and click the system button and wipe system a few times as well.
Sent from my SPH-L710 using xda app-developers app
kobhomye said:
I agree with liquidzoo that you should probably do the wipe cache, wipe dalvik cache and factory reset 3times seems like overkill but you can never be too safe. Also i use twrp recovery and click the system button and wipe system a few times as well.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I wipe /system 3x as well (under Mounts in CWM Recovery) when I'm installing a new ROM.
liquidzoo said:
I wipe /system 3x as well (under Mounts in CWM Recovery) when I'm installing a new ROM.
Click to expand...
Click to collapse
I'm not picking on you personally, but deleting and/or wiping partitions (in the case of /system) or directories (dalvik-cache) three times as opposed to once is completely unnecessary. You'll gain nothing by running the command three times over running it once, assuming you received no errors the first time.
When wiping the dalvik cache, both CM recovery and TWRP perform an "rm -rf /data/dalvik-cache" command using the shell. It's not Windows, and is unlikely to fail when passed the "-f (force)" option along with the "-r (recursive)" option.
In the case of wiping the /system partition, again both CM and TWRP write out zeros to clear the data on the partition. I would be suprised if CWM acted differently from CM and TWRP when wiping dalvik-cache and /system.
The only reason I bothered to look into what these commands actually do is to prevent a user from thinking there's a corellation between a failure to wipe 3x versus a problem they're having. If a 3x wipe "fixes" something for you, whatever the problem was, it's very unlikely that the second or third wipe was what fixed it but instead it was more likely a result of a clean install of the ROM.
References from source:
TWRP Wipe Dalvik - https://github.com/TeamWin/Team-Win...548de276b62c0e9af8661e/extra-functions.c#L986
TWRP Wipe/Format System - https://github.com/TeamWin/Team-Win...8de276b62c0e9af8661e/mtdutils/mtdutils.c#L498
CM Wipe Dalvik - https://github.com/CyanogenMod/andr...aa7ff3d06d5dd115b16c/extendedcommands.c#L1292
CM Wipe/Format System - https://github.com/CyanogenMod/andr...aa7ff3d06d5dd115b16c/mtdutils/mtdutils.c#L498
Have fun modding!
No worries, it's just something I've always done as it's been recommended to me in the past (there are some ROM developers that recommend 5x, actually). I'm not saying that 3x over 1x is any better, but I've never had issues. YMMV, but it doesn't take much more time and I like being thorough.
liquidzoo said:
Wipe data/factory reset is an option in CWM Recovery. Really all it does (from the screen messages) is format both /data and /cache.
Assuming you have CWM Recovery (though I imagine that there are similar entries in TWRP, I've just never used it), to wipe both of the caches you will first need to go to the entry "Wipe Cache Partition", which I believe is directly below Wipe Data/Factory Reset. Do that 3x (that's always been the recommendation, anyway) then go to Advanced and click on Wipe Dalvik Cache (again, 3x).
Click to expand...
Click to collapse
sorry, but can you confirm that when i upgrade to the new ROM (from the same author), it is really necessary to Wipe cache &Dalvik cache?
i am confused because somebody told me that i can just flash the ROM by installing the ZIP file (containing the ROM), and reboot the Nook without having to wipe or clean anything.
thanks,
JK
Flashing a ROM
junkoi said:
sorry, but can you confirm that when i upgrade to the new ROM (from the same author), it is really necessary to Wipe cache &Dalvik cache?
i am confused because somebody told me that i can just flash the ROM by installing the ZIP file (containing the ROM), and reboot the Nook without having to wipe or clean anything.
thanks,
JK
Click to expand...
Click to collapse
I don't know if I am doing it right or wrong but I have flashed numerous ROMs and lately have flashed every version of SGT7+CM10+Cherry Picks,By meghd00t. from 24/09 thru my current installation of 08/10 with only one glitch and that was when I flashed enhancements v2 on top of v1.
I have never had any other issues with the above mentioned ROMs except when I flashed 04/10 with enhancement v2. I didn't have the tablet option.
The way I do it is as follows:
1. format /system
2. format /data
3. Flash ROM
4. Flash CWM emmc
5. Flash GAPPs
6. Reset Factory/format data
7. Remove CWM SD card put in data SD Card with Flash Player (no longer avail on Google Play)
8. Boot from CWM menu
Takes awhile to boot this first time. When booted up I bypass the setup screens.
9. Manually set up wireless (need to access auth web site at work and need wireless to be working to accomplish that)
10. Browse to a web site and get redirected to auth page.
11. Auth
12. Set up Google account and other settings, especially under Security <Install from other locations>
13. Download apps I want from Google.
At this first boot SD card is not mounted.
14. Shut down and do a cold boot.
Now I can see SD Card.
15. Install Flash Player from External SD Card.
16. Install Crackle from Play Store.
Now I check Pandora for Audio, Crackle for Video, other apps I use, utilities, keyboards, launchers, games, etc.
So far since Version 24/09 everything has worked for me with the two exceptions above, tablet mode with 04/10 with enhancement v2 and when I flashed enhancement v2 over enhancement v1.
I am now running 08/10 and am very happy with the performance, battery drain is more than CM7 but that is to be expected from a fairly new ROM but not so bad that it is unacceptable, to me at least.
I have never had a black screen or arbitrary reboot (knock on wood). However I do turn my tablet off when I am finished using it, so don't know about deep sleep. I'm using OnDemand, and three launchers without one being the default....Apex, Nova and Trebucket.
All I can say is these developers really ROCK, way to go guys!
--------------------------------------------------------------------------------
MojoGB said:
The way I do it is as follows:
1. format /system
2. format /data
3. Flash ROM
4. Flash CWM emmc
5. Flash GAPPs
6. Reset Factory/format data
7. Remove CWM SD card put in data SD Card with Flash Player (no longer avail on Google Play)
8. Boot from CWM menu
Click to expand...
Click to collapse
You don't need to re-flash CWM every time you flash a ROM. Also, it doesn't make sense to me why you would do a factory reset/format after flashing the new ROM, I would think it would be done prior to flashing the ROM but maybe it doesn't make a difference, I don't know.
I've got TWRP installed to the emmc so I just download the new ROM to the SD with GooManager, reboot into recovery, do a backup, factory reset, flash new ROM & GApps and reboot. Only takes a few minutes.
Reflash ROM
LifeWOutMilk said:
You don't need to re-flash CWM every time you flash a ROM. Also, it doesn't make sense to me why you would do a factory reset/format after flashing the new ROM, I would think it would be done prior to flashing the ROM but maybe it doesn't make a difference, I don't know.
I've got TWRP installed to the emmc so I just download the new ROM to the SD with GooManager, reboot into recovery, do a backup, factory reset, flash new ROM & GApps and reboot. Only takes a few minutes.
Click to expand...
Click to collapse
Tried it as you mentioned, doing a factory reset before flashing the ROM and got a black screen and wouldn't boot. May have been a fluke but the way I mentioned above gives me a good image and alway boots. Don't know why, but if it works for me, I will continue to do it this way as long as it works for me. I have flashed numerous other ROMs the same way with good results each time.
junkoi said:
sorry, but can you confirm that when i upgrade to the new ROM (from the same author), it is really necessary to Wipe cache &Dalvik cache?
i am confused because somebody told me that i can just flash the ROM by installing the ZIP file (containing the ROM), and reboot the Nook without having to wipe or clean anything.
thanks,
JK
Click to expand...
Click to collapse
For an update, yes it is recommended to clear both caches. To be clear, this is only for an update. If it is a new ROM, or if the author recommends it, you should also wipe /data and /system first.
You can just flash without clearing them, but you might run into unexpected issues, so it's not recommended.
MojoGB said:
Tried it as you mentioned, doing a factory reset before flashing the ROM and got a black screen and wouldn't boot. May have been a fluke but the way I mentioned above gives me a good image and alway boots. Don't know why, but if it works for me, I will continue to do it this way as long as it works for me. I have flashed numerous other ROMs the same way with good results each time.
Click to expand...
Click to collapse
I get a black screen for a while on first boot too, but it only last a couple minutes at the most and if you shine a bright light at the screen you can see the CM logo spinning. Are you sure it was hung?
Sent from my Barnes & Noble Nook Tablet using xda premium
When you clear the Dalvik cache, it clears out data stored in your applications. When you turn on your Nook after clearing the Dalvik, the first thing it does is it rebuilds the Dalvik cache, that's why it seemed like it hung on startup. I believe the long black screen in the beginning is when it rebuilds Dalvik for core Android apps and then when it says "Optimizing Apps", that's for the rest of your applications. The more apps you have, the longer it will take to build the Dalvik. No need to freak out, just a little patience is all you need. Correct me if I'm wrong, however, as I'm still pretty much a noob at this... :laugh:
Flash a Rom
topdawg7793 said:
When you clear the Dalvik cache, it cleares out data stored in your applications. When you turn on your Nook after clearing the Dalvik, the first thing it does is it rebuilds the Dalvik cache, that's why it seemed like it hung on startup. I believe the long black screen in the beginning is when it rebuilds dalvik for core Android apps and then when it says "Optimizing Apps", that's for the rest of your applications. The more apps you have, the longer it will take to build the dalvik. No need to freak out, just a little patience is all you need. Correct me if I'm wrong, however, as I'm still pretty much a noob at this... :laugh:
Click to expand...
Click to collapse
Well fhe screen was black, no light at all and I waited for over five minutes for the Flash Screen to come up and it never did. Yes I know when you are waiting time drags. But due to the ROMS always taking awhile to boot up the first time I actually pay attention to how long it takes. No more then 2 minutes in my experience. I had to hold the power button in for a long time until it finally booted in B&N Recovery. Used my sequence mentioned in earlier post to flash the ROM again and everything worked as it should, GREAT. The number of APPs shouldn't be an issue as these ROMS only have the very basic apps.
I have read this forum and see the various and asundry errors some are getting, so far I have never gotten a major error, except for when I forgot to do the Wipe Data/Factory Reset after flashing.
I also got the "No Tablet Mode Option" with 04/10 with enhancement v2.
But I consider these minor issues and currently am running 08/10 with no issues, works smoother then any version of Microsoft Windows I have dealt with.
These developers are exceptional.
MojoGB said:
I don't know if I am doing it right or wrong but I have flashed numerous ROMs and lately have flashed every version of SGT7+CM10+Cherry Picks,By meghd00t. from 24/09 thru my current installation of 08/10 with only one glitch and that was when I flashed enhancements v2 on top of v1.
I have never had any other issues with the above mentioned ROMs except when I flashed 04/10 with enhancement v2. I didn't have the tablet option.
The way I do it is as follows:
1. format /system
2. format /data
3. Flash ROM
4. Flash CWM emmc
5. Flash GAPPs
6. Reset Factory/format data
7. Remove CWM SD card put in data SD Card with Flash Player (no longer avail on Google Play)
8. Boot from CWM menu
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
oh, so you always reset factory every time you upgrade the ROM? that way will delete all the old data/apps you installed, so you need to install all the apps again?
this is my concern, because i dont want to reinstall apps, or lose my data. so i think i just need flash the new ROM, then Wipe cache/Dalvik cache, and hopefully all the old apps and data are still intact.
thanks.
MojoGB said:
I don't know if I am doing it right or wrong but I have flashed numerous ROMs and lately have flashed every version of SGT7+CM10+Cherry Picks,By meghd00t. from 24/09 thru my current installation of 08/10 with only one glitch and that was when I flashed enhancements v2 on top of v1.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
i have some questions on the "Enhancements":
(1) the correct way to install them is to flash version 1 first, then immediately flash version 2 right after version 1 (without having to reboot first)?
(2) i am not sure what i will get with this "enhancements". they will make video/audio playing more smoothly? is the quality improvement really noticable? anything else, like they make the battery last longer, for example?
thanks,
Jun
If you're running 08/10, the enhancements are not needed. That's my understanding at least. I had problems with V2 so I decided to not install them while on 04/10.
Sent from my Barnes & Noble Nook Tablet using xda premium
Flash Rom
junkoi said:
i have some questions on the "Enhancements":
(1) the correct way to install them is to flash version 1 first, then immediately flash version 2 right after version 1 (without having to reboot first)?
(2) i am not sure what i will get with this "enhancements". they will make video/audio playing more smoothly? is the quality improvement really noticable? anything else, like they make the battery last longer, for example?
thanks,
Jun
Click to expand...
Click to collapse
If you flash enhancement v2 on top of version 1 you will have problems, UI will stop. If you only flash v2 you will not have the Tablet Mode Option. So my understanding is that you can use either v1 or v2 but not both.
ROM 08/10 does not need either enhancement as indicated by the developer. ROM 08/10 works great by itself is my experience.
If I'm installing a ROM, backup the existing ROM and wipe everything.
If I'm installing a .zip package like GApps or an enhancement, backup the existing ROM, wipe Data/Dalvik.
Folks, these are development ROMS. Thar be bugs in thet thar code. It's going to take you longer than the time you think you're going to save by doing a dirty flash, and then having to restore the thing to stock (worse case) only to start all over.
Don't ask how I know.
wellersl said:
If I'm installing a ROM, backup the existing ROM and wipe everything.
Click to expand...
Click to collapse
so it is possible to back up the existing data/apps, then restore them back after the new ROM is flashed? could you please confirm this?
if so, how & what is the right steps to do the backup? can we still use CWM, or use ROM Manager, or other tools?
thanks