[KERNEL][5-2-11]Stock Kernel - No Recovery Flash - Fascinate Android Development

These kernels are the stock ED01 kernel that have been modified to remove the recovery flash that happens with the standard stock kernel on every boot. Nothing else has been modified. If you flash this, you can retain CWM, but these do not have any other changes or enhancements. There are two versions, stock and boot animation support. Stock uses the stock Samsung boot animations that the phone comes with. The second version enables custom bootanimation.zip support. These packages are Odin only, and I have no plans on making a non-Odin version.
Download:
Stock
Boot Animations

Thanks for the work man!
Sent from my SCH-I500 using XDA App

The stock boot animation one fails in Odin with an invalid MD5 hash, but I extracted the zImage, put it into a CWM flashable zip and it installed fine.

Is there really any benefit to these kernels? Because
I get great results with your -100uv kernel!!

ChrisDDD said:
The stock boot animation one fails in Odin with an invalid MD5 hash, but I extracted the zImage, put it into a CWM flashable zip and it installed fine.
Click to expand...
Click to collapse
You do realize that the MD5 hash is the verify that what you downloaded isn't corrupt? And that redbend_ua has no method to verify the validity of a file? And that what you did completely ignores the point of making the files .tar.md5 files?

imnuts said:
You do realize that the MD5 hash is the verify that what you downloaded isn't corrupt? And that redbend_ua has no method to verify the validity of a file? And that what you did completely ignores the point of making the files .tar.md5 files?
Click to expand...
Click to collapse
Yea, I know all that, but I thought I'd give it a try anyway. I figured I could always Odin one of the whole packages if it didn't work. I did download it several times to see if it was a corrupt download, and they were all the same.

pntballer505 said:
Is there really any benefit to these kernels?
Click to expand...
Click to collapse
Yes, they can be packaged together with CWM for newbies.

I'm on stock ED01. To prevent running the stock recovery, I renamed the following files:
/system/recovery-from-boot.p
/system/bin/recovery
/system/etc/install-recovery.sh
After they were removed, I re-flashed Clockwork 3 via Odin.

I have to say, I've been running this totally stock ED01 kernel for a week now, and I'm getting the best battery life out of ANY of the 2.2 (EB01 through ED01) kernels I've tried. Consistently getting 48 hours per charge pretty easily with normal use. I tried the undervolted kernels, and I tried underclocking, both of which had some instabilities, but this has been totally solid. Who'd have thought... from a stock kernel...

ChrisDDD said:
I have to say, I've been running this totally stock ED01 kernel for a week now, and I'm getting the best battery life out of ANY of the 2.2 (EB01 through ED01) kernels I've tried. Consistently getting 48 hours per charge pretty easily with normal use. I tried the undervolted kernels, and I tried underclocking, both of which had some instabilities, but this has been totally solid. Who'd have thought... from a stock kernel...
Click to expand...
Click to collapse
The best battery life I have ever had with my Fascinate was using the EC01 ROM which is nearly the same as ED01. I've had horrible and now bad (it's better now, but not what I would call good) battery life with the community rom combined with OTB reloaded kernel.
I'm going to un-voodoo and flash this kernel and see what happens.

Is the kernel from ED03 any different at all? Could it be made recovery safe?

Any chance of adding the tether null to this? I love the stock kernel but need to tether without worry. Thank you

Thanks a lot

Related

[ROM][Radio][4.10.11]EC01

EC01 must be old, right? Not so. I cannot give you the build date however, per request of...someone else. Its considerably newer than EC10, however. For some it may be hard to take my word for it, but I have never lied to anyone here.
In here you will find a new shiny radio, a voodoo or non voodoo EC10 kernel, courtesy of JT1134, and...a ROM!
No more hacking pieces together from other devices. No more crappy radios (hopefully). No more poor GPS (hopefully).
Please do not ask where it came from. I will not tell you. All file dates have been changed, the build.prop has been masked.
Please do not ask for an Odin. I will not give you one at this time.
Please enjoy yourself, I insist.
This ROM is ever so slightly tweaked. It is not a quality release by my standards (mostly because its stock). I recommend folks wait for the community rom to be finished. If you can't wait, by all means, flash away.
Does not include a kernel.
Debinged, browser included.
Debloated, yet contains most stock apps.
Custom boot animation, because I am not including the original kernel.
Dialer voicemail button points to Google Voice.
Your current kernel will be retained. So if you are using a Froyo kernel, you will be just fine.
Xoom boot animation because you will be using a custom boot animation supporting kernel.
Installation Instructions (read carefully)
---------------------------------------------------------
Make a nandroid backup.
Odin back to EB01 stock.
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
Boot once, then Odin clockwork recovery.
http://adbdev.com/danknub/cwm-recovery-ALL-3-30-FIX.tar
Boot straight to clockwork recovery, and flash my kernel of choice from here:
http://forum.xda-developers.com/showthread.php?t=1003017
Boot once, convert to voodoo if need be.
Boot back to clockwork recovery and flash rom.
Boot once, then Odin the radio.
Please follow these directions. There are apparently some kernel/cwr issues that are causing boot loops. If you decide to flash another kernel afterwards, be my guest. Don't wipe, however. The above directions are after hours of testing by IRC folks, and I THANK all of them!!!!!
Radio:
http://adbdev.com/danknub/ec01_radio.tar
Rom:
http://www.multiupload.com/ETEG610SJR
Reserved.
Edify compatible version coming out tomorrow.
<3 your the man
Much thanks man. You're always coming through for us. Thanks for continuing to work on the fascinate.
Sent from my SCH-I500 using XDA App
excellent work man, i new you werent going to give up on us, im gonna have to get the tbolt just so i can continue to use your work. ive been with your roms since my omnia
edit-kernal links are down, both of them.
NM me. I followed your post to a T and I was able to flash a diff kernel then. THanks guys
Great work! Thank you for the work. I'll take your advice and wait for the community rom, but VERY much appreciate your work.
jrobinsky said:
for me, only your kernel works dude. I tried a few other ones after my initial boot and i get stuck on boot loops. IDK about anyone else, but thats my results.
Click to expand...
Click to collapse
I was able to get times_infinity's comavolt voodoo to work, but only if I ODIN'd back to EB01 stock, then ODIN'd ec01 radio, ODIN 03/30 cwm fix, boot directly to recovery, flash ec01 rom, flash comavolt kernel, boot was successful. Going to play with it a bit tomorrow.......errr later today after I get some sleep.
Copied from my "Most Thorough Method of Fixing Every Problem You Might Have" section in the recovery thread, and adapted to this post.
This will wipe your data, btw, so be sure to backup any important info. You can make a nandroid backup, but you will probably have issues if you try to restore the data to use with this ROM.
[SIZE=+2]Bestest Best Way to Install This ROM[/SIZE]
Download to PC
CWM-Recovery 3-30 Odin Package
MD5 Checksum: 00e90e790a70e2d66b6cba6a152de504
ec01_radio.tar Odin Package
MD5 Checksum: 099c7cf67e14fea5c9bbd886a83e48b1
CI500_VZW_EB01_FROYO_REL.tar.md5
MD5 Checksum: d04733ce540ab1af291cfa44d42c768e
atlas_v2.2.pit
MD5 Checksum: a0eaf496375cf72b90f7ceef4f0a4538
Place on /sdcard
ec01_rom.zip
MD5 Checksum: 30849feb8d53b05c611fc9b03263a414
The kernel of your choice
Step-by-Step Installation - Important!
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package
Close odin, Unplug/replug the phone from USB, re-enter download mode, Re-open odin.
ODIN the modem
Unplug USB Cable, THEN reinsert your battery
Hold both of the volume keys and the power button down until a second after you see the Samsung boot logo, then let go
It should now boot into red CWM recovery
Wipe Cache only. Flash the ec10_rom.zip
Flash the kernel of your choice
Reboot. If you have installed a voodoo kernel, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
I can't stress enough how important it is to check your files for the correct checksum to verify that your download did not get corrupted (you can also use it as a way to make sure you have the right version). Also, follow these instructions exactly. You could potentially be wasting your time and anyone else's who is trying to help you fix whatever random issue you might be having, merely because you didn't follow the instructions.
I've been scanning threads for news of this mystery drop since your first hint and just as I'm about to cash out for the night... OMFG! You f'ing rock mate! Now, if I can only find the strength to hold out for the community brain child... I know it will be worth the wait. Oh, but a tasty new radio sure sounds delicious right now!
Thanks again Adryn for everything you've done to make this phone great!
Sent from my #@&$ing SCH-I500 using my %!#@ing XDA App
justin94 said:
excellent work man, i new you werent going to give up on us, im gonna have to get the tbolt just so i can continue to use your work. ive been with your roms since my omnia
edit-kernal links are down, both of them.
Click to expand...
Click to collapse
For now you can just get them from the superclean thread. Same ones.
Might be a silly question, but is it safe to odin just the modem and nothing else? I want to hold off on flashing the ROM and kernel.
Sent from my SCH-I500 using XDA App
tripacer99 said:
Might be a silly question, but is it safe to odin just the modem and nothing else? I want to hold off on flashing the ROM and kernel.
Click to expand...
Click to collapse
Yes, I believe it was verified to work just fine.
is there a reason why after i odin in the first step then go to odin recovery ... it just sits on "setup connection..."
lucas.scott said:
is there a reason why after i odin in the first step then go to odin recovery ... it just sits on "setup connection..."
Click to expand...
Click to collapse
Are you using Adrynalyne's steps or GizmoDroid's steps? Did you reboot phone and let it fully boot into OS before powering down to pull battery to start new ODIN session?
of course ... and im no stanger to odin or anything .. new problem for me
lucas.scott said:
of course ... and im no stanger to odin or anything .. new problem for me
Click to expand...
Click to collapse
Oh, ok, sorry. I didn't run into that problem when testing it before release so that's a new one on me. Only thing I can think of is trying to download the cwm-fix file again and try flashing it in ODIN again. Maybe you got a bad download. Try this one, different link location:
http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
landshark68 said:
For now you can just get them from the superclean thread. Same ones.
Click to expand...
Click to collapse
Which kernel are you using from the superclean thread? eb01 or eb16?
DeezNotes said:
Which kernel are you using from the superclean thread? eb01 or eb16?
Click to expand...
Click to collapse
Neither. EC10
landshark68 said:
Oh, ok, sorry. I didn't run into that problem when testing it before release so that's a new one on me. Only thing I can think of is trying to download the cwm-fix file again and try flashing it in ODIN again. Maybe you got a bad download. Try this one, different link location:
http://www.mediafire.com/file/06al8prkgj29gps/cwm-recovery-ALL-3-30-FIX.tar
Click to expand...
Click to collapse
thanks for the link man . that did the trick . bad DL i guess . thanks .

***READ THIS!!!!!!*** Going from CM7/MIUI/OMFGB to another rom/Unbricking your device

I figured I would put this out there for those who have flashed or are thinking of flashing CM7/MIUI/OMFGB/OMGB or any mtd rom for that matter. If you have flashed one of the aforementioned roms, then you will need to use odin if/when you choose to go to another non-mtd rom. But, you cannot simply use any odin file and there is a particular procedure that is needed to execute this correctly. *Note* This method will also work to unbrick your device from pretty much anything. ***PERFORM ALL OF THE FOLLOWING STEPS WITH THE BATTERY IN YOUR PHONE, DO NOT REMOVE BATTERY***
STEP 1. Open odin (http://www.mediafire.com/download.php?73ta726ghelw381) and place the linked file below in the "PDA" section and WAIT. You will need 7zip or the like to extract the tar image from the zip file below. This particular type of odin file is the only kind that I know of that contains the proper bootloaders to re-partition your phone. ONLY THE PDA SECTION!!!!
Link removed. My dropbox account was suspended due to excessive traffic. I'll figure out another place to upload and then post the link.
STEP 2. Then, place this file in the "PIT" section in odin and WAIT.
http://dl.dropbox.com/u/20070269/atlas_v2.3.pit <---*Atlas_v2.3 Re-partitioning "PIT" file*
STEP 3. And place a check in the "Re-partition" box in odin.
STEP 4. At this point you need to power off your phone. Then, enter download mode by holding the volume down button and continuing to hold it while you plug the cable into your phone, you should then see a yellow "downloading" screen popup. If/when this happens, go to step 5.
STEP 5. When you have done the first 4 STEPS, THEN hit the "START" button in odin and wait about 5-10 minutes until you see the green "PASS" in odin and profit. ***You must allow the phone to boot fully one time after running this odin process so that it can wipe the phone and complete the the re-partitioning.*** However, when the phone boots, you will be on stock, binged, bloated, unrooted TouchWiz. So odin a recovery and remedy that situation quickly!!! And just in case there are any misconceptions, you do NOT need to be rooted to install a custom cwm recovery.tar file with odin. So unless you plan on staying stock, you don't need to root again because any rom you flash will already be rooted. So just odin a recovery and boot immediately into the recovery via the 3 finger method (holding both volume up and down buttons and the power button at the same time and continue to hold them until you see the samsung logo). YOU MUST DO IT THIS WAY BEFORE THE PHONES BOOTS UP NORMALLY OR YOU WILL LOSE THE RECOVERY THAT YOU JUST ODINED! Then, as good practice, follow the instructions of the next paragraph.
And as a good suggestion, if you want voodoo converted partitions (in others words, if you want to flash a voodoo kernel) after odin does it's thing, flash this package (courtesy of navenedrob) from cwm recovery 3x before flashing whatever rom in conjunction with a voodoo kernel you were wanting to flash after coming from CM7 MTD/GB MIUI. Here is the link, flash this if you want voodoo partitions (ext4): http://dl.dropbox.com/u/20070269/ext4_formatter_all.zip . This will help to insure that you obtain a clean install of whatever rom/voodoo kernel you are flashing after coming from CM7 MTD/GB MIUI ***If you flash the Ext4 package, you must flash a voodoo kernel afterwards or you will have another brick.***
It is absolutely mandatory that you follow these steps exactly to properly get off of CM7 MTD/GB MIUI so that you can flash another rom. Attempting another method or not following these steps implicitly will result in eventual problems down the line and/or a bricked phone and you will have to follow this guide to fix it.
Thanks for the info.
Sent from my SCH-I500 using Tapatalk
kidserious said:
I figured I would put this out there for those who have flashed CM7 MTD or GB MIUI. If you have flashed jt's new CM7 MTD or andmer's AOSP GB MIUI, then you will need to use odin if/when you choose to go to another rom. But, you cannot simply use any odin file and there is a particular procedure that is needed to execute this correctly:
Open odin (http://download1422.mediafire.com/ii578172dylg/429fcpdtpckkcea/Odin3+v1.83.exe) and place one of "ONLY" these two files in the "PDA" section: These are the only odin files that contain the proper bootloaders to re-partition your phone. ONLY THE PDA SECTION!!!!
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5
Then place this file in the "PIT" section in odin:
http://download248.mediafire.com/z5q4aw8ablig/26xbh796jmwvwqb/atlas_v2.2.pit
And place a check in the "Re-partition" box in odin.
When you have done all of these things, hit the "START" button in odin and wait about 10 minutes until you see the green "PASS" in odin and profit.
It is absolutely mandatory that you follow these steps exactly to properly get off of CM7 MTD/GB MIUI so that you can flash another rom. Attempting another method or not following these steps implicitly will result in a bricked phone and you will have to follow this guide to fix it.
Click to expand...
Click to collapse
I will have to give this a try since I just chewed out Big Red for screwing up my phone with their ED04 OTA, wich I odin'd back to stock from JT's CM7 to get it.
I vote for a sticky
Sent from my SCH-I500 using XDA Premium App
Moved to the development section and temporarily stuck for now.
yep big +1
If you do all this and Odin hangs or something else fails to work, make sure you are using an OEM data/charge cord to do this. I did this exact beautiful brick a month ago was stuck believing for a good 8 hours that I had done it this time, because I was using a data/chord that was supposed to be an upgrade from the OEM chord. Fun times
kidserious said:
I figured I would put this out there for those who have flashed CM7 MTD or GB MIUI. If you have flashed jt's new CM7 MTD or andmer's AOSP GB MIUI, then you will need to use odin if/when you choose to go to another rom. But, you cannot simply use any odin file and there is a particular procedure that is needed to execute this correctly:
Open odin (http://download1422.mediafire.com/ii578172dylg/429fcpdtpckkcea/Odin3+v1.83.exe) and place one of "ONLY" these two files in the "PDA" section: These are the only odin files that contain the proper bootloaders to re-partition your phone. ONLY THE PDA SECTION!!!!
http://adbdev.com/danknub/CI500_VZW_EB01_FROYO_REL.tar.md5
http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5
Then place this file in the "PIT" section in odin:
http://download248.mediafire.com/z5q4aw8ablig/26xbh796jmwvwqb/atlas_v2.2.pit
And place a check in the "Re-partition" box in odin.
When you have done all of these things, hit the "START" button in odin and wait about 10 minutes until you see the green "PASS" in odin and profit.
It is absolutely mandatory that you follow these steps exactly to properly get off of CM7 MTD/GB MIUI so that you can flash another rom. Attempting another method or not following these steps implicitly will result in a bricked phone and you will have to follow this guide to fix it.
Click to expand...
Click to collapse
Bro, just a thought...But for people who follow these steps and STILL get issues, like force closes, the phone not saving your contacts or settings, etc. Then go to http://forum.xda-developers.com/showthread.php?t=1090127&highlight=ext4+formatter. Most of us, I think, use ext4, but RFS is the default for Samsung phones. Ext4 is what VooDoo converts your file systems to. Download the file system .zip of your choice, flash it in CWM, then re-flash your ROM, kernel, theme, etc. and it should fix your issues. I had many issues, this killed them all.
I am pretty sure the atlas file is not required if you are using the dl09 package. At least I was able to revert just fine without it.
solido888 said:
I am pretty sure the atlas file is not required if you are using the dl09 package. At least I was able to revert just fine without it.
Click to expand...
Click to collapse
you are correct, if you odin dl09 with the atlas 2.2 pit, it will only boot to recovery.
Copperhed said:
you are correct, if you odin dl09 with the atlas 2.2 pit, it will only boot to recovery.
Click to expand...
Click to collapse
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
kidserious said:
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
Click to expand...
Click to collapse
TRUE !!
even i have positive experience of using both these files .. either one works with the 2.2 pit file and i didnt loose root either !
Copperhed said:
you are correct, if you odin dl09 with the atlas 2.2 pit, it will only boot to recovery.
Click to expand...
Click to collapse
You HAVE to let it boot into stock recovery once after flashing the full Odin. Stock recovery needs to do an automatic data wipe before it boots into the OS. Which is why if you were to flash cwm right after flashing the full Odin, you'd get the datadata/dbdata issues.
Sent from my SCH-I500 using XDA App
krispuniq said:
TRUE !!
even i have positive experience of using both these files .. either one works with the 2.2 pit file and i didnt loose root either !
Click to expand...
Click to collapse
Wow, I don't know how you didn't lose root seeing as how neither one of those Odin packages are rooted and it does a complete data wipe.
Sent from my SCH-I500 using XDA Premium App
Good advice! regarding that ext4 formatting...
kidserious said:
I figured I would put this out there for those who have flashed or are thinking of flashing CM7 MTD or GB MIUI...
[...]
And as a good suggestion, after odin does it's thing, flash one of these two packages (courtesy of navenedrob) from cwm recovery 3x before flashing whatever rom you were wanting to flash after coming from CM7 MTD/GB MIUI. Flash this one: http://forum.xda-developers.com/attachment.php?attachmentid=614756&d=1307095153 if you want voodoo partitions (ext4) or this one: http://forum.xda-developers.com/attachment.php?attachmentid=614757&d=1307095153 if you want nonvoodoo partitions (rfs).This will help to insure that you obtain a clean install of whatever rom you are flashing after coming from CM7 MTD/GB MIUI ***If you flash the Ext4 package, you must flash a voodoo kernel afterwards or you will have another brick.***
[...]
Click to expand...
Click to collapse
This was essentially the process I followed a few days ago when I reluctantly reverted back to touchwiz framework for reliable call operation (CM7 MTD is getting so close).
After letting the DL09 image boot for the first time, I odined Times_Infinity's CM3 and booted straight into it with the intention of running navenedrob's ext4 formatter utility. I immediately heard the familiar scary voodoo lady reporting the lagfix conversion operation, backing up & restoring DL09 system and data files that I had no interest in keeping around, etc. Once it finished and I had TI's CWM on screen, I flashed navenedrob's ext4 utility to reformat.
So, to save some time and an unnecessary format cycle, here's a reminder to create a "/sdcard/voodoo/disable lagfix" file before starting this process .
FWIW, the latest imnuts PBJ kernel has a modified CWM (in yellow) that reportedly incorporates navenedrob's ext4 formatting enhancements, but I've had other issues with that kernel and there's no version to apply via Odin...
kidserious said:
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
Click to expand...
Click to collapse
While it may work with those 2 files, the atlas file is not required if using the dl09 tar. I am not a coder, but I believe it may be redundant to use that file with the dl09 tar. Either way, my phone has been fully functional on comrom for the past 3 days now, and I did not use the 2.2 pit file to revert from the 6.09 CM7 build.
solido888 said:
While it may work with those 2 files, the atlas file is not required if using the dl09 tar. I am not a coder, but I believe it may be redundant to use that file with the dl09 tar. Either way, my phone has been fully functional on comrom for the past 3 days now, and I did not use the 2.2 pit file to revert from the 6.09 CM7 build.
Click to expand...
Click to collapse
I hear you and that may be true, but it is just safer to post it the way I did.
solido888 said:
While it may work with those 2 files, the atlas file is not required if using the dl09 tar. I am not a coder, but I believe it may be redundant to use that file with the dl09 tar. Either way, my phone has been fully functional on comrom for the past 3 days now, and I did not use the 2.2 pit file to revert from the 6.09 CM7 build.
Click to expand...
Click to collapse
The atlas_v2.2.pit is required for repartitioning. Which is mandatory for coming off of MTD.
Sent from my SCH-I500 using XDA App
times_infinity said:
The atlas_v2.2.pit is required for repartitioning. Which is mandatory for coming off of MTD.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
What problems should I be anticipating since I didn't use it? I haven't had any problems yet.
Edit: I am under the impression the DL09 tar repartitioned for me.
kidserious said:
This isn't true. I have odined with DL09 and 2.2 pit file and repartition checked many times and it causes the phone to boot normally to stock. I have actually done it with both files many times. They both work just as I wrote it, at least for me and everyone else that I know.
Click to expand...
Click to collapse
+++++++1. I have used the DL09 file plus the atlas 2.2 pit file many times. It's the best thing for a good, clean, fresh start to build from. If you aren't using the PIT file, you aren't restoring your partitions back to where they need to be.
landshark68 said:
+++++++1. I have used the DL09 file plus the atlas 2.2 pit file many times. It's the best thing for a good, clean, fresh start to build from. If you aren't using the PIT file, you aren't restoring your partitions back to where they need to be.
Click to expand...
Click to collapse
And I'll reiterate, what problems will I be experiencing? Since I haven't had any yet?

[Heimdall][Odin][Stock][Root]UCKH7/KK6 Return/Unbrick to Stock (or Root)

Multiupload links removed - MU seems to be gone forever. I will repost an unrooted UCKH7 package in the next week along with a modem package - Until then, use the rooted package and then remove:
/system/xbin/su
/system/bin/su
/system/app/Superuser.apk
And then reboot
I have uploaded Heimdall/Odin flashable kernel ,rooted system, and modem images to dev-host. This should be sufficient to unbrick most hosed-up phones, as long as you didn't flash a bad .pit. Note that after flashing this, you might need to wipe data depending on what ROM you were coming from. If you bootloop or things behave wacky, enter 3e recovery (stock kernel means stock recovery) and do a Wipe Data/Factory Reset. If you are reverting from UCKK6 back to UCKH7 you MUST perform this step or wifi will not work. If you're coming from a 100% stock ROM and only using this to gain root, you should be able to keep all your data and not need to wipe.
The kernel is 100% bone stock, the system image is stock except that it is pre-rooted (su binary and Superuser.apk)
I am including the modem in a separate package since that goes in a separate modem slot, and I don't want to reupload a 200+ MB file if I don't have to.
The kernel + rooted UCKH7 system package is here: http://dev-host.org/UWm
Kernel + cache + rooted UCKK6 system package: http://dev-host.org/8LA
Download, extract the package using 7-Zip, which can be downloaded from http://www.7-zip.org/download.html, then either:
1) (Tested on Linux, should work on MacOS) - Extract the tar and flash the components with heimdall from the commandline as follows:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
for the kernel + system package, and:
Code:
heimdall flash --modem modem.bin
for the modem package
I've never had good results with the Heimdall Frontend GUI.
2) (Tested by Jivy26 for kernel + system, untested for modem) - Flash the .tar in Odin. I'm a Linux user, so I have only tested this with Heimdall so far.
Kernel + system package goes in PDA slot I believe, modem package in Phone slot.
If you are wondering why I used 7-Zip to compress the archive:
7-Zip provides better compression ratios than Zip
7-Zip is open source unlike RAR
If it were a zip file, some doofus would probably think it was CWM-flashable and complain that it didn't flash.
Also - great thanks goes to Jivy26 for providing a stock /system dump. Without that it would not have been possible to make the system image or get a kernel dump.
Coming in the next few days - stock unrooted /system package.
Also just added - a param.lfs backup from my device. This is NOT contained in an Odin-flashable .tar file yet, I'll work on cleaning up my packages when I'm feeling better. I came down with a nasty cold a few days ago.
UPDATE:
creepyncrawly has written an EXCELLENT step-by-step guide for flashing this with Odin. The guide is at:
http://forum.xda-developers.com/showthread.php?t=1313659
In addition, he posted an Odin-flashable tar package for just the stock kernel, for those who want to do a ! removal. I have mirrored the file (I don't trust Dropbox for long-term hosting) at http://www.multiupload.com/MD7SMMNG24 - his original post is at http://forum.xda-developers.com/showpost.php?p=18535109&postcount=174
Awesome, thanks. Downloading now.
*If it were a zip file, some doofus would probably think it was CWM-flashable and complain that it didn't flash.*
LOL! Enough said right there. Thanks Ent!
Worked great with odin, thanks.
If one was to add the correct pit file to your package would that fix a bad pit flash, as well as fix if one had messed up partitions?
They would be useful for flashing back from cm7 wouldn't it? Or am I completely off?
Sent from my SAMSUNG-SGH-I777 using XDA App
dayv said:
If one was to add the correct pit file to your package would that fix a bad pit flash, as well as fix if one had messed up partitions?
They would be useful for flashing back from cm7 wouldn't it? Or am I completely off?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Flashed from CM7 using just the PDA
jivy26 said:
Flashed from CM7 using just the PDA
Click to expand...
Click to collapse
Was that without or with a .pit file?
Sent from my SAMSUNG-SGH-I777 using XDA App
With a good .pit file, yes it could recover from a bad .pit flash.
As far as going back/forth to CM7 - I believe that differences in architecture between the original GS and the GSII (mainly no FSR/RFS proprietary modules) make going to/from CM7 much less painful.
dayv said:
Was that without or with a .pit file?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Yes without a .pit file
thank you for all your work and for educating me. I will make sure and hit the thanks button next time I'm on a PC.
Wish we could hit thanks button from xda app.
Sent from my SAMSUNG-SGH-I777 using XDA App
Flashed w/ Odin...stuck in a boot loop. Any other suggestion? I had CM7 on there but had no sound when making calls. Tried to go back to stock...SOL.
Had the phone 9 hours and haven't been able to make a single call yet.
Drew489 said:
Flashed w/ Odin...stuck in a boot loop. Any other suggestion? I had CM7 on there but had no sound when making calls. Tried to go back to stock...SOL.
Had the phone 9 hours and haven't been able to make a single call yet.
Click to expand...
Click to collapse
Enter recovery (this kernel has stock 3e recovery) and wipe data/factory reset.
Power off (may need to battery pull), then:
Hold VolUp+VolDn
Push Power until the screen turns on
Let go of Power, keep holding VolUp+VolDn until you're in recovery
Entropy512 said:
Enter recovery (this kernel has stock 3e recovery) and wipe data/factory reset.
Power off (may need to battery pull), then:
Hold VolUp+VolDn
Push Power until the screen turns on
Let go of Power, keep holding VolUp+VolDn until you're in recovery
Click to expand...
Click to collapse
thank you!!! worked
Thanks for the Kernel work!
Will it hurt anything if I'm already rooted and SU'd with other kernel method or should I factory reset? Also out of curiousity will sgs kernel flasher work?
not rooted
do u have a version for odin without the root ? im looking for 100% stock out the box rom ? (future warranty purposes ) thanks
drawde40599 said:
do u have a version for odin without the root ? im looking for 100% stock out the box rom ? (future warranty purposes ) thanks
Click to expand...
Click to collapse
+1 thanks
10char
Not able to access the download site, could you please attache here?
mjgspr95 said:
Thanks for the Kernel work!
Will it hurt anything if I'm already rooted and SU'd with other kernel method or should I factory reset? Also out of curiousity will sgs kernel flasher work?
Click to expand...
Click to collapse
No, shouldn't hurt anything. Should only need to wipe if coming from a significantly different ROM such as CM7 or an I9100 ROM.
drawde40599 said:
do u have a version for odin without the root ? im looking for 100% stock out the box rom ? (future warranty purposes ) thanks
Click to expand...
Click to collapse
Yes, but I figured this would be more popular and uploading one of these takes an hour. I'll put up the unrooted stock in a day or two as I'm doing kernel work. However it's easy enough to unroot, just remove the two following files:
Code:
/system/app/Superuser.apk
/system/xbin/su
keeploading said:
Not able to access the download site, could you please attache here?
Click to expand...
Click to collapse
It's WAY larger than XDA's attachment limit, sorry, no can do.
You end up getting the phone Entropy? Thanks for this btw.
Hey kids! Don't know if anyone here knows me, but I am an ex avid Captivate user. But I've been out of the game for so long (exploring webOS and BBOS7) that I am very behind. Anyone kidn enough to post a link to the newest Odin? Also, what slot do .tar files go into? The first one, PDA?
EDIT: Opened the file, definitely PDA Still, anyone have a good link to a working Odin? I remember at one time some Odin versions worked really badly, and I used the original 1.00 but I heard there is a 2 and I'd prefer to use that with this new phone.

Flash Cwm with Odin

Hi guys I am having a lot of trouble, I am trying to get ICS on my phone, but I don't have CWM, first I did some stuff with odin, and got a soft brick, luckily I returned to stock and am back. I am root, I tried flashing cwm but it won't stick, and I can't flash the zip in the stock recovery. Is there a way I can flash this with Odin?
You have root? No need to use Odin then. Use Mobile Odin; it's much easier, and it won't trip the flash counter.
It wants me to get the pro version, can I have an apk for the free one because I can't find it on the market
It says the device is not supported =[
nsilverman15 said:
It wants me to get the pro version, can I have an apk for the free one because I can't find it on the market
Click to expand...
Click to collapse
It's attached in the first post of this thread
oahceasgnikgneas said:
It's attached in the first post of this thread
Click to expand...
Click to collapse
still giving me android system recovery and not clockworkmod.... =[
nsilverman15 said:
still giving me android system recovery and not clockworkmod.... =[
Click to expand...
Click to collapse
Can you link what exactly you are attempting to flash to get cwm.
On the i777 recovery is part of the kernel so to get cwm recovery you should be flashing a kernel with cwm.
Sent from my SGH-I777 using XDA Premium HD app
dayv said:
Can you link what exactly you are attempting to flash to get cwm.
On the i777 recovery is part of the kernel so to get cwm recovery you should be flashing a kernel with cwm.
Sent from my SGH-I777 using XDA Premium HD app
Click to expand...
Click to collapse
Ooh, can you please give me a link to an odin kernel with cwm?
I can't use a cwm flashable one because I don't have ics, so I am going to need a tar.
Read this: http://forum.xda-developers.com/showthread.php?t=1511838
http://forum.xda-developers.com/showthread.php?t=1289460
You can use any of these - you just have to use some kind of archive manager and extract the "zimage" file (the zimage is the kernel) from the zip you download from this thread. Put that zimage on your phones sdcard (note there is no file extension on the zimage file) and you can flash that with mobile Odin.
Also I have not read through the op in a while but I think entropy included at least one straight Odin flashable kernel download link, but like I said above you can extract the zimage from any one of his links and that can be flashed in mobile Odin.
Sent from my SGH-I777 using XDA Premium HD app
Flashed, now it is just blank, I guess i'll wait a bit
nsilverman15 said:
Flashed, now it is just blank, I guess i'll wait a bit
Click to expand...
Click to collapse
What did you flash? And what do you mean by "it is just blank"?
Sent from my SGH-I777 using XDA Premium HD app
Dayv, Can you flash any of Entropy512's DD on 2.3.4 KH7 stock with root to get CWM with no probs? I know to flash the Zimg in mobile odin. Is that the only way to get CWM on the phone by flashing another kernel? Just wondering how to back up my stock kernel with out flashing another kernel with CWM. So I guess Entropy512's kernel is a stock modified kernel? Just trying to get this all figured out. Thanks for any info you can provide!
Edit: N/M I need to back up my stock ROM with CWM not the "Kernel" I get it now.... Will Entropy512's DD work with 2.3.4 KH7 stock with root with no probs?
snipe2nite said:
Dayv, Can you flash any of Entropy512's DD on 2.3.4 KH7 stock with root to get CWM with no probs? I know to flash the Zimg in mobile odin. Is that the only way to get CWM on the phone by flashing another kernel? Just wondering how to back up my stock kernel with out flashing another kernel with CWM. So I guess Entropy512's kernel is a stock modified kernel? Just trying to get this all figured out. Thanks for any info you can provide!
Edit: N/M I need to back up my stock ROM with CWM not the "Kernel" I get it now.... Will Entropy512's DD work with 2.3.4 KH7 stock with root with no probs?
Click to expand...
Click to collapse
Yes, Entropy's DD will work with KH7.
So what you're trying to do is...what? Back up your stock ROM? If you're just talking about the stock system image and kernel, you don't need to back those up; you can always download them again from the Return to Stock thread.
If you're trying to do a nandroid backup (full system + data backup), you can't do that without flashing a kernel containing CWM Recovery. Entropy's kernel is one of these. Just flash that kernel using Mobile Odin.
It seems you've confused a couple things, I'll clarify.
On these phones, CWM is included with the custom Kernels provided by Entropy512, or Ktoon or Siyah, et al. CWM however, is not a Kernel, when you boot into CWM mode, your bypassing the loading of the Kernel. Think of it like this. When you press the power button (and only the power button) on your phone, it's hard wired into the phone to boot the Kernel, the Kernel sets up a hardware environment, loads the RAMDisk etc and does it's thing. IF you have a Kernel that includes CWM, you can bypass this by loading CWM INSTEAD of the Kernel. Note, you need to reboot into CWM or use a different set of buttons to get there, power alone, is hard wired to boot the Kernel.
If you came from a different manufacturer, say Motorola, the above process is different, as they lock their bootloaders and you cannot change the Kernel, you use a different process to load CWM, and boot to it instead of the Kernel. As Samsung has an unlocked bootloader, the process of getting CWM is much simpler.
And Mattdm is 100% correct, no need to flash your stock recovery, it's easy enough to download it. If you've got your phone all setup just the way you want it and want to make a backup of it, boot into CWM, scroll to backup and restore, press power, choose backup, use volume up/down to scroll to backup and press power. It will create a backup in a folder called Clockworkmod. It can easily be restored via CWM if you have the need too.
Hope this helped a lil.
Wink
Thanks Mattdm and Winklie I see now it's a full system + data backup not a Kernel back up... Any tips on what one of Entropy512's DD to flash? I see people in that thread saying 12/8/2011? I just don't want the battery problem people talk about. I prob should be asking these questions in that thread huh? Thanks again!! XDA and all (well most) the people on here are the BEST....
snipe2nite said:
Thanks Mattdm and Winklie I see now it's a full system + data backup not a Kernel back up... Any tips on what one of Entropy512's DD to flash? I see people in that thread saying 12/8/2011? I just don't want the battery problem people talk about. I prob should be asking these questions in that thread huh? Thanks again!! XDA and all (well most) the people on here are the BEST....
Click to expand...
Click to collapse
Yeah 12/8 is a good one. I've always been partial to 2/28 though, and I've also had good results with 3/4. Try a couple and see which one works better for you.
Kernels behave differently on different phones. I am using the NEAK Kernel with amazing performance and battery life. Others have had problems, with the exact same hardware, so it shows a lack of maturity in the fab process for these kinds of variances.
As for changing Kernels, use a Kernel cleaning script found here http://forum.xda-developers.com/showthread.php?t=1428530 before each change.
Barring a problem (lockup, reboots, etc) you need a give a Kernel 3 or so battery charges to 'settle in' before you can really access the battery life. Like I said, different Kernels behave differently on different peoples phones, so what works for me, might not work for you. However it's so simple to change Kernels, feel free to experiment to find what suits your needs best.
Hope this helped.
Wink
Winklie said:
As for changing Kernels, use a Kernel cleaning script found here http://forum.xda-developers.com/showthread.php?t=1428530 after each change.
Click to expand...
Click to collapse
Shouldn't you use the script before each change?

Kernel Problems

I've found the old flashable Odin copy of Gingerbread, and I've flashed it with the default kernel being inside. However, after the process completed I still have 6.0 JB kernel. I cannot remove it.. anyone can help me out?
(This might be the problem I had with system dump and flashing previously)
Zip or tar?
Sent from my YP-G70 using xda app-developers app
tar
Jistropy said:
I've found the old flashable Odin copy of Gingerbread, and I've flashed it with the default kernel being inside. However, after the process completed I still have 6.0 JB kernel. I cannot remove it.. anyone can help me out?
(This might be the problem I had with system dump and flashing previously)
Click to expand...
Click to collapse
Try using a PIT when flashing. That will make sure Odin maps partitions correctly.
Pushed with Heimdall, and honestly had no luck. There is about 20 different things I tried to get this working and none of them worked correctly. Giving up as of now.
Jistropy said:
Pushed with Heimdall, and honestly had no luck. There is about 20 different things I tried to get this working and none of them worked correctly. Giving up as of now.
Click to expand...
Click to collapse
I've always been able to flash Entropy's kernel (assuming yr on US) with CWM, even when coming down from ICS/JB. Try that if you haven't yet tried

Categories

Resources