This thread was initially an inquiry on the Cyanogen Rom however is now a Rom thread so here we go.
Background on the Rom is here http://www.cyanogenmod.com/about
On the Hd2/Leo mod see here http://pastebin.com/BBf1hr50
memin1857 said:
INSTRUCTIONS
Cyanogen Mod RC1 - Leo build by Zego WITH ADOBE FLASH and 3G WORKING
There is a new nice build called CM6-HTCLEO (Cyanogen Mod RC1 - Zeto)
It needs a lot of prep work to get to good working order, then its really good.
I have also managed to get adobe flash working. (It doesn't work out of the box)
This build
(after all the steps) have gps, camera (with proper flash exposure), camcorder, camera flash/led/torch, adobe flash, nice look and most other goodies available.
Here are the steps
1) Download cm6-htcleo.7z from:
http://www.mediafire.com/?kzo7fxi2hp917s8
2) Download phone button (keypad) fix:
http://www.mediafire.com/?qrs4w0kd470keqm
3) Download MTU fix from:
http://www.mediafire.com/?tqggvgrzb79gm24
or
http://www.megaupload.com/?d=JL368N3N
4) Download Cotulla 23 July nospeed zimage from:
http://cotulla.pp.ru/leo/Android/Cotulla_zImage_CABDET_NOSPEEDDY.rar
5) Extract the cm6-htcleo.7z file and put the cm6-htcleo to your sd card root.
6) Extract the cm6-htcleo_keypadfix.7z file and put the FOLDER NAMED root UNDER cm6-htcleo folder in your sd card. (Not to sd card root folder. I really mean a folder named root. You will see it in the archive)
7) Extract the cm6-htcleo-datafix.zip file and put the FOLDER NAMED root UNDER cm6-htcleo folder in your sd card. Just merge them. (Say yes when windows asks) Credit: ElBartoME
8) Extract Cotulla_zImage_CABDET_NOSPEEDDY.rar
and put zimage file to cm6-htcleo folder and overwrite.
credit: cotulla
9) ONLY DO THIS STEP IF YOU CANNOT BOOT (linux complaining about mmcblk0): Open startup.txt with notepad and
replace the line
set cmdline "rel_path=cm6-htcleo"
with:
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
credit: dusty_nz
10) Run clrcad and haret as usual but from cm6-htcleo folder. Once Android has booted start terminal app.
11) write
su
and press enter. It will ask for superuser permission. Tap allow.
12) write
mount -o rw,remount /system
and press enter. You should not get any response or error.
13) Now launch ES File Manager and tap \ on top left.
Navigate to /system/app and find
com.adobe.flashplayer apk file and delete it.
14) Power off your phone in a normal way and reboot to Android CM6.
15) Go to Market and install Adobe Flash 10.1 Beta 3 (use your gmail account)
Done!
Notes:
-FIRST BOOT WILL TAKE A LOT OF TIME! BE PATIENT. IT WILL TAKE A LOT LONGER THAN YOUR USUAL BUILDS.
-ADOBE FLASH does not work out of the box. You have to reinstall it but since it was cooked in to the rom as system app and you can't uninstall it, you need to mount /system directory read/write and delete flash so you can install it again. This time it works properly.
-You may not be able to boot if you do not edit the startup.txt
-You may not be able to wake up if you do not replace the zimage with the older 23 july one. You can use 25 july panel on off zimage if you CAN wake up from sleep. It depends on hd2 lcd panel type which is more than one.
Optional: Install Launcher Pro and make it default home screen to get a smoother experience.
After ALL these operations, this seems like the most functional build.
Cyanogen is normally a mod for android and someone named zego turned it into a hd2/leo build. A lot of stuff was missing and there was no central infromation. That was what I did. You don't need to read 6 pages to get this build working this good now.
I recommend disabling live wallpaper. Static wallpapers are faster. Formatting sd card beforehand and using a class 6 sdhc card is also recommended.
I don't have time to package all this stuff into a build. Maybe someone who does above steps can package it in a new single file and put to megaupload/mediafire (mskip/Mark?) For now you have to do it yourself. You will like the end result.
Packagers please don't call yourselves devs and give credit to original hard working people. Donation is also recommended.
I am sorry if I forgot to give credit to anyone.
I got all this information by reading all the pages of this thread and some more. Now you don't have to.
Click to expand...
Click to collapse
From makavelitha
Good
+ Successfully booted on the first try
+ Camcorder is finally working with the original HTC app (i hope someone will port this to the other android builds)
+ Flashlight is finally working with the original HTC Flashlight App
+ No SOD or GSOD with cotullas zImage 25.07 (maybe i have a Sharp Panel?)
Bad / Problems
- Bad Performance (especially at scrolling)
- Can't Download anything from the Market, i get always the message that my Storage Card is full, i've checked it and android shows me 0mb left on my SD Card, but i have more than 4GB free on this Card (it was working in all other Android Builds)
- Needs time to boot-up
- No or Bad Battery Management (already optimized in other Android Builds)
- USB Storage not working (already working in other Androids)
- Bluetooth finds other devices but can not be paired
- Compass works but it doesn't show magnetic north.
- Low volume issue is already known. During a call other party hears echo of his own sound when speaker is on. No echo in normal mode.
Performance Tweaks
Update I:
Using Cotulla zImage 7/25/10 makes a huge difference in speed!
The only thing still sluggish is scrolling through the apps....
Otherwise from that this is a very good build. Nice pre installed apps, good out-of-the-box build.
Update II:
Changing the application drawer to "Horizontal" like on the Galaxy S eliminates scrolling speed issues when scrolling through the apps.
dusty_nz said:
So looking at the Cyanogen rom, Swapping out the Zimage and trying to boot.
Has anyone tried this?
Would it work?
Looks like it has heaps of Qualcomm optimized components
Click to expand...
Click to collapse
http://www.mediafire.com/?kzo7fxi2hp917s8
And don't forget to add the phone button fix:
http://www.mediafire.com/?qrs4w0kd470keqm
any changelog of this mod/port ?
Readme:
http://pastebin.com/BBf1hr50
on this build flash doesn't work for me in the browser.
I am running it at this moment, it boots correctly until android froyo wizard.
It runs correctly for a minute and SOD
Ah it wake up, great
For the first time in the leo android world, the camera works
I give you more feedback later ...
Update:
- GPS works perfert
- Reboot not work, like other builds
- Import contact from SD not works
perhaps the one based on RC2 will be better, where have you find the links for this build ?
I can't get this to boot.
Initrd keeps looking to mount /mnt/sdcard against /dev/block/mmcblk0p1 and falling over. I only have the one FAT32 partition on my sdcard which normally is at /dev/block/mmcblk0.
Also should I be extract the .tar.gz file into the CM6 directory or put it up at the root of the sdcard.
Thanks.
idcom said:
I can't get this to boot.
Initrd keeps looking to mount /mnt/sdcard against /dev/block/mmcblk0p1 and falling over. I only have the one FAT32 partition on my sdcard which normally is at /dev/block/mmcblk0.
Also should I be extract the .tar.gz file into the CM6 directory or put it up at the root of the sdcard.
Thanks.
Click to expand...
Click to collapse
Try replace cmd cmdline
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
m4ck said:
Try replace cmd cmdline
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
Click to expand...
Click to collapse
Thanks. Worked a treat. Now to play.
Nuja said:
any changelog of this mod/port ?
Click to expand...
Click to collapse
Yeah I agree guys, can you please be a bit more specific about what is additional from other froyo with/witout sense or Eclair?
readme file does ntoe give much in fact.... A couple of screen shots would be fantastic...;-)
general statement: Donate, so all mods/chefs/devs can eventually pay some flowers or perfums or sex toys to their girls friends (all of them so angry that they spend so much time developing stuf !!!)
Well.... more info on what cyanogenMod is on:
http://www.cyanogenmod.com/about
Anyone having problems with 3g on this build?
nordicfastware said:
Well.... more info on what cyanogenMod is on:
http://www.cyanogenmod.com/about
Click to expand...
Click to collapse
Thank you, but there is no mention of build for our HTC HD2
Who is the maker of this build for HD2 ?
the build is done by Zego from the IRC channel compiled from source of CyanogenMod 6.0.0 release candidate 1
I tried it last night and it gives me SOD repeatedly, it's fast, but the SOD is killing me, I am falling back to Darkstone's FroyoV1
Hmmmm
Not booting for me.
Formatted a SD card. Single Fat32 partition.
Extracted zip to \cm6-htcleo\startup.txt etc.
Changed the Startup.txt to
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
error
/init: line 88: mmcblk0=mmcblk0: not found
Logical sector size is zero
mount: mounting /dev/block/mmcblk0 on mnt/sdcard failed: invalid argument
lucian777 said:
Anyone having problems with 3g on this build?
Click to expand...
Click to collapse
Yes. I had the same with Dan's Froyo v.1 but Darkstones works a treat. Changed the apn's to voda uk and all that.
booted first time - took a while but OK
Loaded with apps
camera working
Video recorder working
GPS working
man it's fast..........
will test further and report back
dusty_nz said:
Not booting for me.
Formatted a SD card. Single Fat32 partition.
Extracted zip to \cm6-htcleo\startup.txt etc.
Changed the Startup.txt to
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
error
/init: line 88: mmcblk0=mmcblk0: not found
Logical sector size is zero
mount: mounting /dev/block/mmcblk0 on mnt/sdcard failed: invalid argument
Click to expand...
Click to collapse
took out the set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0" ands its booting further. Got wizard
I for one am excited for this development. The collaboration from the devs here along with cyanogens work is fantastic. Any chance of getting cyanogen directly involved and/or once a build is completed would an official thread on this be desired?
I am not a coder but I'm working on it. Until then I'm just a fan and a donor. I've been a long term user of cyanogens work and I can safely say with the joint efforts of everyone here, this would be a powerful development. Keep up t the awesome work!
-------------------------------------
Sent via the XDA Tapatalk App
Related
Ok thought might as well start this off myself seen as people keep talking about it, lets have a Q&A thread instead of bashing up the original thread so it can be used just for news and updates.
Does Android work on my HD2?
yes and no, at the moment it boots, no touch-screen driver so that's it so if you try this is what you get
microang has made up some pretty nice versions that dont blue screen check them out here
http://forum.xda-developers.com/showthread.php?p=7032400#post7032400
Can I flash Android?
NO NO NO, it will run from Haret, it will not be a ROM, (yet maybe one day)
Can I boot Ubuntu?
yes you can, but touch-screen issues again,
UPDATE there now is a TS image to use
you would be better off using a mouse and keyboard via a powered usb hub.
Startup txt
Who can I donate to?
Dcordes' PayPal
Cotulla's PayPal
Netripper's PayPal
Links for fatsal-ubuntuX1-20100225 running on you're HD2, there is 3 but i cant find them all post if you have a working link.
http://hotfile.com/dl/51297725/02a8295/fatsal-ubuntuX1-20100225.7z.
thanks to yumm_007 for packaging this up
This Blog site & this Video is as FAKE as it get don't bother with it.
http://alltechdownloads.blogspot.com/
http://www.youtube.com/watch?v=BujRY_q53JI
http://androidforhd2.tk/
This is the IRC channel please dont go and post loads of crap there either
http://webchat.freenode.net/
use channel #htc-linux
Netrippers channel log
http://irclog.netripper.com/?chan=htc-linux&msgonly=0
__________________
Ok I have to go out i will add more and see about a ubuntu Tut to get it running when i get back, please post in here from now so we don't block up the original thread so we can leave that for news and development,
the 2 images are of how i have my folders set up and the other pic of proof it boots
I take no credit for the hard work gone in to this development just tried top clear the thread a bit but that didnt work did it lol, ALL CREDIT GOES TO
Dcordes'
Cotulla's
Netripper's
What I found was that the ubuntu folder must be inside another folder which is on sd root. So tree wise its setup as...
1) SD root
2) Folder (containing the ext2 and the ubuntu folder which contains the haret files)
If you do it like you did, it hangs, I had the same problem. If you do it the way I explained, it gets to the actual linux kernel (tux) but kp's when the modules are to be loaded.
Click to expand...
Click to collapse
Ok, this solves the cpu coherency freeze, what next? what is that we're doing wrong and can't boot the image?
thanks in advance.
artn3r said:
Yes, but i downloaded it over the rapidshare mirror.
what i did:
-copied everything to the sd root
-replaced zimage with the kernel that boots on hd2 (from irc log)
-merged the default.txt and startup.txt of the ubuntu build with the irc-log-build
start haret.exe
Click to expand...
Click to collapse
have you tried this yet???
hi guys,
i currently don`t understand what exactly i have to do to run the HaRET. i`ve downloaded the "fatsal-ubuntuX1-20100225". there are haret and so on and a folder named ubuntu. when i extract it to my sdcard an boot haret i got a stop error "can not access SDroot".
what is wrong? maybe i am stupid?
braumeister said:
hi guys,
i currently don`t understand what exactly i have to do to run the HaRET. i`ve downloaded the "fatsal-ubuntuX1-20100225". there are haret and so on and a folder named ubuntu. when i extract it to my sdcard an boot haret i got a stop error "can not access SDroot".
what is wrong? maybe i am stupid?
Click to expand...
Click to collapse
I got it working on touch diamond start of the year, just downloading for leo now
this was posted
ayilm1 said:
What I found was that the ubuntu folder must be inside another folder which is on sd root. So tree wise its setup as...
1) SD root
2) Folder (containing the ext2 and the ubuntu folder which contains the haret files)
Click to expand...
Click to collapse
Demon_man said:
have you tried this yet???
Click to expand...
Click to collapse
That's the first of it, but go grab artn3r's pre packed ubuntu from the official Android/Linux thread a few posts after the one you quoted I think, and set it up folder wise as...
1) SD root
2) "fatsal-ubuntuX1-20100225" (containing the ext2 and THEN the ubuntu folder which contains the haret files)
That's what I did to make it work but as stated in the official thread, it hangs at the module loader
the name doesn`t matter?
well I'm downloading now, i have to pop out but i will be be back in 45 mins, and ill play try n get it running, if you get it going in the meantime let us no
braumeister said:
the name doesn`t matter?
Click to expand...
Click to collapse
Not sure TBH. Something interesting happens if renamed to something other than the original name though. The coherency test hangs but if reverted, it runs up to the tux.
Just upload ur files if you got it runing
Great idea man!
Demon_man said:
Ok thought might as well start this off myself seen as people keep talking about it, lets have a Q&A thread instead of bashing up the original thread so it can be used just for news and updates.
Click to expand...
Click to collapse
Nice idea man! Glad to see that lot of people is running in the correct way to help this development!
Cheers from Portugal
Ok, SOME progress. Mine HALF succeeded in rebooting after deleting then recopying the files over (making changes of course). It got past the rebooting in 5 seconds hang and now has actually made an attempt to restart. (yay!) But all I got was it declaring it was about to reboot and the Kernel version number. i.e. 2.6.32.9
ayilm1 said:
Not sure TBH. Something interesting happens if renamed to something other than the original name though. The coherency test hangs but if reverted, it runs up to the tux.
Click to expand...
Click to collapse
no it doesn`t matter where the files are or in which folder or how it is called.
tried this:
1) haret, ubuntu folder and co in the root of the sd card
2) new folder called "fatsal-ubuntuX1-20100225" with alle the files and ubuntu folder in there
3) renamed the folder "fatsal-ubuntuX1-20100225" to anything else
does not matter...the result is all the same.
haret booting, init the panel and stops after a line "welcome to kovsky aka xperia - ubuntu" with an error
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed - invalid argument
failed to mount the sd card. cannot continue
/bin/sh: can`t access tty: job control turned off
/ # _ (blinking cursor)
BUT...hardware controls response
braumeister said:
no it doesn`t matter where the files are or in which folder or how it is called.
tried this:
1) haret, ubuntu folder and co in the root of the sd card
2) new folder called "fatsal-ubuntuX1-20100225" with alle the files and ubuntu folder in there
3) renamed the folder "fatsal-ubuntuX1-20100225" to anything else
does not matter...the result is all the same.
haret booting, init the panel and stops after a line "welcome to kovsky aka xperia - ubuntu" with an error
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed - invalid argument
failed to mount the sd card. cannot continue
/bin/sh: can`t access tty: job control turned off
/ # _ (blinking cursor)
BUT...hardware controls response
Click to expand...
Click to collapse
Ok maybe it was just mine acting up then.
have you any partitions on sd card? one or more? if so on which parti do you have the files?
@braumeister
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed - invalid argument
failed to mount the sd card. cannot continue
/bin/sh: can`t access tty: job control turned off
/ # _ (blinking cursor)
Interesting, mine gets none of that. In fact, the loadmodule shell extension is the only think stopping mine from progressing. Oh and umm. It also attempts to switch to rootfs.
braumeister said:
have you any partitions on sd card? one or more? if so on which parti do you have the files?
Click to expand...
Click to collapse
No other partitions, hmmm. But in case this helps, its still got winmo stuff on it, so not formatted to ext2. Doubt that'd make a difference though as the SD's format shouldn't effect the format of the ubuntu image.
transferring files now to my sd card
BOOTED
Hi,
Touchscreen working fine for me.. thanks to cotulla
At bootup it will stuck shortly and show your TS type.. the ones with 2A are the lucky
Image here:
http://cotulla.pp.ru/leo/ImageTS.rar
Do you mind uploading ur setup for unbuntu image?
Thanks you
chris5932 said:
Hi,
Touchscreen working fine for me.. thanks to cotulla
At bootup it will stuck shortly and show your TS type.. the ones with 2A are the lucky
Image here:
http://cotulla.pp.ru/leo/ImageTS.rar
Do you mind uploading ur setup for unbuntu image?
Thanks you
Click to expand...
Click to collapse
do you mean me?? and how you got touchscreen working lol
ok so im not a really noob to xda but i have been looking for 3 days on a clear how to update a new kernal... i just cant find it im not sure if im wording it wrong or what please help you will be my internet hero and my mind will stop going insane...
thanks
Is this for hd2? If it is then all u do is find the kernal u want and replace with the old one. What build are u using by the way.
Read this:
http://htc-linux.org/wiki/index.php?title=Leo/UpdateKernel#Installing_latest_Linux_kernel_image_.28zImage.29
All you need to do is copy in the zImage and .ko files. The .ko files go in the "modules" folder, a subdirectory of "root."
Most of the kernels will come with following files :
zImage - The Kernel
bcm4329.ko - Wireless Module
tun.ko - Networking Module
yaffs.ko - File System (Optional at this time)
The way I apply the kernel is shut down the phone and use card reader and attach to my laptop. Assuming your build is under SDCARD\Android, files are copied to following locations :
zImage -> Android
*.ko -> Android\root\system\lib\modules
Anything to do with the lights modules goes to Android\root\system\lib\hw
Anything to do with RIL (like libril*) goes to Android\root\system\lib
Create the \root\system\lib\* directories if they dont exist, like for Sense builds. Now just back normally.
Hope it helps
v-b-n said:
The way I apply the kernel is shut down the phone and use card reader and attach to my laptop.
Click to expand...
Click to collapse
Is it also possible to update kernel without external card reader, by connecting HD2 to the PC (USB) and replacing files while in Windows Mobile HD mode?
THANKS!
What if a certain developer updates his android build and version, do I just copy the new stuff on the SD card, overwrite, and keep the Image iso file so I dont lose my settings ?
Do any of the above and finally to verify that a kernel is installed start Terminal Emulator (or any available terminal program) and enter:
uname -r
Should give you the kernel version.
Hmmm usually, what I do is either connecting the phone in USB in Windows Mobile mode, or power off and use a micro-SD card reader. Then:
- BACKUP the DATA.IMG to desktop or whatever
- Delete the root directory in your Android folder if there is one
- Delete all the .something directories (temp dir created by android)
- Copy the content of the kernel in the Android dir : Haret (emulator), initrd.gz (boot logo), zImage (drivers/kernel)
>Ignore the dev folder in hastarin build for example
>DO COPY the "root" folder (of hastarin 7.6 for example) to the android folder : HARET will update the android OS "suppletive drivers parts" without any need to enter commands or else (what i've been told)
Done
Desire Spot (clean) 2.0 based on HTC Desire 2.29
new initrd.gz, no rootfs, incremental updates​
Features:
- cedesmith initrd ( see post 3 )
- no rootfs
- incremental updates
- based on desire 2.29
- spot clean, system.img is a exact dump of unyaffs (with permissions) to ext2, not 1 bit modified
- auto set apn ( update )
- everything should work
- great for understanding android on h2
Not working:
- 720p video recording
- rmnet
Notes:
- i don't want yet another build, i made this mainly for my own use and to show the power of my initrd and exemplify incremental updates options it offers
- i hope that chefs will like and use my initrd.gz and a update to X build will work on all builds ( or all builds based on same rom: ex: desire, cm6 )
- i think we relay need a unified update system for all builds especially with development soon forking between nand and sdcard builds
- this is for purists, the ones that have stock windows rom and reluctant to change
- tested on stock 3.14 rom
Included updates:
- update.kernel.linux-on-wince-htc.15.11.2010
- install.init.15.11.2010
- install.hd2_libs.15.11.2010
- install.ril_wrapper.15.11.2010
- update.camera.15.11.2010
- install.busybox.cm6.14.11.2010
- install.su.15.11.2010
Credits and big thanks:
- Cotulla, NetRipper, danij3l, Markius, Rajko, LeTama, gauner1986, Cass, hastarin
- anyone who worked on hd2 android port and i forgot to mention
Disclaimer:
- all this comes without any warranty not even that it does something useful
- IF YOU USE IT YOU DO IT ON YOUR OWN RISK
Download and install:
- desire_cs.7z 2.0
- update.initrd.gz.20.11.2010 ( fix reboots for cards formatted in windows )
- update.autoapn (only if you have a data plan)
- extract to desire_cs on card ( case sensitive )
Updates
Download updates you want/need and extract on desire_cs directory on sdcard
Mandatory updates:
- update.initrd.gz.20.11.2010 fix reboot at startup
Optional updates:
- update.kernel.hastarin_8.5_eb.23.11.2010 (thanks vartp )
- update.kernel.hastarin_8.5.23.11.2010 (thanks vartp )
- fingerprint.19.11.2010 restore default desire fingerprint if you have problem with marketplace
- evo_keyboard.19.11.2010 (thanks vartp, see post )
- kernel hastarin_8.4_eb.18.11.2010 (extended battery)
- kernel hastarin_8.4_18.11.2010
- autoapn auto set apn
Read readme in archive, keep readme folder to record what you have installed and what version.
Attached updates in this post except autoapn are included in build
Dev info:
- install.init.15.11.2010 is the only mandatory update to install, your build will not boot without it
initrd.gz
Description:
- I build my initrd.gz mainly to allow updated and to be more like android phones boot process.
- It contains the directory structure of boot.img from desire 2.29 + /bin directory
- /bin contains a small busybox (with necessary commands to booth the phone ) + dosfsck + e2fsck all compiled with android toolchain and uClibc.
- It supports different partition on sdcard for system and data but probably nobody will use that.
- It only supports ext2 (for now) but i think nobody used anything else for hd2
- it is backward compatible (common cases)
Boot process:
- mounts sd card to /mnt/sdcard_boot not to interfere with android mount points
- checks and mounts /system and /data
- copy init.rc, init.htcleo.rc, default.prop, bootcomplete.htcleo.rc, shutdown.htcleo.rc ( blanks ) to /system if they don't exist
-- this is done to allow persist as / is ramfs
- execute uninstal*.sh then install*.sh in update directory
- copy AndroidApps and root as previous versions did
- execute update*.sh in update directory
- execute /system/init*.sh to perform build specific init tasks ( this can be installed by previous operations )
- symlink ( and creates dir ) /cache to /data/.cache if /cache not configured by build /system/init*.sh
- deletes /bin directory to free ram used by ramfs for busybox, dosfsck and e2fsck
- executes init.android - original android init program
- someware in process moves /sbin/adbd to /system/xbin/adbd and creates sysmlink in /sbin to free ram
Notes:
- if you create a install/update script please include readme file
- if you create a install/update script use a proper editor (notepad++) and convert file to unix format, line endings in dos format \r\n will brake sh
------ reserved -------
thanks for your great work
Sounds interesting. I look forward to reading more about it.
Sent from my HTC HD2
Thanks,
We always appreciate fresh blood.
I don't know how much this, if any, is based on the work of zegobit (who eventually got copied by shui8), but I'm very interested in this.
Coming from an android-on-Dream background, I've always thought of the rootfs as unecessary, and seeing how zegobit's initrd handled updates, I always thought that his way of doing things was the best (the rootfs used on most builds now came from the XDAndroid project which is made to support as many devices as necessary, something of a waste if you're building only for Leo).
You say your ext2 is just a re-packed, unyaffs'd image of the Desire rom, if so, are your leo-specific files stored in the initrd?
How will you handle updates?
And, this is for my learning, how is it you handle mounting and booting from SD. I'm trying to come up with an initrd that can be used to make an AOSP vendor that will produce a ramfs and an ext2 image that can be booted on Leo with little or no modification.
Any pointers you could give me.
In the mean time, I'm trying, and this might be, my main build.
Wow, very well documented. Kudos. Favortie build starting now.
jubeh said:
I don't know how much this, if any, is based on the work of zegobit (who eventually got copied by shui8), but I'm very interested in this.
Click to expand...
Click to collapse
and i thought i was completely original
unfortunately i did not see zegobit's work before, things might been easier.
on the other hand the most tricky part was compiling busybox 1.17.3, dosfsck and e2fsck with google toolchain ( well with codesourcery too but it produces 50% bigger exe )
jubeh said:
Coming from an android-on-Dream background, I've always thought of the rootfs as unecessary, and seeing how zegobit's initrd handled updates, I always thought that his way of doing things was the best (the rootfs used on most builds now came from the XDAndroid project which is made to support as many devices as necessary, something of a waste if you're building only for Leo).
Click to expand...
Click to collapse
this should work on any device also as long it works with cortex-a8 compiler optimizations and rename the init.htcleo.rc bootcomplete.htcleo.rc and shutdown.htcleo.rc as this are device dependent.
extracting initrd is simple: gzip -d -c initrd.gz | cpio
remaking: find . | cpio -o -H newc | gzip > ../initrd.gz
remember to do it on linux to preserve permissions
but ppl plz don't go rampage and make your own just because you can
i think they went rootfs because the utilities needed to boot are big ( 4mb old initrd and ~16MB rootfs ) and initrd uses ram for storage vs rootfs witch is on sd
i decided to make initrd after i got the tools to ~500Kb and read that memory is freed after file delete ( that is why i delete /bin directory when no longer needed ).
jubeh said:
You say your ext2 is just a re-packed, unyaffs'd image of the Desire rom, if so, are your leo-specific files stored in the initrd?
How will you handle updates?
And, this is for my learning, how is it you handle mounting and booting from SD. I'm trying to come up with an initrd that can be used to make an AOSP vendor that will produce a ramfs and an ext2 image that can be booted on Leo with little or no modification.
Any pointers you could give me.
In the mean time, I'm trying, and this might be, my main build.
Click to expand...
Click to collapse
blank init files are in initrd that is why install.init is only required update/ package
blank files also allows for this to work with CM6 builds
also all my install/update script edit files with sed not just drop file on /system
edit: install.init contains desire boot.img init files unedited (renamed .bravo.=>.htcleo. tho), install sh script does the editing. this way is crystal clear what is modified.
oh not to forget... : do not sed -i 's///' /init.rc and co, sed creates files and breaks symlink, your changes will revert after reboot. use sed -i 's///' /system/init.rc
I got robot voice on T-MOUS 3.14 rom. All else works wonderfully.
--edit---
ah, nevermind. A reboot fixed the problem. Perfect.
cedesmith said:
extracting initrd is simple: gzip -d -c initrd.gz | cpio
remaking: find . | cpio -o -H newc | gzip > ../initrd.gz
remember to do it on linux to preserve permissions
but ppl plz don't go rampage and make your own just because you can
Click to expand...
Click to collapse
My linux is still poor, I haven't really studied the boot process much. I knew how to extract/repack initrd.
Oh, and whatever changes I make, it's all for learning and my personal use. No interest in making a release. If I do do something and use your scripts, I'll credit appropriately, though the only release I'd be interested in is instructions and a vendor profile for AOSP so that people can make their own AOSP builds (you know, with gingerbread coming and all)
I tried to run the build (after execuring crlcad)but it stays on htc black screen for 5 seconds and then reboot the phone...i've just copied your archive in Android folder...
FD10 said:
I tried to run the build (after execuring crlcad)but it stays on htc black screen for 5 seconds and then reboot the phone...i've just copied your archive in Android folder...
Click to expand...
Click to collapse
me too, keep rebooting, the android folder is desire_cs btw.
dandiest said:
me too, keep rebooting, the android folder is desire_cs btw.
Click to expand...
Click to collapse
i second that emotion!! me 2 or maybe i just dont fully understand the info on post 1????
JR
cool i love mdj
but always willing to try out new stuff
thank you Sir!
sorry i forgot to mention extract archives to desire_cs directory (case sensitive) on SD card not Android.
if you still get reboot try format sd card from wince then extract again.
it happened to me when i switched to 8gb card from 2gb but was fine after card reformat.
for me i suspect dosfsck may caused a kernel crash but could not test as it not happened again after format
Thanks a lot!!!
Keep it up!!!
So what's the difference between this and any other sense rom out there?
Sent from my HTC Desire using XDA App
cedesmith said:
if you still get reboot try format sd card from wince then extract again.
Click to expand...
Click to collapse
sorry bud i dont understand that sentence what is wince and how do i go about using it to format my sd card, is formatting under my OS (win7) not good enough? because i still get a reboot.
Regards JR
Mods: If you think this should go in general section feel free to move it, thanks.
I built a script that will install the new camera (nexus based), it will replace all necessary files to get the camera working as well as hastarins 8.5.1 modules (to get wifi working and all) and finally liblights and libhtc_ril_wrapper (might be overkill, but it works)
Instructions: Unzip CamScript folder to SD Card (anywhere is fine) and then as su (adb shell or terminal emulator, anything you use to run bash scripts is ok) run cam_install.sh
Note: It will replace zImage in either /sdcard/HD2ONE or /sdcard/Android; it will not work if you have a kernel in a folder different to those so edit your startup.txt file if necessary.
Credit goes to hastarin for the kernel and camera files
-OCM
V1.5: Everything should work now, i've tested on stock HD2ONE_Latest. Backup versions of all modified files are saved in /data/cam_backups.
Good job
Sent from my HTC HD2
Thanks for the script,
Noticed that in the Replace_Libs function you copy liboemcamera.so to libcamera.so.old overwriting the other libcamera.so.old!!
I'm guessing you don't want to do that??
I've just tried this on my JDMS 1.5 that already had Hastarin8.5.1 old camera and my Andorid wouldn't reboot.
Anyone got any tips on troubleshooting non-restarting phones??
I've got the HTC splashscreen and I can adb into the phone but from there on I'm a bit lost.
bobjbain said:
Thanks for the script,
Noticed that in the Replace_Libs function you copy liboemcamera.so to libcamera.so.old overwriting the other libcamera.so.old!!
I'm guessing you don't want to do that??
I've just tried this on my JDMS 1.5 that already had Hastarin8.5.1 old camera and my Andorid wouldn't reboot.
Anyone got any tips on troubleshooting non-restarting phones??
I've got the HTC splashscreen and I can adb into the phone but from there on I'm a bit lost.
Click to expand...
Click to collapse
try chmod -R 777 /system/lib/*
bobjbain said:
Thanks for the script,
Noticed that in the Replace_Libs function you copy liboemcamera.so to libcamera.so.old overwriting the other libcamera.so.old!!
I'm guessing you don't want to do that??
I've just tried this on my JDMS 1.5 that already had Hastarin8.5.1 old camera and my Andorid wouldn't reboot.
Anyone got any tips on troubleshooting non-restarting phones??
I've got the HTC splashscreen and I can adb into the phone but from there on I'm a bit lost.
Click to expand...
Click to collapse
Same problem here...i've tried your script on the HD2ONE 0.3.3 Rc2 version. I've followed all the instructions and now im stuck on the green HTC logo.....Can you please tell me how to Manually apply this script because i think it doesnt work properly....thanks
I don't think this fix is going to work with build that is based on cm6 .1 rc2 because it gets boot loops on the htc screen. I will still give this fix a try and report back....
Edit
Tried it and it did not work for me, black screen on the camera...
atoore said:
Those new builds that is based on cm6.1 rc2 wont work with any new kernels with the new drivers. I will try this fix and report back...
Click to expand...
Click to collapse
What do u mean??
ocm7 reported he succefully applied new camera drivers to the HD2ONE_latest build that is based on the cm6.1 rc2...
Any solutions????
Working on it, shouldnt take more than a few minutes
ocm7 said:
Working on it, shouldnt take more than a few minutes
Click to expand...
Click to collapse
Really thanks, anyway tomorrow (now its late night here) i'm going to reinstall the latest HD2ONE build and then applying your script again (still if you told me how to manually add all the stuff it would be better for me)
Uploaded the fixed version, worked on stock HD2ONE_Latest, so it *should* work on other builds but i cant guarantee this. If you're stuck on boot screen you can try running this new script and see if it works, if it doesnt replace system.ext2 with stock from your build then run the script. Sorry about the initial errors...
So, I used your 1.5 script and this time managed to reboot back into Android.
Everything seemed fine except that my camera still had a green tinge when used with the flash.
THEN I realised that I still had the root directory in the Android folder. So assumed/guessed that the libs were being oerwritten by those in the root folder.
So I renamed root to root_old, re-ran your script, rebooted.
Hung like a mule!!
Restoed original JDMS 1.5 system.ext2, rebooted fine.
Except now my accounts don't sync, my camera takes a picture then hangs
I will get it all back thanks to Titanium Backup
--
Looking at your script it's what I've always been doing to install new Kernels. The green tinge was there when I first tried Hasatrin 8.5.1
The only thing that you do different is include a build.prop file (which is wildly different from mine BTW).
So, my question, is it something in the build.prop that is stopping the grren tinge? If so, what??
TIA
as far as i know, this new lib file in CM or MIUI build make camcorder freeze..does it? or does it not?
I have a weird problem: when i'm in terminal emulator, then su (#), but when i try to type run cam_install.sh it says....run: not found......i think it doesnt recognize the run command..is it possibile??
Is there a way to avoid using this script and SIMPLY manually put all the needed files in the correct directories??
Thanks in advance!!!
P.S. I'm doing that in a HD2ONE stock unmodified latest build...
clockcycle4mobile said:
I have a weird problem: when i'm in terminal emulator, then su (#), but when i try to type run cam_install.sh it says....run: not found......i think it doesnt recognize the run command..is it possibile??
Is there a way to avoid using this script and SIMPLY manually put all the needed files in the correct directories??
Thanks in advance!!!
P.S. I'm doing that in a HD2ONE stock unmodified latest build...
Click to expand...
Click to collapse
Try
Code:
./cam_install.sh
there is no 'run' command in linux. Programs are executable and are run by just typing their name.
Of course the file has to be chmod'd to be executable too, but the ./ gets around that mostly.
It didn't work with HD2ONE-0.3.3.RC2
Just stuched in HTC welcome page
bobjbain said:
Try
Code:
./cam_install.sh
there is no 'run' command in linux. Programs are executable and are run by just typing their name.
Of course the file has to be chmod'd to be executable too, but the ./ gets around that mostly.
Click to expand...
Click to collapse
Thanks, i've done everything....android rebooted correctly but black screen on camera application...
ocm7 tell me how you made the camera application work properly....i tried and didn't work...
Mine says on every file "file not found" or something like that.
lesjaw said:
as far as i know, this new lib file in CM or MIUI build make camcorder freeze..does it? or does it not?
Click to expand...
Click to collapse
It does if you record on the highest setting (720p)
hhhawasly said:
It didn't work with HD2ONE-0.3.3.RC2
Just stuched in HTC welcome page
Click to expand...
Click to collapse
Worked perfectly for me on a stock system, are you sure all the files got copied right (no errors printed)?
clockcycle4mobile said:
Thanks, i've done everything....android rebooted correctly but black screen on camera application...
ocm7 tell me how you made the camera application work properly....i tried and didn't work...
Click to expand...
Click to collapse
Since everyone is having such a hard time getting it to work here are the manual instructions:
Replace your current kernel with hastarins 8.5.1
Replace Camera.apk in /system/app
Replace libcamera.so, liboemcamera.so, libOmxCore.so, libOmxVdec.so, libOmxVidEnc.so in /system/lib
Optional but recommended: replace lights.qsd8k.so in /system/lib/hw and rename or remove /system/lib/hw/lights.htcleo.so also replace libhtc_ril_wrapper.so in /system/lib
replace bcm4329.ko, tun.ko and cifs.ko in /system/lib/modules
place 99complete in /system/etc/init.d and chmod it to 755 (important!)
replace build.prop to fix green tint (I got it from the green tint fix thread and just replaced some lines to match CM6)
reboot
Also, i said these libs were nexus based so if your build is desire based it simply wont work
ocm7 said:
It does if you record on the highest setting (720p)
Worked perfectly for me on a stock system, are you sure all the files got copied right (no errors printed)?
Since everyone is having such a hard time getting it to work here are the manual instructions:
Replace your current kernel with hastarins 8.5.1
Replace Camera.apk in /system/app
Replace libcamera.so, liboemcamera.so, libOmxCore.so, libOmxVdec.so, libOmxVidEnc.so in /system/lib
Optional but recommended: replace lights.qsd8k.so in /system/lib/hw and rename or remove /system/lib/hw/lights.htcleo.so also replace libhtc_ril_wrapper.so in /system/lib
replace bcm4329.ko, tun.ko and cifs.ko in /system/lib/modules
place 99complete in /system/etc/init.d and chmod it to 755 (important!)
replace build.prop to fix green tint (I got it from the green tint fix thread and just replaced some lines to match CM6)
reboot
Also, i said these libs were nexus based so if your build is desire based it simply wont work
Click to expand...
Click to collapse
Well I've done every single step you wrote but still camera app is totally black after reboot.....this is very weird since i've used the same build you used (nexus based) but my result is so different from yours....
Hey all!
I am new to the NC community, but have quite a bit of experience working with my Samsung Fascinate. I have some minor themeing experience.
Just ordered a NC from ebay for 119 and was curious what sort of setup (ROM, KERNEL) etc are stable and working well?
What OC is stable?
Is Honeycomb worked out as fully functional?
I have done some sticky reading, and I would like to just make a bootable sdcard, and leave the Emmc alone for now.
What are the recommendations?
Thanks!
CM7 is definitely the best for this. Honeycomb did not have access to the sources and so was more of a demo.
We hope that ICS may make it onto the NC one day but for now CM7 gives a really good stable experience.
You can choose to use the latest stable CM 7.1 or choose to use one of the late nightly builds. There has been an issue with what is called SOD (Sleep of death) where the device occasionally doesn't wake up from sleep and needs a reboot. This was an issue even with 7.1 on some devices. It now appears to have been solved but requires an extra patch which should make it into a nightly soon.
Installing onto a boot SD or emmc is both easy tasks and there are plenty of guide material on this. If you are going to boot from SD make sure you use a Sandisk card (e.g. a class 4 16 or 32GB). These give much better performance when used in this role over other brands.
If you end up primarily using CM7 and not reverting to stock then I would say it is worth going full emmc. It is easy to revert to stock if you ever need to. Running from emmc gives more overall memory and makes management and back up more straightforward.
Most Nooks OC fine up to 1300 and remain stable. The boost in performance is fairly dramatic. For some reason some graphics benchmarks peak at 1200MHz and get worse if the OC is pushed higher. I guess the GPU may end up clocking lower if the main clock is pushed too far.
Thanks BOB!
I had used CM7.1 on my fascinate, but it was a short stay as it wouldn't play nice with wifi at my house. Hopefully that's not the case with the NC.
How is MIUI on the NC? From what I see it has done pretty good. Do you have any particular experience with it?
As far as kernels, what are the stable ones by name?
I have plenty of experience of writing ROMS to the internal memory with CWM so I shouldn't be too far off if I need to do that, or choose to go that route.
If you use cm7 can you still use the stock Nook Reader? or what is the reader of choice?
I believe you can only use the Stock reader in the Stock ROM. There is a standard Nook App for Android but it is not the same. Works OK for your standard reading etc but not as nice as the stock reader.
If you want to use the Stock Reader and CM& then I think your choices are ...
1) Run CM7 on the SD card and boot into Stock whenever you want to use the Stock reader.
2) Make a Stock ROM set up on a SD card, Install CM7 on emmc and reverse the procedure of 1.
3) Install a dual boot Stock and CM7 off the emmc. At start up you then choose whether to boot into Stock or CM7 and the SD card remains fully usable as data.
I did use method 3 for a while when I first started with Nook but I so rarely went into stock and I don't really need to access the stock reader that I gave up and redid the emmc as full CM7.
I did try MIUI out but I ended up reverting to standard CM7 really just to keep compatibility with other CM7s I use.
Advantages of Internal Dual boot over SDcard boot?
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles
charles_w said:
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles
Click to expand...
Click to collapse
I personally would stay away from dual booting on emmc. It plays with your internal partitions which is not a good idea. I would keep stock on emmc and the newly released 7.2-RC1 on SD. By making one simple change to stock you can have both systems share the 32GB card and not have to take the card out ever. The boot menu of CM7 makes it very easy to boot between the two.
Sent from my Nook Color running ICS and Tapatalk
Thanks for the reply.
leapinlar said:
By making one simple change to stock you can have both systems share the 32GB card
Click to expand...
Click to collapse
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles
charles_w said:
Thanks for the reply.
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles
Click to expand...
Click to collapse
It does have advantages, you don't have to worry about SD card switches, etc. I was just saying it is non-standard and risky to your partitions. One of the partitions, (2) is vital to your system (it has your serial #, etc in it) and since you have to write to the partition table to accomplish dual boot, you risk the possibility of corrupting it as you are setting up dual boot. But a lot of people have done it with no problem.
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file. But there are plenty of rooting threads that tell you how. You can even unroot after you have fixed the file if you want. The other way is to change the file on your PC using adb. Both methods take a little extra effort, but it is worth it to not have to swap SD cards all the time. Both systems then share the SD card storage area. By making this change, I know of no advantage to dual boot and it is much safer (and you already have the SD set up).
And you use the boot menu to select which operating system you want to boot to. That comes with CM7. (But you know that having run CM7 for a year).
Sent from my Nook Color running ICS and Tapatalk
found the link for sharing sdcard
leapinlar said:
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file.
Click to expand...
Click to collapse
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles
charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmx to be rooted.
Charles
Click to expand...
Click to collapse
good job!
Sent from my Nook Color running ICS and Tapatalk
charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles
Click to expand...
Click to collapse
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2
Sherip said:
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
The free version of ES Explorer allows mounting system as r/w.
Little update....
I have found that the best setup I have found so far is CM 7.2 RC1 (03042012) with V6 (Update 9 RC6.9) supercharger set to option 9 (super 1000HP) supercharge (link for the V6 is on Mr666's page). The ICS transitions included in RC1 are swift and with the supercharger everything is super smooth. I can say I have noticed a small increase in my battery life as well. I toyed around with the UV/OC settings and returned to the sleep of death's I was getting on 7.1. So I re-flashed and just have left everything set to default in the peformance settings that comes with 7.2. So far, no SOD"s and I have a very capable tablet.
leapinlar said:
The free version of ES Explorer allows mounting system as r/w.
Click to expand...
Click to collapse
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2
Sherip said:
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
You don't need to mount it where racks said. You can mount it in /data, which you should be able to make r/w. Where it says /mnt/nooksys, substitute /data/nooksys. First go to /data with es explorer and manually create the nooksys folder (you need to set your home directory to / in es explorer before you can see /data). Then follow his steps except don't do the mkdir command since you did it manually. And wherever it says /mnt substitute /data.
Edit: you need to modify the mount command, it now needs to have appended to the end, -t ext4. - Scratch that. It's only necessary if you are trying to do it from CM9. CM7 works OK as written.
I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2
Sherip said:
I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
What is the -o in the line for? And you manually created the folder first? And you did check the root button in settings?
All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"
Sherip said:
All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"
Click to expand...
Click to collapse
After you created the folder, did you check it. By that I mean open it? It should be an empty folder. Exit out of the folder, but leave Es explorer open. Use the home key to get back to home screen so you can open terminal. I don't know much about es, maybe it has to stay open to keep root access.
Edit: the :not found error is saying it cannot understand the mount command. Are you using all lower case? Very important. Terminal does not like upper case.