Hi,
Me for one, likes testing and flashing, but i am not always at a pc to do fastboot commands to restore kernels.
So i decided to make a flashable kernel so i can test roms while i am away from pc, home or at work.
The kernels i have made flashable are EDGANS overclock kernel from here http://forum.xda-developers.com/showthread.php?t=1173225
And also -eval kernels for the OFRF GB port to atrix internationals
http://forum.xda-developers.com/showthread.php?t=1169409
Thanks Edgan
Thanks -eval
It includes SetCPU support. It is only a 1.1ghz overclock. It is still 1ghz by default, you have to use SetCPU to trigger the overclocking.
Click to expand...
Click to collapse
Make sure you know which kernel you should be flashing by doing
cat /proc/cmdline
Click to expand...
Click to collapse
If you see tegrapart=mbr:d00:100:800,kpanic:2100:400:800: use d00
If you see tegrapart=mbr:1100:100:800,kpanic:2500:400:800: use 1100
Steps
Reboot into cwm recovery
Factory reset
Flash Rom of your choice
Flash my kernel.zip
Reboot
I have tested personally the d00 kernel and have flashed without the use of pc in any way. I have flashed kens 4.5 rom, Cherryblur (issues with wifi), redpill, Ninjas, Quickrom,
If all fails use
fastboot flash boot
Click to expand...
Click to collapse
And report it here Thanks
will this fix the ram bug issue? as im struggling to get fast boot to flash it just hangs untill i pull battery
Thanks, hope to see the list increase and get stickied.
chuckyd said:
will this fix the ram bug issue? as im struggling to get fast boot to flash it just hangs untill i pull battery
Click to expand...
Click to collapse
yes it will.
first attempt to flash failed (error code: bad)
d1100
y2whisper said:
first attempt to flash failed (error code: bad)
d1100
Click to expand...
Click to collapse
Yep needed someone to test that one will fix
Edit: ok fixed .............
Sent from my MB860 using XDA Premium App
Great job dude... worked perfectly... fixed ram as well... kudos
Edit: found answer
I've set SETCPU to max 1000mhz and the phone still uses 1100mhz (as shown in the "time in state"). Any fix?
Related
Support Has been Dropped for xda...
Please Delete Thread Mods.
~Eugene
Great work.
Lets see the tests
Good to see you on here Eugene
Sent from my SGH-T959 using XDA App
can you add mimocan lag fix to this? Thanks
Im waiting for a ginny pig to try the test flash hehehee
rhcp0112345 said:
Im waiting for a ginny pig to try the test flash hehehee
Click to expand...
Click to collapse
I always Test & make sure My stuff works 100% before I post anything..
P.S.
You need to Wipe before Flashing via ClockworkMod Recovery..
Currently Testing the zImage Flash atm, so I'll likely have an update shortly that lets you flash the zImage as well.
thang422 said:
can you add mimocan lag fix to this? Thanks
Click to expand...
Click to collapse
Please Post a Link.
Which was the zImage again? Kernel?
rhcp0112345 said:
Which was the zImage again? Kernel?
Click to expand...
Click to collapse
Correct
I can't post the link... Im not allow too
showthread.php?t=727279
do we put the stock vibrant file on the memory card or the internal storage ?
sorry its methood 2 that is needed.
Thanks
showthread.php?t=727279
fivestar0234 said:
do we put the stock vibrant file on the memory card or the internal storage ?
Click to expand...
Click to collapse
internal storage
thanks. it works great!
So (just to be clear) Do I download this, rename it to update.zip, then "reinstall" in recovery?
Or do i have to install rom manager, and flash from its boot screen
basataom said:
So (just to be clear) Do I download this, rename it to update.zip, then "reinstall" in recovery?
Or do i have to install rom manager, and flash from its boot screen
Click to expand...
Click to collapse
Don't Rename, well you can... But never rename to update.zip as this is how Clockwork is Used.. You select from install from .zip & select the name...
You and do either
adb reboot recovery from cmd prompt once you Have the update.zip downloaded from Rom Manager
or
You can Flash from Rom Manager.
Hey,
Great work here.
but, one question. I was told by koush during our talks about getting the bricks un-bricked that the only way to flash the baseband/radio was through odin.
does this flash the radio/baseband?
Thanks. Just want to clarify.
rhcp0112345 said:
Hey,
Great work here.
but, one question. I was told by koush during our talks about getting the bricks un-bricked that the only way to flash the baseband/radio was through odin.
does this flash the radio/baseband?
Thanks. Just want to clarify.
Click to expand...
Click to collapse
This only flashes the system partition that is all.
ah ok. so its the same as the nandorid backup only using the stock-firmware.
Gotcha. Just wanted to be clear what is what
Eugene got a vibrant nice
Sent from my SGS Vibrant using tapatalk
This is More useful for
- Themes
- Removal Of Bloat Ware
- Mod's & Edits
- etc....
All the Heavy stuff ie.. radio / zImage etc... needs to be flashed by odin flasher.
Also, this Man justanothercrowd knows his Stuff, so remember that
P.S.
Those using ODIN Flasher,
There should never be a Reason to select Reformat Partitions unless Samsung Tells us to!
im trying to flash clock work 3.0.0.5 to install the aosp ginger... i tried various steps terminal and adb and the rom manager .. its not working i have a hero sprint im stuck ...
Try flashing Darch's eng.spl and then go to the thread of sexy the latest aosp update. Look a few pages back and find the link for the wiki. On there they posted 5 different ways to flash it. But after you flash the eng.spl you'll be looking for the fast boot method and you should be straight from there good luck.
Root-Hack-Mod-Always™
Download and flash: ENG-SPL. This is an engineering SPL to allow access to fastboot and the ability to flash unsigned zips from HBOOT.
The quickest way to do this after flashing the eng-spl is to do as it says in the romrepo.info/wiki. The direct link is here, you will want method 4.
Should take 5mins tops, if that.
Also, if you have flashed it and get confirmation that it worked, but it still will not boot, my guess is your phone can't handle 768 clock speed. For the GB rom you can just flash a capped 691 kernel, as for the recovery you will need to wait until aosp posts the underclocked version or 3.0.0.5 (yes he made one already) and in the meantime use 2.5.0.1, you can still flash GB with that recovery, just make sure you flash a capped kernel before you try to boot.
I have flashed clockwork 3.0.0.5 with method 2 in below link, you may try out.
http://romrepo.info/wiki/index.php?title=Flash_the_ClockworkMod_Recovery
i cant find a capped kernel which do i choose?
killacammiami said:
i cant find a capped kernel which do i choose?
Click to expand...
Click to collapse
Dec"s # 589 691 check his thread.
Root-Hack-Mod-Always™
yea im dl now i hope this works so this the steps correct install rom the gmaps then capped kernel? and reboot correct ?>
il Duce said:
Also, if you have flashed it and get confirmation that it worked, but it still will not boot, my guess is your phone can't handle 768 clock speed. For the GB rom you can just flash a capped 691 kernel, as for the recovery you will need to wait until aosp posts the underclocked version or 3.0.0.5 (yes he made one already) and in the meantime use 2.5.0.1, you can still flash GB with that recovery, just make sure you flash a capped kernel before you try to boot.
Click to expand...
Click to collapse
wow it worked duce thanks alot man ..... i flashed that 691 kernel from defacut and im good to go its loading ....
So we don't have one of these yet and cmenard has inspired me
What's included
cmenard's gingerbread bullet kernel (1.2)
KB5 modem
fixed haptic feed back & fixed home button
power menu options
removed battery full notification
couple added apps (titanium being the most important)
CRT off animation & overscroll added of course
removed startup sound
Juwe's RAM script
rooted & busybox included
How To Install (with Bootloaders)
flashed GB bootloaders (be careful!) - thanks adyscorpius
flashed cmenard's kernel via heimdall
rebooted into recovery & flashed
rejoiced
How to install without bootloaders
ok ladies, thanks to the wonderful cmenard you can do it!
put rom on your internal SD for flashing
flash Bullet-1Ghz-NRB-v2-voodoo.tar with heimdall or odin
this is a gingerbread kernel that does not rainbow, get into recovery and flash the ROM
the ROM will flash the newest kernel (which will give you rainbows without gingy bootloaders)
if you want to get rid of them just flash Bullet-1Ghz-NRB-v2-voodoo.tar again, but be aware your camera will not work
Bullet-1Ghz-NRB-v2-voodoo.tar is NOT a CWM flashable. It will NOT boot into the ROM correctly. It is used to flash Gingerbread ROMs & use recovery for Gingerbread. So if you don't have GB bootloaders installed and need to use CWM. You may want to flash it. Flash your desired ZIP. Then flash GB_Bullet back. It's a pain but that's how it's gotta be for now.
I included the tar file (which should work in ODIN, stick it in PDA and don't touch anything else), but I just flashed the zImage straight through heimdall.
What doesn't work?
GP FRACKIN S - oh wait, it does
Oh, and my extended power menu I think I messed up somewhere, and everything only reboots. Sorry.
everything else seems to work
Changelog
update 2
--EDT settings now accessibly from System settings window, removed from icons tray
--added Whitehawks 9 lock screens
--newest kernel
--included gps fix (mostly, I may have missed a file, if it doesn't work, just flash the fix )
--added a couple apps (spare parts, titanium, etc)
--included hacked cam & browser (found on I9K forums)
--3D fix too
update 1
--included my statusbar mods as posted on I9K forums
--included my permission script
--included newer kernel which fixes USBActivityManager issue visible in logcat
--optimized a few APKs & frameworks
Download Update 2
md5: 5AE86879B74438C8D4AA57CA0EE6574D
As always, read, wear a helmet, and don't do anything stupid. ಠ_ಠ
If you do not flash the bootloaders, you will see rainbows making it almost impossible to see the recovery from the kernel. I am not responsible for you breaking your device!
NRB kernel means no rainbow. It is used if you don't want to flash bootloaders. Flash it, then flash the ROM. The ROM will flash a new kernel (which will give you rainbows). If you need to access CWM you can flash the NRB one again, but your camera will not work on it.
stock theme?
bearsfan85 said:
stock theme?
Click to expand...
Click to collapse
yep, I'll post screenshots in a min
Can we do this from stock jfd?
hitman818 said:
Can we do this from stock jfd?
Click to expand...
Click to collapse
If you follow the instructions...
Woohoo checking it out!
Sent from my SGH-T959
When we flash the bootloaders from stock, should I untick the auto-reboot button, then remove the battery, go into dl mode, flash the kernel with auto-reboot unticked, go to recovery and flash the rom, is that okay?
Thanks Birger!
Shame the GPS is still not working....I had read a post a few days back stating that the GB ROM for the i9000 had working GPS but phone calls were not working!
Hopefully one of these days it will have working GPS....whilst it's not the best on our phones, I still use it everyday and can't do without it.
Globespy said:
Thanks Birger!
Shame the GPS is still not working....I had read a post a few days back stating that the GB ROM for the i9000 had working GPS but phone calls were not working!
Hopefully one of these days it will have working GPS....whilst it's not the best on our phones, I still use it everyday and can't do without it.
Click to expand...
Click to collapse
That was the honeycomb port and come to find out that due to using the i9000 gb drivers was the only reason the gps worked. This is also the reason why we can port the official gb rom over to our phone yet still not have gps. No official gb drivers for the vibrant from samsuck
Sent from the always morphing, always changing, Vibrant Galaxy.
hitman818 said:
When we flash the bootloaders from stock, should I untick the auto-reboot button, then remove the battery, go into dl mode, flash the kernel with auto-reboot unticked, go to recovery and flash the rom, is that okay?
Click to expand...
Click to collapse
Follow his instructions exactly.
Sent from my GT-I9000 using Tapatalk
Thanks for this birg
Sent from the always morphing, always changing, Vibrant Galaxy.
birgertime said:
Follow his instructions exactly.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Hmm, when I do the part when you flash the kernel, it doesn't want to flash, and when I try to boot the phone, it throws me into Phone ! PC (I can fix that by re-flashing the Froyo bootloaders).
I don't know why it won't flash the GB Kernel. :/
Hey birg, how did you fixed your phone? You tweeted about it right.
Sent from my SGH-T959 using XDA App
I followed his instructions exactly. But, not work. loop in Bullet screen.
hoquangthaiholy said:
I followed his instructions exactly. But, not work. loop in Bullet screen.
Click to expand...
Click to collapse
I'd suggest a reflash to stock JFD after flashing Froyo bootloaders, then reboot once.
Go back to download mode, flash GB bootloaders and follow Roman's instructions for the ROM...
If you've used CM7 or MIUI it seems to screw bootloader partitioning...
Sent from my T959 using Tapatalk
Thanks, I's work !. .
But i can't see status bar ?
is it support Arabic ?
Longcat14 said:
Hmm, when I do the part when you flash the kernel, it doesn't want to flash, and when I try to boot the phone, it throws me into Phone ! PC (I can fix that by re-flashing the Froyo bootloaders).
I don't know why it won't flash the GB Kernel. :/
Click to expand...
Click to collapse
I probably packaged up the TAR incorrectly like a moron, I used heimdall to flash the zImage directly.
hoquangthaiholy said:
Thanks, I's work !. .
But i can't see status bar ?
Click to expand...
Click to collapse
Try pushing this to /system/app
HOw is the battery life? Do I need to do anything special coming from 2.3.3 ROM?
I got overclocking fully working on my 2.3.4 kernel. It is tested, and works for me. It is only for 4.5.91, not 1.2.6, 1.5.7, or 1.8.3.
It includes SetCPU support. It is only a 1.1ghz overclock. It is still 1ghz by default, you have to use SetCPU to trigger the overclocking.
You phone needs to be in fastboot mode to flash a new kernel and ramdisk. To do this follow the steps below.
Steps:
1. Power off phone
2. Hold volume down
3. Plug USB cable into computer
4. Plug USB cable into phone
5. Wait for it to say Fastboot at the top of the phone's screen
6. Press Volume Up to select Fastboot
7. On computer run, moto-fastboot flash:raw boot zImage CG59.img-ramdisk.gz
Kernel
Ramdisk
If you are just installing the kernel and ramdisk above, ignore these patches!
Both overclocking oatches are required when recompiling the kernel for overclocking support.
Original patch
Fixes SetCPU in 2.3.4
Also look at my 2.3.4 kernel post for the rest of the information.
2.3.4 kernel post
This is still based on faux123's and kholk's work.
Thanks faux123!
Thanks kholk!
Just to ask the question for information purposes. Will the adb flash commands work as well?
Sent from my MB860 using XDA App
I am not familiar with adb's flash features. If you have previously used it to flash kernels in pieces, then yes. If it expects a boot.img, no.
can I just ask what features does this kernel has?
Thanks
does this have working wifi edgan?
Thanks again for a great kernel I have had the least issues with your kernels.
Great work !
Will try and let you know.
EDIT : Flashed with fastboot booted up fine no boot loops trying clock and benchmark
OLD\NEW
EDIT : got at 2100\3040 score on quadrant running linpack next.
ps Wifi does work so does everything i have tried.
Edgan, does it perhaps "affect" the haywire battery issue?
Sent from my Motorola Olympus using XDA Premium App.
any way u can compile this for CWM ?
Wow 3040 you must have a snapy experience....
And I complete agree from all the OC around I got a pleasant experience with edgan one (conservative but full stables and thats what I need)
Edgan can you please confirm if actually are you deving from a retail att atrix or any retail flavor
Xenocyde said:
Thanks again for a great kernel I have had the least issues with your kernels.
Great work !
Will try and let you know.
EDIT : Flashed with fastboot booted up fine no boot loops trying clock and benchmark
OLD\NEW
EDIT : got at 2100\3040 score on quadrant running linpack next.
ps Wifi does work so does everything i have tried.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Awesome
Sent from my MB860 using XDA Premium App
C:\Documents and Settings\S>c:\fastboot\
fastboot flash:raw boot zImage CG59.img-ramdisk.gz
cannot load 'zImage'
error: cannot load bootable image
on windows using fastboot. i get the same error when using moto-fastboot. what am i doing wrong?
moehagene said:
C:\Documents and Settings\S>c:\fastboot\
fastboot flash:raw boot zImage CG59.img-ramdisk.gz
cannot load 'zImage'
error: cannot load bootable image
on windows using fastboot. i get the same error when using moto-fastboot. what am i doing wrong?
Click to expand...
Click to collapse
very foolish question but the kernel and ramdisk should be in the same folder as moto-fastboot
they are i know that much about what im doing
Flashed fine for me, no problems. Will benchmark in a little bit when I get a chance.
what about wifi?!
EclipseX said:
what about wifi?!
Click to expand...
Click to collapse
answered by one in the front page. said to have worked
Wi-Fi is working beautifully! And for those interested in benchmarking information, in 5 runs on stock kernel, I averaged around 2500-2600. on 5 runs on OC'd kernel I averaged 2900-3000! (got over 3k twice and others were 2900+)
Ok now u convince-me =)....trying now
have no lucky
C:\Users\ISLA\Desktop\fastboot>fastboot flash:raw boot zImage CG59.img-ramdisk.gz
creating boot image...
creating boot image - 3397632 bytes
< waiting for device >
I Use launcher ex Seems to speed things up alot.
Hi !
I have a big problem with WerewolfJB kernel/ROM
1. I tried to flash WerewolfJB kernel v006 on my CM RC5. It either stucks on boot animation or the phone restarts after few seconds and then stucks on boot animation.
2. I tried to flash whole ROM - results? It turns on normally but randomly restarts after few seconds/minutes.
3. I tried flashing older versions of kernel on other versions of ROM (different RCs, nightlies and tried on stock - I am sure I didn't make any mistakes when it comes to choosing right kernel for stock/CM rom)
I have no problems with EPR kernel or iodak kernel. I even tried to flash original rom through KDZ and then root and flash custom ROMS but it didn't work.
Some suggestions? I am a complete noob when it comes to giving some logs (i've read about it in other topic) so it would be great if You could describe steps how to do it.
Thanks in advance !
Kontal said:
Hi !
I have a big problem with WerewolfJB kernel/ROM
1. I tried to flash WerewolfJB kernel v006 on my CM RC5. It either stucks on boot animation or the phone restarts after few seconds and then stucks on boot animation.
2. I tried to flash whole ROM - results? It turns on normally but randomly restarts after few seconds/minutes.
3. I tried flashing older versions of kernel on other versions of ROM (different RCs, nightlies and tried on stock - I am sure I didn't make any mistakes when it comes to choosing right kernel for stock/CM rom)
I have no problems with EPR kernel or iodak kernel. I even tried to flash original rom through KDZ and then root and flash custom ROMS but it didn't work.
Some suggestions? I am a complete noob when it comes to giving some logs (i've read about it in other topic) so it would be great if You could describe steps how to do it.
Thanks in advance !
Click to expand...
Click to collapse
hmm, sounds like an OC issue...
please provide a last_kmsg
and what's your CPU variant?
laufersteppenwolf said:
hmm, sounds like an OC issue...
please provide a last_kmsg
and what's your CPU variant?
Click to expand...
Click to collapse
My CPU Variant is 0.
Is attached last_kmsg good?
Kontal said:
My CPU Variant is 0.
Is attached last_kmsg good?
Click to expand...
Click to collapse
well, this file somehow is corrupted, and it doesn' show the crash, and it's not my kernel, but the recovery that has created that log
So how should I create last_kmsg? I would be grateful if You guided me. I changed back to iodak kernel but I still have Your kernel on my sdcard.
Kontal said:
So how should I create last_kmsg? I would be grateful if You guided me. I changed back to iodak kernel but I still have Your kernel on my sdcard.
Click to expand...
Click to collapse
when it crashed, boot directly into recovery and open an adb command line on your PC and type:
Code:
adb shell
cat /proc/last_kmsg >/sdcard/last_kmsg
[ctrl + c]
adb pull /sdcard/last_kmsg C:\path\to\your\desired\directory\last_kmsg