Where are all the tools for the vibrant kernels, for mt3g it was easy to build kernels, mkbootimg, then sign and flash.
For acer liquid I needed an adjustment for the mkbootimg source, since they used different offsets, then could flash boot.img via fastboot, good enough (never built kernel, just lulled boot.img, unpacked, added superuser, su, then repacked to have root on new rom)
Ok, fast forward, for Samsung Vibrant, I see people build kernels, but google finds nothing about modules outside kernel tree, mkbootimg/signing/*
Where is the stuff, I hope for user error, but can't find where I went wrong in search.
Sent from my Vibrant.
morfic said:
Where are all the tools for the vibrant kernels, for mt3g it was easy to build kernels, mkbootimg, then sign and flash.
For acer liquid I needed an adjustment for the mkbootimg source, since they used different offsets, then could flash boot.img via fastboot, good enough (never built kernel, just lulled boot.img, unpacked, added superuser, su, then repacked to have root on new rom)
Ok, fast forward, for Samsung Vibrant, I see people build kernels, but google finds nothing about modules outside kernel tree, mkbootimg/signing/*
Where is the stuff, I hope for user error, but can't find where I went wrong in search.
Sent from my Vibrant.
Click to expand...
Click to collapse
We are waiting for Samsung to release an OTA update that updates the kernel. That way we can see how they replace a kernel w/o using ODIN, and we can do the same (we all hate ODIN lol). Pretty much, we dont know how to do it yet.
There is an Update Agent on the original Galaxy S http://forum.xda-developers.com/showthread.php?t=765724 so that might be the engine behind the OTA update.
I will see if it is avail on the Vibrant.
EDIT: The same is available on the Vibrant, at least this part looks the same LOL
Moved to Q&A.
Related
I'm sure this has been covered before, but I can't get any answers. (When I search, I keep finding threads asking the same question and being told to search...)
I know I've seen a thread somewhere with some info. If anybody knows where this is and can post a link...
I've downloaded the kernel source for 2.1 from samsung and have been able to compile it. I took a voodoo kernel zip and unzipped it - replaced zImage with mine, and zipped it back up. When I use clockwork to flash the zip file, it goes into a reboot cycle. I figure this should work since the kernel versions are the same and my kernel should just use the existing modules, (in the same way it appears the voodoo kernel does).
I'm guessing I'm packaging it wrong, but I'd like to see a whole build procedure to make sure I didn't miss anything.
EDIT: Also, I'm running Ubuntu and its getting annoying to boot back and forth between Linux/Windows to use ODIN. Are there better ways to test kernels?
Thanks in advance.
Did you add the ramdisk? I use odin in virtualbox under ubuntu. There's a thread in the i9000 development forum that explains how to do it.
The ramdisk is finicky as hell. It's much simpler to start from a known good one. The voodoo project has one posted. You can also extract one from a working kernel.
Damn that ramdisk. It seems that only one way of adding it to the kernel works. I could never get the gzipped cpio file to go into the kernel. Have to ungzip/cpio and create the stupid list. But thats probably your issue.
http://forum.xda-developers.com/showthread.php?t=697938
This should have all the info you need to get started, need further help or clarification, can ask a dev. or do a google search
Thanks guys for the quick responses. I'm going to try and pack intramfs with my kernel and try again. I'll let you know how it goes.
A friend of mine found this link as well - I'll be trying to use that as well.
forum.xda-developers.[com]/showthread.php?t=777380
Why Samsung chose to write a Linux ROM flasher in Windows boggles my mind. It won't even run under WINE. What were they thinking?
dattaway said:
Why Samsung chose to write a Linux ROM flasher in Windows boggles my mind. It won't even run under WINE. What were they thinking?
Click to expand...
Click to collapse
They were probably thinking that most people run Windows...which would be a safe assumption.
Because what the world needs now is another R800x related thread.
I'm going to try to document all of the kernels and ROMs posted currently about the forum and exactly what they will or will not do when used in their current state on the R800x. This thread will be for developers to help figure out issues related to the CDMA differences and for end users trying to figure out what works or doesn't.
Please post your experiences with testing different builds and kernels. Also, if applicable, post any software that you were able to remove with root and if you ran into any complications because of the removal.
Note that this can also serve as a directory for GSM users as well. Just disregard the comments and do diligent research.
If you are not using a custom kernel (and you're probably not at this point because of how poorly they are responding) then you will need to run this command to make your system read/writable so that you can remove apps:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
If you have not already done so, download Omnius! Backup your TA file. This can save a lot of headaches in the long run for everyone!
Root
Basic Root Steps
Link: R800x Root
Status: Steps to follow if you have an unlocked bootloader....
zergRush Root Method
Link: [HOW-TO] Root R800x/i v2.3.3+ (zergRush Method)
Status: Instructions for rooting without a unlocked bootloader. Works on stock 2.3.3.
Bin4ry's Original Root
Link: [How-to] Root your Play
Status: No. Bin4ry's file contains the entire system for the GSM plays. This is an original rooted generic system build. Do not flash this.
Kernels
DooMLoRD's CDMA Kernel
Link: [KERNEL][PLAY][CDMA] DooMKernel [Rel:v01][Dt:30/Nov][FW:3.0.1.A.0.145]
Status: Currently in very active development, check the thread for most recent updates and information about whether this will work for you. Probably most recommended for stock ROM.
Blagus' SEtweak Kernel
Link: [Kernel] SEtweak - insecure ADB, ext4, NTFS, overclock, USB OTG - updated 24th July
Status: Boots stock ROM. Unusably slow. Root shell in adb.
DooMLoRD's GSM Kernel
Link: [KERNEL][PLAY][GSM] DooMKernel [Rel:v08][Dt:17/Nov][FW:4.0.2.A.0.42]
Status: Newest Doom revision will boot stock 2.3.3 system without wifi or camera. Version 3 of the kernel will allow you to use both of these items. Will also boot other systems with same results.
FreeXperia's (jerpelea) Kernel
Link: [DEVELOPMENT] - CM7.1.0 - FXP041 RELEASED - FreeXperia Project
Status: It works like it should for the most part. Regressions in and out on camera, but overall stable. Used for CM7 only.
Roms
Stock ROM
Link: Check stock section below for downloads
Status: Boots and roots with everything available to use as it should be. See kernel info above for finer points to it. Stock ROM is easily rootable.
FreeXperia's CyanogenMod 7.2.0 CDMA
Link: {GSM/CDMA}[DEVELOPMENT] - CM7.2.0 - FXP049 RELEASED - FreeXperia Project
Status: Newest builds work almost 100%. If you are having camera issues, check out this post and apply the linked update.zip. You should have a working system with everything except MMS. And even the MMS is hit or miss. So give it a try.
ZeroROM
Link: [ROM] zerorom v0.4 (GSM/CDMA, CWM Install)
Status: Boots great using Doom's kernel, however, system is based on 4.0 series generic GSM roms and the radio doesnt function yet. Work in progress.
UK ROM For R800x
Link: [CDMA][ROM] R800x with UK firmware
Status: Work in progress but good reports about it running great. Check out thread for most current information and build data.
FrAsErTaG's FTS
Link: [SYSTEM] FTS v05 ONLINE [FINAL] DooMLoRD Kernel Compatible
Status: Seems there is lots of success with new patches and some minor tweaks starting about there in the thread. Well suited for using as a daily driver at this point with the tweaks. Easiest method is just flashing the awesome nandroid backup zero_1_2 made.
Requests
Kernels for 2.3.3
Back to Stock
Stock Kernel 2.3.2
Link: Attatched to this post
Status: Its the stock kernel. So of course it works just fine. Flash the same as you would any kernel: fastboot flash boot kernel.sin
Stock System 2.3.2
Link: Multiupload
Status: Should work just fine. This is just the .sin. Use this command: fastboot flash system system.sin
Stock System 2.3.3
Link: DropBox
Status: Untested system img. Use this command: fastboot flash system system.img
Stock Kernel+System TFT 2.3.2
Link: Multiupload
Status: Should contain a tft file with the kernel and system. From what I understand this is not the complete restore?
Full system FTF 2.3.2
Link: Multiupload
Status: Full system restore tft. This should bring you back to 100% stock (minus the bootloader being returned to locked)
Full system FTF 2.3.3
Link: Multiupload
Status: Full system restore tft. This should bring you back to 100% stock (minus the bootloader being returned to locked)
All Original System APKs
Link: Multiupload
MD5 Values for Stock Items
This isn't an optional check. The following values must match up or you need to download the file again.
Code:
R800xkernel.zip (Attatched to the post)
1a2e9a665fee7332867157c11aa321c9
System.sin
3ebf12d10c195b92ff72c41d325592de
Kernel.sin (Should be inside attatched file to the post or inside full ftf)
7ba1e6e3b698ad55f6bea0406196d337
Stock kernel and system.ftf
d519365f7220382a42fdecd554aa4b64
Full Stock Minus TA. FTF
465d52867582a4d1eee8166807bb97ac
Potentially Safe to Remove Applications
Users have personally removed and verified the following apps. Removing all of these will take every Verizon application out of your menu. And all of the games. Except for Crash. Because, honestly, who doesn't want to keep Crash.
I remove all of these apps completely (cause I live on the edge like that and I dont mind flashing a system file) but you are also free to simply rename the package and put .old on the end of it or something similar. The point will be served to get them out of your menu, but it, of course, wont clear up any of the precious little space we have. It saddens me to have to say this but I think its wise to remind everyone: you are not required to remove all these applications. If you don't know what you are deleting, don't. If you still manage to screw this up, the apps are all linked in the stock section above.
/system/app/starbattalion.apk
/system/app/Asphalt.apk
/system/app/madden.apk
/system/app/Sims.apk
/system/app/tetris.apk
/system/app/com.skype.android.verizon.apk
/system/app/com.fusionone.android.sync.sonyericssonr800xbaclient.apk
/system/app/com.vzw.vvm.androidclient.apk
/system/app/com.amazon.kindle.apk
/system/app/com.vznavigator.r800x.apk
/system/app/com.gravitymobile.vzwinstaller.apk
/system/app/com.gravitymobile.app.hornbill.apk
/system/app/Launcher2.apk
/system/app/Camera.apk
/system/app/com.vzw.hss.myverizon.apk ##This one has to be done last. If your phone is running, prepare for it to hate you. Reboot after its gone and you should be alright.
There is a more comprehensive guide here but together by sonicfreak360. Check it out.
Tips or Tricks
Question: Cant boot or pass the Sony Ericsson logo? Can you still get into fastboot (power off and plug in USB with search button held)?
Status: Check out the post made by gwaine later on in the thread
I will pm you what I have tomorrow for stock kernel.
I seem to now be unable to install anything from the market at all. It doesn't go past the "Starting download..." step. my logcat is filled (literally hundreds a minute) of this error: Waiting for service drm.drmManager... I'm betting its related. But I dont know if its due to the kernels or due to the DRM partition getting erased at bootloader unlock time. This poor device has gone through every kernel and rom available in the last two hours. Such a hoss, she is.
Ash, just flashed the "stock" kernel you have on your thead. Where did that come from? And did it come with root?
Uninstall any updates and see if the fixes it.
Also if frasertag and doomlord are the things working right now could it be that just the kernel alone is the problem and it would have to flashed together with the system?
I just tried pretty much every combination of kernel and rom. I just flashed back that kernel I just mentioned in my edit (the stock one you posted) and then wiped in CWM and recovered my original backup and now its clean. Market downloads are working. And that error is gone out of the logcat.... it must be something thats different about the CDMA builds.
But did that kernel file you post have root pre built into it? Because I appear to still be rooted...
Nope it was a stock kernel.sin I pulled from blob file. The thing is, you keep root after kernel flash. Nifty huh?
ashergray said:
Nope it was a stock kernel.sin I pulled from blob file. The thing is, you keep root after kernel flash. Nifty huh?
Click to expand...
Click to collapse
Yeah it sure is. The backup I restored was made right after I flashed the first thing, which was Doom's kernel. Looks like that kernel actually copies the su and superuser programs into the system as opposed to running them from the kernel persistently (like CWM or busybox or the other neat tricks he had up his sleeve with that kernel because apparently none of them are still on my phone, just su and superuser). So basically I'm back to where i would have likely ended up just doing these steps:
Unlock Bootloader
Flash system zip file from Bin4ry for root
But I have compiled a kick ass list so far of my journeys. Cant wait till the CM nightlies start dropping. Bet there will be a good chance that they run fine right out the gate.
Also note that the freexperia kernel for cyanogen was the only custom kernel that didnt have the "slow" feeling on the stock rom, and the stock rom was the only rom that had the slow problem at all it seemed because frasers worked fine with all of them, i just had the issue with the market, but again thats probably due to the kernels.
Also, in regards to the roms feeling slow, we talked earlier about it maybe being a clock issue. But it doesnt seem like it is. I've never seen response times this bad. I also cat checked all the proc info for the cpu and could see that at its low end it wouldnt have been dropping below 200mhz. although slow i would have at least been able to load the launcher, which is something that I am yet to get on these at all. top isnt being very responsive so its hard to see whats going on there and the only output i was seeing from logcat was the stupid DRM error i was having. phew.....
time for bed.
Yeah we did go around our elbow to get to our hand this time. But we certainly learned a bit about what does and doesnt work for our cdma variant.
I can post the entire stock image when I get a chance or forward it to you to upload.
Also it is surprisingly easy to build one if you have seus and flashtool.
I do have one, just not with me at the moment. I have it on a windows computer at work ready to go. Had it around since the time I tried to flash the GSM TA to my first play. Three plays later...
Awesome work and progress tonight. All downhill from here.
Agreed. Off to bed now.
The stock kernel attached is a .sin file. Are these flashed in the same way as a boot.img file?
Code:
fastboot flash boot kernel.sin
crono141 said:
The stock kernel attached is a .sim file. Are these flashed in the same way as a boot.img file?
Code:
fastboot flash boot kernel.sim
Click to expand...
Click to collapse
Yes sir, but it's ".sin", not ".sim." Just didnt want you tearing your hair out over that
Also, I am yet to have any success with just a straight fastboot command like that. I always put in the USB identifier, so it would look more like this:
Code:
fastboot.exe -i 0x0fce flash boot kernel.sin
Probably doesn't matter if you can get it to go the other way though, it should be the same thing and its probably related to the way my hardware is setup.
Afaik, .sin files are flashed with Flashtool.
Yeah, I realized my typo as I was attempting to flash. I corrected my original post. I've followed the instructions kinda once, and it didn't work (didn't do a full boot under doomlord kernel). I've just finished following the directions exactly and report a successful root. WOOHOO!!!
BTW, flashed the sin file with fastboot and it worked just fine.
Logseman said:
Afaik, .sin files are flashed with Flashtool.
Click to expand...
Click to collapse
or through fastboot.
that was what I used to get back to stock.
I could never get Flashtool to work properly with my play.
Doomlord's kernel runs slow? I assume you tested with SetCPU configured to run faster than stock speed? Because at 1.5GHz it's really speedy, but I do not have an R800x so I have no idea. The kernel architecture is probably a bit different between the GSM and CDMA models... just enough that it's causing conflicts of some kind. A dmesg and logcat could shed some light.
axiomjunglist said:
Doomlord's kernel runs slow? I assume you tested with SetCPU configured to run faster than stock speed? Because at 1.5GHz it's really speedy, but I do not have an R800x so I have no idea. The kernel architecture is probably a bit different between the GSM and CDMA models... just enough that it's causing conflicts of some kind. A dmesg and logcat could shed some light.
Click to expand...
Click to collapse
Yes, mill tried it with the setcpu speed to well over stock and no improvements. I think it is the stock Verizon firmware that is the issue, since he had no problem with frasertags system and the Doomlord kernel.
ashergray said:
Yes, mill tried it with the setcpu speed to well over stock and no improvements. I think it is the stock Verizon firmware that is the issue, since he had no problem with frasertags system and the Doomlord kernel.
Click to expand...
Click to collapse
Ah, makes sense. If Frasertag's rom works fine with the custom kernel then it's got to be something in the stock VZ rom causing the conflict.
If Frasertag's system.img worked via fastboot, since his image was from an R800i theoretically the stock 2.3.3 pre-rooted system.img that Kazone posted should work too. Anybody try that yet?
http://forum.xda-developers.com/showthread.php?t=1098736
axiom, i dont know if anyone has tried that one yet but jellofreak tried the full system image from Bin4ry's post which did a similar thing. it flashed the entire r800i build on his r800x without issue. he says there are a few bugs here and there but over all usable.
Is anyone aware of a ROM, or even a basic mod/patch that enables an insecure boot? I'd like 'adb remount' back
You have to install a rom that has it edited/enabled.
Right
Yes, I understand that -- Though strictly speaking no, you can just replace the right bits yourself to allow it. Regardless, that's why I asked - I am not seeing a ROM with it, but there aren't exactly a ton of ROMs for this one just yet...
That's a surprise since most of the roms in the dev section are created using dsixdas kitchen and part of the rooting process in the kitchen involves editing the boot.img for exactly what you are asking for.
Regardless, it's better to have the rom have the boot unsecure then to replace the bits. At least with the edited boot it will always be unsecure even after a reboot.
Hi everyone I'm pretty new to the whole Android world, I've read a lot of stuff through this forum and in general through the internet but I haven't got to the point of really understanding this clear.
I performed the rooting and sim unlocking following the guide on this forum, so basically I had to install the ClockworkMod Recovery.
I read that having installed a custom kernel (or rom, not clear the difference) or a custom recovery (or bootloader, like CWM in this case) voids the warranty.
I also read that is pretty simple to restore the stock kernel/firmware by simply flashing it on with Odin, but what about the Recovery?
I found this post http://forum.xda-developers.com/showthread.php?t=1286432&highlight=stock+bootloader my questions are:
1. Is having the phone flashed with stock kernel (but a different than the original recovery, e.g. CWM) enough to bring the phone back in warranty conditions?
2. flashing the stock unrooted kernel following the above thread will restore also the original android recovery console?
3 if not is there a way of getting rid of CWM and restoring the original android recovery? (I read "just flash it with odin like you did with CWM, but where do I find the package (image) to flash?)
4 the stock kernel in the post seems to me "not official" in the sense that has been ripped from a user, is there any chance that we (SGHI777) will get something more official like the international kernels (GTI9001) that you can find on samfirmware?
5 this is extra, if I have a rooted GS2 (following the forum procedure so CWM+original kernel) will I be able to install official update through Kies? (I'm asking cause the unlock security flaw bugs me a lot...)
Thank you very much to everyone that will answer.
frabass said:
Hi everyone I'm pretty new to the whole Android world, I've read a lot of stuff through this forum and in general through the internet but I haven't got to the point of really understanding this clear.
I performed the rooting and sim unlocking following the guide on this forum, so basically I had to install the ClockworkMod Recovery.
I read that having installed a custom kernel (or rom, not clear the difference) or a custom recovery (or bootloader, like CWM in this case) voids the warranty.
I also read that is pretty simple to restore the stock kernel/firmware by simply flashing it on with Odin, but what about the Recovery?
I found this post http://forum.xda-developers.com/showthread.php?t=1286432&highlight=stock+bootloader my questions are:
1. Is having the phone flashed with stock kernel (but a different than the original recovery, e.g. CWM) enough to bring the phone back in warranty conditions?
2. flashing the stock unrooted kernel following the above thread will restore also the original android recovery console?
3 if not is there a way of getting rid of CWM and restoring the original android recovery? (I read "just flash it with odin like you did with CWM, but where do I find the package (image) to flash?)
4 the stock kernel in the post seems to me "not official" in the sense that has been ripped from a user, is there any chance that we (SGHI777) will get something more official like the international kernels (GTI9001) that you can find on samfirmware?
5 this is extra, if I have a rooted GS2 (following the forum procedure so CWM+original kernel) will I be able to install official update through Kies? (I'm asking cause the unlock security flaw bugs me a lot...)
Thank you very much to everyone that will answer.
Click to expand...
Click to collapse
On nearly all Samsung phones, recovery is a part of the kernel. Flash a new kernel, you've flashed a new recovery.
The stock kernel zImage is as official as it gets - nothing is more official than what was actually flashed into the device by the manufacturer and sold on launch day. The additional evidence that it's official is that it passes the bootloader signing checks, eliminating the "custom kernel" warning screen.
We won't see a samfirmware release until AT&T releases an update.
Stock rooted shouldn't affect OTA updates, however sometimes things you do WITH root (such as debloating) will interfere with OTAs.
Once an OTA update becomes available, expect its fixes to be integrated into ROM releases fairly soon.
FYI there are three components you should know about. Kernel>ROM>Modem
The kernel It's the core/kernel of an operating system. It's main functions are to interact with the hardware a.k.a. Device Drivers, to manage resources (things like memory management and processor time sharing a.k.a. multi-tasking), service interrupt requests, network services and the like. It also provides a System Call Interface (API) to the user space (apps running on the machine) so the apps can use system resources.
Now the why so many part... First of all in general there are MANY options available when compiling (building) the kernel. Things like CPU schedulers, file system support, system type support, etc. etc. etc. So there are many different ways to configure the kernel and that gives many options to "test" and see which might work better or not. Some of them are dead giveaways like compiling the kernel for MIPS and trying to run it on the SGS2 won't work but some are "tweaks" that may help a little or a lot, like CPU management options.
Second part of the why so many is the code. Again as mentioned above things like changing code to make the colors of the display more or less sharp (display device driver), make the file system faster (voodoo lag fix) or overclocking the processor, and different "modem" tweaks are all "enhancements" that people have made to the original Linux kernel source. So those things "creep" into existence over time, since there are many people working on them, and you see different versions of the Kernel from that as well.
Anyone that plays music can relate to the options available in that there are only 12 notes on a guitar fret board but millions (or more) ways to put them together to play music. There are certain things that have to be present in the Kernel (notes) but writing code to enhance them and/or combining options at compile time is much broader (music).
The ROM. ROM is actually Random Access Memory and we flash an image to the "ROM" (which it really isn't but I'll leave that one alone). The "ROM" in this case is the operating system (a version of embedded Linux), which is the basic software needed to run and admin the phone, things like the Kernel, bootloader, device drivers, and file system plus any user apps like the phone dialer, launcher, etc. that are included in the ROM. As you can imagine the possibilities of customization are almost endless when it comes to the ROM. Different kernels, different drivers, different apps and many combinations of those.
The modem is actually part of the kernel. It's the device driver for the phone hardware. Being that it's part of the kernel it "works with" other code that's elsewhere in the kernel and ROM that is "tweaked" for a particular phone in this case. So when you see "use an i777 modem with an i777 kernel" it's because the code in the modem is written to work with the other code in the kernel. It doesn't necessarily mean it will brick the phone and/or not work but it quite often means it won't work the best if it's not "matched".
Actually the modem is NOT part of the kernel. The modem firmware runs on an entirely separate processor (not one of the main application cores.) - the RIL (Radio Interface Layer - part of the ROM) bootloads that processor by sending the modem firmware to it via a serial port when the system boots.
The baseband processor is almost never listed in a phone's specs because it's a "hidden" part of the system. Very often a device like ours will have more CPU cores than just the advertised application processor cores. For example, early Qualcomm MSM7000-series chips had two processors, one for applications and one for radio. Some people labeled these chips as "dual core" even when they really weren't - the two CPUs were completely different.
Similarly, we have two ARM Cortex-A9 cores acting as applications processors, an unknown ARM core doing radio work (much simpler, slower, and power-efficient than the two A9s), and possibly another application-specific ARM core hidden in the GPS chipset. Maybe more.
Development on the phone I have has gotten as far as rooting stock (SCH-I110, Samsung Illusion). As I've toyed around with my Nook, I like the idea of cutting edge software still running on older hardware. Yes, yes, I realize that this is a "cheap phone" and not "in demand" and "why don't you just go and get a S2 or S3", but isn't the whole idea of open source the ability for people to learn? I've loved reaping the benefits of others' hard work, but it's time to get my own hands dirty...
Basically it comes down to this: I need to be pointed in the right place to learn how to build recovery for my device (ie CWM).
It's currently rooted, running stock and busybox, but that's as far as I have gotten. The source code HAS been released already, so it's out there. I've tried to read up about Odin in order to figure out how to pull a recovery image and start building, but just about every tutorial I've come across teaches people how to cook their own ROMs after CWM or TWRP is already installed. I'm not quite there yet.
So if anyone has a good place that contains information on building recovery, thank you for your help in advance. I just need a little direction.
Ok, so I pulled a boot.img off the phone as well as a system.tar. I used the boot.img on builder.cyanogenmod.com and have the following output files:
android_device_unknown_unknown.zip
inputrecovery.img
manifest.xml
recovery.img
The recovery image can be found here: http://builder.clockworkmod.com/redirect/5dbb87a058d1bb5fcd0bcbeca347c45b.img
I did see on the console output that it was building for CM10.1. Is this going to be an issue?
Thanks for helping an Android Noobie.
Would this be any help: http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
XyanumX said:
Would this be any help: http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Click to expand...
Click to collapse
Yeah, that was one source I was reading. I saw his note about initramfs, though. I believe the Illusion uses it as opposed to the standard boot image format, so his guide doesn't work. Thanks for suggesting it, though!