Related
Please Read
This will not change anything on your phone that would prevent you from ever flashing a new rom or nandroiding back to a working one. Everything this update will do can completely be erased with a wipe or nandroid. Also flashing any rom, clean install or not, will preplace the boot.img this update.zip puts on your phone. So dont blame these downloads for your simple user errors of not being able to flash a new rom or nandroiding.
This is an overclocked kernel from toastcfh godmode .29 source. The kernel was actually pulled from Fresh Toast
This works on DamageControl and roms based off of his, it will not effect any of DC mods, including the Dconig app.
UPDATE
6/6/10- This should be working on the newest damagecontrol 2.09. Please report (if overclocking has worked in the past for you) if you have a problem on the newest release.
Click to expand...
Click to collapse
I made an attempt to get compcache to work, so it might or it might not. Someone with more experience might want to double check it.
Both include setcpu.txt for Setcpu OC app.. Select "custom" at the very bottom for device. Do not select hero. Or you can select "Auto Detect" at the top, this does not need the setcpu.txt.
*View attachment damage710v2.zip* THIS IS A TEST KERNEL FOR THE NEWEST DAMAGECONTROL 2.09.. It is the exact same as damage710 but with a newer ramdisk, this is in hope of fixing any problems anyone is having with 2.09 and OC kernel. There might not even be a difference in the new ramdisk between the old one. I didnt have time to check. Sooo ya.
*View attachment damage537.zip* 537mhz is the default.. scalable to 768 if you use an OC'ing app
*View attachment damage768.zip* 768mhz default clock speed -read below
*View attachment damage710.zip* 710mhz default clock speed -read below
Both can be scaled from 19.2 to 768mhz..
DAMAGE710--The damage710 will default 710mhz, you must use an OC app to scale it to 768. Use damage710 if your phone can not boot the 768mhz. And dont scale any higher then 710mhz or your phone might reboot.
DAMAGE768--If your phone can boot the 768mhz then either download will work. But if you dont want to use an OC'ing app then the damage768 will scale to 768mhz.
This IS a flashable update.zip.. This will only replace your boot.img of your phone. So it is not a full rom. This is applied on top of your rom.
ALWAYS MAKE A NANDROID BEFORE FLASHING.
You Do Not Need A Partition On Your Sdcard For Overclocking
THIS IS A MUST FOR SWAP/compcache
To get swap working, you must have an ext partition on your sdcard. This will format you sdcard erasing everything, so do the following. Back up everything from your sdcard to your computer(exp- In a folder on your desktop named Sdcard). In recovery, select partition sdcard, use all default values, 32mb swap, 512mb ext partition, the rest fat32. Then when its finished change ext2 to ext3. Then reboot the phone. And then move all the files you backed up to the computer back to your sdcard.
If thanking me for putting this together. You should also give an even bigger thanks to Toastcfh for this kernel.
Thanks also goes to flipzmode, cuz i pulled the kernel from his boot.img in fresh toast.
Also darchstar for the defaulting clock speed tip.
So does this mean we can get the real AOSP dialer on Damaged's ROM?
mattshaver said:
So does this mean we can get the real AOSP dialer on Damaged's ROM?
Click to expand...
Click to collapse
No.. this just adds overclocking and the few extra things that come along with it in the kernel. Has nothing to do with AOSP.
you rock
10 char
Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
If anyone wants to know how to do this, follow this guide starting at Step 8.
Essentially just extract the kernel you want from the right boot.img, extract the ramdisk from the other boot.img, then use mkbootfs and makebootimg to put them back together.
PM me if you need help.
mattshaver said:
Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
Click to expand...
Click to collapse
I dont mind, ask anything here. Its how we learn
But that was the issue with all 2.1 roms. Toastchf cracked the code (in a way, not literally). And was able to give us a working source for .29 kernel. That kernel can then be used to work on any cdma hero 2.1 rom. But there are different things you have to do to get it to work on Darchdroid AOSP rom, he has already done that and its in his newest release. This one I posted above is just to work with damagecontrol roms or ones based off of it.
To get the AOSP dialer working you would have to have a rom based on AOSP, which darchdroid is the only rom so far. All the other roms are based on htc framework or just something different then AOSP. But im pretty sure theres AOSP dialers for damagecontrol. Go check the apps and themes section.
EDIT: the dialers are also completely separate from the kernel. Its based on what the rom is.
i'm running ic3rom and in the process testing it out
jeremysterling said:
i'm running ic3rom and in the process testing it out
Click to expand...
Click to collapse
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Jus10o said:
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.
Click to expand...
Click to collapse
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Re: [KERNEL] Toast-godmode .29 source for DamageControl
So I can flash this and oc icerom? Etc....
-------------------------------------
Sent via the XDA Tapatalk App
mattshaver said:
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
Click to expand...
Click to collapse
Haha well you are right sorta on what the kernel does, but all cdma htc heros use the same kernels but it depends on what android version you are using. 1.5 uses .27 kernel, and 2.1 can use a edited .27 kernel but something things wont work, like camera. What toast did was made his own .29 kernel based on other sources and what we already have then we use for our 2.1 roms. The 2.1 roms that come from sprint use a .29 kernel that work, but we cant edited anything within the kernel until they release the source to the kernel. You must have source to the kernel to be able to change anything with in it. You cant download a rom from xda and take the kernel out and change the files and put them back. You have to already have the files to the kernel, change what you want, make your own kernel and then put it on the rom. Cuz once you compile the kernel its not able to be opened back up.
In a boot.img there are 2 parts, the kernel and a ramdisk. The ramdisk CAN be opened back up and changed. But if its trying to call something within the kernel it has to already be there, since you cant add anything to it. If you start with all the kernel files and compile your own like what toast did, then you can add the special things like overclocking frequencies.
I know I really suck at explaining things. I only know the basics of how it all works.
jeremysterling said:
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Click to expand...
Click to collapse
And you have the compcache.. or the newer one i posted?
Jus10o said:
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
Click to expand...
Click to collapse
Decad3nce said:
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Click to expand...
Click to collapse
sweet im gonna give it a try
Jus10o said:
And you have the compcache.. or the newer one i posted?
Click to expand...
Click to collapse
i downloaded and flashed damage1.zip with compcache
jeremysterling said:
i downloaded and flashed damage1.zip with compcache
Click to expand...
Click to collapse
Ok thanks.. yea compcache and swap arent working. Ill work on it.
But overclocking and everything else is. So its not gunna make a noticeable difference.
CAUTION: ANY CUSTOM ROM WHICH HAS A MODIFIED KERNEL, PROBABLY WILL BREAK BY USING THIS.
More than likely you will need to copy over the ramdisk. If you don't know how to do this, then wait until your ROM developer does it for you!
Who: For those who are ANXIOUS and the DEVELOPER type (more advanced users) who want to load the new kernel which comes with the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip released today.
If you're not an advanced user or the developer type, please wait for the builder of the ROM you're using to release their own update!
What: I've pulled the boot.img from the firmware.zip inside of the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip and put it into this update.zip.
Tech Details: This update.zip copies flash_image and boot.img to /system/bin and /system, flashes the new boot.img and deletes boot.img from /system. My first time creating this type of update.zip on the EVO!
Advantages:
npace said:
Here's a rundown of the issues that I tested for fixes:
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
Click to expand...
Click to collapse
http://www.joeyconway.me/evo/stock/jk-stock-OTA-1.47.651.1-kernel-signed.zip - WiFi will not work until the System Software portion of the OTA update is loaded
I got my retard helmet on and I'm ready to test this baby on Avalaunch's Froyo ROM.
Sorry for the noob question, I'm new to android. Is this for stock rooted roms? I am running stock evo rom rooted and nand unlocked, so is this essentially an update for rooted users running stock rom? And will I have to update the radio with a seperate flash? Thanks for your help, and everyone's hard work!
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
snandlal said:
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
Click to expand...
Click to collapse
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Any comments from people that have this applied (and working with full root)?
Shane Pitman said:
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Click to expand...
Click to collapse
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
That worked Thanx
Kernel's working just fine with Avalaunch's Froyo ROM.
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
I've got most of the Sprint/HTC crap removed, rooted, nand unlocked, custom recovery, running joeykrim-original-1.0.8 deodex rom, and this worked just fine.
lafrad said:
Any comments from people that have this applied (and working with full root)?
Click to expand...
Click to collapse
this ONLY updates the kernel and will not effect root access.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
this is ONLY the kernel. has nothing to do with ANYTHING in /system including bloatware/apps.
npace said:
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Click to expand...
Click to collapse
nice. i remember seeing this once but had forgot about it.
i prob wont delve into this yet cuz i haven't modified the ramdisk at all, but this is encouraging!
ill prob wait till we get some htc source code for the kernel, and then dive into customizing the kernel and the ramdisk or if i get bored and wanna customize my ROM with this stock kernel and custom ramdisk!
this is def good to know! thanks for the link!
Did anyone else have an issue with 4G stuck saying its turning on? Worked fin again after.restoring a backup.
Yep... 4th got stuck for me. Camera ad ADW also crashed a bunch too
Sent from my PC36100 using Tapatalk
This kernel is intended to be a simple rooted kernel, based off samsung stock, with only simple mods ... its feature are:
NEW!!! NOW HAS CWM 3.1.0.1 RFS/EXT/USB CWM REBOOT RECOVERY AND ROM MANAGER SUPPORT!
I do think this will be my last froyo kernel build... unless some bug comes up, that has to be fixed...
Kernel developers: feel free to rip my initramfs, for cwm 3.1.0.1 reboot recovery, it should work with all known builds, and may need just a little editing of the .rc files and sdx.sh in /sbin, to get your mods in place. The github is updated, and is ready for prime production!
Changes and features as of v1.05:
* CWM reboot recovery updated to 3.1.0.1 Purple edition, with customized recovery for the Epic4G
* Voodoo sound updated to v9, from supercurio
* busybox 1.18.0 removed, and cwm recovery busybox full 1.16.2 is replacing it, making the kernel even smaller
* thumbEE kernel support reverted, as my testing indicates that deep sleep is affected, draining battery faster
Changes and Features as of v1.04:
* ClockworkMod 3.0.2.5 Reboot Recovery, compatible with RFS and ext4
* fixed busybox DNS, thanks Rodderik!
* Added scripts for USB Mass Storage, mountums & umountums
* Voodoo Sound Driver v8 update, from supercurio
* RNDIS / wired USB tethering support built in from kernel
* THUMBEE built in from kernel for cortex a8 optimization, thanks Rodderik!
* build_kernel.sh modified to reflect EpicCM/nullghost script, but with some special revisions.
* rclean updated, to clean root files without any errors, in case would like to be used, before a stock kernel flash
* Root and busybox with minimal system mods
* designed to allow OTA update after flashing back the stock kernel, provided the user hasn't modified other necessary system files
* RFS and ext4 compatible
* REBOOT RECOVERY TO CWM 3.0.2.5 BOTH RFS AND EXT4, ROM MANAGER COMPATIBLE
* CIFS, TUN, & TMCPSS Clamping enabled from kernel
* market app malware patch, writing blank /system/bin/profile at boot
* mkasick sysfs keyboard patch, with my keytimer script
* voodoo sound 7 by supercurio, controlled by voodoo control app in android market
* additonal custom scripts in /sbin for cleaning root, busybox, and flash kernels and recoveries
This kernel was built to replace the traditional one click root method for my all in one root and recovery script.
Link:
DRockstar.Clean.Kernel.EC05.v1.05.zip
NEW!!! for flashing with Odin, we'll have to get used to this, in future, for rooting the phone by flashing a rooted kernel
You can use this odin flash to effectively root the phone:
Clean.Kernel.EC05.v1.05.tar.md5
Sources:
http://github.com/DRockstar/Clean-Kernel-EC05
Credits:
* kain203: donated the use of an 8 core linux vm for my use in compiling kernels and the cwm binary. This *greatly* increased my productivity, and allowed me to edit and compile everything for cwm and my kernel, *all* from my Epic 4G, believe it or not...
* noobnl & joeykrim- this kernel was originally inspired by noobnl Andromeda kernel for eclair, and uses the same joeykrim root and busybox method
* Rodderik, without his guidance, patience, and original working victory_03_defconfig, this kernel wouldn't have been possible. Some commits in sources taken from his sources.
* supercurio, for his voodoo sound, commits directly from his github source
* mkasick, for his sysfs keyboard patch
* nullghost and tanimn, for help getting github set up, and having easy to follow github sources
* koush, for ClockworkMod, and help in finally getting dualfs support, and direct input for cwm
* vocaltreat, for purple cwm icon
* skeeterslint and Rodderik, for helping me get packages installed, and ClockworkMod binary compiled
Sent from my SPH-D700 using Tapatalk
NICE!
Do you BONSAI?
Nice work man keep it up!
goodness, I went to vote this 5star and my machine hiccupped and rated it one star. your work here is awesome, keep it up
contradude said:
goodness, I went to vote this 5star and my machine hiccupped and rated it one star. your work here is awesome, keep it up
Click to expand...
Click to collapse
You can always go back, and revote the star rating...
Sent from my SPH-D700 using Tapatalk
Hey there, thanks for this, but I'm unable to update profile or prl. I get the unknown error. I am running ace rom v2. Any tips?
Sent from my SPH-D700 using XDA Premium App
lattiboy said:
Hey there, thanks for this, but I'm unable to update profile or prl. I get the unknown error. I am running ace rom v2. Any tips?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
There was a fix for this in another thread. I don't think it's related to the kernel though cause I was able to update my profile and prl successfully.
EDIT: This is the thread I was referring to, may want to check it out:
http://forum.xda-developers.com/showthread.php?t=1041415
Good work man.
Sent From My Evo Killer!!
blazinazn said:
There was a fix for this in another thread. I don't think it's related to the kernel though cause I was able to update my profile and prl successfully.
EDIT: This is the thread I was referring to, may want to check it out:
http://forum.xda-developers.com/showthread.php?t=1041415
Click to expand...
Click to collapse
Thanks. I followed the instructions, but it now says "Internal Error". Hmmm.....
I wouldn't care, but to use my Airave correctly I'm supposed to update PRL and Profile.
lattiboy said:
Thanks. I followed the instructions, but it now says "Internal Error". Hmmm.....
I wouldn't care, but to use my Airave correctly I'm supposed to update PRL and Profile.
Click to expand...
Click to collapse
Strange, you may want try rebooting the phone and trying again. This issue should have been resolved but then again I always had problems updating the profile/prl even when it wasn't on Sprints side with my first epic. I got a replacement (refurb) and haven't had any issues since.
Why would someone rate this thread less than 5 stars? ...
Anyways great job dude you released some good stuff
Hey DRockstar,
good work on putting out a clean kernel. I havent had any time to look into the modem delta thing lately.
Since you compiled the kernel you must know if the USB driver is compiled into the kernel. I'm suspecting it is right? If so maybe flashing a new kernel can actually fix my USB problem.
LiberatorUSA said:
Hey DRockstar,
good work on putting out a clean kernel. I havent had any time to look into the modem delta thing lately.
Since you compiled the kernel you must know if the USB driver is compiled into the kernel. I'm suspecting it is right? If so maybe flashing a new kernel can actually fix my USB problem.
Click to expand...
Click to collapse
I didn't mess with the usb drivers, and no one has reported any problems connecting usb. You can feel free to see if this fixes your USB problem, but I doubt it will have any bearing on it, honestly.
Sent from my SPH-D700 using Tapatalk
Well I still don't understand how people with DK28 can have USB problems since they seem like independent systems. So if flashing DK28 screws up a USB config or something then flashing a new kernel might help. Its a long shot but worth a try.
Do you know if this one works with CM7 A4?
LiberatorUSA said:
Well I still don't understand how people with DK28 can have USB problems since they seem like independent systems. So if flashing DK28 screws up a USB config or something then flashing a new kernel might help. Its a long shot but worth a try.
Do you know if this one works with CM7 A4?
Click to expand...
Click to collapse
No, it won't.
I wish I could give this a try right now, but i don't have a computer to install clockwork on my phone. guess i'm waiting till quitting time.
just a side note the link in the OP has a typo
http://drockstar.devphone.org/EpicKernel/DRockstar.Clean.Kernel.EC05.v1.02.zip
Does anyone know, is there something like this I can flash, that will give me ext4 cwm3? Cant get to a computer right now.
Oops, wrong thread.
Sent from my SPH-D700 using Tapatalk
Can someone point me in the direction of a clockworkmod flash that doesn't also root. all the ones i have found seem to be expired links
Can't wait to try this. Thanks
@ masterface: Use the one posted by Dameon. Right click to open it. Open in new window. Then you should be able to download it like normal instead of getting blank page. Hope that helps
Sent from my SPH-D700 using XDA Premium App
Originally this was going to be something I would do for Kyorarom v0.2.0, but I will also let the general public in on my works.
I am currently going through every single file in CM6.2 and seeing if it will work on Froyo with little to no effort. Why? Well think of it as a poor mans alternative to a fully functioning CM6.2. I respect marcellusbes work 100% but there are so many people who are being impatient about the non-existant ETA of CM6.2 and CM7 (BECAUSE IT SAYS THERE IS NO ETA AND THERE SHOULD NOT NEED TO BE AN ETA), I decided to give the people half of what the want: the performance and open sourceness of CM6.2 while still retaining 100% functionality of the Samsung firmware.
Current Status
99% of the bins are working
A few CM apps are working
Some of the libs are working (but they are more just sitting in there)
--- CONSIDER THIS VERY MUCH IN BETA - THIS WILL HAVE A FEW BUGS HERE AND THERE SO PLEASE REPORT ALL OF THEM SO I CAN FIX THEM ---
Now remember, this is by no means an alternative to CM6.2, it is more of a stopgap for people who really want our phone to have CM6.2 on it.
I have been working on this all day today and haven't been able to actually test it properly, but it appears to be stable with the files I have added, and it also appears to be quicker. Not by much, but it feels a little smoother.
Why would I need this?
As I said, it's a poor mans CM6.2. It will give you 90% of the performance of CM6.2 while still giving you 100% functionality (provided I haven't broken anything) from Samsung firmware. Programs run quicker, the system responds faster, and the system just feels smoother in general. It's not like FuguTweaks or V6 Supercharger which gives you a tiny change, the goal of this is to give you a HUGE change.
What is noticably quicker?
Well I need people to tell me that, but what I have noticed is quicker is:
Screen rotate happens quicker
Scrolling through menus
Swiping around websites
System boot time
What do I need to use this?
Well I have only tested this on Kyorarom v0.2.0 alpha (unreleased), so I don't know how your results may go, but it SHOULD work on all JPS based SAMSUNG ROMS.
THIS IS NOT A PATCH FOR CM6.2! THIS IS A PATCH FOR SAMSUNG!
You will also need CWM with update.zip signing disabled. This is provided as an update.zip as there are SO MANY permissions that need to be set in the bins/xbins/libs that it would be ridiculous to tell people to run an ugly script which will probably not work on 99% of peoples computers, so an update.zip without signing is how I will do this. Why no signing? Because every guide I have followed to tell me how to sign a zip or an APK has done nothing useful. SOMEONE TELL ME HOW PLEASE!
How do I install this?
Just put this on your SD Card, go into CWM and tell it to update from an update.zip. Pretty simple. I highly recommend doing a system.img backup first though to be on the safe side in case something goes terribly wrong. Format your /system before restoring the system.img.
What should I do if I get a bug such as a force close or a random reboot
Get your phone right to just before the crash happens
Plug your phone into ADB
Go into ADB SHELL
Type logcat > /sdcard/crashlog.txt
Reproduce the crash
Wait until it has rebooted/force closed
Press Ctrl-C on ADB SHELL
Get the crashlog.txt off your SDcard and paste the last about 20-30 lines in a code box here telling me what you did to cause the crash.
Links
Patch 0.3.1 (requires Samsung firmware, recommended to be on JPS)
CMapps 0.3.0 (should work on Samsung firmware without CMbins)
CMbins Remover (will only replace the bins with the original Samsung bins)
Patch v0.2.0 (requires Samsung firmware, recommended to be on JPS)
Busybox Fix (for in case you installed any of the patches v0.0.3 and below - NOT AN UPDATE.ZIP: THIS IS A BUNCH OF FILES WITH A README)
Please note that this may play up with some custom themes, especially large ones such as MIUI as this replaces a lot of files which these themes may be using or rely upon.
Credits
marcellusbe for his incredibly hard work on CM6.2 and CM7 which sadly seems to not be appreciated as much as it should by some of this community. Please go over to both the CM6.2 and CM7 threads and thank him for his hard work, even if you have already done so.
Change Log
v0.3.1
Removed more pointless stuff such as the etc and libs as they won't provide a performance boost. They were more decoratio.
Fixed install script which removed TW apps but didn't replace them from v0.3.0.
v0.3.0
Removed pointless bins which don't provide any performance boost, such as ping and stuff.
Fixed force close lag bug.
v0.2.0
Added the last few bins that were missing. Only bins missing are the ones that cause the system to break.
Added a few more things from etc from CM. They shouldn't cause any difference.
v0.1.1
Fixed dalvik-cache building.
v0.1.0
Removed xbin. It was causing too many problems
Added a few libs (ones that aren't in Samsung)
Added a few items from etc
Replaced a few stock Samsung apps in order to clean the system up before I remove twframework.
v0.0.3
Fixed the missing meta-inf folder in the update.zip. Sorry guys!
v0.0.2
Fixed the busybox issue. the patch removed the old busybox and replaced it with a broken one. If this doesn't fix it then 'mount -o rw,remount /dev/block/stl6 /system' and 'chmod 755 /system/xbin/*'
I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!
cdesai said:
I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!
Click to expand...
Click to collapse
If you wish to help me then by all means I'll be grateful. I am nowhere near finished as there are a few files in /system/bin that still need checked to see if they cause issues. I just went through the alphabet and if a file such as 'dexopt' caused problems then I left out all of D. However that's just an example. Dexopt is left out, but I left in the rest of D as I found it causing problems later down the track. I know I am missing Q and S. I'm gonna go through them all tomorrow.
EDIT: Not to mention I want to go through frameworks and libs and the etc folder too.
I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.
Sergiales said:
I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.
Click to expand...
Click to collapse
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.
@hillbeast
you also plan to port the framework of cm6?
ale_bot said:
@hillbeast
you also plan to port the framework of cm6?
Click to expand...
Click to collapse
I hope I can. The plan is to get everything that will work from CM6.2 in Samsung firmwares to work.
New version uploaded. See first post for details.
I fixed the busybox issue. I thought I fixed it earlier but aparently not. It was CM6.2s Busybox being in there that killed it. I put the Samsung one into v0.0.2 so it'll fix the grief it caused with version 0.0.1.
If it still causes issues then go into adb shell (or Terminal Emulator) and run this code:
Code:
mount -o rw,remount /dev/block/stl6 /system
chmod 755 /system/xbin/*
Donate and get rewarded
Good work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
You (just caught you user reading this), could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones (dharamg3, marcelubes.. and some of all the other great programmers) donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!
(•.•) said:
Gut work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
Yes You, could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!
Click to expand...
Click to collapse
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.
hillbeast said:
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.
Click to expand...
Click to collapse
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.
(•.•) said:
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.
Click to expand...
Click to collapse
Yeah that is the entire point of the XDA: developers helping developers to make our phones incredible and help them reach their true potential.
People bash the Galaxy 3 but undreneith it's actually a really good phone with really good hardware. It's no dual-core Cortex-A9 with 1GB of DDR2 RAM or anything, but it's certainly a very good mid-range phone. It was just held back by Samsung not programming it right.
Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!
niteshtak said:
Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!
Click to expand...
Click to collapse
Yes however I also need to find what is compatible with the rest of Samsungs firmware.
hillbeast said:
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.
Click to expand...
Click to collapse
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.
Guys I totally forgot the meta-inf folder in v0.0.2. You can just use the one from v0.0.1 as there is no signing or anything. I'll see if I can get the link on my phone for v1
Sent from my GT-I5800 using XDA App
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
Well its just a try to get the CM6.2 speed and smoothness on the samsung ROM..without having the bugs of CM6.2 which arent solved yet...
Sergiales said:
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.
Click to expand...
Click to collapse
Same problem in 0.2 with busybox installer, even trying to fix it with adb.
Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
As I stated in the OP, Cyanogenmod is incomplete and is buggy. The camera doesn't work, the FM radio doesn't work, no Bluetooth, and some things are buggy. By working in the opposite direction of moving to Cyanogenmod with small steps by using the working components from it, we get a balance.of speed and functionality which is what a lot of people have been moaning about all this time since CM went alpha.
Again, huge respect to marcell for getting it this far. This is a huge achievement from him.
Also here is the mediafire link for v1 so people can grab meta-inf and insert it into the v2. I will fix this in v3 later today.
Sent from my hybrid Kyorarom + Cyanogenmod Galaxy 3
Hi guys!
As some of you must have noticed, latest Samsung GT-I9500 firmwares carry a kernel configuration supposed to prevent SETUID privilege elevation.
Stock unmodified firmware with root is my preferred setup but also a strong dependency for all my development, for me this change is a massive setback if not a dealbreaker.
While poking around I found in about an hour something weird that reveled being a vulnerability, so I created a little thing to make it useful for now.
README:
Stupid SU: Galaxy S4 root helper by François SIMOND aka @supercurio
Circumvent an extremely weak false-security "Anti Root" mechanism implemented
on latest Samsung Galaxy S4 devices (on both Exynos and Qualcomm versions)
Preventing proper root function on official firmware breaks all my Voodoo apps
requiring stock+root and is a move that's hostile to both users and developers.
Samsung security might be embarassed by this proof of concept, as it defeats
their mechanism in a single line... not even with complex ARM assembler
but *one* line of shell script.
However, the goal here is to show Superuser solutions developers how to
deal with those devices for now, and provide a working solution to people who
bought a Galaxy S4 expecting to root it cleanly and easily but cannot.
This proof of concept is slightly slowing down Superuser calls, but its
"plain text" implementation has the merit of showing how stupid this exploit is.
SELinux configuration stays unmodified and active.
Features:
- Detect and supports both SuperSU and Koush's Superuser
- Installs Super SU binary by default
Make sure you have one of those Superuser apps installed:
- https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
- https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Root feature doesn't rely on a "StupidSU kernel" which is only an installer.
Feel free to flash back Samsung's original boot.img from their official firmware
after booting at least once.
Important Note:
This "exploit" is so lame that it will be fixed in no time, making updated S4
a pain to root again.
I wish Samsung will reconsider their "Anti Root" approach, which is damageable
in every regard and defective by design as demonstrated here.
Also, I'm simply not interested developing for and promoting devices from
manufacturers hostile to developers: It's just a waste of valuable time.
Click to expand...
Click to collapse
INSTALL
1/ copy rooting/ directory in your initramfs
Make sure "root.sh" file is has an executable permission (chmod 744 recommended)
2/ Add those lines at init.universal5410.rc end:
# Stupid SU
service rooting /stupidsu/root.sh
class main
user root
group root
oneshot
3/ Assemble your initramfs with the associated Samsung official kernel binary
of choice in a regular boot image
4/ flash as boot.img
5/ At each boot, Superuser app are detected automatically and su binary adjusted
accordingly.
Click to expand...
Click to collapse
Source code
On GitHub
License
Kernels downloads, only for demo purposes of the concept, you can flash back original Samsung boot.img once rooted
GT-I9500 Stock + root StupidSU v4 UBUAMDE
GT-I9500 Stock + root StupidSU v4 XXUAMDK
GT-I9500 Stock + root StupidSU v4 XXUAME1
What's next
Owners of Qualcomm Galaxy S 4 devices experiencing the same dificulties with Samsung the anti root strategy might want to try this method, please let me know if you're ready for some experimentations.
Supercurio pleas add thraed t General section i think ther well bee lots of testers for i9505.thx for suport
Sent from my LG-P500 using xda app-developers app
Going to try this on latest LE1 stock kernel now .....thread is in correct section
edit: did not work on LE1 kernel. I will try once again. DId any one tried the MDK kernel..I am having again the problem with SU binaries installation..
Edit: Thanks bro. working on ME1 kernel now. Did mistake while doing tar. Appreciate it! Root is working fine but cant update the binaries of Supersu, still the root works fine.
Here comes the master welcome to SGS4 development forum mate.. (rahulzeven from twitter here )
So the BEST thing's just happened?!:laugh::good:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Edit: New file uploaded
grgsiocl said:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Click to expand...
Click to collapse
Thanks fo much! Will Titanium Backup work on this kernel?
Hope chainfire will start working on mobileOdin soon. So much easier to flash than.
... tapat*lked
GSeeker said:
Thanks fo much! Will Titanium Backup work on this kernel?
Click to expand...
Click to collapse
wrong file uploaded. Please download the same in 5 minutes. Uploading is on and the kernel date should be MAY 04
---------- Post added at 12:33 PM ---------- Previous post was at 12:28 PM ----------
GSeeker said:
Thanks fo much! Will Titanium Backup work on this kernel?
Click to expand...
Click to collapse
it should work as i dont use titanium backup and instead i use gobackup pro and it works fine anyway
MDK from OP working good, thanks
grgsiocl said:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Edit: New file uploaded
Click to expand...
Click to collapse
I'm trying to repack the kernel of korean gs4,
but I am a noob in kernel devs.
I can edit ramdisc, but fist trying in initramfs, zImage.
Is rooting directory means both root.sh and files(folder)?
and paste them on first class route?
hope you give some advices.. thanks
aslak89 said:
I'm trying to repack the kernel of korean gs4,
but I am a noob in kernel devs.
I can edit ramdisc, but fist trying in initramfs, zImage.
Is rooting directory means both root.sh and files(folder)?
and paste them on first class route?
hope you give some advices.. thanks
Click to expand...
Click to collapse
when you unpack the kernel you will have two folders one is ramdisk and other one is split_img (zimage). You need to copy the folder stupidsu folder in ramdisk and modify the init.universal5410.rc as per OP stated and repack the image
grgsiocl said:
when you unpack the kernel you will have two folders one is ramdisk and other one is split_img (zimage). You need to copy the folder stupidsu folder in ramdisk and modify the init.universal5410.rc as per OP stated and repack the image
Click to expand...
Click to collapse
then, is not necessary to recompile zImage?
ok I m going to try it right now, thank you grgsiocl
muhamet said:
Supercurio pleas add thraed t General section i think ther well bee lots of testers for i9505.thx for suport
Click to expand...
Click to collapse
Yes in fact I was hesitating, but as soon as someone is ready to assist me to try on a Qualcomm device (I9505 or T-Mobile Galaxy S4) I'll make a thread here too.
grgsiocl said:
Going to try this on latest LE1 stock kernel now .....thread is in correct section
edit: did not work on LE1 kernel. I will try once again. DId any one tried the MDK kernel..I am having again the problem with SU binaries installation..
Edit: Thanks bro. working on ME1 kernel now. Did mistake while doing tar. Appreciate it! Root is working fine but cant update the binaries of Supersu, still the root works fine.
Click to expand...
Click to collapse
Great then
aslak89 said:
then, is not necessary to recompile zImage?
ok I m going to try it right now, thank you grgsiocl
Click to expand...
Click to collapse
The point here is to have stock (unmodified Samsung binary) kernel running, with associated modules and no other modification.
Which gives you several usage options:
keep the StupidSU stock+root kernel (same kernel binary, same kernel modules, only very slightly initramfs scripts) that will auto-root depending on which Superuser APK you installed
you can flash back the official kernel and still enjoy root the same.
supercurio said:
The point here is to have stock (unmodified Samsung binary) kernel running, with associated modules and no other modification.
Which gives you several usage options:
keep the StupidSU stock+root kernel (same kernel binary, same kernel modules, only very slightly initramfs scripts) that will auto-root depending on which Superuser APK you installed
you can flash back the official kernel and still enjoy root the same.
Click to expand...
Click to collapse
Thank you for awsering
then I repacked my kernel but still not work.
copyed stupidsu and edited init.universal5410.rc in ramdisk and repacked boot.img.
I guess permission is the thing,
attach my shots
hope you loot at once.
Sent from my SHV-E300S using XDA Premium HD app
walda said:
Hope chainfire will start working on mobileOdin soon. So much easier to flash than.
... tapat*lked
Click to expand...
Click to collapse
He will after he will come back from his vacation.
I'll look into a fixed CF-Auto-Root for the I9505 as soon as I'm back on Sunday. I imagine that will be tested by Sunday evening, with a I9500 test version available sometime Monday. If all is well
In StupidSU environment and for this initial release Koush's Superuser app would
be preffered as SuperSU main UI refuses to launch because it cannot detect its
original su binary. Aside from that both work as expected.
Click to expand...
Click to collapse
This is because you're not installing the backup su binary. The UI app detects this is missing and triggers an update. Bug in StupidSU
aslak89 said:
Thank you for awsering
then I repacked my kernel but still not work.
copyed stupidsu and edited init.universal5410.rc in ramdisk and repacked boot.img.
I guess permission is the thing,
attach my shots
hope you loot at once.p
Click to expand...
Click to collapse
Alright I'm adding some logging in my scripts so you'll be able to see what's happening − or not
supercurio said:
Yes in fact I was hesitating, but as soon as someone is ready to assist me to try on a Qualcomm device (I9505 or T-Mobile Galaxy S4) I'll make a thread here too.
Click to expand...
Click to collapse
Brilliant news!!!! Thanks a LOT!!
Let's make it work!! It will be AWESOME if I could use latest STOCK Kernel in my ROM's......
I'll give you a hand