03/15/2013, 12:50 PM
Status Update - So this afternoon I updated to the latest CM9, moboot, CWM6 using ACMEInstaller3. I thought that would be a good way to update moboot and CWM as well as installing CM9.
Everything came up after quite a while, lots of messages with invalid and status ok screaming past. I don't know if that was the best way to go about upgrading everything, but it seemed to work.
I did that to get a good backup of CM9 if I need to go back.
So I have some questions: Did ACMEInstaller3 create the bigger system space when it updated CM9?
If so, can I move to CM10 from CWM now? If not, then the ACMEInstaller3 again, this time with a CM10 build and a new gapps file?
I had a bugger of a time getting all the parts to work on my new laptop. I had done the last upgrade from the old laptop which had been used to develop webOS apps so most of the interface stuff was in place. The new laptop is running Win7 64bit which added a host of install the tool problems, no JAVA, wrong JAVA, need Virtualbox, but not the new one, 64 bit SDK fails to install the Novacom stuff, can't extract it from the exe, get the doctor from HP, gives me some java file that won't run on my machine, so get the doctor from the direct link on webos-internals, cancel the install after the driver is installed, wow I can see bootie now!!
Thanks to all the tool makers for helping to make this happen.