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
Related
maxdamage2122 said:
Since "official" nightlys have not been compiling for the g-tablet, I have been compoiling them myself on my personal computer. I'll compile the source every so often and upload it here https://www.dropbox.com/s/w3vhon1u5a2orsk/smb_a1002/kang?v=l. The time stamp in the file name (MMDDYYYY-HHMM) is the time that the repo sync was done.
In the meantime I'm setting up an old computer that I have as a buildbot to automatically compile every night for us. I'll let you guys know when I have it up and running.
Click to expand...
Click to collapse
I thought it might be nice to get a thread going for discussion on the CM7 port for harmony for our gtablet device. There are nightly builds which are starting to incorporate some great things such as video acceleration and the new google release of 2.3.4 could be around the corner. In fact some 2.3.4 code made it into nightly#60.
I am in no way associated with CM7. If someone from CM7 or someone in some way associated with CM7 wants to run this thread or create a similar one please do so.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Rule #1 of CyanogenMod: Don't ask about release dates.
CM7 Harmony Stable Releases
http://mirror.teamdouche.net/?device=harmony&type=stable
CM7 Harmony Nightly Releases
http://mirror.teamdouche.net/?device=harmony&type=nightly
Changelog
http://cm-nightlies.appspot.com/?device=harmony
Tablet Tweaks II (original TT is already incorporated)
http://forum.xda-developers.com/showthread.php?t=1002000
For firsties...
How-To Guide:
(slightly edited from Wiki http://wiki.cyanogenmod.com/index.php?title=Viewsonic_G_Tablet:_Full_Update_Guide)
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced the device with a Google account, then the contacts, calendar, Gmail & select other Google-related data will not be lost and will come back after the next sync. However, you should backup anything you want to keep that is not stored on the SD card:
Bookmarks,
Applications; use Titanium Backup or the Astro File Manager, for example,
Any application data not on the SD card.
It would also be a good idea to backup everything stored on the SD card in the rare case the SD card must be formatted to resolve any major problems.
Backup for Root Users is a free application that can assist with backing up your data.
Installing ClockworkMod Recovery
For this guide, it is not necessary to root the Viewsonic G Tablet in order to flash CyanogenMod. You can simply install ClockworkMod Recovery & continue on.
Warning: Installing ClockworkMod Recovery on the Viewsonic G Tablet will void the warranty.
Download the ClockworkMod package: Download
Unzip the ClockworkMod package & copy the recovery folder & the update.zip to the root of the internal memory (NOT in any folders & NOT to the removable SD card).
Power off the Viewsonic G Tablet and reboot holding the Volume Up button and the Power button until the device is in the stock recovery.
While in the stock recovery, use the Volume buttons to navigate to the apply update.zip & press the Home button to select it.
Once the it the update.zip is applied the Viewsonic G Tablet will have ClockworkMod Recovery. Please continue to the next section.
Flashing CyanogenMod
*******************
adampdx said:
...according to this tweet we're not supposed to flash between the stable releases and the nightlies. ....
Click to expand...
Click to collapse
*******************
jerdog said:
Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.
Click to expand...
Click to collapse
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The Viewsonic G Tablet should now boot into CyanogenMod.
Having issues with finding your Internal Storage?
Check your fstab. CM has a different paradigm. See below from maxdamage2122
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
Edit: Thanks and props to the CM team and all involved. No thanks to me, I am just a copy/past whore.
Edit: Removed RomManager Method (thanks badfrog and jerdog)
Edit: Added reference to fstab mod. Thanks maxdamages 2122
Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
And that bad frog is right. Use bekit's 0.8 GTab recovery and forget about Rom Manager. You'll just end up having to nvflash...
Thanks!
MC
thebadfrog said:
Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
Click to expand...
Click to collapse
Are you sure about this? If so I dont mind editing that part of the CM instructions.
Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.
Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.
MicroChip said:
Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
Thanks!
MC
Click to expand...
Click to collapse
Been a long time droid, dInc user. I had sent you a PM about half way through the OP but decided what the heck. I hope this helps keeps discussion in one place for our gtab and CM7 (soon to be 7.1)
Oozura said:
Are you sure about this? If so I dont mind editing that part of the CM instructions.
Click to expand...
Click to collapse
Yes, I'm sure he is sure about this. Do NOT use Rom Manager to install any of the roms or to update CWM. Only use bekit 0.8 recovery.
I don't even install Rom Manager on my Gtab.
thebadfrog said:
Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.
Click to expand...
Click to collapse
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.
+10000 I learned this the hard way on day one.
Sent from my CM7 GTablet
Oozura said:
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.
Click to expand...
Click to collapse
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).
RomManager method removed
OP Edited. Thanks.
jerdog said:
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).
Click to expand...
Click to collapse
I quoted your post. Link was already there to correct version in the clockwork mod package. thanks.
Thank you. There is something flakey about these devices and they don'y like Rom Manager
So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk
Oozura said:
So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I am. No issues to report, camera is still grainy. Video playback is still great.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Hardware Decoding?
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?
adampdx said:
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?
Click to expand...
Click to collapse
Progress is being made but we aren't there yet. Did you try mobo player? Engage software decoding and you'll be good to go.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
I've been using RockPlayer and havent had any issues. Most notably for me though was YouTube HD videos now play with no lag.
I think Irs421 is right. Its progress but not complete hardware acceleration until Nvidia releases GB drivers I would guess.
I figured as much. Progress, even slow progress, is good. I'm liking CM7 so far any how.
Just got my T-Mobile G2X on October 18. My very first Android phone!
Played with it stock for two days, then backed it up, rooted it and flashed the latest CyanogenMod.
After installing about a dozen apps from the App Store and getting things nice and settled, I noticed that startup for my G2X was pretty slow, maybe around one minute? So, I plugged it into USB and ran Diskeeper. Told me fragmentation on the G2X internal drive was 1.41 (very high).
There is conflicting information out there about whether defragging an Android internal flash drive makes any difference. I shut down my G2X, restarted, then connected to USB and defragged the internal flash.
Boots to the lock screen in 22 seconds.
Never had to do that on my G2x and i'm running Cm7 Stable. And i can honestly say that boot-up was always less than 20 secs.
I think it may be a placebo effect since CM7 doesn't use the internal storage as the main storage, plus mine always boots in about 20 seconds.
Actually, mine did take a long time to startup. Maybe it was because I had done so much to it in a short period of time.
Just turned my phone off and timed it, exactly 20 seconds to lock screen. Running CM7 177 nightly.
Joseg1320 said:
...Running CM7 177 nightly.
Click to expand...
Click to collapse
Sorry for the newbie question but... what does "CM7 177 nightly" mean?
I know CM7 = CyanogenMod 7.
EEngineer said:
Sorry for the newbie question but... what does "CM7 177 nightly" mean?
I know CM7 = CyanogenMod 7.
Click to expand...
Click to collapse
http://cm-nightlies.appspot.com/?device=p999
lannister80 said:
http://cm-nightlies.appspot.com/?device=p999
Click to expand...
Click to collapse
O.K., so to update, I download the latest CM7 .ZIP to my SD card, then from ROM manager do Install from SD Card.
This will install the new CM7 firmware while keeping my phone's flash data intact.
Am I correct?
Another thing to remember, you can't use windows tools to defrag, (which personally I don't see the point in defragging a linux file system.) The filesystem that is used by android on our phones is ext4. (ext3 for stock) Windows can't even read the filesystems for the most part, so all you did was defrag the internal sd card memory, (which on cm7 is at /mnt/emmc), didn't do anything with the filesystem.
Android, especially on a new install, takes a while to settle down. You usually can't gauge speed for a day or two, because you need to fully create the dalvik-cache. Once that happens, then see how fast it loads up.
EEngineer said:
O.K., so to update, I download the latest CM7 .ZIP to my SD card, then from ROM manager do Install from SD Card.
This will install the new CM7 firmware while keeping my phone's flash data intact.
Am I correct?
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
Yeah it will flash the newest version of CM7 while still keeping your apps and data.
Sent from my LG-P999 using XDA App
Thanks!
Seems that if these are the recent stable releases:
http://download.cyanogenmod.com/?device=p999&type=stable
I'll stick with stable releases until I get to know Android better.
EEngineer said:
Thanks!
Seems that if these are the recent stable releases:
http://download.cyanogenmod.com/?device=p999&type=stable
I'll stick with stable releases until I get to know Android better.
Click to expand...
Click to collapse
The newest nightlies are ahead of the stable releases.
You can follow the progress here.
http://forum.xda-developers.com/showthread.php?t=1108201
I don't flash the nightlies one after another when a new one comes out. I'm still on Nightly 177 and I have no problems with it, so I still have it on my phone.
But if you have problems with your phone, you can try flashing the newest nightly.
Here you can see the what has been added to the newest nightly.
http://cm-nightlies.appspot.com/?device=p999
Do the nightlies include the Google apps?
What about my installed apps? And I have one paid app (ROM Manager) and want to flash so I don't lose it.
EEngineer said:
Do the nightlies include the Google apps?
What about my installed apps? And I have one paid app (ROM Manager) and want to flash so I don't lose it.
Click to expand...
Click to collapse
Paid apps stay in the market. Cm7 does not include gapps and must be flashed seperately.
Sent from my LG-P999 using XDA App
EEngineer said:
Do the nightlies include the Google apps?
What about my installed apps? And I have one paid app (ROM Manager) and want to flash so I don't lose it.
Click to expand...
Click to collapse
Once you flash CM7 for the first time onto your phone, you have to also flash the Google apps because they don't come with CM7, but you only have to do that once. When you flash a nightly you still keep all your apps including Google apps.
EEngineer said:
Just got my T-Mobile G2X on October 18. My very first Android phone!
Played with it stock for two days, then backed it up, rooted it and flashed the latest CyanogenMod.
After installing about a dozen apps from the App Store and getting things nice and settled, I noticed that startup for my G2X was pretty slow, maybe around one minute? So, I plugged it into USB and ran Diskeeper. Told me fragmentation on the G2X internal drive was 1.41 (very high).
There is conflicting information out there about whether defragging an Android internal flash drive makes any difference. I shut down my G2X, restarted, then connected to USB and defragged the internal flash.
WOW! Boots to the lock screen in 22 seconds!
I recommend defragging your Android internal flash.
Click to expand...
Click to collapse
You don't need to defrag a Linux-based system. The internal memory that application saw as being fragmented was likely the "internal sdcard" partition which has nothing to do with your system booting.
When you flash a new rom, the first boot takes significantly longer because it has to build the dalvik cache. Its only on the first boot that it takes that long, or possibly on the boot after installing or restoring several apps. All subsequent boots will be much quicker. Mine boots in less than 20 seconds and I have several dozens of apps installed.
Joseg1320 said:
Once you flash CM7 for the first time onto your phone, you have to also flash the Google apps because they don't come with CM7, but you only have to do that once. When you flash a nightly you still keep all your apps including Google apps.
Click to expand...
Click to collapse
O.K., so, I've already flashed CM7 7.1.0.1 (Oct 11). I installed the Google Apps after that, and two T-Mobile apps (from .apk) off my backup.
So now if I flash Nightly 177 over my existing install, I keep all my existing apps. Do I use ROM Manager to update to Nightly 177, or do I boot into ClockworkMod Recovery and flash Nightly 177 from there?
When I tried to download from ROM Manager, I got a popup that said "install additional update zips off the sd card?" I can't find any explanation for that - what is it asking for and I do need it?
Joseg1320 said:
I don't flash the nightlies one after another when a new one comes out. I'm still on Nightly 177 and I have no problems with it, so I still have it on my phone.
Click to expand...
Click to collapse
The last stable release still does not support HDMI.
Does Nightly 177 support the G2X's HDMI interface?
FYI, the first boot will always take long because the system has to build the cache, I think. Something like that
Any reboots following the initial boot should be fairly quick
Hi Guys,
I'm running the 21y update for my G2x and not Cyanogen MOD. Maybe Cyanogen Mod 7 is stable on a G2x, but CM9 is awful on my Dell Streak 7 (much better after dropping trebuchet 0.1 and switching to ADW Launcher), so I'm apprehensive about trying it. However, it takes roughly 3 minutes to boot my phone and it's very annoying. Is it possible I've configured it to rebuild my dalvik cache at every boot? How would I check that? Any other suggestions? Is there a boot log with the program being loaded and the load times?
Thanks,
Christian Blackburn
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
Finally here it is, the long awaited CM10 for Nook HD+ (early snapshot, anyway).
This codebase is currently hardcoded to work from sdcard only.
How to build from source (you need to meet all the usual cm10 build prerequirements),
Get the source:
Code:
mkdir android/system
cd android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/repo
chmod a+x ~/repo
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
wget -O .repo/local_manifest.xml https://github.com/verygreen/android_manifests/raw/master/ovation-jb/local_manifest.xml
repo sync -j16
(device repo on github)
(temp kludge for source kernel build: get my kernel from https://github.com/verygreen/green_kernel_omap and put it to kernel/bn/ovation (use ovation-3.0 branch for 3.0.31 kernel or ovation-aosp-kernel for 3.0.50), then put B&N source distro copies of wlan and wpan kernel dirs to external inside of kernel dir, and also desired version of sgx proprietary-open tar file into external/sgx)
Build:
Code:
. build/envsetup.sh
lunch cm_ovation-userdebug
. vendor/cm/get-prebuilts
mka bacon
In the out/target/product/ovation output dir you'll have the update file generated: cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip
If you do not want to build from source, here's my current (as of this post, see bottom for newer versions) binary snapshot: cm-10-20130511-UNOFFICIAL-ovation-sdcard.zip
(additionally there's emmc version, follow installation instructions here, but use this install file: cm-10-20130511-UNOFFICIAL-ovation-emmc.zip)
You will also need updated cwm image: sdcard-cwm-early4.img.gz
For first time install only (you will need 4G or bigger sdcard, smaller ones are not supported and not tested):
gunzip cwm image and write it to your sdcard (entire sdcard not just one partition of it), use either dd on Linux/MacOS or Win32 Image Writer for those impaired by Windows. Make sure to use sdcard rated for fast small IO for best results.
(Note: There is now experimental recovery image that does not require adb that's currently documented in this post)
Insert the card into the Nook and reboot the nook, CWM should start.
(This will also automatically repartition the card into a correct layout no matter the size (but no smaller than 4G).
In the CWM:
Go to "mounts and storage", choose "mount /sdcard".
Press power button to go back to the main menu.
Now do
Code:
adb push cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip /sdcard
Also push whatever other zip files you want to install to /sdcard too.
(if you don't have operational adb, you can also just turn off the nook at this stage, put zip files to volume named "CM10SDCARD" (not "boot"), then put sdcard back into nook and start it again)
Next, choose "install zip from sdcard", and then "Choose zip from sdcard" and first cm-...zip, and then whatever other packages you have the need to install.
When done installing, press the power button to go one level up in the menu and then choose reboot.
This will reboot you into CM10.
If you ever need to get back to CWM later, use either "reboot to recovery" power menu, or reboot, and once B&N nook logo shows up, press and hold power and home keys together for about 4 seconds.
To reboot into stock nook software, just poweroff, remove sdcard, then poweron.
Caveats:
- Current sdcard layout is ~800M system and ~900M data for less than 16G and 2G data for 16G+ cards, the rest is a separate sdcard (because having sdcard to live on data is kind of dangerous). I am still taking feedback on these sizes better to change these early on while there are not a lot of users.
- This snapshot uses B&N binary kernel from 2.0, it happens to oops in mtp_open if you have mtp storage mode enabled and plug into a computer, so steer clear of it for now I guess, this will be fixed later. (if your nook reboots when plugged into computer or right on boot while plugged - this is it, likely to happen after first install).
- /cache is shared with stock ROM, helps for slower sdcards at the expense of slower boots when you switch your OS from stock to CM10 or back.
- Upgrade from 20121209 snapshot note: that snapshot had bad kernel that had problems with sdcards. Most advisable thing is to redo entire install (after downloading new, cwm-early3 image first). You might also be able to just install kernel from the update.zip and write it to the first partition on the sdcard, that shuld also fix all issues and will let your existing cwm to work to flash this new image.
Things that I know are not working:
- Coming out of sleep sometimes there's a crash (this is related to wifi, the workaround is to disable wifi while sleeping in the options).
- Rebooting to stock with sdcard still in causes stock to hang at 99% booting and sit there, simply pop out the sdcard and it will finish booting.
- on-headphones microphone is not currently used even if present (I now believe this is actually not a bug, and stock has the same behavior).
- Bluetooth signal strength is very low
- Hulu+ and other such things requiring DRM do not work.
This is now at feature-parity with stock B&N ROM, I believe (other than DRM).
Experimental versions:
Other than the stable version above, there are some experimental versions below that are tested before (hopefully) being promoted to the stable status.
01/07 version with a different kernel, otherwise same as 12/31
01/08 version with a recompiled B&N kernel, otherwise same as 12/31
01/19 version with a yet another different kernel, updated CM10 base and default dpi/screen size changes
02/12 Some CM10 changes from upstream and updated wifi drivers from B&N 2.0.6 code drop (hoping that it will fix the annoying coming out of suspend crash - nope, it did not.)
02/20 Don't reboot into emmc stock on crash, it does us no good. Revert Z-axis in accelerometer for hopefully better responsiveness.
wifi should no longer drain battery when sleeping, cover close will blank screen, gfx issues hopefully fixed
Enjoy.
Finally, a major step in the right direction. Thank you very much for your efforts.
Thanks for that.
One question before try it:
formating /sdcard from CWM will not format the internal "sdcard" directory of the Nook?
Thank you very much. Your work is always appreciated.
The ability to mount and use the internal storage would be great.
Many thanks for this, got it working for some reason the format sdcard step seemed to fail - but got it working by manual format under linux.
Now have gapps and everything else I need installed - so will play with it later but so far seems to run very smooth.
Agree that seeing nook internal storage would be good
Wow, fantastic, will try it tonight. Just checking, no problem using 64G card? Also, I'm assuming for the moment it leaves the complete data structure in tact on the B&N internal memory? Just mostly not mounted? Reason I ask is its a shortcut to get the apps that are already installed there, especially the B&N specific ones. Otherwise I could pull with ADB.
Thanks again!
verygreen said:
Caveats:
- Current sdcard layout is ~800M system and ~900M data, the rest is a separate sdcard (because having sdcard to live on data is kind of dangerous). I am taking feedback on these sizesm better to change these early on while there are not a lot of users.
- There's no access to "sdcard" on internal nook drive, though this could be organized if people think that's useful.
- This snapshot uses B&N binary kernel from 2.0, it happens to oops in mtp_open if you have mtp storage mode enabled and plug into a computer, so steer clear of it for now I guess, this will be fixed later. (if your nook reboots when plugged into computer or right on boot while plugged - this is it).
- /cache is shared with stock ROM, helps for slower sdcards at the expense of slower boots when you switch your OS from stock to CM10 or back.
Click to expand...
Click to collapse
Nice, just some quick questions here.
when you said build, I assume you means cross-compile, right? I know most people are not gonna compile stuff themself, and just use the binary. But so people know if they wanna learn since x86 and arm are different architecture. Just compiling from x86 isn't gonna work.
I agree the size is a bit bloated ATM. Even the gigantic Galaxy Note 2 is about that size also.
The access to internal SD can be useful. Assuming you brought 32GB version of Nook, then you have like 25GB+ worth of storage sitting there. If possible it should be mounted(only old /mnt/sdcard area), whether that be to /mnt/sdcard or /mnt/int_sdcard
I notice you build this based on JB version of android, which is what 4.1 or 4.2? But still using the B&N kernel which is 4.0.4? I'm sure some of the stuff works. I made that mistake as well when attempt to put Play market on the nook earlier.
Thanks for your hardwork.
someone0 said:
Nice, just some quick questions here.
when you said build, I assume you means cross-compile, right? I know most people are not gonna compile stuff themself, and just use the binary. But so people know if they wanna learn since x86 and arm are different architecture. Just compiling from x86 isn't gonna work.
Click to expand...
Click to collapse
Yes, it's cross-compiling, which is still building.
The cm repos provide necessay cross-compilers and all that stuff, though.
I agree the size is a bit bloated ATM. Even the gigantic Galaxy Note 2 is about that size also.
Click to expand...
Click to collapse
So the better sizes are?
I notice you build this based on JB version of android, which is what 4.1 or 4.2? But still using the B&N kernel which is 4.0.4? I'm sure some of the stuff works. I made that mistake as well when attempt to put Play market on the nook earlier.
Click to expand...
Click to collapse
build is based around 4.1.2.
B&N kernel is pretty much inline with JB (3.0.31), so it works pretty well (other than the mtp_open oops). I'll switch to building it from source anyway, but this will take some time.
dbh369 said:
Wow, fantastic, will try it tonight. Just checking, no problem using 64G card?
Click to expand...
Click to collapse
I don't have anything this big, so only tried 16G.
Also, I'm assuming for the moment it leaves the complete data structure in tact on the B&N internal memory? Just mostly not mounted?
Click to expand...
Click to collapse
Mostly. /cache is shared so this one is modified.
Also to get recovery we are reusing stuff in /bootdata (BCB and boot counter).
Reason I ask is its a shortcut to get the apps that are already installed there, especially the B&N specific ones. Otherwise I could pull with ADB.
Click to expand...
Click to collapse
You should not be sharing apps between the two, they might be different version too, anyway.
Is there any reason to think this would not work on the NOOK HD as well? I understand that the reason it may have not been tested is that no one is willing to test it, but if it "should work" then I'd be willing to purchase the HD and test and report results.
Verygreen, thank you for all your continued hard work with the CM/NOOK bases.
Thanks for this.
A few things , you are maybe already thinking of implementing these:
1. It would be good if you could dual boot both systems with a menu or holding a volume button to boot to stock nook os, instead of having to take out the sd card, save a bit of time and ease (the slot is quite hard to open )
2. Access to internal storage would be good. I have 32gb nook, so not being able to use 25gb of free space on the internal storage is not great, but I'm sure its quite easy to fix. Is it just a matter of mounting it correctly ?
Everything seems great, with the tearing issue do you know what the problem is ?
jay_ntwr said:
Is there any reason to think this would not work on the NOOK HD as well? I understand that the reason it may have not been tested is that no one is willing to test it, but if it "should work" then I'd be willing to purchase the HD and test and report results.
Verygreen, thank you for all your continued hard work with the CM/NOOK bases.
Click to expand...
Click to collapse
I could be proved wrong but I don't think it will work for you on a HD. It doesn't work on a HD for me....
With Nook HD, try rebooting a few times with card installed see if it goes to cwm,
tried on HD
CelticWebSolutions said:
I could be proved wrong but I don't think it will work for you on a HD. It doesn't work on a HD for me....
Click to expand...
Click to collapse
I tried the CWM card in my HD. I can concur that the HD doesn't boot from the card, it just goes to rooted stock.
ArcSmurf said:
Many thanks for this, got it working for some reason the format sdcard step seemed to fail - but got it working by manual format under linux.
Now have gapps and everything else I need installed - so will play with it later but so far seems to run very smooth.
Agree that seeing nook internal storage would be good
Click to expand...
Click to collapse
I got this problem too, format sdcard from cwm doesn't work.
It says Failed to mount /sdcard ... Skipping format ..
How did you fix ?
Really loving your efforts! Damn, thank you very much! I'll see if I can contribute soon, after I get my new computer. Can't wait for CM10 on HD+, it'll actually utilise the Nook HD+'s potential. It's dual-core, it can playback full HD, but it's limited by software.
Managed to get it to format sd card after I messed about formatting the sd card completely again and writing the cwm image
HiddenG said:
Really loving your efforts! Damn, thank you very much! I'll see if I can contribute soon, after I get my new computer. Can't wait for CM10 on HD+, it'll actually utilise the Nook HD+'s potential. It's dual-core, it can playback full HD, but it's limited by software.
Click to expand...
Click to collapse
quadcore.
jay_ntwr said:
Is there any reason to think this would not work on the NOOK HD as well? I understand that the reason it may have not been tested is that no one is willing to test it, but if it "should work" then I'd be willing to purchase the HD and test and report results.
Click to expand...
Click to collapse
Yes, this will not work on the nook HD directly, that has different uboot, different kernel and different SoC (not to mention different display).
I can't get /sdcard to mount or format no matter what I do. I'm using Windows, which seems to always be a hindrance in the root community.
Also, I'm fairly certain the the Nook HD+ processor (OMAP 4470) is a dual-core. Besides the main cores it has the two ARM Cortex-M3 cores, but it is still technically a dual-core processor.
PS- I'm running the Nook HD+ 16GB. Could the 16GB vs. 32GB cause any issues? Just wondering.
The changes to fix the GPS and SD problems, formerly pending at CyanogenMod, have now been merged with the base code. I will keep new relatively current builds for CM13 d850 posted, with links here, until CyanogenMod starts posting official nightly builds. The builds I post may or may not include unreviewed pending changes to the CM base code as seems fit.
(if you elect to follow me on the above link you will be automatically notified when I post updates...)
UPDATE – SD card fix, too – see below
As of yesterday (2015 Dec 29) there are fixes in the works at CyanogenMod for the GPS problems on LG G3 with CM13 (Marshmallow, 6.0.1). These fixes are in code review and are not yet merged, so if you just git the current code you won't get them. To get them, see change IDs If1d1772952a303b9378579e22c8248805cc191a5 and Iab2c5df90c59b34e33450a7d400cf73c4bef5fa4 at review.cyanogenmod.org and the change to the recommended vendor blobs at TheMuppets on github.com, change ID Iaae7dc3d8bd4aae5e6deb1ee248554217a0adae8.
I did a scratch build for my d850 overnight and GPS works GREAT! For those of you who are too impatient to wait for the reviewed and merged code, here is a ROM image to try. This is as experimental a ROM image as you will find. Use it at your own risk. If you do, make sure to first manually wipe system, dalvik, and cache; then flash the ROM image and an Android 6 compatible version of gapps at the same time.
cm-13.0-20151230-UNOFFICIAL-d850.zip
Update: minutes before 2016/01/01
I have included in this update code that is in review at CyanogenMod to fix the exFAT formatted SD problem. That is change ID I6e9bb732eee110ba75f680ea964538712bc33979. This code permits the use of a 128GB SDXC exFAT format card as external storage. I have not so far tested this code for using the card as internal storage. Maybe somebody with a similar card would like to test it in that mode. Here's the ROM image.
cm-13.0-20160101-UNOFFICIAL-d850.zip
Works great, thank you!
Downloading now. What about SD cards? Are you able to format as internal storage? The CM13 builds I've tried get stuck at 20%.
well this is a GPS fix so it's probably not going to increase your megapixel count or make your downloads faster. or fix your SD card.
Sent from my LG-D850 using Tapatalk
Works well. Ran it all day. Dunno about formatimg internal because I didnt need too. But its a DD. Well done sir...:good:
chuckhriczko said:
Downloading now. What about SD cards? Are you able to format as internal storage? The CM13 builds I've tried get stuck at 20%.
Click to expand...
Click to collapse
I've just made an updated ROM image with the proposed fixes for SD card that are in the works at CyanogenMod. See here.
wseverin said:
I've just made an updated ROM image with the proposed fixes for SD card that are in the works at CyanogenMod. See here.
Click to expand...
Click to collapse
Loading it now I'll run it all day and let you know
Seems to be working fine with my extended battery . The regular battery was running hot kept shutting the phone down. Make sure after flash to wipe dalvik before reboot.
Edit : 64gb SD card working fine GPS locked on no problem
Any way to just get the patch instead of the entire ROM? I'm running a CM based rom and having the SD card issue (and probably gps if I tested).
MCFADONNA said:
Seems to be working fine with my extended battery . The regular battery was running hot kept shutting the phone down. Make sure after flash to wipe dalvik before reboot.
Edit : 64gb SD card working fine GPS locked on no problem
Click to expand...
Click to collapse
what size extended you have ?
magicmanfk — Sorry, no good way to publish just a patch. That would be an over-the-top complicated endeavor.
Raz12 — I'm using a 128GB exfat external sd with no problems (so far and fingers crossed).
Raz12 said:
what size extended you have ?
Click to expand...
Click to collapse
Zero lemon 9000mah
my friend, thank you for all that you do
Sent from my LG-D850 using Tapatalk
MCFADONNA said:
Zero lemon 9000mah
Click to expand...
Click to collapse
i have the same one. Did they battery push in one of your pins ? it did it for me but it still works .
wseverin said:
magicmanfk — Sorry, no good way to publish just a patch. That would be an over-the-top complicated endeavor.
Raz12 — I'm using a 128GB exfat external sd with no problems (so far and fingers crossed).
Click to expand...
Click to collapse
yes thanks i'm using 64gb exfat and it has no problems. No problems at all with this rom.... i'm trying to think of some but haven't found any. been using for 3 days now.
Raz12 said:
i have the same one. Did they battery push in one of your pins ? it did it for me but it still works .
Click to expand...
Click to collapse
Yes it did . For that main reason I am in research mode for a new phone .
MCFADONNA said:
Yes it did . For that main reason I am in research mode for a new phone .
Click to expand...
Click to collapse
So tell me this .. How's your battery life ? do you think this affects our battery life ?
Just wanted to say thanks to the dev for making this rom. I haven't tested everything, but for my normal day-to-day use it has been absolutely rock solid. No problems doing a clean install of the 1/18 build, and totally smooth dirty flash to the 1/22 build (I haven't checked whether there's an update since). Battery life, including screen-on time, has been great- big step up from the 5.1 rom I had been using. Seems to keep running smoothly even when the phone gets hot. Well done.
:good:
I wiped and flashed this on my D850, and now I have lost root on my phone. I've been searching on line all day for a way to get root on the D850 on MM but have yet been unsuccessful. My phone have been doing weird things sing flashing this ROM on it, and I either need to flash the new version of this ROM or try another or restore from back up, but I need root. Can anyone point me in the right direction?
davidsinnergeek said:
I wiped and flashed this on my D850, and now I have lost root on my phone. I've been searching on line all day for a way to get root on the D850 on MM but have yet been unsuccessful. My phone have been doing weird things sing flashing this ROM on it, and I either need to flash the new version of this ROM or try another or restore from back up, but I need root. Can anyone point me in the right direction?
Click to expand...
Click to collapse
Root is included in CM. Go to Settings -> Developer Options -> Root Access
If you don't have "Developer Options" then go to Settings -> About Phone and touch "Build Number" 6 times quickly and it will unlock the Developer Options.