I have noticed a couple threads popping up about cm7 nightlies. I figured we could use one thread to post all of our finding, tweaks, workarounds, ect.
I'll try and keep on top of this thread and make the OP some what of a FAQ.
Stable Releases: http://download.cyanogenmod.com/?type=stable&device=harmony
Latest Google Apps: http://goo-inside.me/google-apps/latest/7/
List of all Google Apps: http://goo-inside.me/google-apps/
Nightlies are to be considered as alpha/beta builds. They are compiled every night (usually but not always) and include the latest additions to CM.
Disclaimer directly from CyanogenMod forum:
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Nightlies: http://download.cyanogenmod.com/?type=nightly&device=harmony
Nightly Mirror (thanks to DrMacinyasha): http://goo-inside.me/cm/harmony/
This is a "changelog" showing all of the commits to CM that pertain to the harmony
http://cm-nightlies.appspot.com/?device=harmony
This is a flashable zip file that I have created to backup the vold.fstab file and replace it with one that mounts the internal storage as /sdcard.
http://goo.gl/DS8u9
EDIT: maybe this can become a sticky so its easier to find
I agree. Thanks for gathering all the information. I closed my thread because I saw many duplicate posts. I really hope that this thread becomes sticky thread.
This is a flashable zip file that I have created to backup the vold.fstab file and replace it with one that mounts the internal storage as /sdcard.
Click to expand...
Click to collapse
Voila! Worked like a charm. Thanks so much!
maxdamage2122 said:
This is a flashable zip file that I have created to backup the vold.fstab file and replace it with one that mounts the internal storage as /sdcard.
http://goo.gl/DS8u9
Click to expand...
Click to collapse
This worked great for setting emmc to sdcard... could this zip be updated to also set the external sdcard to sdcard2?
Edit...nevermind, now I see that the file maps the external sdcard back to emmc. I will check it out after I get my sdcard formatted.
jhedfors said:
This worked great for setting emmc to sdcard... could this zip be updated to also set the external sdcard to sdcard2?
Edit...nevermind, now I see that the file maps the external sdcard back to emmc. I will check it out after I get my sdcard formatted.
Click to expand...
Click to collapse
It's a Gingerbread thing - Gingerbread uses emmc and sdcard, Froyo used sdcard and sdcard2.
I just want to be sure here...
I flash the ROM then the gapps then the vold.fstab zip?
Also, where do I put my titanium back up license? Usually on the root if my sd card but this whole emmc/sd card has my head spinning.
Thanks.
dlaciv12 said:
I just want to be sure here...
I flash the ROM then the gapps then the vold.fstab zip?
Click to expand...
Click to collapse
That is correct.
dlaciv12 said:
Also, where do I put my titanium back up license? Usually on the root if my sd card but this whole emmc/sd card has my head spinning.
Thanks.
Click to expand...
Click to collapse
I don't have a titanium pro license but I do believe it is just an app you install. If it is then you would just install it and it would be place in /data not /sdcard or /emmc
dlaciv12 said:
I just want to be sure here...
I flash the ROM then the gapps then the vold.fstab zip?
Also, where do I put my titanium back up license? Usually on the root if my sd card but this whole emmc/sd card has my head spinning.
Thanks.
Click to expand...
Click to collapse
You may have already figured this out, but you would put the license file in the root of the internal sd now that it is being seen as the sdcard. I have this same setup.
Nightly 38 is up. Nothing big added just some bugfixes.
Another noob question: Does this include an updated kernel too? Or do I need to flash a gingerbread kernel?
rancidcrab said:
Another noob question: Does this include an updated kernel too? Or do I need to flash a gingerbread kernel?
Click to expand...
Click to collapse
I installed the nightly v38 this morning and discovered that my cifsmanager didn't work. I flashed Clemsyn's GB v9 and now cifsmanager works. I noticed that it replaced Pershoot's kernel but I didn't pay attention to which version that was before I flashed.
Unfortunately, now my USB mount doesn't work. Oh well, I can still boot to CWM for my USB stuff.
marcjw said:
I installed the nightly v38 this morning and discovered that my cifsmanager didn't work. I flashed Clemsyn's GB v9 and now cifsmanager works. I noticed that it replaced Pershoot's kernel but I didn't pay attention to which version that was before I flashed.
Unfortunately, now my USB mount doesn't work. Oh well, I can still boot to CWM for my USB stuff.
Click to expand...
Click to collapse
in order to use cifs, push the module in to place from lib...gz to your system. then in cifs manager load it in.
http://droidbasement.com/db-blog/?p=1728
ViewSonic Gtab/Malata Zpad (Gingerbread):
lib-2632.36_gb.tar.gz (kernel modules)
Download: lib-2632.36_gb.tar.gz
rancidcrab said:
Another noob question: Does this include an updated kernel too? Or do I need to flash a gingerbread kernel?
Click to expand...
Click to collapse
the nightlies contain the latest kernel, 2.6.32.36
pershoot said:
in order to use cifs, push the module in to place from lib...gz to your system. then in cifs manager load it in.
Click to expand...
Click to collapse
Thanks, cifsmamager now works. Back to running your kernel.
It's now moving into STABLE stage ... wooo wooo ...
Stable released!
Stable is posted now:
http://mirror.teamdouche.net/?device=harmony
Forgive my ignorance but which GAPPS file do I need to use from the posted link? There are several and I am unsure which to use. Thanks in advance!
vipergtsr6 said:
Forgive my ignorance but which GAPPS file do I need to use from the posted link? There are several and I am unsure which to use. Thanks in advance!
Click to expand...
Click to collapse
In the chart at the top choose the only one for CyanogenMod 7. It should be labelled gapps-gb-20110307-signed.zip
Ill update the OP and make it clearer.
Cm7.1 nightlies have begun to roll out.
I also updated the OP.
Can anyone get any version of swype working in cm7? That is the last piece I need.
Related
Sorry can't post in dev section yet but drod was nice enough to let me get my hands on cyanogen mod 7 release candidate 2 and said I could share. This is not an official release and not supported yet. To flash place zip on internal sd boot in clockwork wipe data and install zip.
I used clockwork .08
Update: fix for internal sd problem
Credit goes to drod2169
Updated Install
www.mediafire.com/?usumbwxusn8vnzj
Here is a link to the gapps for Gingerbread that gives full market out of the box
I installed the rom first and let it boot up then went back in clockwork and installed gapps. Don't know if it matters.
http://goo-inside.me/gapps/latest/7/universal/
When you say the internal SD doesn't work, do you mean it doesn't show up at all? Or could it possibly be /mnt/emmc?
Roadzero said:
Sorry can't post in dev section yet but drod was nice enough to let me get my hands on cyanogen mod 7 release candidate 2 and said I could share. This is not an official release and not supported yet. only problem I saw is the internal sd doesn't work. To flash place zip on internal sd boot in clockwork wipe data and install zip. Clockwork sees the internal sd just not cm 7.
Sorry can't post links yet
w w w dot mediafire dot c o m /?wxbtl23g46vxvho
Click to expand...
Click to collapse
Anyone tried this yet?
Went thru the archive, seem genuine, I may give it a try later, I'll post mileage...
Lets make this easy: http://www.mediafire.com/?wxbtl23g46vxvho
Up and running as I type. Looks really nice. Put soft buttons on status bar which will help me at night not having to feel for the home and back buttons on the side since they don't illuminate. Market is full and working quite nicely as it backed up all of my purchases and dl's right away.
Only thing not working for me so far is the docking station. Still a nogo. Just came off of bitrix to try this......
Well done!!!
dezufnoC said:
Up and running as I type. Looks really nice. Put soft buttons on status bar which will help me at night not having to feel for the home and back buttons on the side since they don't illuminate. Market is full and working quite nicely as it backed up all of my purchases and dl's right away.
Only thing not working for me so far is the docking station. Still a nogo. Just came off of bitrix to try this......
Well done!!!
Click to expand...
Click to collapse
FruitLoop here, even after wipe... curious... retrying...
Tried wipe, removing SDHC cart, reflash still a FruitLoop oh weel back to
my trial of Calkulin's G-Tab v1.0 [ 3991 l Battery Saver script w/ Profiles
which boot...
P00r said:
FruitLoop here, even after wipe... curious... retrying...
Tried wipe, removing SDHC cart, reflash still a FruitLoop oh weel back to
my trial of Calkulin's G-Tab v1.0 [ 3991 l Battery Saver script w/ Profiles
which boot...
Click to expand...
Click to collapse
Odd it worked fine for me coming out of vegan 5.1.1 just by wiping data. you could try wiping system or re downloading the zip
Where is the recovery folder? I downloaded the update...... .zip folder and it wouldn't load the rom, CWmod said it was "bad"
tomgillotti said:
Where is the recovery folder? I downloaded the update...... .zip folder and it wouldn't load the rom, CWmod said it was "bad"
Click to expand...
Click to collapse
What version clockwork are you using? I used .08
Installed this last night from a link he sent on twitter. Think its the same version. Only issue i see so far is my sdcard is not showing up. I get sdcard for internal memory but not for my actual card. A message comes up when I insert it saying that one was inserted then it says its safe to remove. Not sure how to mount it. I don't see it in /mnt either.
P00r said:
FruitLoop here, even after wipe... curious... retrying...
Tried wipe, removing SDHC cart, reflash still a FruitLoop oh weel back to
my trial of Calkulin's G-Tab v1.0 [ 3991 l Battery Saver script w/ Profiles
which boot...
Click to expand...
Click to collapse
Calkulin has a nice format all zip (see first post here)that you flash like a rom before flashing a new rom. works good only 1 step instead of many. only thing it doesn't seem to format is Delvik so that has to be done manually but it cuts out a few steps in the rom prep work.
This rom has the same shape icons in the right corner as the vegan roms and the same notification icons as cm rc2. The mounts are sdcard and emmc for external. The res has been changed so some apps wont scale properly. If it wasn't for that I would have kept using it because I prefer the minimal notification icons compared to vegans experimental new icons.
qubit76 said:
This rom has the same shape icons in the right corner as the vegan roms and the same notification icons as cm rc2. The mounts are sdcard and emmc for external. The res has been changed so some apps wont scale properly. If it wasn't for that I would have kept using it because I prefer the minimal notification icons compared to vegans experimental new icons.
Click to expand...
Click to collapse
On my tab the internal storage is mapped to /sdcard while /emmc is empty. my external (actual) sdcard is nowhere to be found. settings-storage shows the sdcard as having 13.07gb total. my actual sd card is 4gb so this is confirming its actually the internal memory. All the Vegan roms showed my sdcard as mounted at /sdcard2. was just curious as to how I should go about mounting my sdcard so i can access it? I have no issues with this memory mounting setup just curious how to get my card to be mounted. Can i type something in a terminal to mount it?
I realize that the vegan series is a moddified version of cm and this is an attempt to be true cm tweaked to run on our tabs and that some things are gonna be different. So if I am missing something with the sdcard mounting please let me know. I think Drod2169 does great work and have loved rubix on my X for months now.
I jumped on this rom from Bitrix and my sd card reads exactly the same as it did before as sdcard while my internal is emmc. It seems as if it's not liking the change from your previous association to this new association of internal/external storage. Were you using a pre-Gingerbread rom before? If so check out this link for the association of storage files...this may help
I also use rootexplorer and have no problems accessing/copying/moving files etc.
I was on Calkuins beta, then wiped and installed vegan ginger experimental 3/8/11. After it started and loaded apps from market Drod2169 sent me a link to this one on twitter so I wiped and installed this. Maybe that the kernel didn't install right our something.will try to redownload and try again.
Sent from my DROIDX using Tapatalk
Unofficial? So it isn't really Cyanogen 7 RC 2 then. Just saying.
adampdx said:
Unofficial? So it isn't really Cyanogen 7 RC 2 then. Just saying.
Click to expand...
Click to collapse
It is cm 7 rc2 I say unofficial release because it may be changed slightly before they officially announce its release. If you don't want it you don't have to use it, I just thought I would post it for people that do.
So. It turns out that if I knew how to read I could have fixed my problem a while ago. The first post says right on it that it was updated to fix sdcard problem. The version I had was from before this "fix". Downloaded updated one and installed. All is well. Market seem good so far all items are mounting speed seems good. Don't use youtube so cant comment on video but flash works on the sites i've tried it on. Thanks Drod2169 for giving us some more of your time.
I'm curious as I've ran bittrix's unofficial and several of gojimi's Ginger vegan. Do installed apps show up on the market under My Apps? On every other Ginger rom I've tried, Market-My Apps just shows nothing. Love gingerbread but it makes it a pain trying to keep apps up to date. Also does purchasing work, or does vending FC when trying to?
Thanks
Hi all,
here's the official ClockWork Mod recovery, built from the Gingerbread branch.
Disclaimer: this piece of software is not for the unexperienced and might bring you in a situation you can't resolve yourself. So don't use it if you fear the potential danger of bricking your device. I am responsible for nothing related to this piece of software and therefore won't help. If you decide to use it anyway you agree to be ultimately responsible for all consequences that may occur. So you have been warned !
I don't use ODIN, so I only provide the images file.
If someone want to make the Odin files, just reply in this post with the download link so I can update this post.
recovery-clockwork-5.0.2.8-2.zip
Install through adb:
Code:
$ bsdtar xfv recovery-clockwork-5.0.2.8-1.zip
$ adb push recovery-clockwork-5.0.2.8-1.img /sdcard/
$ adb shell
# dd if=/sdcard/recovery-clockwork-5.0.2.8-1.img of=/dev/block/mmcblk0p13
Odin package by broodplank1337
recovery-clockwork-5.0.2.8-2.tar.md5
Changelog said:
5.0.2.8-2:
* Mount /dev/block/mmcblk0p28 as /emmc
* Mount /dev/block/mmcblk1p1 as /sdcard
5.0.2.8-1:
* First
Click to expand...
Click to collapse
Suggestions are welcome.
Cheers!
may i know what's the difference this and feamod?
It's working, but I'll keep Feamod 1.4 since there is no difference at all except the logo
annoymous1234 said:
may i know what's the difference this and feamod?
Click to expand...
Click to collapse
Sure, from the FeaMod thread:
FeaCore Phoenix includes:
-BFQ I/O scheduler 2 r1
-SIO I/O scheduler
-OC up to 1.8 GHz
-smartassV2 governor (ondemand is default)
-JFS and CIFS support
-tun included
-bootanimation support
-new boot sound
- I8150 GPU librarys
-cleancache
Click to expand...
Click to collapse
This one is the upstream vanilla clockworkmod: https://github.com/CyanogenMod/android_bootable_recovery
I don't apply any patch.
broodplank1337 said:
It's working, but I'll keep Feamod 1.4 since there is no difference at all except the logo
Click to expand...
Click to collapse
This is vanilla. If you install this _after_ the feamod recovery you'll notice no change because the FeaMod installs the GPU driver and a custom boot, and this recovery do not remove them.
bashlnx said:
Sure, from the FeaMod thread:
This one is the upstream vanilla clockworkmod: https://github.com/CyanogenMod/android_bootable_recovery
I don't apply any patch.
Click to expand...
Click to collapse
That list is a list of Kernel features, the recovery can't have those tweaks inside,
Feacore Phoenix = Kernel
Feamod = Recovery
broodplank1337 said:
That list is a list of Kernel features, the recovery can't have those tweaks inside,
Feacore Phoenix = Kernel
Feamod = Recovery
Click to expand...
Click to collapse
Right, my fault. I misunderstood things.
The differences between this and the FeaMod recovery are these:
https://github.com/manveru0/FeaMod-Recovery/commits/gingerbread/
Every manveru0 commit (like replacing sd-ext by sdcard or changing some message) isn't included in the official one. Also, this one has some upstream change that aren't included in the FeaMod recovery because manveru0 left.
Hey, thank you for this. Finally someone is working again on the CWM recovery.
I just want to ask you something about a problem which I encountered during the development of my ROM Crybernation with AROMA-INSTALLER.
Its about the colors in CWM.
The colors on the screen seems to be right, but when I take a sreenshot in CWM with DDMS I get a red picture.
In AROMA there is a blue tint in CWM. But the screenshots have the correct colors. ( See attachments below)
So amarullz the developer of AROMA-INSTALLER said that there is something wrong with the framebuffer.
I'm not that familiar with this but perhaps you have an idea what could be wrong. So you think you can solve this problem?
Also could you delete the additional "No's", like manveru0 did it?
Thank's Man Nice work
I didn't think you would do it so fast
crybert said:
I'm not that familiar with this but perhaps you have an idea what could be wrong. So you think you can solve this problem?
Click to expand...
Click to collapse
I've no time right now to play with the framebuffer, but I'll let you know if I find something weird.
crybert said:
Also could you delete the additional "No's", like manveru0 did it?
Click to expand...
Click to collapse
No, sorry but I wanna keep it vanilla
tomsteel1 said:
Hey, Does this support "Rom Mananger" then?
Anyway, Thanks for carrying on CWM for i9001. Nice to see another dev working for our device, Too bad manveru0 left.
Anyway thanks again!
Click to expand...
Click to collapse
For some reason this doesn't work with ROM Manager yet. I asked some CWM dev, and they said ROM Manager works only if the ClockworkMod is installed using it.
I'll try to play a bit with it.
I suppose "newer" FeaMod backups can still be restored with this "older" version?
It detects my internal sdcard as the external and vice versa
nail16 said:
It detects my internal sdcard as the external and vice versa
Click to expand...
Click to collapse
Looking at the CWM code, the /emmc is called "the internal card".
I googled a bit, and the behavior is right.
thanks
odin http://www.mediafire.com/file/du42yxqswg5a3vl/recovery.tar.md5
still i didn't try it
good luck
mazen912 said:
thanks
odin http://www.mediafire.com/file/du42yxqswg5a3vl/recovery.tar.md5
still i didn't try it
good luck
Click to expand...
Click to collapse
with me Odin crashes when add the file as one package, somebody else have this problem??
wintel_mac said:
I suppose "newer" FeaMod backups can still be restored with this "older" version?
Click to expand...
Click to collapse
That never work... you have to set a backup BACK with the same cwm versios as you made the backup.
Someone correct me if i'm wrong....?
Here is a fixed odin version:
http://www.mediafire.com/download.php?z84wnnn55tihqmq
broodplank1337 said:
Here is a fixed odin version:
http://www.mediafire.com/download.php?z84wnnn55tihqmq
Click to expand...
Click to collapse
thx you your fixed version works fine!!
---------- Post added at 06:07 PM ---------- Previous post was at 05:57 PM ----------
Sh0rty007 said:
That never work... you have to set a backup BACK with the same cwm versios as you made the backup.
Someone correct me if i'm wrong....?
Click to expand...
Click to collapse
think your right, with feamod i could not restore data backed up with 1.4 and do a restore with 1.2. flashing back to 1.4 and there where no problems, so i think it will be the same for cwm
sorry guys i made it hurry
bashlnx said:
Looking at the CWM code, the /emmc is called "the internal card".
I googled a bit, and the behavior is right.
Click to expand...
Click to collapse
in cwm emmc is external storage, i find that behavior strange
By popular demand, I am bringing to you CM10.1 that you can install into Nook's internal ROM.
Note, this version totally overwrites your ROM, so back up everything important before proceeding. This is not a dual-boot solution as before, you do loose B&N ROM for good after installing this.
This is work in progress, yadda yadda.
Simplified instructions if instructions below don't work for you or you cannot follow them.
Get emmc-cwm-early2.1.img.gz, gunzip and write it to an sdcard of at least 1G in size (all content on that card will be lost).
Download CWM recovery (text) or TWRP recovery (gui) zip if you want internal recovery to be replaced with CM one (if you don't know what is it about, then you need ONE of these).
Also download latest binary zip from CM nightlies: http://download.cyanogenmod.com/?device=ovation
Add all these files + whatever other packages you might need right away on to the sdcard.
Boot from that sdcard, and install recovery (if desired) and the cm10.1 binary and whatever else you put there.
Erase /data (During initial install only. this is important to avoid crashes on bootup! Naturally, make sure you have copies of whatever important info from there).
unmount /sdcard and remove the card from the Nook. You might need to use this sdcard for your recovery needs in the future should EMMC content become badly damaged, so probably a good idea to have a copy of it somewhere.
Congrats, now on reboot you'll get into cm10.1 on your Nook HD+.
When you need to get into recovery, you can either do "reboot to recovery" in reboot menu (need to enable that in settings) or reboot the nook, and when you see original nook boot logo, press and hold power + home buttons for about 4 seconds.
If you plan to use USB Host feature, you will need a gender changer, as B&N decided not to release a special cable so far. The control to enable USBHost is in quick settings panel (slide down in the top right corner of the screen to bring it up). (QS controls are not available in CM nightly builds so you'll need to install the switcher app for now if you need it).
Known problems:
- Nook app reports incompatible in market (workaround1: just sideload it ; workaround2: change ro.product.device to nookhdplus in build.prop) - This is because they specifically blacklist Nooks! Note that workaround #2 will actually kill your sound, so revert back when you are done.
- Certain sdcards still remain unstable.
- Google Earth crashes when pressing "my location" button (but works fine otherwise).
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (not really needed, as you can use Quick Settings panel): USBHostSwitcher.apk
Changelog:
13/08/09 - We are official part of CM now, yay! Further updates will be at http://download.cyanogenmod.com/?device=ovation
13/08/01 - cm-10.1-20130801-UNOFFICIAL-ovation-emmc.zip
- Data usage display should work now
13/07/19 - cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip
- Picked some kernel fixes from omapzoom tree that I think would be useful for us too, this includes some voltage changes (decreases).
- Disabled hwui scissors optimization as it seems to be doing more harm than good.
- Reverted too greedy davlik vm settings
13/07/16 - cm-10.1-20130716-UNOFFICIAL-ovation-emmc.zip *Experimental*
- Update wifi drivers to R5.SP3.06
13/07/11 - cm-10.1-20130712-UNOFFICIAL-ovation-emmc.zip (backup link)
- Added Apple keyboard support
- Updated to CM-10.1.2 for security fixes
13/07/10 - cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip
- Updated to CM-10.1.1 for security fixes
13/07/08 - cm-10.1-20130708-UNOFFICIAL-ovation-emmc.zip
- NTFS and ExFAT support from upstream
13/07/06 - cm-10.1-20130706-UNOFFICIAL-ovation-emmc.zip
- redone touchscreen sensitivity changing mechanism. (app to control touchscreen sensitivity NookTouchscreenSensitivityAdjuster-4.apk)
13/07/04 - cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip
- upgraded to fixed SGX DDK [email protected] (this fixes Google Earth, and a bunch of games)
13/07/03 - cm-10.1-20130703-UNOFFICIAL-ovation-emmc.zip Experimental
- experimental touchscreen sensitivity change
- usb ids changed to match stock
- swap support enabled
13/06/30 - cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip
- Serial number is now visible in Android
- usb audio now actually works (only for output)
13/06/29 - cm-10.1-20130629-UNOFFICIAL-ovation-emmc.zip
- in-kernel bluetooth
13/06/26 - cm-10.1-20130626-UNOFFICIAL-ovation-emmc.zip Experimental
- cpu frequency changes for screen on scenario, new sgx binary blobs.
13/06/24 - cm-10.1-20130624-UNOFFICIAL-ovation-emmc.zip
- more kernel drivers for bt hid, usb 3g modems and gps devices
13/06/15 - cm-10.1-20130615-UNOFFICIAL-ovation-emmc.zip
- WiFi Direct and BT tethering are now working
- /sdcard now points to internal storage.
13/06/13 - cm-10.1-20130613-UNOFFICIAL-ovation-emmc.zip
- Boosted speaker volume. If you do not like new loud volume, flash this reversal zip after every ROM update: quietvolume-2.zip
- zinio now should work out of the box
13/06/11 - cm-10.1-20130612-UNOFFICIAL-ovation-emmc.zip
- Fixed HDMI audio
- Added USB audio support
13/06/08 - cm-10.1-20130608-UNOFFICIAL-ovation-emmc.zip
- Fixed nav bar settings crash
13/06/05 - cm-10.1-20130605-UNOFFICIAL-ovation-emmc.zip
- USBHost access is now conveniently located in QuickSettings. (IF you use some mod that disables quick settings, you still need my old ugly USBHost switcher app, just sideload it).
- now any (one at a time) usb storage should be automounted no matter how you plug it.
13/06/02 - cm-10.1-20130603-UNOFFICIAL-ovation-emmc.zip
- Forced USB Host support.
13/05/30 - cm-10.1-20130530-UNOFFICIAL-ovation-emmc.zip
- No Nook-specific changes, based on CM10.1-RC3
13/05/27 - cm-10.1-20130527-UNOFFICIAL-ovation-emmc.zip
- Fixed microphone input volume
- Kernel change to hopefully better work with some sdcards.
13/05/12 - cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip
- Fixed A2DP audio
- Fixed booting when not connected to PC/charger.
13/05/11 - cm-10.1-20130511-UNOFFICIAL-ovation-emmc.zip
- Should fix sgx crash on startup for those affected -- not.
- Cover close now should sleep the device (please test)
- Updated screen properties to highdpi (though that did not fix Nook app compatibility in market)
- Baselined on CM10.1-RC2
13/05/10 - cm-10.1-20130510-UNOFFICIAL-ovation-emmc.zip
- Wifi battery drain should be gone now.
13/05/05 - cm-10.1-20130505-UNOFFICIAL-ovation-emmc.zip
- Fixed mmc presentation, BT, sdcard mounting.
13/05/04 - cm-10.1-20130504-UNOFFICIAL-ovation-emmc.zip initial release.
Thanks for this though.
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Also I don't think cm10 is needed really.
I think its best to put the work into cm10.1 as its the latest platform and try bring that up to the same stage as cm10.
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
HiddenG said:
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
Click to expand...
Click to collapse
Is the reboot to 99% problem solved ? This is the biggest issue to me.
sorrowuk said:
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Click to expand...
Click to collapse
Same method as Bauwks, B&N forgot to fix it, they fixed some other possible vectors only.
I was holding to this knowledge hoping that it would be useful on next B&N reader, but it does not look like they'll release another omap-based one, so no need to keep suffering anymore.
So here's hope whatever they release next, the debugging code will remain in place
HiddenG said:
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Click to expand...
Click to collapse
Yes, this does overwrite stock ROM, so no dualboot.
While it's possible to perform some hair-splitting by putting multiple kernels into boot partition, that's quite a bit of hassle + all the /data splitting, so I decided to not go that way, at least yet.
There are performance differences. I did not perform any real studies, but I was shocked at how fast the install phase in cwm works compared to sdcard.
lchen5 said:
Is the reboot to 99% problem solved ? This is the biggest issue to me.
Click to expand...
Click to collapse
Yes, it is solved by removing the ROM, so nothing is left there that could complain about cards with too many partitions
Awesome
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
aszid said:
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
Click to expand...
Click to collapse
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Click to expand...
Click to collapse
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Follow up question
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
For restore (note, I did not really test any of these steps, but that's how it should unfold):
boot into recovery image from sdcard you made at the beginning.
Upload the backup boot image there (adb push mmcblk0p4 /tmp)
then do adb shell and in there write the image in place:
dd if=/tmp/mmcblk0p4 of=/dev/block/mmcblk0p4 bs=1048576
then do:
mount /bootdata ; rm /bootdata/BootCnt
The removal of BootCnt will tell stock u-boot to force factory restore.
now remove sdcard and reboot, the Nook will do factory restore and you are back to some sort of early 2.0.0 B&N release.
verygreen said:
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Click to expand...
Click to collapse
I've been trying to examine what you have done here, and have most of it figured.
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
A suggestion on the CWM recovery.fstab. Change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
Click to expand...
Click to collapse
Yes, it's pretty straight-forward, and that was one of the goals. Unlike Kindle where you need to jump through some crazy hoops due to Amazon design decisions, Nook is significantly more relaxed.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
Click to expand...
Click to collapse
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
The only difference between this CWM and sdcard cwm for sdcard installs are: removed repartitioning code in postboot script and updated fstab to point back at emmc.
A suggestion on the CWM recovery.fstab, change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Click to expand...
Click to collapse
Aha, thanks. I'll try this and it'll probably solve the remaining CWM problems for me.
Also need to do twrp image, I guess.
verygreen said:
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
Click to expand...
Click to collapse
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
And if you make those mods to the recovery.fstab, then users can use that CWM to reflash back to stock using the B&N zips.
leapinlar said:
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
Click to expand...
Click to collapse
Whoops, forgot to remove.
This is how I zero out sdcard content so it better compresses before uploading it somewhere.
jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Got it going
Thanks Verygreen and Leapinlar.
I got it installed and I saved the boot partition just in case. I hopefully will not be needing to restore, but it is nice to know that I can.
The installed ROM appears snappy and I will report back any issues I discover.
my sdcard is working great after updating the mount. Thanks!
leapinlar said:
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
Click to expand...
Click to collapse
verygreen said:
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Click to expand...
Click to collapse
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Thanks for all the great work!
aszid said:
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Click to expand...
Click to collapse
There's no great logic in my recovery, just an image I use to test-drive my installs for now.
So you can use whatever other recovery you like.
This mod for CM11 on moto_msm8960 brings back the classic sdcard mount we know from devices like the Nexus One.
No more cluttering of /data with files which should go to sdcard.
Features:
- External sdcard mounted as /sdcard
- Internal memory fully available for /data
Installation:
- Have a nandroid backup of /boot and /system at hand if something goes wrong
- Simply flash the zip over your existing CM11 installation
- Wipe data is not necessary but will help if you have problems.
Deleting only the data of the concerned apps should be sufficient. (Only apps storing data on sdcard are effected)
- Files which were on the emulated sdcard can be found at /data/media/0. This is also the location where you have to put your zip files to be able to flash them with OpenRecovery.
Method:
Adjusting of following CM11 files to be in line with Nexus One example configuration according to:
http://source.android.com/devices/tech/storage/config-example.html
boot.img
- init.qcom.rc
- fstab.qcom
framework-res.apk
- storage_list.xml
See my github for details: https://github.com/S-I-M-O-N/android_device_motorola_moto_msm8960
Disclaimer:
This was developed and tested on a Photon Q but should work on all moto_msm8960 devices with CM11.
I cannot be held responsible if anything goes wrong while using this mod.
Thank you to everyone this work is based on: Cyanogenmod team for providing CM11, Google for providing Android and everybody else
Download
I will try to keep this thread updated and provide a flashable zip for the latest CM11 snapshot.
See attachment at the bottom.
Regards,
Simon
Downloads for:
cm-11-20140609-SNAPSHOT-M7-moto_msm8960.zip
cm-11-20140708-SNAPSHOT-M8-moto_msm8960.zip
cm-11-20140916-SNAPSHOT-M10-moto_msm8960_jbbl.zip cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl.zip
cm-11-20141112-SNAPSHOT-M12-moto_msm8960_jbbl.zip
Cool, Thank you
Any updated version for CM11 M8 build?
I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.
S-I-M-O-N said:
I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.
Click to expand...
Click to collapse
Yeah..I've tried it over M8 and my phone stucked in bootloop. Thanks for your work. I've missed my sdcard as primary storage since JellyBean days. I'm glad I can use my 32gb sdcard usefully.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Download for M8 added.
S-I-M-O-N said:
Download for M8 added.
Click to expand...
Click to collapse
Thanks a lot..Downloading it now.
Hmm so I'm guessing the likelihood of this working on nightly builds isn't good?
You could give it a try.
Nandroid backup boot and system, then flash the mod.
If it screws up, just go back and restore boot and system.
Apart of that I think we should wait a few days to see if we get a moto_msm8960_jbbl M9 build. If yes I will, make the patch for it. If no, I will pick the latest nightly.
After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon
Please...!
A new version.
The M10 CM is out now for the Photon Q!
S-I-M-O-N said:
After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon
Click to expand...
Click to collapse
Download for M10 added. Have fun!
Download for M11 added. Enjoy!
Are there any issues with this mod when flashing a new ROM? Say you're going from a snapshot build to a newer snapshot build, or even from a snapshot build to to a stable build?
Flashing a new ROM will overwrite the mod. So you are using the emulated sdcard on internal memory. Apps which stored data on the sdcard will not find their data, just like when you install the mod the first time.
Nevertheless if you stick to CM11 snapshots for which the mod has been adapted and you flash another release, just flash the mod for this release while you are still in recovery and you will have no problems.
Made the mistake of installing a nightly restored my backup. But can't get the classic sdcard back. Have re flashed no joy. Is there a way to get it back, with out doing a clean install?
Did you create the backup including the mod?
Did you restore system and boot?
Did you try to just flash CM11 M11 + MOD for M11?
Do you have bootloops?
YDid you create the backup including the mod?
No
Did you restore system and boot?
Not sure about the boot, will check.
Restored backup m11 and flashed sddcard mod.zip.
Do you have bootloops?
No
Might be a mute point.
The restore is eating my battery!
Doing a clean m10 updating to m11 Now.
Will install sdcard mod and see how it goes.
Thanks.
I should know here in the next 15 min.
OK!
With out flashing sdcard mod after m11 installed I now have
4 gig.
My guess is my back up was not m11 or JB bootloader?
Thanks for the fast reply!
The PQ has no KK bootloader, so every (working) ROM for the PQ is based on the JB bootloader.
As long as you haven't modified your /system after updating to M11 and flashing gapps and sdcard_mod, you should be fine by just do the same again.
But it's always risky, from a nightly to a snapshot. Downgrades are also risky and might not work.
You might just wait until M12 comes out and use your backup to restore it.
M12 is here
[ROM][7.1][UNOFFICIAL] CM14.1 for Nexus 7 2012 (grouper)
*** Disclamer
By downloading and installing this ROM you agree that you do so at
your own risk, and that you understand that it probably voids your
warranty. (But does anyone still have an active warranty on this 2012
device?)
Introduction
@AndDiSa's AOSP 7 builds look pretty nice, but I needed something that seamlessly upgrades from CM13. @GtrCraft who provided our CM13 builds has moved on to other devices, so we need a new CM maintainer. I may not be the right person for that job... but I can at least share the build I made for myself. Perhaps someone will be motivated to join the fun or even take over.
[Images on screenshots tab.]
Installation instructions
Back up your data and previous ROM with TWRP 3.0.2.
Download from link below.
Wipe system, cache, dalvik.
Also wipe data unless you are coming from CM13.
Install the ROM.
Optionally add opengapps-pico.
With default settings it will give an error about insufficient space. To avoid that, first copy this gapps-config-grouper.txt file, perhaps edit it to your taste (instructions here), then copy to the device in the same directory as the opengapps zip. The opengapps updater-script will look for it there when you install opengapps.
Reboot.
WAIT for system to settle before you decide it is slow. Some of the app optimization which used to happen during initial boot now seems to happen in the background. When it's finished, responsiveness will improve.
Download
cm-14.1-20161226-UNOFFICIAL-grouper.zip (AndroidFileHost)
Credits / Thanks
Google / AOSP
CyanogenMod
@AndDiSa for AOSP 7.1 -- I use his kernel tree directly, and many of his device tree mods
@GtrCraft for the CM13 tree upon which mine is based
XDA:DevDB Information
Unofficial CM14.1 for Nexus 7, ROM for the Nexus 7
Contributors
aaopt, AndDiSa,GtrCraft
Source Code: https://github.com/aperomsik/cyanogenmod_android_device_asus_grouper/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-25
Last Updated 2016-12-31
Reserved
Changelog
Nearly all builds include CM sync -- only mentioned specifically when it was the main point of the build.
20161226 (AndroidFileHost)
LiveDisplay works (due to upstream work).
20161212 (AndroidFileHost)
NFC
20161208 (AndroidFileHost)
CM sync, including 7.1.1r4
20161130 (AndroidFileHost)
Stock camera works.
20161125 (DevHost)
Initial posting.
seems to be pretty stable so far but i cant get pico gapps to install even after installing the rom with the gapps-config.
There is a 3.4 kernel build for grouper which was helpful for cm13. Can you incorporate that into your build ?
why is this not even on development thread?
is this based on anddisa's device,vendor trees? cuz that build is super fast. i am downloading anyway.
turnert said:
seems to be pretty stable so far but i cant get pico gapps to install even after installing the rom with the gapps-config.
Click to expand...
Click to collapse
Sorry about that. I meant to say .gapps-config goes with the gapps zip, not with the ROM. Corrected, and also edited for clarity. If it still doesn't work for you, look at the log file it generates in the same folder as the zip, and make sure it says it read your config file.
abhifx said:
why is this not even on development thread?
Click to expand...
Click to collapse
I had originally put it in development, but it took me too long to fill in the devdb new project page... after it made me reload the page and reenter some things, apparently I wound up in general by mistake.
abhifx said:
is this based on anddisa's device,vendor trees? cuz that build is super fast. i am downloading anyway.
Click to expand...
Click to collapse
Yes, when I saw how fast @AndDiSa's AOSP 7 ROM was, I had to try a CM14 build. I'm using his kernel and vendor trees, and many of his recent device tree commits cherry-picked into a fork of @GtrCraft's CM13 device tree.
Requested mods to move this to development section.
Also can't install gapps with the given script. Anyone up for new gapps zip?
abhifx said:
Also can't install gapps with the given script. Anyone up for new gapps zip?
Click to expand...
Click to collapse
Please pastebin your resulting open_gapps_log.txt, and send me the link . You should find the log file on the device in the directory where you had put the gapps zip and config files. For comparison, mine is here.
aaopt said:
Please pastebin your resulting open_gapps_log.txt, and send me the link . You should find the log file on the device in the directory where you had put the gapps zip and config files. For comparison, mine is here.
Click to expand...
Click to collapse
will post it in the evening, i dont think gapps is picking up the config file, should the config file go inside the zip file? i am just pasting it outside the zip file.
Frankly the ROM is working fine, however i have yet to lock gps and test it which is my main usage.
After seeing CM booting, i would love to see other derived ROMs (AICp, RR etc)
Maybe you can post a guide others may build it too (i dont have the disk space or the bandwidth to do it anyway)
abhifx said:
will post it in the evening, i dont think gapps is picking up the config file, should the config file go inside the zip file? i am just pasting it outside the zip file.
Frankly the ROM is working fine, however i have yet to lock gps and test it.
Click to expand...
Click to collapse
Not in the zip file... Just alongside, in the same folder on the device (or usb stick if you install via OTG) where the Gapps zip is.
Sent from my MotoG3 using Tapatalk
The config files name needs to be "gapps-config.txt" or ".gapps-config". I just tried the first option an gapps installed just fine!
abhifx said:
will post it in the evening, i dont think gapps is picking up the config file, should the config file go inside the zip file? i am just pasting it outside the zip file.
Click to expand...
Click to collapse
I was having issues as well with the config file. I tried putting it in all kinds of places, but no dice.
I ended up using the Aroma Open Gapps package which worked great.
Haven't tried much on this ROM yet, but things feel snappy.
hawkshot said:
I was having issues as well with the config file. I tried putting it in all kinds of places, but no dice.
I ended up using the Aroma Open Gapps package which worked great.
Haven't tried much on this ROM yet, but things feel snappy.
Click to expand...
Click to collapse
ah yes.. Aroma Gapps, which keeps on cancelling this huge package. oh well will try renaming the text file
---------- Post added at 01:25 PM ---------- Previous post was at 12:49 PM ----------
ok this was even more weird, i copied the files in a separate directory (the config file was in txt format as suggested by @gothier) and this worked. earlier everything was in the root directory and nothing worked no matter was was the file extension, hidden or not.
Thanks OP.
I've successfully installed the ROM on my Grouper device.
Also, I've installed Opengapps via CF's Flashfire app and it worked very well.
Thank you for the rom.
I updated from CM13, install gapps with config , only rename it to ".gapps-config-grouper". I use all from USB drive via OTG for all my android devices.
All work fine.
Even in pico gapps package I had to exclude some apps so it could be installed. I've written in in gapps-config.txt this way:
GoogleTTS
calsync
A bug
When I pull down the notification/ quick settings, the device crashes and reverts to lock screen.
eNVy said:
When I pull down the notification/ quick settings, the device crashes and reverts to lock screen.
Click to expand...
Click to collapse
havent crashed on me yet.
@aaopt, it seems anddisa has a made some changes wherein camera is also working, maybe you can update the same for CM14.1?
It doesnot happen always. Sometimes only.