Related
I'm no longer keeping up with NAND on the vogue. So if anyone would like to keep me informed and email me or post me on any changes with NAND, ill be happy to add the news on the first post. The lock up issue with NAND has been fixed!
This is simply for any noobs or others who are having issues with Android and NAND.
IMPORTANT!!!
FOR VOGUE USERS ONLY
I am not responsible for any bricked or messed up devices. By continuing you are agreeing to my simple rule.
MY SIMPLE RULE: I owe you nothing.
I will help you through the way though if you bricked or need any sort of help.
How-to Video up NOW!!!
http://www.youtube.com/watch?v=3gTkJkOc7m4
First off, What is NAND?
To keep it simple...its your phones internal memory. Up untill recently we (Vogue Users) had to run Android off our SD cards using HARET. But thats another story.
What are the benefits of running from NAND? (based on what I have seen)
-Runs faster
-Longer Battery life
-faster boot up
-can be faster to put together.
-Easier to connect your vogue with android to your pc and sync
-Much more convenient.
So how do I start?
STEP1:
The Build
First you need to find a Build that is usable with NAND. Most Hero builds at this moment are not. Here are some links:
Donut 1.6
http://forum.xda-developers.com/showthread.php?t=591104
Hero
http://forum.xda-developers.com/showthread.php?t=603028
Cupcake 1.5
Method 1 from http://forum.xda-developers.com/showthread.php?t=593786
DO NOT DOWNLOAD ANYTHING JUST YET! I WILL TELL YOU WHEN A GOOD TIME WOULD BE
You may want to consider reading the rest...
STEP2:
Base Files (Most builds will supply these)
For all builds (Except the Link in Cupcake "instructions are givin in the download.) you will need a basic set of base files. The link below contains the 3 basic empty files for all builds and Systems.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/Androidstuff.rar
IF
You are using Hero make sure you download hero.user.conf too:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/hero.user.conf
-create a new folder called conf
-and place hero.user.conf in your new folder.
STEP3:
Rootfs
After you have the Base files you will need a rootfs. Depending on your Build, you may need a different type then the one I am going to supply you. Most builds will supply you with one. This one is DZO's rootfs.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/rootfs.img
STEP4:
Prepare
-You need to clean out your storage on your SD. Make sure you delete everything.
-Create a file called android on your desktop.
-Download the base files, unzip, open folder, and place all 3 in your android folder
-Download the rootfs and place them in your android folder. Make sure you either download DZO's or the one your Build provides.
-Download a System.img. When you download a System most likely it will have a different name such as system-hero-123.img. You need to rename it system. So it should look like system.img . Then place it in your android folder.
-If you are using Hero place your conf folder in your android folder.
-Depending on your Build (mostly Hero) you may also need a Data file. The build you select should supply one. Download it and place it in your Android Folder
STEP5
Placing
Open up your android folder of all your collected files and select all, copy, and paste into your empty SD card.
STEP6
Unlocking
If you have never flashed a ROM before than you don't have HardSPL installed. So unlock your phone with...
http://forum.ppcgeeks.com/showthread.php?t=20370
Make sure you follow the forums directions.
STEP7
Method
Method1: The way I do it.
Download ROMUpdateUtility.rar
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/ROMUpdateUtility.rar
Extract to a newfolder
Download a kernel with your screen size
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Don't know your screen size...check this out
http://forum.xda-developers.com/showthread.php?t=544906
After you have have gotten the kernel:
rename it to RUU_signed and place it in the ROMUpdateUtility folder you created.
NOW you need to plug your phone into your computer. Establish active sync. And run ROMUpdateUtility.
-Follow the Instructions on the screen.
Method 2 and 3 can be found here:
http://forum.xda-developers.com/showthread.php?t=593786
This also shows my method...but a little less detail. You can also find many other helpful things there.
If you fail OR think your bricked your phone.
You will need to download one of these depending on your carrier...Make sure you download the shipped gps rom. (If you are Verizon skip down)
http://forum.ppcgeeks.com/showthread.php?p=191607
Than you will put your phone in boot mode. Hold the Camera and Power button. While holding both of them...get a pen or something small and hit the little restart button on the bottom of your phone. You may have to hold it for like a second.
-you will see three color bars on your phone
-plug your phone into your computer
-run the backup
After your phone is all back to normal. Make sure you run internet explore on your phone. It will enable you to get data.
For Verizon follow the instructions here.
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
That is about it. I'm sure I forgot some stuff and will add on to this. Make sure you donate to the Devs for all their hard work.
DZO
http://forum.xda-developers.com/showthread.php?t=593786
jamezelle
http://forum.xda-developers.com/showthread.php?t=603028
plemen
http://forum.xda-developers.com/showthread.php?t=591104
vilord
http://forum.xda-developers.com/showthread.php?t=523692
They deserve it.
thank you this was very helpful
inphin1ty said:
thank you this was very helpful
Click to expand...
Click to collapse
No problem...
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
jamezelle said:
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
Click to expand...
Click to collapse
Whats that?
staud8469 said:
What are the benefits of running from NAND? (based on what I have seen)
1 Runs faster
2 Longer Battery life
3 faster boot up
4 can be faster to put together.
5 Easier to connect your vogue with android to your pc and sync
6 Much more convenient.
Click to expand...
Click to collapse
great thread. I've run both from nand and sdcard. i have not messed with ext2 on the sdcard.
I agree with 3 for sure. I would also add that there is a deep gratification in wiping win mo off the sdcard
6 is debatable, depends on which conveniences you want. changing lcd.density, changing resolution are all much faster running from the sdcard - no flashing or messing with build.prop, just edit default.txt and reboot (aside - if you have a non-sdhc card you can flash on the fly from the sdcard, but changing lcd.density still requires pulling and pushing files from the system, which is not as easy as changing the default.txt). also more convenient to back-up or revert to a data.img when running from sdcard. definitely booting straight into android is convenient, as is the new mass storage on boot method, as well as having a re-writable system (which you also have using ext2).
1 and 2, I honestly have not noted a significant difference in battery life. With a fast sdcard, I don't think there is a significant difference in speed either - dzo has said this in one of the non-vogue forums as well. i have not tried any sense builds from the sdcard though, and that's where you would notice the greatest difference in speed if there is any.
4 I agree with in general.
I think running from the nand is a huge advance, and great for everyone to try. but, running from the sdcard is still a decent way to use android. choosing between the two comes down to choosing which conveniences suit your usage style the most.
One last thing - please add vilord to your donate links (his google ion on vogue thread), he has been instrumental in developing the ril and advancing android on the vogue. srwalter also deserves mention for his reverse engineering of the libgps.so to bring gps first to cupcake and now to donut as well. jamezelle, plemen, mssmison, zenulator, enatefox, f00bar (no specific order) have all worked hard porting roms and working on things like compcache, swap, modem, etc, which has all been invaluable (zenulator and mssmison deserve special credit for spearheading the porting business). however the gruntwork of porting to the vogue has been done mainly by dzo who brought us the kernel and initial ril and now nand (he's just frickin amazing, he singlehandedly got the first functioning port to the vogue and others helped from there), then vilord who took the ril and really refined it. I guess suffice to say, there have been a lot of people involved along the way, thanks to all of them.
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Barogi44 said:
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Click to expand...
Click to collapse
When do you get this error? During linux kernel bootup?
Verizon users.
I just update a fix for Verizon users. Shows you how to get GPS too!
Also...there will be a video up soon. It seems that there are so many people having issues. So I will create a video from start to finish. Will be posted up late tonight/ tomorrow morning.
staud8469 said:
When do you get this error? During linux kernel bootup?
Click to expand...
Click to collapse
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Barogi44 said:
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Click to expand...
Click to collapse
i running with a 8gig PNY sdcard
it could theoretically run off of a 512, but you would be a little cramped on space
i guess android doesnt like some of them
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Barogi44 said:
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Click to expand...
Click to collapse
short answer, yes.
Hey guys...I will try my best to get that video up today. I am about to start recording it.
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
stopthebus said:
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
Click to expand...
Click to collapse
Yes that is correct, as for deleting the files...I would assume you could. But im not sure. Maybe they are still needed on boot. Never hurts to try though.
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
gigermunit said:
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
Click to expand...
Click to collapse
Wait...NVM you want data to work right?
If you are using donut...try to restart your phone one time. After it boots back up you should see a 3g symbol appear on the notification bar.
If that does not work...go to your apps and open modem. Click once on disconnect and then once more. Then click connect.
Tell me if that works...
HTC Legend build for the Vogue
As always, I take no responsibility for what this may or may not do to your phone. Do it at your own risk. This Build Overclocks your phone to 500, we've found that to be the fastest and most stable, however it may overheat and kill your cpu.
INSTRUCTIONS- YOU MUST FOLLOW!
Start by installing the androidinstall.tar to your sd or img file, (not nand)
Boot and wait a long time, there is no boot animation at all so the screen is blank., go through the setup.
After you've gotten rosie to load the first time, reboot and install the update.tar
This is going to set your lowmemoryparameters (androids build in taskkilller) to some very aggressive settings, as well it overclocks to 500. (I don't love it but it's the only way to run this rom nicely). Also the userinit sets compache with 96MB.
On reboot the phone/ril seems to be the last thing to kick in. (that or it just takes the png a bit to update) Don't worry about it, just be patient and it will enable your radio and connect.
For best results
Use system on sdcard partition, data on nand put a swap parition on your sdcard and edit the userinit.conf to use the swap parition as backing for compache. (this is how I'm running this build and it's good)
What doesn't work;
Bluetooth
Camera
What's cool;
The friend feed is actually cool
Hold the camera button for 2 seconds to view all the rosie screens.
Youtube works
Try something in flash, some works, some doesn't..
Notes
I don't expect to put alot of time into updating and tweaking this build as it is not my primary build that I work with. It is very hard to make 200MB nandable, but I may work on it in the future.
Tweaking;
If you want to play with the memory settings or the overclock just adjust the /system/bin/clock.sh or the /system/sysinit in the androidupdate.tar and re update.
Put your system on SDCARD partition, but put your data on nand. There's definitly a performance increase there.
New Version 03-20
Added LWP if using non rosie launcher
More speed tweaks.
Added HelixLauncher as a good alternative to rosie, to use clear defaults in settings -> manage applications -> HTC Sense. Than hold the cam button for 2 seconds to select different home app.
Next version
More space on /data
More speed tweaks
VogueSense Parts app
DOWNLOAD Works on Nand and Regular
https://sourceforge.net/projects/androidhtc/files/2010-03-20/legendnand.rar/download
Downloading! (37mn left ><)
Thank you for giving us an alternative to "standard" Eclair builds
Kiiv said:
Downloading! (37mn left ><)
Thank you for giving us an alternative to "standard" Eclair builds
Click to expand...
Click to collapse
a.) slow internet?
b.) need to use a different sourceforge mirror (cause I get 1MB/sec on sourceforge)?
mssmison said:
a.) slow internet?
b.) need to use a different sourceforge mirror (cause I get 1MB/sec on sourceforge)?
Click to expand...
Click to collapse
a.) slow internet
I have Darch's Legend on my Hero and LOVE it. Im tryin this on my son's vouge now!
edit...does it have the cool weather home screen animations?
Yes it does!!
Ahh ive recently switched back to windows mobile for speed and stability reasons..
but your builds and your reputation is the driving force for me to try this one.
Ill chime in on what i think.
screenshots?
It looks a little better than every other legend build.. lol seriously just google htc legend it looks the same as whatever pics and videos you'll see Except of course it's that tiny tiny bit blurry that everyone complains about with 320x480 on the vogue
k I've got a build done that should be fully nandable. but to be completely honest I don't really feel like wiping/testing today. I'll give it a shot this weekend and post if it works.
Otherwise the next update will include the ability to use livewallpapers (if your using a launcher other than rosie). and some other speed tweaks.
This is a nice build to play with it has the apps i need in the market I hope somebody can help speed it up
nand added.
Read first post.
is it possible to use it on polaris? not sure if the overclocking would suit the polaris
iseeka said:
is it possible to use it on polaris? not sure if the overclocking would suit the polaris
Click to expand...
Click to collapse
yeah sure, just open the update tar and in /system/bin delete the clock.sh file.
I haven't tried to put in wifi yet though
mssmison said:
HTC Legend build for the Vogue
For best results
Use system on sdcard partition, data on nand put a swap parition on your sdcard and edit the userinit.conf to use the swap parition as backing for compache. (this is how I'm running this build and it's good)
Click to expand...
Click to collapse
I would like to run this from ext2 partitions with Haret. Could someone please describe what partitions I should put on my sd card? (I know HOW to partition, just need some guidance as to sizes needed, especially if putting on a Linux swap.) Also, please describe what options to select on booting the first time. Running from Haret, do I really install data to NAND?! And, if so, without unlocking and flashing? Mssmison also mentions editing the userinit.conf, if using a swap partition. Please tell me which values need to be edited.
I am used to NoMoRootfs and the old sqsh running from Haret.
TIA.
I can't get this release to mount on my sd card I keep getting the wake up errors
sak211l said:
I can't get this release to mount on my sd card I keep getting the wake up errors
Click to expand...
Click to collapse
Me too. I tried to install the latest 3/20 nand builds into my sd, but failed. I will try the 3/29 builds
Can anyone tell me how fast this build runs?
I had the old SenseHero build from Jamezelle, but most of the time when the phone rang my phone was too slow to pick it up, and I missed the call.
I hope this one is faster
Deodex
Theres a way to make this build smaller
Deodex apps. This build has 21.8MB of .odex files.
tiagoclc said:
Theres a way to make this build smaller
Deodex apps. This build has 21.8MB of .odex files.
Click to expand...
Click to collapse
the files being odex'ed makes them faster. That's why I've left them like that
kiwilime said:
Can anyone tell me how fast this build runs?
I had the old SenseHero build from Jamezelle, but most of the time when the phone rang my phone was too slow to pick it up, and I missed the call.
I hope this one is faster
Click to expand...
Click to collapse
It's not atleast on my tilt its probably the worst sense build I have run yet props to mssmison on getting it ported though. Good job, it looks good but way too slow for me to run even on nand. back to playing with the other sense build on SDcard ext2 img, for some reason I cannot get any build installed to partitions I have tried with both cards
Note: Please keep this thread restricted to Atrix-specific and general issues. Threads for other devices are referenced at the top of the main webtop2sd thread.
Discuss webtop2sd here (the other thread will be kept clean for announcements, FAQs, etc.).
Before you report an issue:
Make sure it's not on the Known Issues list first!.
Basic debugging, since these are going to be questions I ask anyways:
If you hit problems with the Android webtop2sd application, you'll need to tell me the error, and give me the last few lines of adb logcat. Run this adb command, which will filter out most of the unimportant lines:
adb logcat ActivityManager:i AndroidRuntime:i webtop2sd:i *:s
Are you actually booting from your SD card? You can find this out by checking the Diagnostics tab in webtop2sd, under "Currently mounted webtops". If mmcblk1p12 isn't listed, you're not booted from your SD card. If this is the case, report what ROM you're running from.
Is the webtop configurator application showing, but not running successfully? If so, plug your device into your dock and run a terminal (either locally or adbWireless + adb shell) and run the following:
su
/usr/bin/sudo -H -u adas bash
export DISPLAY=:0
python /usr/local/bin/webtop-configurator.pyc
I'll need whatever output shows up.
great! thanks for making it so much easier.
haven't actually tested it b/c i sort of figured out how to do that a few days back, but still need to manually install it.
maybe i'll test your app next time i decide to reinstall my ubuntu.
btw, which script are you using to mount /osh? for me only /data/logging.sh works (it's safer anyway).
I suspect that what I'm doing isn't rocket science by any means. But, what I do seem to be pretty good at is packaging semi-complex things up for people into a manageable form with a fairly solid level of reliability. You couldn't imagine the things I'm happy that I managed to accomplish with this app, because they're so... quirky.
Anyways, I've been using /system/bin/mountosh since the beginning. I need to tweak the copy I'm using right now, since my goals have expanded beyond what I initially wrote it for. On the other hand, it'll mean that I can separate out my "personal" Ubuntu versus my "debugging" one, and that should be quite helpful.
These advances with linux customization in webtop have turned me on to Ubuntu in general. I just dumped windows xp on my desktop server and now run ubuntu super OS and studio. This takes a phone to a new level. Thanks OP!
i would love to try this out but i'm on a mac.. can you partition through disk utility?
I would complain that you beat me to it, my initial post here, except it looks like what you created is way more advanced and polished than anything I could do.
I will check it out right now. Oops, i see it is only a shell at the moment. Well I am very eager to try it.
A few questions then:
1. I assume this is similar to your last mod, in that you have just moved the Motorola environment onto the SD card, no chroot or other tricks?
2. Is the dependency problem better? Are we able to replace the motorola packages?
3. Are we still stuck with jaunty or is there a possibility to upgrade to a supported version of ubuntu?
I know this might seem like a useless question (installing regardless), but your previous work was based off the 1.5.7 firmware, would this app be supported/functional on the current 1.8.3 firmware?
Oh, and...
Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! XD
-djazin
Yes I believe the most important questions here are:
1 - which version will it work for? .83? .57? or just up to .52?
2 - If the Ubuntu version could be upgraded to, say, 11? Probably not, but hey...
Regardless, your work is the only reason why I'm buying myself a lapdock and replacing my netbook, so thank you very much for this hobby of yours =)
Looks great, thanks for the hard work
Sweet!! I just bought a 32 GB card the other day. Happy Fathers day to me.
Looks like no sleep week.
n1ckr0th said:
i would love to try this out but i'm on a mac.. can you partition through disk utility?
Click to expand...
Click to collapse
Possibly; I'm not sure. At least one person I talked to said that it should be possible via command line utilities, but I'm not the best person to ask about this particular issue, not having convenient access to Mac OS X...
krkeegan said:
I would complain that you beat me to it, my initial post here, except it looks like what you created is way more advanced and polished than anything I could do.
I will check it out right now. Oops, i see it is only a shell at the moment. Well I am very eager to try it.
A few questions then:
1. I assume this is similar to your last mod, in that you have just moved the Motorola environment onto the SD card, no chroot or other tricks?
2. Is the dependency problem better? Are we able to replace the motorola packages?
3. Are we still stuck with jaunty or is there a possibility to upgrade to a supported version of ubuntu?
Click to expand...
Click to collapse
Heh. I've actually been planning this for over a month, after some pointers from eval- - I had a rough version running, but I wanted to make something that users would be able to take advantage of easily. Oddly, it's the UI that's been the difficult part - actually having it do stuff is (relatively speaking) the easy part.
1. Yes, this is moving the Motorola environment to the SD card. Nothing special otherwise.
2. Not really - nothing's changed on that front. I'll be tweaking some of the package states on the filesystem to make upgrades less liable to completely blow up, but if we want to keep some of the niceties that Motorola added, I'll need to port those changes forward (which I have no particular problem with doing).
3. We're stuck with Jaunty for now. Unfortunately, it looks like information I had previously in regards to a version upgrade for Ubuntu don't apply to our phone, so I'll likely start working on an upgrade to 10.04 LTS after this stabilizes.
Djazin said:
I know this might seem like a useless question (installing regardless), but your previous work was based off the 1.5.7 firmware, would this app be supported/functional on the current 1.8.3 firmware?
Click to expand...
Click to collapse
Viamonte said:
Yes I believe the most important questions here are:
1 - which version will it work for? .83? .57? or just up to .52?
2 - If the Ubuntu version could be upgraded to, say, 11? Probably not, but hey...
Click to expand...
Click to collapse
This is the fun part. Since this is an Android application and not a script, this part should work with any version. I'm currently running 4.1.57 on my phone (I never did get around to upgrading), but once I verify it works there properly, I'll be upgrading to 4.1.83 and testing there as well. There are no issues that I'm aware of that would prevent this first application from running, and the second application (the Python/Gtk one I have planned) should be able to handle any differences between the various ROMs out there.
And the Ubuntu version upgrade question, I answered just above this.
everything is greyed out when i try to use the app..
Epic Sogarth
The ui looks nice though can't wait to test it on 1.8.3 been on 1.5.7 with v2 awhile now updated to 1.8.3 installed the app played with the setting everything looks sweet cant wait for the go ahead XD wouldnt mind testing anything.
-Djazin
dicksteele said:
Sweet!! I just bought a 32 GB card the other day. Happy Fathers day to me.
Looks like no sleep week.
Click to expand...
Click to collapse
32g class 10 has proven to fail on the atrix
it corrupts. Lets hope you didn't spend the extra money for the class 10
n1ckr0th said:
everything is greyed out when i try to use the app..
Click to expand...
Click to collapse
Greyed out? I know that the "Go!" and "Uninstall" buttons tell you that it's not implemented yet, but nothing should be grayed out?
PAulyhoffman said:
32g class 10 has proven to fail on the atrix
it corrupts. Lets hope you didn't spend the extra money for the class 10
Click to expand...
Click to collapse
That's good to know. Luckily they were out of 10's, and I got a four. Already formatted 16 GB fat32 the rest ext3.
Sogarth said:
Greyed out? I know that the "Go!" and "Uninstall" buttons tell you that it's not implemented yet, but nothing should be grayed out?
Click to expand...
Click to collapse
Now that I really look at it mine is also. So I'm guessing that's due to 1.83, or GladiAtrix. That's what I'm using.
I'll post a screenshot if you need.
I could go to stock 1.57 upgrade to 1.83 but not until tomorrow night
Thanks for the answers, Sogarth. And congratulations on your gift man, because your sum of intelligence and dedication sure is one. I'll be installing this on my Atrix as soon as it has been stabilized (and, well, actually made useful xD)
I am on Gingerblur 4.5 only things greyed out are Partitioning section, both 'Device to partition' and 'Webtop partition size' items if "Partition ext. storage" is not selected. Also under "Locations" 'Delete filesystem file' is grey if 'Source webtop' is set to 'internal storage'.
All of these being grey makes sense if you read what they are doing......
_Dennis_ said:
I am on Gingerblur 4.5 only things greyed out are Partitioning section, both 'Device to partition' and 'Webtop partition size' items if "Partition ext. storage" is not selected. Also under "Locations" 'Delete filesystem file' is grey if 'Source webtop' is set to 'internal storage'.
All of these being grey makes sense if you read what they are doing......
Click to expand...
Click to collapse
Unchecking the Partition ext. storage option "ungreyed" the Locations options and Advanced options. Didn't think about doing that since that was one of the goals of this app.
Since I manually partitioned already I should have thought of that.
I hope mods will find this thread informative and not remove it as I think I have few things to share that people can really use and be aware of when getting their Nook Color rooted and stup with CM7 ROMs.
Reason I am writing my experience is that I feel there was some info that could have been more informative and straight forward (other than confusing minor parts that wasted some of my time )...
I started without much of the knowledge about how to root Nook, etc and read several stickies on "how to" stuff... After all I managed to get following flashed onto my nook color:
CM7 (7.0.2 stable ROM version)
Gapps
Dalingrin's OC kernel (4/24/11)
Clockworkmod (updated it through the ROM Manager at the later time).
Here is several advices I think you should know about;
1. Do go and check "How to videos" on Youtube in regards to installing CM7 on your Nook Color!
2. If you are going for CM7 ROM, there is no need to root your Nook with "manual nooter" ... you can use MN only if you want to keep all options but gain Market app and other apps as well... I recommend going CM7 since it is rooted already and everything gets taken care of in three simple steps:
a) Burn bootable SD Card with Win32DiskImager and use 1GB Clockworkmod Image you can find here at xda forums.
b) Once done, copy ROM and Gapps and Kernel .zip archives onto the root of yor SD Card (do not rename any files at any time)
c) Insert SD Card into Nook and boot it, it will go into Clockwork mode and do the following:
***FIRST go to "Mount/Storage" and format SYSTEM, then format DATA and then format CACHE
***Select Install from SD Card and then install files in this order:
-1- CM7 ROM
-2- Gapps pack
-3- OC Kernel
3. Once done with everything shut down Nook, take out SD Card and place it back into SD Card reader (do not use any phones to do this - SD Card readers are preferable... if you ask me, yes I did use my phone and it worked just fine).
4. Find Panasonic SD Formatter v2 (or v3) online, install it and then format the SD Card to wipe all of the stuff on it... I formatted the old fashioned way and it worked just fine... either or you go for it's up to you.
5. Place back formatted SD Card into the Nook and boot it.
Note: CM7 uses SD Card for a storage and that's why format was necessary
IMPORTANT 1: CM7 comes pre-loaded with ADWLauncher (regular non-EX version) and I have to say it was bit choppy (even with OCing CPU to 1.2GHz)... I went and installed LauncherPro to test it and have to say MUCH SMOOTHER... yes, iPad smooth if you are asking me when it comes to sliding home screens (video is pending update, you will see it for yourself).
IMPORTANT 2: Lots of people is talking about battery life, renaming Phone apk and Telephony service apk ... IT IS SIMPE: when you are using WiFi have Airplane mode OFF; when you are done with WiFi, simply turn Airplane Mode ON and that will (as made to do) disable phone services. Just one button more to press BUT it saves you whole lots of battery. I charged it about 2hrs ago and since then used tablet for about 10 minutes on Wifi and that was it. Phone idle is 5%!!! until I figured to try with airplane mode... and it works...
UPDATE - Important Note: I forgot to mention that kernel does allow OCing but currently I am testing it under regular clock (800MHz and 300MHz) - launcher scroll home screens works just as smooth and I turned off fade-in/out when clicking on App Drawer just because I am not big on eye-candy.
Try it for yourself and report back - I would be glad to hear this worked for others and not only me
Great post. I personally found Zeam Launcher to be the snappiest luancher for my device but YMMV. To add to the original post I made a thread concerning the volume settings for the Nook that can be found HERE. I have mine overclocked to 1.3Ghz and I can get a full day of heavy use out of it as long as I turn off WIFI when it is not needed. Just add a shortcut to your notification bar under the Cyanogen Tablet Settings option. Also add a brightness shortcut to it and keep it as low as possible. Make sure to turn off auto-brightness in the display menu that's found under Settings.
If you posted this a few months back, it would be great.
Now, it's a bit outdated.
Thanks for the effort.
There's really no reason to be using 7.0.3, much less 7.0.2. Grab a recent nightly (I can vouch for 176, but have seen some trouble reports on 177, haven't looked into the just released 197) and up-to-date gapps (bottom of this page). Dal's overclock kernel is built-in, along with other features designed to work with the Nook Tweaks app.
The problem with battery life in older versions of CM7 is that the device will not deep sleep. That was solved with the move to 7.1.
Taosaur said:
There's really no reason to be using 7.0.3, much less 7.0.2. Grab a recent nightly (I can vouch for 176, but have seen some trouble reports on 177, haven't looked into the just released 197) and up-to-date gapps (bottom of this page). Dal's overclock kernel is built-in, along with other features designed to work with the Nook Tweaks app.
The problem with battery life in older versions of CM7 is that the device will not deep sleep. That was solved with the move to 7.1.
Click to expand...
Click to collapse
This.
Stables are so far behind its not even funny.
Sent from my NookColor using Tapatalk
votinh said:
If you posted this a few months back, it would be great.
Now, it's a bit outdated.
Thanks for the effort.
Click to expand...
Click to collapse
Did you REALLY have to post that? Outdated for who? You? Maybe a few months ago this would have been outdated for me but its helpful and useful.
Congrats Mo on 602!
chefdave12118 said:
Did you REALLY have to post that? Outdated for who? You? Maybe a few months ago this would have been outdated for me but its helpful and useful.
Congrats Mo on 602!
Click to expand...
Click to collapse
Why did you jump on too hard?
Did you see I posted "thanks for the effort"?
You don't see it's outdated?
Have you seen any threads asking why format /data yielded problem?
If you install lately nightly build, would you recommend others to install OC kernels version 04/21/2011?
I just pointed out for new comers that if they have their NC, mostly likely version 1.2, this instructions are outdated and they should NOT go out and hunting for old stuff. That's all.
Huge thanks to Hashcode for all his hard work thus far, what with the totally ingenious Safestrap and his latest victories with CM9. I hope this helps somebody out and that at least *someone* out there thinks this is as cool as I do.
Pushing OK+Backspace will force the console to kick you out back into the recovery, in case you get stuck. Keep in mind that the console is pretty powerful but also really dangerous if you don't know exactly what you're doing. Although, you'll never learn how to do anything awesome unless you get your hands dirty.
The Microphone button is now ESC, command history works, tab-autocompletion works via either the hardware Tab key or by pushing OK+i, and you can scroll back up through the text one line at at time with Alt+Up or Alt+Down or in chunks of 8 lines with Shift+Up and Shift+Down. Home is the home softkey, or the Search button on the keyboard, and End is the Power button. You could also push OK+A or OK+E for Home and End, respectively.
Make sure you uninstall Safestrap and then remove the application before you install this one. I just jacked Hashcode's .apk and stuffed my new binaries inside the .zips, if you don't want to bother with uninstalling and reinstalling the .apk, you can extract the recovery.zip and 2nd-init.zip from the archive and push them both to /system/etc/safestrap and reboot. Enjoy.
..............................................................
EDIT: I finally got my act together and put my modified sources on github:
http://github.com/buddyrich/android_bootable_recovery
............…………………………………………
EDIT: Just finished up my latest update to this branch of Hashcode/Koush's work. Added:
-Use numbers on the hardware keyboard to select menu entries. Got really tired of scrolling around and thought this would make things a bit quicker.
-Scrolling/repeating keys. Holding in for longer than about half a second will repeat even faster now, similar to a real terminal on a PC for instance.
-vim statically compiled to avoid the need for any external libs (ie: having /system or /systemorig mounted). Full color support and syntax is working great now; the only thing missing is background colors, which will be tricky to implement.
-a $HOME directory is now made at /emmc/safestrap/home. This is set up when the .apk is installed; it isn't necessary so it can be deleted if you want, but it is required if you want to have a persistent command history in bash as well as the ability to customize your .bashrc and .vimrc files. Most of you won't really know what this means, but if you do you'll probably appreciate it.
-Revamped all the menus and made everything look a little cooler. Let me know what you guys think! I got rid of the highlighting box that shows which menu entry is currently selected and changed it to simply highlight the text in white to distinguish from the green/yellow menus; I think it's a little easier on the eyes but some feedback would be cool. It wouldn't be very hard to allow the users to customize the menu colours themselves via external files placed on the sdcard/through a menu option.
-Fixed the issue some people were having with restoring to /systemorig; there aren't any more issues mounting/unmounting /systemorig or /system during a restore
-Probably many more things I've forgotten
-.bashrc tweaks, fixed a few aliases, nothing major
-You can flash updates from either safe or non-safe mode now, look in the advanced menu. Really though, be careful and remember to make backups of your /systemorig partitions. Don't say I didn't warn you! Guaranteed, someone out there will complain that they broke their phone so I was pretty hesitant to let that out in the wild, but I know I've found myself in the situation where I could've used it so there you have it.
Let me know if anyone finds any issues, I've done a pretty thorough job testing this over the last few weeks but there's always something to be missed. The new .apk is over the size limit to be posted in the forum due to the new bash and vim binaries and the vim runtime files, so you can download the new version from my dropbox here:
Safestrap (Tweaked) v1.08e for Droid 3
http://db.tt/CArenxr7
EDIT:
----------------------
Just finished thoroughly testing my latest release and think it's ready for human consumption! Another batch of sweet additions:
1) Proper implementation of /systemorig flashing while in non-safe mode... without any modifications needed to the updater-script present in any flashable zip. Even if the updater-script inside the. zip file you are flashing targets "/system", if you confirm it about three times in non-safe mode it will know to copy the files onto /systemorig to replace your stock system.
You can install Gingerbread-based ROMs such as MavROM 3.5 to the stock /system partition while in non-safe mode via the Advanced menu. Safestrap will backup and afterwards restore it's own files needed to ensure you can still get back in after a flash of the /systemorig partition. Note that flashing your original /system partition with an ICS ROM won't work yet because they need custom init.*.rc scripts in place during the 2nd-init process; this isn't hard to do but I was getting anxious to get something out so it'll have to wait until next time.
2) Redesign of the layout for the menus, much more organized
/* 3) Allow for rebooting directly into the recovery, either via the shell command "reboot recovery" or through the Reboot Menu */
// EDIT: Seemed to be causing some users to persistently boot straight into the recovery so on the backburner for now
4) Allow for custom colors for either safe or non-safe mode; to change the colors for now you have to execute a few little shell commands. Here's an example to change safe mode colors to a blue-grey and then non-safe mode colors to maroon:
Code:
s_rgb 139 137 137
ns_rgb 127 34 10
cc
Basically, "s_rgb" sets the colors for safe-mode and the three arguments (139 137 137 in the above example) are the codes for the red, green and blue components of the end result; you can look up rgb color codes for your own custom colors. "ns_rgb" is the command for non-safe colors. "cc" just tells the recovery to update the colors to whatever they've been changed to. If you don't like what you've done and just want to revert back to the stock ones, you can just wipe your /cache partition and they'll go back to normal.
Eventually I thought it'd be cool to be able to do this via the recovery UI but I haven't been able to envision how it would work yet.
5) Added background colors/highlighting in the console now, makes vim look a lot prettier. If there's anyone out there who cares, I preinstalled a few plugins (MiniBufExplorer, MRU (most recently used files), bash-style path completion, etc.)
Also, changed the cursor from the big ol' ugly white block to an easier-on-the-eyes one-character underline.
Yeah, it's overboard.
6) Much faster backups and somewhat quicker restores now. I clocked full backups (including /systemorig and ~350mb /data partition) at around 2 mins and full restores at around 7 minutes. Also fixed up the progress bars so they give a more accurate representation of how much longer the backup/restore will be.
7) Moved $HOME and other misc. Safestrap files to /cache instead of the /sdcard
8) Probably half a dozen other OCD details that I've already forgotten.
Test it out and let me know what you guys think!
As always, sources are posted on my github:
https://github.com/buddyrich/android_bootable_recovery
You can get the new .apk here:
Safestrap (Tweaked) 1.08f for Droid 3
http://db.tt/u4vAwv2u
i need this about 6 hrs ago lol.
Quite useful mate cheers.
=smc
Thank you so much for sharing this file. Your work is greatly appreciated.
This is a nice little(big)addition to safestrap! Thanks for adding it in!
I can't think of any better use for Christmas Eve than coding a bash console into recovery! Merry Christmas to the D3! Thank You!
Sounds good. I haven't grabbed it yet (as I need to keep my own customised Safestrap for ME863 nandroid support) but one thing I'd note is that the "OK" button (i.e. trackball click) is used for "Control" in Console+, and the console in Amon_RA's HTC Dream recovery. That saves you losing the @^ key.
Edit: Also: Source? Sounds like something that could be pushed upstream. I always found the console in Amon_RA's recovery very useful, missed it on my current device, when I didn't have a computer with ADB handy.
TBBIe,
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
I'll commit my sources to github shortly so you have take a look.
I am trying to get through the preinstall problem myself after flahing xt883 and I was wondering if I could fix it with this?
Sent from my DROID3 using xda premium
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
redsox985 said:
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
Click to expand...
Click to collapse
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Endoroid said:
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
ovelayer said:
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
Click to expand...
Click to collapse
Oh I'm sure I'll be damn thankful at some point. Made a point of installinng it
Sent from my XT860 using xda premium
Rick#2 said:
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
Click to expand...
Click to collapse
The difference is the other way 'round. The /data partition is extended backwards over the end of the /preinstall partition.
It doesn't cause problems during init, it was causing nandroid to fail mounting /system, and presumably would make switching to safe-mode fail (although I never tried)
My patch to fix this for nandroid was based on 1.06. The only way this could be 'fixed completely' in safestrap was if safestrap had had repartitioning code added at some point to resize /data back down and grow /preinstall to be large enough to hold a safe system. And Hashcode'd said he didn't have time or real inclination to do that, I thought.
I'm fairly strapped for time at the moment, so I don't know when I'll have a chance to look at the source and/or try out your build. But it's definitely somewhere in my TODO list. ^_^
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
@rick#2
I'm running CM9 for daily use, but it's a bit wobbly at times, so I run 7.1 as the "non-safe" system. The big limitation to this is that I can't maintain the 7.1 fallback properly as hashcode deliberately disabled installing zips in non-safe mode.
If the wife has forgiven you by now - any chance of adding the ability to install .zips when in non-safe mode?
The alternative is to keep swapping bootstraps all the time, and all it takes is one late night sleepy mistake to stop the device booting one system or both.
I'm in favor of this as well, and have even mentioned it in the main SS thread. Could you add flashing to non-safe, but say with like 3 layers of warnings saying something like "THIS IS YOUR NON-SAFE, MAIN SYSTEM. FLASHING HERE CAN BRICK YOU."
This would be really nice because it's a PITA to keep switching strappers, albeit it easy, just a burden.
This is a great hack! I was considering doing this myself but you beat me to it! BTW, is your modified source code on github or somewhere like that, or can you send it to me if not? Thanks again!
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Rick#2 said:
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Click to expand...
Click to collapse
Dude you rock!
Sence you introduced your mod i have used nothing else..
The scrolling feature would be a HUGE improvement i agree ..
Also it would be nice if you could flash on the non-safe system as well..
Hope you can get er done..
I allways seem to watch this thread for updated..i really hope you can continue this adventure without the wife killing you lol..stay real!
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
denpad2010 said:
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
Click to expand...
Click to collapse
Hey bro if you want wifi teather look up android-wifi-teather..it works!