Arnova 10b G3 with EXT4 and CWM - BETA 2 ROM

[snakekiller]

Sow you did a fresh flash with the pc and then you restored your backup.
And then you did the build.prop flash and it works.
Wierd because if you restore your backup then is it the same as before

Verstuurd van mijn Freaktab met Tapatalk

[bay1902]

ok - snakekiller - a little update for you. As I reported the flash appeared to work & then rebooted into the system ok - but I was a little suspicious looking through the system files with root explorer that the build.prop was dated 15th July (when you're version is today's date). Looked & compared the code with text viewer & sure enough it wasn't the updated build.prop file. So I have no clue.

I'm going to go back & do the manual version - i.e. use root explorer to drop the modified build.prop in, reboot, wipe cache (but not dalvik) and see what happens now. But i'll do another cwm backup first!

[bay1902]

Nope, that didn't work either. renamed old build.prop to build.old, copied new build.prop into system folder (alongside build.old), set permissions that same as original build.prop, rebooted into recovery and wiped cache only (not dalvik), rebooted again & went straight into my old friend, the resistive calibration.

Re-flashing anew again & will restore then leave it! I'll wait now until the final rom is cooked, i'm sure it being embedded in the rom won't have such problems. I just can't understand how this is going on, especially when you've had the correct results?!?!?!

[snakekiller]

the problem is not my zips or manually files.
I use it rriley used it and mrweelson too and all worked fine for them.
I don't now what you do wrong.
Use you beta 2 from bob ?

Verstuurd van mijn Freaktab met Tapatalk

[bay1902]

Yup. On beta 2 - reinstalled fresh this morning. No idea either why it's doing this.

Got it installed - I manually edited a copy of the build.prop with your additional code. Have rebooted & code appears to have stuck ok.

[snakekiller]

Ok im happy you did it working now

Verstuurd van mijn Freaktab met Tapatalk

[Finless]

Watch out guys.... with ICS sometimes /system gets remounted as READ ONLY! Root explorer will not error when you try to copy or save a file when /system is mounted RO. ES FIle explorer will give you an error that the file could not be saved. Root explorer just acts like it did what you asked when if fact it did not.

So if you using root explorer ANYTIME you open /system make sure at the top it say mounted RW. If it says mounted RO, then press the little "mount RW" button at the top.

My bet this is what happened to Bay1902.

Bob

[snakekiller]

Ok

Verstuurd van mijn Freaktab met Tapatalk

[bay1902]

Just to confirm - when I did the manual edit it was set as r/w. Still no clue what happened with either the flash of the zip or the copying of the file itself.

Still at least it's there now - albeit the 'harder' way. I did a little test to see if code was sticking (changed the device ID code to look under the hood), rebooted & hey presto it took. So I know I have SK's modded build.prop now.

Cheers guys, now looking forward to the final rom.

[Finless]

Anyone want ICS 4.0.4 AOSP?

Hey guys..... So I am trying to find and rip out this stupid calibration thing. But in the process I decided to try something. You know how I used the Cube Gingercomb stuff for the Arnova 10G2 gingercomb ROM. Well I just recently did a Cube ICS 4.0.4 ROM and I decided to flash this to the Arnova. It works. However I do not know what all works and what doesnt. Chnaces are sound and maybe even wifi may not work. I just cannot test that stuff on the 10G2,

So anyone willing to try a standard AOSP ICS 4.0.4 ROM? Any guinea pigs? You guys will have to tell me what works and what does not and then I can go after fixing it like I did when I made Gingercomb.

One thing... if it works, you will have a true ICS not some basturdized Arnova implementation.

Bob

[bay1902]

I'm sure a number of us will give it a go Bob, including me - so long as we have the means to restore from cwm should it go pear shaped.

On the other matter - i'm leaving the build.prop alone now. Went & did another cwm backup, just for the hell, rebooted & it went back into resistive. There must be something in the code which from cwm / reboot sends it in. I don't know why just on my tab, but its confirmed.

I'm re-flashing (again) and restoring from earlier backup as we speak. If the Snakekiller's updated prop is included in final, i'll be happy.

But if we can have cwm backups count me in as a guinea pig.

[snakekiller]

I don't understand the zips working for me why not or you?

Verstuurd van mijn Freaktab met Tapatalk

[snakekiller]

I'm in bob .
Do it master bob

Verstuurd van mijn Freaktab met Tapatalk

[Finless]

You can alsways return with CWM. After flashing AOSP if you want to go back you flash BETA2 and do a CWM restore. The reason you must flash back beta2 is the parameter file will be different.

Bob

[rrileypm]

I'm in on the test flash, and Bob.

One thing when testing Snakekillers framework and build prop, make sure you have a good download. Yesterday, I had to try several different browsers to get a complete file. Compare the file size of the original file with downloaded version before trying to use it. If you have to, download from a pc and copy it over. I never got the calibration screen, but I think that was one of the reasons mine wouldn't boot. The permissions were also a problem after doing it manually. The framework apk was supposed to be 8mb,but the file I was getting was only 4mb, until I went to my pc to get it. The strange thing was in was downloading to internal storage, not external, so there shouldn't have been any corruption issues.

Randy