Thanks for the confirmation.
On my side, I did upgrade stock to 3.2.78 and I confirm that SDE build is preserved. I also confirm that removing "'android kernel" in sde menu let the tablet boot straight to sde without needing volume-up and menu.
You must launch the script from your mac, not from the device.
If adb is in path, I presume you should run the .sh from shell/console (don't know the exact name on mac). If you can't run it after unzip, try chmod 755 enable_sde.sh first.
I don't have mac so I can't help much more, sorry...
I am on the latest firmware (3.2.78) and am about to enable SDE.
I noticed in your SDE package that you flash zimage and initrd.cpio.lzma which I presume are from an earlier firmware level. Is there any reason to replace these file from this SDE package with the ones from the 3.2.78 firmware?
Apologies if this is a dumb question, although I do cook ROMs (mainly for tegra devices) this is the 1st Archos device I have so am learning.
Thanks! FredT
Since recovery/SDE is done using init.rc and couple other .sh files- is it possible to add wiping dalvik-cache (rm -r -f /data/dalvik-cache)?
As it turnes out this would be quite usefull- after trying the first custom firmware I had to "reset Android" (wipe data and settings) which most likely shouldn't be necessary after wiping dalvik-cache
I understand, good pointYour idea would be to add "wipe dalvik-cache" to recovery menus ?
It's possible to modify recovery, but I strongly discourage it. I won't release the tools that could do that, a mistake there and your tablet is paperweight.
However, if your idea is to add a pre-boot menu in the build initrd, yes, it can be done. But this is not really sde-related, it's more build-related. You should ask surdu_petru if he would be interested to add this to his build ?
Well, G9 is not "HTC/Google standard".Maybe we should define a "standard" way of doing this between build cookers ? Or a "standard" initrd ? My initial goal was to port ClockworkMod and have it done from there, but it makes sense only if you repartition the whole device which is a bit dangerous.
Well, G9 is not "HTC/Google standard".
"Standard" way of applying updates uses a)wipe command in update script (reformats /data and removes /sdcard/.android_secure) in case of totally different rom or b)requires user to wipe dalvik-cache using recovery in case of an update.
In G9 only "wipe data" option is available as Reset Android and I don't know if it can be triggered with official update or by issuing a command over adb.
Wipe dalvik-cache could save a lot of time
EDIT:
If there would be working adb in SDE menu there should be no problem to run a custom script from pc
Yes, that's why I used the quotes for "standard", meaning only establishing common conventions between rom cookers. Unfortunately, Archos recovery is purely scripts on top of kernel boot, no android init, no adb, the only location where we have room for that is in sde initrd before booting android.
Not working for me with 80 G9 updated before to 3.2.79, get stucked trying to start in SDE mode, had to reupdate original firmware with .AOS file from archos´ web (v3.2.79 too). Has anyone AOS file 3.2.78 which is supposed to work? thnx!!!
Did you install firmware that works with SDE menu? SDE itself just enables multiboot.
Hi All.
I followed the relevent guides published here and attempted to enable the SDE menu on my G9 101 HDD model after I had upgraded with the official ICS update.
Last lines of the command prompt after running gen9_enable_sde script were...
Generating KD...
Updating KD (3053305 bytes)...
0
100
I am unable to boot the device into recovery mode, the archos startup screen appears then shuts down abrubtly.
I am unable to boot normally, it just keeps going into a boot cycle.
While connected to my PC, the device is briefly recognised.
Is there anything else I can do to recover ?
adb shell rm /data/local.prop
Well, it should work, except if Archos fixed the exploit to get the temp root.