I guess the most complicated portion would be if you wanted a senseless frankenrom. But default, the install is like his "Second Wave" ROM. Running the vanilla script on it basically removes HTC and stuffs in default apps. If you "frank" it, then it'll put it into Sense'd version of the EVO/DInc combo-ROM (EVO port test ROM, loving dubbed FrankenROM). Running vanilla is literally the exact same process as performed on "second wave".
So basically, you will have a Froyo 2.2 ROM out of the box based on the 8/1 Leak, and tweaked.
The other commands are for customization purposes.
As far as the Linux stuff goes... I am by far not a Guru, but once you get into the swing of things it's really pretty straightforward. If the old post was still here I'd refer to the source code of the scripts that Adrynalyne had posted; now I'm just going to say if you unzip the file, and go into the ./system/xbin/ folder, you'll see a bunch of files. If you open up "frank" for example, you'll see the following code:
Code:
#!/system/bin/sh
rm -r /system/framework/
mkdir /system/framework/
cp /sdcard/sw_files/frankenrom/framework/*.* /system/framework/
rm -r /system/app/
mkdir /system/app/
cp /sdcard/sw_files/frankenrom/app/*.* /system/app/
echo **ITS ALIVE!**
echo **Factory reset/data wipe now.**
Oh... I might want to clarify, Linux is funky with carriage returns, so use NotePad++ for something similar instead of Notepad/Wordpad, otherwise it'll look the same but without the new lines.
Anyway, each one of those lines is a command:
rm is short for "remove"; the -r is a flag to recurse and remove subfolders, and then there's the folder he's wanting to remove.
mkdir makes a new directory.
cp is short for copy
and echo is just printing out to the shell (so you can see what it's doing)
If you open the vanilla one, all it's doing (essentially) is a ton of rm statements, and then a few cp statements.
I'm blanking on Windows batch file commands, else I'd try to duplicate the lines for a Windows environment.
The earlier scripts he mentions (rem_vvm, etc.) only exist because they can be run while the phone/OS is running. If you look at them you'll see that he has to mount and unmount things for read/write access, since otherwise we technically wouldn't have permission into those parts of the file system.
Vanilla and frank *have* to be run within adb shell while the phone is in recovery/Clockwork solely because it's changing files that the OS/Framework. It's I guess the same reason why Windows can't Scandisk itself while it's running.
TBH my DInc is my first Android (and first smart) phone, and I'm by no means a Linux guru, but I hope this kind of explained things. If you want a certain setup (ie you want EVO/Sense) then you'd install the ROM just as you would any other, and then plug phone into the computer, boot into recovery, open the shell, type in ./frank, and you're good. *shrug* If you want frank minus VVM then it's ./rem_vvm after that.
Why do I feel like I could simplify this so much better... I've been awake too long.
28 hours and still not entirely tired. Just loopy.
