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.
Related
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, I just got a hand me down samsung fascinate to replace my barely functioning OG Droid. I rooted it and installed rom manager and it kept failing the custom rom installation or any installation of anything from recovery manager. It kept saying the signature verification failed if I remember the error code correctly. That was with the 3e recovery software. I read a few posts that said the older 2e version would work better with rom manager.
So I used odin and reverted to an older software revision, 2.1-update1. That successfully shows 2e as the recovery manager version. But now the market doesn't show rom manager(free) as an install option, premium shows up though. If I use the web browser to look at the market and look for it it shows up but it shows four devices, my old droid, a nook I rooted and converted for a friend, and then two devices that just show a question mark and doesn't allow them to be selected for installation. I thought thats ok I'll just download it from clockwork mods website and install it manually. I downloaded it but astro opens it and shows no info, details tab says it cannot open RomManager.apk as APK file. If I open it with file manager it says it cannot parse package. I tried downloading it on my computer and transferring it to my phone and it still says the same thing.
So I'm really confused as to what is going on. I do have install non market stuff checked.
I was hoping someone could give me some advice. I want to install miui as that was what I ran on my droid and liked it. Want to see how it runs on a faster phone.
Thanks in advance hopefully I provided enough information and didn't miss something simple.
When you were on Froyo, did you install the modified 3e Recovery needed for CWM to stick? I'm sure this is your problem if you didnt take this step.
Here is a link to the thread with everything you will need. If you have additional problems, dont hesitate to ask!
Hope this helps!
BTW: 1. Dont worry about this being for the infuse. It will work fine & 2. These types of threads should go in the Q&A section, for future reference
Rom manager is pointless unless you run cm7 nightlies. Get the recovery fixed for cm7 (first post of jt's cm7 thread in development) put miui rom on sd. Pull batt, flash fixed cm7 recovery in odin, insert battery (don't boot), 3 finger to recovery and flash miui. Profit.
good day.
First thank you for the replies very appreciated.
Tone_Capone I was going to try your method first. You are correct when I was on the updated firmware I did not flash the "fixed" 3e recovery did not realize there was one. My question now is I'm currently at 2e recovery, on the older firmware. Can I still follow those directions and put the modified 3e recovery onto the phone how it is. Or does the modified file count on other files being in place that I don't have since I'm downgraded? Do I need to update it again? I hate to ask but I just want to make sure.
chopper the dog Sorry about wrong section, thought q and a would be for commonly asked questions and the answers for them. I was gonna try this method then but I'm not sure if I choose bootloader in odin or pda like I did when downgrading the firmware.
joebells said:
First thank you for the replies very appreciated.
Tone_Capone I was going to try your method first. You are correct when I was on the updated firmware I did not flash the "fixed" 3e recovery did not realize there was one. My question now is I'm currently at 2e recovery, on the older firmware. Can I still follow those directions and put the modified 3e recovery onto the phone how it is. Or does the modified file count on other files being in place that I don't have since I'm downgraded? Do I need to update it again? I hate to ask but I just want to make sure.
chopper the dog Sorry about wrong section, thought q and a would be for commonly asked questions and the answers for them. I was gonna try this method then but I'm not sure if I choose bootloader in odin or pda like I did when downgrading the firmware.
Click to expand...
Click to collapse
refer to section 3...just replace ics rom with miui... although honestly I would go with ics 4.0
http://forum.xda-developers.com/showthread.php?t=1238070
thanks everyone, droidstyle I followed your links directions and miui is up and running. Very appreciated. I considered ics but I'll wait a while.
joebells said:
First thank you for the replies very appreciated.
Tone_Capone I was going to try your method first. You are correct when I was on the updated firmware I did not flash the "fixed" 3e recovery did not realize there was one. My question now is I'm currently at 2e recovery, on the older firmware. Can I still follow those directions and put the modified 3e recovery onto the phone how it is. Or does the modified file count on other files being in place that I don't have since I'm downgraded? Do I need to update it again? I hate to ask but I just want to make sure.
chopper the dog Sorry about wrong section, thought q and a would be for commonly asked questions and the answers for them. I was gonna try this method then but I'm not sure if I choose bootloader in odin or pda like I did when downgrading the firmware.
Click to expand...
Click to collapse
Glad we got it figured out.
Just for future reference, It is customary of this forum that if someone were to find a post helpful, go ahead and hit the thanks button on their post. Some guys take this very seriously.
Hello all!
So, after successfully flashing CM7 onto my LG Optimus One, after using a (very) simplified guide, the whole process has become a bit clearer. But as I am still a newbie, I will still need some help.
I would like to put CM7 on my Galaxy Player 4.0. I have seen the thread, but I have a few questions before I start.
One, the sticky in the dev section for CM7 on the 4.0 says I need to make some sort of back up with Odin/Heimdall. Well. I know what Odin is, I bought it from the marketplace only to realize that my device is incapable of running it, and after the dump file is created, I don't really know what to do with it. Any help, please?
Also, I downloaded CWM Recovery (I assume this is okay to use to flash CM7 on my device?), but when I tell the application to flash the recovery, it gives me a list of devices to choose from...the Galaxy Player 4.0 isn't listed. Does it matter which one I choose?
These next two I am seriously confused about. The prep instructions say to have a good kernel handy. Is this something that I'm going to flash onto my device? Install? Copy over? Or is it something that I'm going to do with whatever Odin/Heimdall is? Also, the instructions say to verify MD5 on the device...and I have no idea what that means.
Could anybody please, please clarify these for me? I just trying very hard to avoid any damage to my device.
Anyways, thank to anybody who posts any help, its highly appreciated.
ErkelMan said:
Hello all!
So, after successfully flashing CM7 onto my LG Optimus One, after using a (very) simplified guide, the whole process has become a bit clearer. But as I am still a newbie, I will still need some help.
I would like to put CM7 on my Galaxy Player 4.0. I have seen the thread, but I have a few questions before I start.
One, the sticky in the dev section for CM7 on the 4.0 says I need to make some sort of back up with Odin/Heimdall. Well. I know what Odin is, I bought it from the marketplace only to realize that my device is incapable of running it, and after the dump file is created, I don't really know what to do with it. Any help, please?
Also, I downloaded CWM Recovery (I assume this is okay to use to flash CM7 on my device?), but when I tell the application to flash the recovery, it gives me a list of devices to choose from...the Galaxy Player 4.0 isn't listed. Does it matter which one I choose?
These next two I am seriously confused about. The prep instructions say to have a good kernel handy. Is this something that I'm going to flash onto my device? Install? Copy over? Or is it something that I'm going to do with whatever Odin/Heimdall is? Also, the instructions say to verify MD5 on the device...and I have no idea what that means.
Could anybody please, please clarify these for me? I just trying very hard to avoid any damage to my device.
Anyways, thank to anybody who posts any help, its highly appreciated.
Click to expand...
Click to collapse
Ok so first don't flash CWM using the rom manager. Instead download this kernel: http://forum.xda-developers.com/showthread.php?t=1377771(I recommend 2.1 over 3.0 because people reports bootloops in 3.0). Flash it using odin or heimdall. Then if you want, make a backup using CWM. then download CM7 from here: http://forum.xda-developers.com/showthread.php?t=1527576&page=13 Flash and enjoy!
But as the red warning says: FOR DEVS AND EXPERTS ONLY. So if you don't know if you are doing don't flash it.
Thanks! But I'm still confused as to how to get Odin to work considering the Galaxy Player 4.0 isn't a supported device. Also the MD5 verification is still foreign as to what it is. I know it says only for devs, but I'm sick of the stock os on the player, and as seeing what CM7 can do on my Optimus One, I'm eager to get it on my player.
ErkelMan said:
Thanks! But I'm still confused as to how to get Odin to work considering the Galaxy Player 4.0 isn't a supported device. Also the MD5 verification is still foreign as to what it is. I know it says only for devs, but I'm sick of the stock os on the player, and as seeing what CM7 can do on my Optimus One, I'm eager to get it on my player.
Click to expand...
Click to collapse
You check the MD5 with a md5 check program to see if it matches. Also to use odin check on google or youtube. and for the rom manager app. koush just don't support it.
Thanks a ton, I'll start looking up the Odin issue.
Hello,
This thread does not get the aim to explain how to flash but simply requesting some GNU/Linux users with command line/interfaces of Heimdall because here is some issue I got flashing some packages.
I just installed a package containing stock ROM for Galaxy S for a friend. I got trouble and doubt with the boot.img because there is not a section named BOOT as modem.img which get MODEM or zImage wich get KERNEL (hopefuly I have been clear with that).
While trying to unzip some GT-I9300 firmware (wich is my current device), I found a Tz.img, but here again there is not any section for that file. And I REALLY do not want to lost my new born S3 but it is kind of shame to get an GNU/Linux distro' on my computer and not be able to find any clear tutorial for Heimdall. I really deplore the lack of information about that trully awesome flash program because I know this could be a choosed one software if some devs of the Heimdall project (or anyone else getting a minimal knowledge about it) could do a good, clear, and user-friendly guide. All I need, especially while attributing file .img with their section (again hopefuly I have been clear with that word).
Thanks for reading and If you're like me, make some feedback, I would like to know what are your though about that software.
Drakenlord78 said:
Hello,
This thread does not get the aim to explain how to flash but simply requesting some GNU/Linux users with command line/interfaces of Heimdall because here is some issue I got flashing some packages.
I just installed a package containing stock ROM for Galaxy S for a friend. I got trouble and doubt with the boot.img because there is not a section named BOOT as modem.img which get MODEM or zImage wich get KERNEL (hopefuly I have been clear with that).
While trying to unzip some GT-I9300 firmware (wich is my current device), I found a Tz.img, but here again there is not any section for that file. And I REALLY do not want to lost my new born S3 but it is kind of shame to get an GNU/Linux distro' on my computer and not be able to find any clear tutorial for Heimdall. I really deplore the lack of information about that trully awesome flash program because I know this could be a choosed one software if some devs of the Heimdall project (or anyone else getting a minimal knowledge about it) could do a good, clear, and user-friendly guide. All I need, especially while attributing file .img with their section (again hopefuly I have been clear with that word).
Thanks for reading and If you're like me, make some feedback, I would like to know what are your though about that software.
Click to expand...
Click to collapse
I would suggest getting your hands on a machine with Windows on it to complete the root process just because it has been done on Windows machines more so than any other. At least this way, you'll be able to complete everything rather fast by simply flashing via Odin.
If you are set on using Heimdall, best of Luck. Also do a write up because a lot of mac users & linux users would appreciate it.
Galaxys3root.com has a how to for using heimdall, I've used this method for rooting my phone.
---------- Post added at 07:23 PM ---------- Previous post was at 07:14 PM ----------
Although, depending on what version of Android you are on, rooting can be achieved without using heimdall or odin. The exynos exploit makes it easy just by installing supersu app and clicking root.
Thanks guys for your support, gonna take a look to your links.
Hopefuly we will not be forced to use windows to get an secure and complete flashprogram one day... "I have a dream that one day..."
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!