Take a look here: http://xdaforums.com/showpost.php?p=24951949&postcount=31.
How so? It's the latest post from the developer on what's going on.
He asked what's going on with the A100, you replied with a post about a recovery. Hardly relevant.
He asked what's going on with the A100, you replied with a post about a recovery. Hardly relevant.
Testing right now .A100 Build...
update-cm-9.0.0-RC0-vangogh-UNOFFICIAL-signed.zip
md5 de7df7d1e3046568fc0147a93aa90a05
Enjoy
To all,
The above was ready to post last night after the sneaky one in the a100 forum... long story short, I got distracted & ended up asleep on the couch.
Apologies for the confusion that ensued
wds
Have you seen the link in his post? It's the rom . Anyways, at least he published it openly now.He asked what's going on with the A100, you replied with a post about a recovery. Hardly relevant.
A100 Build...
update-cm-9.0.0-RC0-vangogh-UNOFFICIAL-signed.zip
md5 de7df7d1e3046568fc0147a93aa90a05
Enjoy
To all,
The above was ready to post last night after the sneaky one in the a100 forum... long story short, I got distracted & ended up asleep on the couch.
Apologies for the confusion that ensued
wds
I say move it over to the a100 forum. God knows that forum needs more action. Just flashed this and everything went fine. However I cannot get r/w on /system. Tried some of the a100 rooting method and nothing has worked.
Crazy ass they might be. But it's what it took to get it installed.Finally got this working. Had a lot of trouble at first. I finally got it by following engine95's crazy ass instructions.
Basically flashed cwm1.6 from thor, wiped the bajeezuses out of everything (seriously wiped system cache and factory reset 3 times).
. build/envsetup.sh
lunch cm_a500-userdebug
brunch cm_a500-userdebug
Q: assert.failed:getprop("ro.product.device")=="Picas so" || getprop("ro.build.product")=="picasso" E:Error in /sdcard/Download/update-cm-9.0.0-RC0-picasso-UNOFFICIAL-signed.zip Status 7
A: Open the zip. Go to META-INF/com/google/android/update-sctipt. Remove the top line with the assert then repackage and flash has to do with your recovery. some recovery's name the device differently (thors for example does this, just as an example). our tree uses the device name picasso, if the recovery does not use picasso it will fail, the only fix for this is a unified recovery or to remove the line from the update-script, hope this more detailed answer helps more...