Related
It seems that there are a lot of ROMs out there that are doing some funky stuff from the edify scripting in CWM and providing a poor user experience. This overall hurts the entire custom NookColor community and puts a bad taste in peoples mouths.
This post is to point out best practices when creating CWM flashable zips in a consistant way allowing the user to upgrade and migrate between roms in a predictable way.
Rule #1: Don't touch /data!
There are many reasons why you don't want to touch /data but the most important is to allow the user to be able to upgrade your rom without completely wiping your data.
If you want to bundle in an applications (first of all... don't but if you reaally think it is necessary) put it in /system/app as a system app.
Rule #2: Don't overwrite /boot/uRecRam and /boot/uRecImg!
ROM and CWM should be separate. Users should be able to use your rom with CWM or even the stock recovery if they wish to. Allow the user to choose what version of CWM they want to run and allow them to upgrade it independently of your rom.
This allows you to not re-release roms every time a new version of CWM is released.
Exceptions to the rule are update zip that are intended to install CWM (which is ok) or zips that will restore the entire system to stock.
Rule #3 Learn edify
Edify scripting is quite powerful. It saddens me to open up the updater-script of a rom and see it extracting a script and then executing the script.
Don't store your roms as .tars and require a script to extract them to the right locations, you should be doing this all from edify scripts.
Rule #4: Only touch /system and /boot/uImage and /boot/uRamdisk
All other files should be off-limit! This goes back to rule #1 and rule #2. A rom should consits of a kernel, a ramdisk to boot the system and /system files for running the rom!
Rule #5: NEVER EVER EVER modify partitions or wipe the EMMC completely!
I cannot stress this one enough. Use stock partition scheme for your rom. It may seem like a "waste" to you but this is what will make all our roms compatible with each other!
Also the Nookcolor stores NVRAM type information on /dev/block/mmcblk0p2 and factory restore information and a backup of p2 on /dev/block/mmcblk0p3.
If you wipe these directories in your update.zip you WILL BRICK THE USERS NC! It may work for you but they can never return to stock. Their serial number and mac addresses will be lost!
Just don't even think about doing anything with the partition map or these partitions!
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
For the users I will list the ROM that are compatible with the list above and list ROMs that don't follow these rules.
ROMs that follow proper packaging
These rom have been built properly according to the rules in the OP. I highly recommend testing any of these out.
Cyanogenmod Nightlies
phiremod nook V5.2
Nookie Froyo 0.6.8
(Utility Update.zip) Nook Color SDcard and emmc swap
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
Avoid this rom if you are new to Android or the NookColor. I would call this rom an "Advanced user" rom and not for new members of the community who are unfamiliar with Android, Linux, or the NookColor
Click to expand...
Click to collapse
HC v4 eMMC 2nd ed. - Flashable ZIP
This rom packaging is the poster child for how to do it wrong. They overwrite your /data for app customization. It uses an external script and tar files for extraction and overwrites all of /boot!
AVOID THIS ROM PACKAGE!
Click to expand...
Click to collapse
This looks very wise and in accord with general programming principles.
In the same area of discussion, can you talk about whether or not to clear cache while doing this same update process.
In fact, some explanation of /cache and Dalvik Cache and Market Cache might help to alleviate confusion, especially in regards to specifically what they are, and when one should clear them.
Sure, a "cache" is a piece of data that is frequently used, and so put in a more accessible place, but in typical confusing fashion, that general term is being used in a specific way in Android.
Thanks !
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
If everyone used CW to right to EMMC, this would be easy. But users like myself are running ROMs from SD and are always looking for a way to easily update and flash mods or ubdate ROMs to SD. Yes I use ADB, and other methods, but often I am traveling and away from my office or studio were my PC's are.
Any ideas on CWM to keep things more unified as the op suggests and be able to write to bootable SD cards?
Thanks for starting the discussion.
12
Good explanation/write-up, nemith. Not being a dev, but a user, it helps me to better understand which ROMs to use on my NC. I really liked HC EMMC, but did not realize that it would make it so I could never return back to stock (losing my S/N and such).
Also concur with ADude about cache....a good explanation would be helpful here. I only clear the cache/Dalvik when installing a new kernel. Not sure if even necessary? And, I clear AFTER installing, not before, so not sure if I am even doing that in the correct order. Setting the record straight would go a long way for us non-devs.
Sorry, one more thing, it would be great to have a consistently updated bootable SD card with latest/greatest of CWR on it. I am still on 3.0.0.6 and I am not sure why??
Thanks!
~ Razir
Could have used this a few months ago.
Thank you.
Nemith, your thread is directed at devs. If you want to make sure people don't flash my HC v4 2nd edition, you might want to invite users to read this as well.
nemith said:
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
I would avoid dual booting roms if you can!
Click to expand...
Click to collapse
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
12paq said:
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
12
Click to expand...
Click to collapse
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
cromanorn said:
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
Click to expand...
Click to collapse
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
nemith said:
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
Click to expand...
Click to collapse
THANKS!!! I had the NC for about 4 days now and would hate to have messed it up in the long run. I have a Droid Incredible that has been flashed more times than I can remember. It would be nice if the warnings were incorporated into the OP of these roms. I read the entire thread before flashing and I may not have flashed if this warning was there. I like having the option of going back to Stock without repercussions.
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
nemith said:
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
Click to expand...
Click to collapse
Yup. That would be very nice.
The Nook having SD boot priority really makes it versatile for testing, and quite recoverable. It also satisfies a unique situation where many users have a family device with Nook magazines and children's books not available on the Nook app, so many like myself are booting experiments and daily runners from SD and keeping the wife happy. LOL.
cromanorn said:
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
Click to expand...
Click to collapse
If you go digging at nookdevs.com and on your own NC you should be able to figure out what is safe and what is not.
nemith said:
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
Click to expand...
Click to collapse
the ironic thing is CM Roms don't fully follow Rule #3 since they have multiple scripts that run inside their packages during rom installation.
I'm not sure you are correct in saying that if you flash one of the HC emmc roms you can not revert back to stock. I know for a fact I have done both the dual boot, and HC emmc roms and reverted back to stock multiple times after doing so
I'm not saying you are wrong but I don't think i did anything to "advanced" to get back.
Quoted:
(I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?)
I had it installed and got back to stock no problem... i'm not sure what he is talking about.... i could be wrong though...
It was dualbooted CM7 and HC
went back to stock, registered with BN and all was well.
nooted it and then install HC on emmc
reverted back to stock to set up the ubuntu on NC
got bored of that and am back on HC on emmc
I went back to stock after both as well. Has anyone not been able to after using one of those two roms? I work at b&n and I had to spend time with the stock since they wanted me on the nook counter. I've been back and forth between all the roms more times then I can count.
Sent from my NookColor using Tapatalk
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
[Edit] It was the SD card's fault. It seemingly worked fine in the laptop and it mounted fine in CW Recovery, but as soon as I used a different SD card I could flash zips again.
So, now I'm playing with phiremod v6 and loving the Nook again.
I believe I just bricked my Nook through use of the dual boot script.
I can only boot from SD into CW but not a single zip can be applied to the internal storage. Not even the "reverse dual boot" zip will run. They all error out.
I believe this is due to unexpected partitioning.
I even formatted boot, system and cache and still it will not restore any Roms.
So now I'm hoping to access the Nook through USB and repartition the internal storage manually. But before I do that, I need to learn about ADB and what the correct settings are.
jlt220 said:
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
Click to expand...
Click to collapse
I don't think Nemith was saying that the existing dual boot installer is going to prevent you from returning to stock. He singled it out as a "ROM" that modifies the partition table, which can be a dangerous thing to do. There is information stored in the /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3 partitions that is specific to each device and required by the B&N software. This information can't be rebuilt easily if lost.
The dual boot install and removal tools (in their current versions) appear to leave these partitions in tact. They are modifying the partition table though, so they're not recommended for novice users. You were able to install and uninstall it with no problems, so you're clearly not one .
The other point is that future versions of the dual boot (doubtful since it has a good dev) or other similar style "ROMs" may not be so careful with your 0p2 and 0p3 partitions.
I'm sorry if this info is already posted, I found similar info in my searches but not exactly what I'm looking for.
I just bought a G and its coming tomorrow. I plan to install clockwork and try out some ROMs (probably VEGAN first). I've seen a lot of information that partitioning the internal memory to 2048/0 is a good idea, but that it will wipe out the internal memory. My questions:
1) Is this accurate? Should I do this before installing custom ROMs?
2) When people say it wipes out EVERYTHING, does that mean the stock OS is gone at that point? Will I still be able to boot into Clockwork at that point to install a ROM?
3) Is it possible / what is the best way to backup the internal memory prior to doing this? Or should I not even worry about that as I will be installing a custom ROM after anyways. EDIT: I should say I'm semi-familiar with clockword with my Droid, I know you can do backups via clockword, is doing a clockwork backup prior to partitioning going to get everything I need in case I brick it? This one may have answered itself hehe.
Thanks!
mattbooty said:
I'm sorry if this info is already posted, I found similar info in my searches but not exactly what I'm looking for.
I just bought a G and its coming tomorrow. I plan to install clockwork and try out some ROMs (probably VEGAN first). I've seen a lot of information that partitioning the internal memory to 2048/0 is a good idea, but that it will wipe out the internal memory. My questions:
1) Is this accurate? Should I do this before installing custom ROMs?
2) When people say it wipes out EVERYTHING, does that mean the stock OS is gone at that point? Will I still be able to boot into Clockwork at that point to install a ROM?
3) Is it possible / what is the best way to backup the internal memory prior to doing this? Or should I not even worry about that as I will be installing a custom ROM after anyways. EDIT: I should say I'm semi-familiar with clockword with my Droid, I know you can do backups via clockword, is doing a clockwork backup prior to partitioning going to get everything I need in case I brick it? This one may have answered itself hehe.
Thanks!
Click to expand...
Click to collapse
1- You can use my batch file to backup an image of your tablet, this is not for day to day restore but it may be useful one day...
2- Yes and possibly more...
3- NVFLASH BACKUP then FULL CLOCKWORK Backup
4- then do whatever your are covered...
http://forum.xda-developers.com/showthread.php?p=12434269#post12434269
Ok, so first thing after I get the G Tab, is install nvflash on my PC, hook up via USB and run your batch file? Should I do this before or after installing clockwork? Do I turn the g Tab on after plugging in the USB?
I really appreciate your help.
Partitioning 2048/0 from CWM recovery doesn't wipe the ROM space. I have booted into the tablet right after doing this and nothing else, so clearly it still has the OS. It just wipes /SDCARD (the built in memory).
mattbooty said:
Ok, so first thing after I get the G Tab, is install nvflash on my PC, hook up via USB and run your batch file? Should I do this before or after installing clockwork? Do I turn the g Tab on after plugging in the USB?
I really appreciate your help.
Click to expand...
Click to collapse
Read the batch remark, it explain, but yes you install the APX drivers, then plug usb, power on with volume - and run the batch files.
Ramerco is also right when he say partition of the 2048GB only erase the 2G/16G part
but it's still a good idea to keep a full image from the early tablet, there's a NVFLASH recovery from bekit availlable as well
Also there's a shell script called inandop.sh that is taking care of this if there's no sdcard it will create it...
Thanks again guys!
I was wondering if anyone could point me in the right direction for moving apps to my sd card. I'm currently rooted but on the stock 2.1. Have done some searching but haven't had much luck. I'm a newbie and haven't jumped in to the rom realm yet. Guess, I don't want to run the risk of screwing anything up. Any help would be greatly appreciated!
mattamous said:
I was wondering if anyone could point me in the right direction for moving apps to my sd card. I'm currently rooted but on the stock 2.1. Have done some searching but haven't had much luck. I'm a newbie and haven't jumped in to the rom realm yet. Guess, I don't want to run the risk of screwing anything up. Any help would be greatly appreciated!
Click to expand...
Click to collapse
It would probably be easiest to flash [ROM][GPL][3/15/2011] xtrSENSE5.0.1 [cache2cache,apps2sd,oc,jit]-HTC Sense. It is extremely close to stock but has all the advantages including having Apps2SD built in. You can read zach.xtr's instructions for using Apps2SD under AndroidOS 2.1 in that first post in a section that's titled "Apps2sd and Cache2sd:".
roirraW "edor" ehT said:
It would probably be easiest to flash [ROM][GPL][3/15/2011] xtrSENSE5.0.1 [cache2cache,apps2sd,oc,jit]-HTC Sense. It is extremely close to stock but has all the advantages including having Apps2SD built in. You can read zach.xtr's instructions for using Apps2SD under AndroidOS 2.1 in that first post in a section that's titled "Apps2sd and Cache2sd:".
Click to expand...
Click to collapse
Are you currently running this rom? If so, have you come across an problems with it yet?
mattamous said:
Are you currently running this rom? If so, have you come across an problems with it yet?
Click to expand...
Click to collapse
The last version of this I used was v4.6.5, just less than a couple months ago. Before that I had run many versions of it and xtrROM. At the moment I'm using GSB v2.7.
I don't recall any problems with xtrSENSE at all, it's the ROM I recommend the most to people who ask for a recommendation.
roirraW "edor" ehT said:
The last version of this I used was v4.6.5, just less than a couple months ago. Before that I had run many versions of it and xtrROM. At the moment I'm using GSB v2.7.
I don't recall any problems with xtrSENSE at all, it's the ROM I recommend the most to people who ask for a recommendation.
Click to expand...
Click to collapse
I appreciate that. I'll continue to research it and take your recommendation into consideration. Just a little hesitant to roms still but if I want to better my eris, looks like I need to jump the gun a little.
xtrSENSE is a fantastic ROM and I also recommend it to anybody new to rooting, unless they are specific in wanting to get away from Sense at all costs, or needs something like Google Voice Search/Actions (which requires Froyo or better).
I have one issue with xtrSENSE, but it seems to be unique to me: after running the ROM for a while, the phone becomes erratic about reminders for items in my calendar. For example, if I have a meeting at 4:30 pm and have a reminder set to 15 minutes, after running these ROMs (xtrSENSE, xtrROM and stock, actually) for a while, they may or may not sound the reminder at 4:15 pm, as desired. Sometimes they do, often they don't - often, they will fire off at some random time hours later, and even rarely never remind me at all until I restart the phone, and then they all start pouring in.
This was the major reason why I finally rooted a few weeks after 2.1 finally came to the Eris last year.
I have never seen anybody else report this issue with xtrSENSE, though, so I continue to recommend it to others. It's great advantage is that if you have been running stock, it will look and feel just the same, except faster, with better battery life, without the lag that happens with stock as your text message and call log grows.
doogald said:
xtrSENSE is a fantastic ROM and I also recommend it to anybody new to rooting, unless they are specific in wanting to get away from Sense at all costs, or needs something like Google Voice Search/Actions (which requires Froyo or better).
I have one issue with xtrSENSE, but it seems to be unique to me: after running the ROM for a while, the phone becomes erratic about reminders for items in my calendar. For example, if I have a meeting at 4:30 pm and have a reminder set to 15 minutes, after running these ROMs (xtrSENSE, xtrROM and stock, actually) for a while, they may or may not sound the reminder at 4:15 pm, as desired. Sometimes they do, often they don't - often, they will fire off at some random time hours later, and even rarely never remind me at all until I restart the phone, and then they all start pouring in.
This was the major reason why I finally rooted a few weeks after 2.1 finally came to the Eris last year.
I have never seen anybody else report this issue with xtrSENSE, though, so I continue to recommend it to others. It's great advantage is that if you have been running stock, it will look and feel just the same, except faster, with better battery life, without the lag that happens with stock as your text message and call log grows.
Click to expand...
Click to collapse
That's because your Eris runs outside the normal space-time continuum.
So, after looking into both xtrROM and xtrSense, I'm not sure which would be the better idea. I don't have to have sense but both sound like they would be great roms. Also, should I stick with 2.1 or jump higher to 2.2 or even 2.3??
mattamous said:
So, after looking into both xtrROM and xtrSense, I'm not sure which would be the better idea. I don't have to have sense but both sound like they would be great roms. Also, should I stick with 2.1 or jump higher to 2.2 or even 2.3??
Click to expand...
Click to collapse
It would probably be best if you just start flashing some of them to see for yourself. Keep in mind that without the Sense home, the phone will feel a little different, plus not be able to use the Sense widgets. Since you already have experience with Sense, flash xtrROM and see how you like it. Then I would personally just skip right over 2.2 and go to 2.3 since it's essentially fully developed now.
I'm personally using GSB (soon to flash v2.8) and Tazz's Gingerbread ROM get's rave reviews, too.
Try a few ROMs and find out what you like best.
What's the best back up app? Or, with Astro and a nandroid, would that be good enough?
mattamous said:
What's the best back up app? Or, with Astro and a nandroid, would that be good enough?
Click to expand...
Click to collapse
As far as backing up your apps and/or their settings, I swore by My Backup Pro for quite a long time but since going to Gingerbread, I've taken advantage of Titanium Backup's ability to restore apps to where they were backed up from (not applicable to the stock ROM), which is handy for me because using Gingerbread's (or Froyo's) native Apps2SD, I have a total of 190 user and system apps.
I don't know if they've added any feature like that in My Backup. If they have, then it would have been very recently.
mattamous said:
What's the best back up app? Or, with Astro and a nandroid, would that be good enough?
Click to expand...
Click to collapse
Personally, I use cyanogen as my rom and nandroid to backup the phone...you know in case the rom fubars the phone.
Sent from my Eris ADR6200 using XDA App
I use titanium back up and copy my sdcard to my computer before doing a wipe also make a nandroid copy there as well.
I went with My Backup Pro and made a copy of my sd card to my laptop. I was trying this technique last night but it had an error at the end of the command prompt.
http://www.askstudent.com/how-to/resolve-phone-storage-space-is-getting-low-on-android-phones/
mattamous said:
I went with My Backup Pro and made a copy of my sd card to my laptop. I was trying this technique last night but it had an error at the end of the command prompt.
http://www.askstudent.com/how-to/resolve-phone-storage-space-is-getting-low-on-android-phones/
Click to expand...
Click to collapse
I see this at that link:
However, Google listened and with Froyo or Android 2.2 release, they included the App2SD functionality.
Click to expand...
Click to collapse
You said you're on rooted stock, and those instructions are for 2.2+ ROMs only so it won't help you unless you since flashed another ROM. Have you? If so, which one?
Also, those instructions are purely to help move apps which normally wouldn't allow you to move them, which as I might've said Titanium Backup (paid version) will allow you to do by the Batch, and the free "Install Manager" may allow you to do so in batch, too, I've just read.
roirraW "edor" ehT said:
I see this at that link:
You said you're on rooted stock, and those instructions are for 2.2+ ROMs only so it won't help you unless you since flashed another ROM. Have you? If so, which one?
Also, those instructions are purely to help move apps which normally wouldn't allow you to move them, which as I might've said Titanium Backup (paid version) will allow you to do by the Batch, and the free "Install Manager" may allow you to do so in batch, too, I've just read.
Click to expand...
Click to collapse
Somehow, I must have missed that. I haven't flashed anything just yet; I was hoping that would do the trick before I went to flashing a rom. I downloaded the free version of titanium last night but it wouldn't backup, saying that I didn't have busybox. I downloaded busybox afterwards but it had a few warnings right at the beginning that I wasn't sure about so that's why I went with backup pro. I just checked into install manager but it isn't in the market.
With the help you have already given, is there a set of instructions for the nandroid backup process? I'm kinda interested in xtrROM but want to get all my ducks in a row before I flash it. Thanks for the help! Appreciate it!
mattamous said:
Somehow, I must have missed that. I haven't flashed anything just yet; I was hoping that would do the trick before I went to flashing a rom. I downloaded the free version of titanium last night but it wouldn't backup, saying that I didn't have busybox. I downloaded busybox afterwards but it had a few warnings right at the beginning that I wasn't sure about so that's why I went with backup pro. I just checked into install manager but it isn't in the market.
With the help you have already given, is there a set of instructions for the nandroid backup process? I'm kinda interested in xtrROM but want to get all my ducks in a row before I flash it. Thanks for the help! Appreciate it!
Click to expand...
Click to collapse
BusyBox is included with any custom ROM, another reason it's just easier to flash a ROM like xtrSENSE or xtrROM as you mentioned, although with Apps2SD under Android 2.1, you need to backup the entire contents of your SD card, repartition it to include an Ext2 partition and 0 (zero) Swap, and the rest FAT32 as normal. All can be done from Recovery.
What method did you use to root? I'm assuming that whatever method you used installed a custom recovery. To make sure you do have a custom recovery, turn the phone off, press and HOLD the volume up button and press the End button long enough to turn the phone on. Keep holding the volume up button for a few seconds longer. When it goes into recovery if you have Amon RA recovery it should say something like amon-ra-eris-1.6.2 at the bottom.
In Amon RA recovery, reference http://forum.xda-developers.com/showthread.php?t=648025 there are these menu options:
Use the trackball (up+down) to navigate through the menu, press the trackball to select items. Use the Volume-down key to go back to a previous menu.
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore
Nand backup :: Make a Nand backup, the following partitions are NOT included :
Recovery (to avoid restoring old version)
Cache (no need to backup imo)
Misc (no need to backup imo + restore issues on some phones)
Splash1+2 (no need to backup imo + restore issues on some phones)
Nand + ext backup :: Make a Nand + ext backup
Nand restore :: Restore a Nand backup
BART backup :: Make a BART backup (Nand + ext)
BART restore :: Restore latest BART backup
Flash zip from sdcard :: Flash a zip update file from your sdcard
Wipe
Wipe data/factory reset :: Wipe /data and /cache
Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
SD:ext3 to ext4 :: Convert ext3 to ext4
Other
Fix apk uid mismatches :: Does extacly that
Move apps+dalv to SD :: Moves all apps and Dalvik-cache to sdcard (This will NOT enable apps2sd!)
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Click to expand...
Click to collapse
To make a nandroid, just choose the "Backup/Restore" menu with your trackball, then choose "Nand backup".
The Market search is quirky. Here's a link to Install Manager on the market: https://market.android.com/details?id=com.beidl.chooseloc.
Install Manager or anything else having to do with Apps2SD won't do you any good without either flashing the Apps2SD script from recovery, or flashing a custom ROM that includes Apps2SD.
You can find the most important information via links from the Eris Roll-up Thread.
Thank you very much! A huge help! I used the 1 click Eris root.
Flashed xtrROM based on your recommendation and so far its pretty rad. Really smooth and quick too.
im looking for some info working with a droid eris used 1click method to root ive got the 2.2 froshedyo 11 rom the kernel is 2.6.29 DECAFUCTCFS-dirty the person im doing this for really wants the HTC widgets back so im looking and getting a good feel about the xtrsense5.0.1 rom but the only thing im not sure of is wiping sd ext partition is that something i need to do or is that only if im planning on using the app2sd im alil lost about that part and the whole partition process id ask there but not enough posting yet to do so the recovery is the RA-eris-v1.6.2 so there i should b good to go thanks for any and all info out there
THIS UTILITY IS FOR FASCINATE TOUCHWIZ FROYO/GINGERBREAD ONLY
UPDATED FOR EC09 GINGERBREAD
I have created a format utility that can be used from within CWM3 recovery. Just select the ZIP in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
--------
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4, then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
--------
Packages updated: 6/28/2011 - 12:57PM EST
EXT4 Format ALL (formats everything): http://www.mediafire.com/?6hx7f8g7c8vv6xz
EXT4 Format CACHE: http://www.mediafire.com/?2621a888ydv41mg
EXT4 Format DATA: http://www.mediafire.com/?ck2bb340yybpe4z
EXT4 Format DBDATA: http://www.mediafire.com/?ahxzs8xsyyvemed
EXT4 Format FOTA: http://www.mediafire.com/?42ijpi67grdb6mm
EXT4 Format PREINSTALL: http://www.mediafire.com/?d42as1l3pdbhr2t
EXT4 Format SYSTEM: http://www.mediafire.com/?rgs46hhq8qd951t
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
thanks for this
navenedrob said:
I have created two format utilities that can be used from within CWM3 recovery. Just select the type of file system you want to use, select it in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with either RFS or EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4 or RFS (depending on script used), then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
Click to expand...
Click to collapse
Ok, I think I'm having a complete idiot moment here so please be patient with me. What would be the benefits of me running this on my device that is currently running jt's CM7 with OTB 1.5 kernel and EXT4 (voodoo for those who don't know) already converted? Thanks in advance.
It would be of no use. Unless you need to format your entire device.
So this would be a good thing to flash in place of wiping between rom flashes? Does it have any benefits compared to a regular data and cache wipe when you are already converted to ext4?
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
navenedrob said:
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
Click to expand...
Click to collapse
Ok, so basically what you are saying is this would be ideal to use instead of data/cache/dalvik wipe for rfs to rfs and ext4 to ext4, correct? Thanks in advance.
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
navenedrob said:
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
Click to expand...
Click to collapse
Just to let you know, I ran the ext4 package and I got some serious lag issues after I installed my rom and it actually starting going into a soft boot loop. It began to act very weird and unstable. I booted back into recovery and I wiped everything the way I usually do and formatted the system/data/dbdata/cache manually in mounts and storage and reinstalled. It's better than it was but it still seems like it is kinda slower and more laggier than it was before I ran the package. Any ideas? Thanks man.
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
navenedrob said:
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
Click to expand...
Click to collapse
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Not really sure exactly, it actually could have been a few different things causing the "issues". I'm going to try your exact scenario and see what happens.
kidserious said:
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Click to expand...
Click to collapse
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Coreyc1123 said:
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Click to expand...
Click to collapse
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
kidserious said:
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I had these same symptoms one time that I installed kasonate v7, but after reflashing, the next time it didnt.
I know you're not talking about the same cm version, but they might be related and not related to the format utility.
Ok, I ran this package again to make sure that I didn't do something wrong and to see if I would get the same results. I ran the package, flashed cm7 then gapps then OTB GB 1.5. all from the recommended recovery in your post. Again I ended up in a soft boot loop and wifi was acting up again and was causing a boot loop. So once again I booted into recovery and wiped data/cache/dalvik normally and formatted manually via mounts and storage and reinstalled again and she's running like a dream. Very weird but I must say I am very happy with the results I ended up with, regardless of how I got them. So obviously, this was not your intention for it to be done this way but I do see an improvement in responsiveness, speed and memory being freed up. Before, my free internal memory was 1.49 and now it is 1.52. Thank you sir, I appreciate this.
Thanks for this utility! Works great. Went from Jt's cm7 to the miui/touchwiz rom and ran the utility in between. My phone is running faster than ever and no issues. Thanks again!
Sent from my SCH-I500 using XDA App
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You're welcome, the utility enables a few nice options as far as file system performance is concerned, that Voodoo doesn't at this time.
Do tell oh and thanks a million
Sent from my SCH-I500 using XDA App
I am very familiar with the inner workings of CWM on regular phones, but these devices seem a bit different. Will formatting System brick the device by removing CWM from the partiton, or is it the same as a phone where CWM is in the kernel partition in boot? I ask because I have not seen any developers ask to format the system (along with factory reset/data/cache/dalvik) when going from GB to ICS, which on a phone IS the correct way to change operating systems.
Quick answer would be great as I am in flashing mode tonight!
Thanks
annoyingduck said:
I am very familiar with the inner workings of CWM on regular phones, but these devices seem a bit different. Will formatting System brick the device by removing CWM from the partiton, or is it the same as a phone where CWM is in the kernel partition in boot? I ask because I have not seen any developers ask to format the system (along with factory reset/data/cache/dalvik) when going from GB to ICS, which on a phone IS the correct way to change operating systems.
Quick answer would be great as I am in flashing mode tonight!
Thanks
Click to expand...
Click to collapse
It will not remove CWM. Don't forget, CWM is normally either on a separate partition (recovery) or for samsung devices, in the kernel directly, so It will not brick your device, it will just get to either to a infinite bootloop, stuck at samsung logo or reboot to recovery. In the case you should backup using nandroid before use.
That's what I figured, just wanted to be sure. Things are just different on these g-players. I like to use the system format option to get a true "clean" install.
Thanks for the quick response
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
annoyingduck said:
That's what I figured, just wanted to be sure. Things are just different on these g-players. I like to use the system format option to get a true "clean" install.
Thanks for the quick response
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Click to expand...
Click to collapse
Most ROMs format the system while they are installing so you don't always need to do it manually
Sent from my Nexus 7 using XDA Premium HD app