This is an overclocked kernel from toastcfh godmode .29 source. The kernel was actually pulled from Fresh Toast; What's different between this and Jus10o's is that the kernel is coupled with the ramdisk for the Legend builds
Theoretically this should also work for DarchVanilla.
The rest is how Jus10o puts it.
The reason for this a new thread is that there isn't any confusion between the two, otherwise you'd end up with an un-optomized, but still working, over-clocked ROM.
What's great about this: You still get LWP's in Rosie from Darch's build.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And a working camera!
Jus10o said:
UPDATE
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.
Both can be scaled from 19.2 to 768mhz..
710LegendKernel--The 710LegendKernel will default 710mhz, you must use an OC app to scale it to 768. Use 710 if your phone can not boot the 768mhz. And dont scale any higher then 710mhz or your phone might reboot.
710LegendKernel--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 768 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.
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 710mhz tip.
Click to expand...
Click to collapse
Oh and thanks Jus10o for making this easier
NOTE: If you have ANY problems/bugs/glitches, come to me. Don't bother Darch if I made a mistake.
EDIT: Screenies added!!
---reserved for bugs---
Accelerometer doesn't work with the new kernel.
hmmm...for some reason both of these files throw my phone in to a boot loop that doesn't get past the HTC splash screen. any tips?
murdocthc said:
hmmm...for some reason both of these files throw my phone in to a boot loop that doesn't get past the HTC splash screen. any tips?
Click to expand...
Click to collapse
They shouldn't :S
I've tested both of them multiple times; if anything 710 should be your best bet to get it to boot.
Are you running the latest version of DarchLegend?
And can you get me a logcat of the initial boot?
Decad3nce said:
They shouldn't :S
I've tested both of them multiple times; if anything 710 should be your best bet to get it to boot.
Are you running the latest version of DarchLegend?
Click to expand...
Click to collapse
I just switched over from DamageControl and flashed DarchLegend 5.0.5 since it was noted as the "stable ROM". Should I be flashing 5.0.6?
I got the same boot loop when I tried to use Toast's OC kernel (posted by Jus10o) for DamageControl also, so i'm concerned that the only constant has been my noob arse
murdocthc said:
I just switched over from DamageControl and flashed DarchLegend 5.0.5 since it was noted as the "stable ROM". Should I be flashing 5.0.6?
I got the same boot loop when I tried to use Toast's OC kernel (posted by Jus10o) for DamageControl also, so i'm concerned that the only constant has been my noob arse
Click to expand...
Click to collapse
Ha. Well I'll see what I can do to help you.
(Btw: Works with both 5.0.5 and 5.0.6, though 5.0.6 allows for default US localization)
If you can do me a favor: After you flash the new boot.img(kernel), run an adb logcat when it gets to the htc screen.
Code:
adb logcat > logcat.txt
This will save your logcat to a txt file in your sdk/tools folder. Just upload it or put it on pastebin.
murdocthc said:
I just switched over from DamageControl and flashed DarchLegend 5.0.5 since it was noted as the "stable ROM". Should I be flashing 5.0.6?
I got the same boot loop when I tried to use Toast's OC kernel (posted by Jus10o) for DamageControl also, so i'm concerned that the only constant has been my noob arse
Click to expand...
Click to collapse
I'd say flash damagecontrol and the 710 kernel I posted only cuz its 100% confirmed working. Just flash and boot up then boot recovery flash 710 and boot up again. If it works then try this rom and kernel.
Decad3nce said:
Ha. Well I'll see what I can do to help you.
(Btw: Works with both 5.0.5 and 5.0.6, though 5.0.6 allows for default US localization)
If you can do me a favor: After you flash the new boot.img(kernel), run an adb logcat when it gets to the htc screen.
Code:
adb logcat > logcat.txt
This will save your logcat to a txt file in your sdk/tools folder. Just upload it or put it on pastebin.
Click to expand...
Click to collapse
Cool, thanks! I'm going to flash 5.0.6 and run logcat just in case I get the same results. Will post back in a few...
OK - so I flashed 5.0.6 and the kernel and it's still not booting past the black-and-silver HTC screen. It just keeps turning off and on again.
Also, logcat just sits and says "-waiting for device-". When I checked the logcat file after letting the phone try and boot, it was empty. Would it help if I shot a quick video so you could see exactly what I'm doing and what exactly the issue is?
murdocthc said:
OK - so I flashed 5.0.6 and the kernel and it's still not booting past the black-and-silver HTC screen. It just keeps turning off and on again.
Also, logcat just sits and says "-waiting for device-". When I checked the logcat file after letting the phone try and boot, it was empty. Would it help if I shot a quick video so you could see exactly what I'm doing and what exactly the issue is?
Click to expand...
Click to collapse
I'm starting the think either the upload or the download is corrupt. Try re-downloading.
Decad3nce said:
I'm starting the think either the upload or the download is corrupt. Try re-downloading.
Click to expand...
Click to collapse
Tried to re-download...same issue
I also just tried to flash 5.0.6 and it's giving me the same issue. Maybe my phone just doesn't like darch for some reason
murdocthc said:
Tried to re-download...same issue
I also just tried to flash 5.0.6 and it's giving me the same issue. Maybe my phone just doesn't like darch for some reason
Click to expand...
Click to collapse
what recovery img are you using?
Decad3nce said:
what recovery img are you using?
Click to expand...
Click to collapse
RA 1.6.2
10 char
It's really weird because any OC rom that I try sends my phone in to the loop. I wiped and flashed the new Aloysius 2.1 LWP/OC rom and it had the same effect. I also get the loop if I flash the .29 kernel for DC roms when I have DC 2.08.1 running.
murdocthc said:
It's really weird because any OC rom that I try sends my phone in to the loop. I wiped and flashed the new Aloysius 2.1 LWP/OC rom and it had the same effect. I also get the loop if I flash the .29 kernel for DC roms when I have DC 2.08.1 running.
Click to expand...
Click to collapse
Try the new one that i added for DC 2.08. Its defaulted to 537, just a tid bit higher then the default speed of our htc heros.
Related
You can display a "splash" screen of sorts upon boot. You just have to have a file named initlogo.rle in your root directory. The trick is that the root directory is overwritten each time you boot with the contents of your boot image (mtd2). There are instructions elsewhere on the forums for updating this image.
You can prove to yourself that this works by just copying logo.rle to initlogo.rle in your updated boot image and you will see the "G1" screen twice.
The hurdle I'm running into is generating my own images. There is a program called to565 that takes in an image and spits out the resulting image in the appropriate format (give it the -r flag to generate an rle) [edit, correct flag is -rle]. However, everything I generate with this just looks like random colored bars when I boot up (and sometimes at the bottom of the screen I see part of whatever was left in the framebuffer when I shut down). Supposedly to565 takes in a raw rgb888 file, and perhaps I'm not generating those properly. I tried saving to "raw image" from gimp but so far everything is just different variations on colored bars.
I may give up at this point, but I thought others might be interesting in picking up where I left off.
Huh. Interesting. I'll see if I can give it a whirl. Thanks for posting the info you've found so far
I took a quick look at the source of that to565 program. It looks like you need to use -rle instead of just -r. Did you try that?
JesusFreke said:
I took a quick look at the source of that to565 program. It looks like you need to use -rle instead of just -r. Did you try that?
Click to expand...
Click to collapse
You sir, are correct! I just did it with -rle and it works.
How to create a boot image:
1. put a properly encoded initlogo.rle in root directory
2. insert this line in init.rc in the boot: section (optional, this disables the stock android boot animation)
Code:
setprop debug.sf.nobootanimation 1
3. wrap it all up and flash it to mtd2
Attached:
1. A boot image with these changes made. To try it on your phone, first back up your mtd2 image (the boot image). Type the following in a root shell to back it up to your sdcard:
Code:
cat /dev/mtd/mtd2 > /sdcard/mtd2.img
Then, unzip boot-rc29-customlogo.img.zip it and stick it on your sdcard and type the following in a root shell:
Code:
cat /dev/zero >> /dev/mtd/mtd2
flash_image boot /sdcard/boot-rc29-customlogo.img
(when you do the cat, it will tell you "write: No space left on device," which is fine)
To restore your original boot image, do the cat and then flash_image your mtd2.img backup.
2. Samples of the raw image as well as the rle encoded version.
3. A nifty photo of this working on my phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WOW awesome!! great job will test this out when i get back from the airport
i couldn't wait so i did it works perfectly. i just can't get rid of the first boot .img.(i see the instruction but i need further help) if this helps i have a vista 64 but, I'm also running VM to any operating system.
humble said:
i couldn't wait so i did it works perfectly. i just can't get rid of the first boot .img.(i see the instruction but i need further help) if this helps i have a vista 64 but, I'm also running VM to any operating system.
Click to expand...
Click to collapse
Yeah, actually I haven't found a way to get rid of the G1 logo on boot. If you change logo.rle on the root filesystem, it still shows that image. I'll post a longer guide to generating your own boot.img later tonight (although I posted a bunch of it in another thread already). You could always create your own boot.img and replace logo.rle to prove to yourself that it doesn't change that initial logo... but I've tried it. It must be somewhere else (including, perhaps, some on-phone memory that we can't access).
hmmm so i've done this correctly since the boot image works...however i no longer have WIFI access. Does anyone knoe whats going on? under settings it keeps saying turning wifi ON... but it doesnt.
EDIT: So i reflashed the original backup img and now its fine. I wonder where i went wrong?
mack said:
hmmm so i've done this correctly since the boot image works...however i no longer have WIFI access. Does anyone knoe whats going on? under settings it keeps saying turning wifi ON... but it doesnt.
Click to expand...
Click to collapse
Did you use the boot.img I posted or one of your own? I'm not having any trouble with wifi, and I'm booted with that one. Do you see anything in dmesg about wifi?
Edit: also, it looks like JesusFreke had some issues with wifi not working when he was doing custom boot images. Dunno the details but maybe it's related.
thanks alansj (sorry i miss read). and my wifi still works
alansj said:
Did you use the boot.img I posted or one of your own? I'm not having any trouble with wifi, and I'm booted with that one. Do you see anything in dmesg about wifi?
Edit: also, it looks like JesusFreke had some issues with wifi not working when he was doing custom boot images. Dunno the details but maybe it's related.
Click to expand...
Click to collapse
I used your img that you posted with the hackdroid...LOVED it by the way =)
Could it be i'm on RC19 firmware? I'm reading jesusfreke's post but i'm fairly new to the linux thing so i'm having trouble understanding.
anyway i guess i'll just stick to stock until something new comes a long...
Thanks Alansj
mack said:
Could it be i'm on RC19 firmware?
Click to expand...
Click to collapse
Good guess. You could first apply the RC29 via sdcard and then flash the boot image.
To apply RC29, download this file, put it on your sdcard, name it update.zip, then reboot your phone while holding down power+home and when you get the recovery screen press alt+L then alt+s.
will this work with 30
jriley60 said:
will this work with 30
Click to expand...
Click to collapse
The general process will work, but the boot image I posted is based on rc29. The two things in the boot img are a kernel and a ramdisk (which includes a few of the basic system files). I don't think there was a kernel update in rc30, but I think there were updates to init.rc and possibly adbd (haven't checked). So, flashing with that boot.img I posted would undo the changes in those files done by rc30.
The better approach would be to take the boot.img from the full rc30 release, add your own initlogo.rle, and reflash from that.
I will now go and write a more detailed tutorial on how to edit boot.img
that would be awesome. Thank you!
Kinda off-topic, but where did you get the font that you used in the logo? I'd like to make my own, and I was wondering if I could use it...
amgupt01 said:
Kinda off-topic, but where did you get the font that you used in the logo? I'd like to make my own, and I was wondering if I could use it...
Click to expand...
Click to collapse
I just pixel-edited the logo from the android site (had to invent a couple of characters)... no font.
jriley60 said:
that would be awesome. Thank you!
Click to expand...
Click to collapse
I just posted it here
alansj said:
I just pixel-edited the logo from the android site (had to invent a couple of characters)... no font.
Click to expand...
Click to collapse
Good work, man! Someone is actually working on the android logo font here: http://androidcommunity.com/forums/f37/new-android-ttf-logo-font-ver-1-0-a-6537/#post68847
Just FYI.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Based on HTC Magic/32A Éclair Sense ROM
v2.5 Changelog
Moved CPU values to /data/tweaks/cpu
Now using apks from WWE Hero ROM, making this a hybrid ROM so name changed to Fusion Sense.
New bugless and faster kernel, thanks to laszlo!
IMPORTANT: As of v2.5 you need to flash cMTD Setup 1.1.
v2.1 Changelog
Moved CPU values to /data/cpu
Better swap, should help with memory management, multitasking, messaging problems.
v2 Changelog:
New base, includes enhanced Peep.
CPU Manager script that changes the governor, max, and min frequencies upon screen off and screen on. Look at second post for more details.
v1 Features:
Apps and dalvik cache to sdcard (EXT4)
Working Camera
Crossed over framework from Gingerbread Sense.
Mostly stock but removed Rogers bloateare and Maps. Maps is downloadable from the Market.
What doesn't work:
Camcorder
Bluetooth
Landscape home screen
REQUIREMENTS:
2708/2528 RADIO AND 1.33.0013d IS A MUST!!!
Swap with 96 MB or more. 256 recommended. No swap will make it very very slow. 5 mins to load homescreen without swap.
EXT4 partition.
HOW TO INSTALL:
BOOT INTO RECOVERY.
Flash MTD 150 file
Restart phone and wipe everything.
Flash ROM and reboot.
OPTIONAL: Use Autokiller to adjust minfree settings but I already included my own minfree settings.
VERY IMPORTANT:
On first boot, Sense launcher may not load properly or will be loading forever. This is caused by the lack of ram. To solve this issue:
1. Pull down notification bar.
2. Go to Advanced Task Killer.
3. In ATK, go to Settings.
4. Set Security Level to low.
5. Go home.
6. Go back to ATK.
7. Hold your finger on com.HTC.launcher and go to Force Stop/Details.
8. You will be at another window, click Clear Data.
9. Go back to ATK, kill every process.
10. Go home and the launcher should reload properly.
DOWNLOAD LINK: CLICK HERE
BTW: I am not responsible for any damages or bricks although if you can flash this, you are past that point.
Thanks and enjoy!
Details on the CPU Managing script:
Taken from RaduG's Froyo Sense rom and changed it so that the user can change it without messing things up.
THERE IS NO NEED TO USE SetCPU, IT WILL STOP THE CPU MANAGING SCRIPT FROM WORKING!
Default Settings:
Screen on: 528MHz/245MHz with interactive governor.
Screen off: 245MHz/122MHz with ondemand governor.
These values can be changed by editing the following files:
Screen ON settings:
/data/tweaks/CPU/screenON/governor
/data/tweaks/CPU/screenON/max
/data/tweaks/CPU/screenON/min
Screen OFF settings:
/data/tweaks/CPU/screenOFF/governor
/data/tweaks/CPU/screenOFF/max
/data/tweaks/CPU/screenOFF/min
To know what frequencies and governors you can use:
Open Terminal and:
To see available frequencies, input:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Click to expand...
Click to collapse
To see available governors, input:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
Click to expand...
Click to collapse
This is awesome! Downloading now! Thank you so much!!
Hmm.. I wonder if it would be possible to port 32A EspressoMagic 7.1.0? Espresso is pretty cool! Just saying....lol
Sent from my HTC Magic using XDA App
i downloading now! thanks MAN!!!!!!!
sounds nice
i'll follow this thread!
one question: what about bluetooth? on the most sense-roms there are problems with bluetooth..
as its a sense rom bluetooth is not working everything else is fine
Thanks Namit !
Testing now...
I'm trying to install
I've a 32B Vodafone with radio 2708 and hboot 1.33.0013d
I get stuck on splash screen and I've this error on logcat
Code:
11-04 12:47:43.641: ERROR/dalvikvm(919): ERROR: no valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar'
any clue ? Thanks
QTeknology said:
I'm trying to install
I've a 32B Vodafone with radio 2708 and hboot 1.33.0013d
I get stuck on splash screen and I've this error on logcat
Code:
11-04 12:47:43.641: ERROR/dalvikvm(919): ERROR: no valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar'
any clue ? Thanks
Click to expand...
Click to collapse
Try a full wipe:
Use Superwipe
Then use "fastboot erase system -w"
That works for me.
best rom 4ever! thanks man a lot!
Namit1994 said:
Try a full wipe:
Use Superwipe
Then use "fastboot erase system -w"
That works for me.
Click to expand...
Click to collapse
Just tried...
nothing to do, always same error
Code:
11-04 16:39:26.141: ERROR/dalvikvm(873): ERROR: no valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar'
11-04 16:39:26.151: ERROR/AndroidRuntime(873): JNI_CreateJavaVM failed
probably some hardware error from g1 to 32b... I dunno
What I did ?
Recovery
Partion SD
96mb of swap
1024mb of ext2
then copy your superwipe and your rom on sd
flash superwipe
reboot and power off
power on in fastboot and "fastboot erase system -w"
reboot in recovery
upgrade ext2 to ext3
upgrade ext3 to ext4
flash your rom
no luck
this ROM doesn´t start on my G1
i can flash it properly.
but it says "G1 T-Mobile" for 10 minutes now, nothing happens..
my G1 :
2528 Radio and 1.33.0013d
8GB SD: 256MB swap, 768MB EXT4
clockworkmod recovery 2.5.0.1
QTeknology said:
Just tried...
nothing to do, always same error
Code:
11-04 16:39:26.141: ERROR/dalvikvm(873): ERROR: no valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar'
11-04 16:39:26.151: ERROR/AndroidRuntime(873): JNI_CreateJavaVM failed
probably some hardware error from g1 to 32b... I dunno
What I did ?
Recovery
Partion SD
96mb of swap
1024mb of ext2
then copy your superwipe and your rom on sd
flash superwipe
reboot and power off
power on in fastboot and "fastboot erase system -w"
reboot in recovery
upgrade ext2 to ext3
upgrade ext3 to ext4
flash your rom
no luck
Click to expand...
Click to collapse
Do you have customMTD?
Okay guys I've replicated your problem with my G1. If you have Firerat's customMTD mod, remove it. There is no need for it.
How to remove:
Flash Superwipe
Download FR-remove zip from:http://www.mediafire.com/?lifib6a9ptj5j#0,1
Flash FR-remove package.
Flash my rom
See if it works.
Namit1994 said:
Okay guys I've replicated your problem with my G1. If you have Firerat's customMTD mod, remove it. There is no need for it.
How to remove:
Flash Superwipe
Download FR-remove zip from:http://www.mediafire.com/?lifib6a9ptj5j#0,1
Flash FR-remove package.
Flash my rom
See if it works.
Click to expand...
Click to collapse
Thanks !
i tried to remove it with the 1.5.8 remover but it didn´t work!
Now i used the 1.5.6 and it works fine for me
Namit1994 said:
Do you have customMTD?
Click to expand...
Click to collapse
How to check if I've a customMTD ?
I'm trying to remove anyway........
QTeknology said:
How to check if I've a customMTD ?
I'm trying to remove anyway........
Click to expand...
Click to collapse
nothing... I try with remove 1.5.6.........nothing at all
probably it doesnt works with G2 32b
initially it was blazing fast...but eventually slowed down...but still the best hero out there for g1...thankx
Edit: those who are having problem with g1...you dont need hboot-1.33.0013d.img just flash the ezBiffTestKernel20110222-2708_S.zip after you flash the rom ( before rebooting)
and if the roms starts to slow down...use the autokiller memory tool....
Take out sim card before you install via recovery, and leave it out for first boot You may put the sim card back in after you set up everything properly over wifi.
Hey I tried flashing this to Mytouch 1.2 and it didn't boot! Just stuck on splash screen!
Sent from my HTC Magic/Dream using XDA Premium App
Hi all
Whipped this up for a friend. Thought we'd be nice and share
These packages will work on any current sw version for the Charge.
Please find below kernel and recovery packages hacked for the following:
permanent adb root
installs Superuser and su binary automatically on boot
includes Voodoo ext4 lagfix - CREDIT TO SUPERCURIO! http://project-voodoo.org/lagfix
lowmemorykiller tweaks
sdcard readahead cache speed tweak
If you are using Odin to flash, simply flash the below package. If you are using Heimdall, remove the zImage file from the below package and flash it.
After flashing the first time, you will hear a voice from the phone telling you what is occurring. The conversion to ext4 will take a few minutes. BE PATIENT. Once it boots, Superuser should be installed, and your phone's filesystem will be converted from rfs to ext4. To disable Voodoo lagfix and convert back to rfs, simply create a file on your sdcard inside the Voodoo folder, named "disable-lagfix". Then reboot your phone and listen for the voices again. This will also take a few minutes.
Please familiarize yourself with using Odin or Heimdall and have backup images on-hand if you are going to use this kernel. If you screw up, you will need them
I DO NOT have a Charge, these files have been tested by other users. As always I assume absolutely NO liability for anything that happens if you use this kernel. Phone blows up? It's on you to fix it
If you find this software helpful please click the "Thanks" or the "Donate" button. Either is fine by me. If you would like to investigate the changes that were made, please feel free to find them here, and here.
Enjoy.
EDIT
Uploaded 2nd version
EDIT
Uploaded 3rd version
changed the install scripts around
should copy files more efficiently
fix file ownership and permissions
UNTESTED!
EDIT
Uploaded 4th version
Confirmed root from independent user!
rewrote install process to preserve file path and permissions
will look into the bootanimation graphics issue
http://dl.dropbox.com/u/14764513/VoodooChargeKernel4.tar.md5
EDIT
Uploaded additional recovery file
Flashes custom version of ClockworkMod recovery 3.x
Recovery includes Voodoo specific options for enabling/disabling Voodoo lagfix
Flash with Odin or Heimdall just like the kernel files
HAS BEEN LIGHTLY TESTED! USE CAUTION AND HAVE A BACKUP!
if you do not have root:
* check adb shell and see if you get a '#' prompt. If so, you *have* root on adb, and you may install whatever you want in /system
* check to see if Superuser app is installed
* check to see if /system/xbin/su exists on your phone.
If you have problems, please post the results of those checks. Thanks.
LLGW. Headed to bed now but first thing in the morning, I wondering what I'm doing
Thanks jt!!!! Can't wait to flash this once my charge comes in the mail.
Sent from my SCH-I500 using XDA App
Ok, somebody use this to system dump ED2.
And, uh, is there matching Voodoo clockwork?
s44 said:
Ok, somebody use this to system dump ED2.
Click to expand...
Click to collapse
please
And, uh, is there matching Voodoo clockwork?
Click to expand...
Click to collapse
probably not
What verison of odin should I use? I just flashed this and it failed.
using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1
The kernel flash was successful, and the filesystem conversion took about 8 minutes to run. However, I was not rooted when the phone booted back up. Here is what I did, let me know if I missed a step:
Start on rooted ED1
Accept ED2 OTA
Lose Root
Flash new kernel using ODIN
After ~10 minutes, phone boots successfully, but I do not have root.
asenduk said:
using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1
Click to expand...
Click to collapse
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.
Where's my wifi? Anyone else facing an error when attempting to start wifi?
Yeah it looks like it killed wifi. I also am not rooted.
So if I flash back to rooted ED1 will it wipe my data?
azhockey said:
So if I flash back to rooted ED1 will it wipe my data?
Click to expand...
Click to collapse
I just reversed the filesystem changes and then flashed back to ED1. My data appears to be intact.
moondrius said:
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.
Click to expand...
Click to collapse
had to rename the file to .tar.md5 now its working..
asenduk said:
had to rename the file to .tar.md5 now its working..
Click to expand...
Click to collapse
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?
Updated OP with a new version. Anyone who has flashed the original version, please check adb shell and see if you get a '#' prompt. If you do, then you're technically rooted
NotATreoFan said:
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?
Click to expand...
Click to collapse
Superuser was installed but root was lost... Trying the updated version... On a positive note Quadrant is great! 1400-1550 avg
EDIT: wifi fixed with v2 but still no root.. will try from scratch and report back
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Everything has worked for me. Thank you.
Sent from my ADR6400L using XDA Premium App
yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin
devanmc said:
yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin
Click to expand...
Click to collapse
Click PDA and select the file then just hit start
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks:
TheFuzz4
Grillrd
iamtyy
gunnermike53
EXT4 Support
Extra Storage Support
init.d Script Loading Support
Auto root Install
Auto shell install
Built-in root and BusyBox
Built-in fix_permissions Script
Built-in Bash & Nano Binaries
FC Prevention & Detection ( READ THIS POST FOR IMPORTANT DETAILS )
SD Card / Internal MMC Read Speed Tweak
CPU / VM / Kernel Tweaks
CWM4 Recovery
Charge Mode ADB access
Scheduler tweaks
Use EXT4 Formatter (ALL version)
Flash EP1F/EP1H GB ROM
Recovery being used must support mounting EXT4 partitions
Partitions should be mounted in CWMR before installation
If partitions not mounted in CWMR, ROM installation must support mounting EXT4 partitions
ROM must not reformat RFS during installation
Flash NAMELESS Cleanup Script
Flash NAMELESS Kernel
Reboot
Wait, grab a beer, forget about bills, your job, and misbehaving women
IMPORTANT
New in Version 2 is the NAMELESS Kernel Cleanup Script. The Kernel Cleanup Script is a script which MUST be run when coming from another kernel (including NAMELESS v1). This script should be flashed BEFORE installing NAMELESS v2. After using this script, you may notice that on the first boot after installing the kernel it may take a long time, this is normal.
Download: http://www.multiupload.com/N5NOEGXEVH
MIRROR: http://www.mediafire.com/?302ofs64v4ibp9l
-----------------------
Version 2
NOTE: A problem has been detected with the recovery used in the Gummy Charged ODIN file. When using this recovery and trying to install this kernel, it will reboot the phone during installation, which is not good. This isn't a problem with the kernel, but a problem with the recovery. If you believe you are using this recovery, please flash the ODIN recovery below.
Changelog
init scripts completely rewritten
log disabled for fast boot
system now read-only for security
debugfs disabled
permissions fixed
bluetooth fixed
home/menu keys fixed
DBDATA/DATADATA symlink removed
fix_permissions script updated to support TW
CWMR updated to 4.0.1.4
Volume Up/Down keys go up/down through the menu's
Power button goes back a screen
Home button selects an option
EP1F: http://www.multiupload.com/HMNZGRI8Y1
Can be used with EP1F stock leak, or EP1F/EP1H mixed ROM's
MIRROR: http://www.mediafire.com/?g4cot4ugzxmlhmr
ODIN KERNEL (v2 EP1F): http://www.multiupload.com/M7UYRWDE4R (Remove .md5 extension)
ODIN RECOVERY (v2 EP1F): http://www.multiupload.com/31963EOUA0 (Remove .md5 extension)
Flash this first if you want to be on a functional EXT4 recovery. Then flash the ODIN kernel, or the regular CWM flash.
EP1H: http://www.multiupload.com/ZD87WPTFCT
Should be used with EP1H leak
MIRROR: http://www.mediafire.com/?0f89ej6fmjrt6ri
-----------------------
Version 1
http://www.multiupload.com/0H97NLCFUV
MIRROR: http://www.mediafire.com/?h0j9rrbuc9lmhkk
-----------------------
NOTE: There is no overclocking or core performance optimization made with this kernel. We do not currently have source to allow for such adventures and therefore you may see performance evaluations lesser than prior OS releases. If you acknowledge this, then you are also acknowledging the fact that you are by flashing this kernel running a cutting edge piece of software. As such, you should not expect nor fathom to be entitled to such performance characteristics of the aforementioned.
-----------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
I guess the file is still uploading? Anyway thank a lot for your work. I will try it!
Sent from my SCH-I510 using Tapatalk
porlo said:
I guess the file is still uploading? Anyway thank a lot for your work. I will try it!
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
It's possible I just put it up, though the DL links appear OK for me.
If we flash this, is there a way to return to the stock ep1f kernel easily? Like a cwm flashable zip?
I want to test but only if I can revert
You could use p3droids odin maker to back up kernal.
Sent from my Nexus S using Tapatalk
timgt said:
If we flash this, is there a way to return to the stock ep1f kernel easily? Like a cwm flashable zip?
I want to test but only if I can revert
Click to expand...
Click to collapse
I'm sure odin the full stock EP1F will get the kernel back.
Sent from my SCH-I510 using Tapatalk
Flashed using CWM 4.0.0.8, phone rebooted in 5 seconds, sat at the Samsung logo for a bit, and then booted up normal into Gummy GB. The FS is listed as RFS when I typed 'mount' in a terminal emulator.
---------------------------------------
Sent from a highly customized Droid Charge, using the magic of Verizon's 4G airwaves and Forum Runner.
NotATreoFan said:
Flashed using CWM 4.0.0.8, phone rebooted in 5 seconds, sat at the Samsung logo for a bit, and then booted up normal into Gummy GB. The FS is listed as RFS when I typed 'mount' in a terminal emulator.
---------------------------------------
Sent from a highly customized Droid Charge, using the magic of Verizon's 4G airwaves and Forum Runner.
Click to expand...
Click to collapse
Install process:
Use EXT4 Formatter (ALL version)
Flash Gummy Charged or other GB ROM
Flash NAMELESS kernel
Reboot
navenedrob said:
Install process:
Use EXT4 Formatter (ALL version)
Flash Gummy Charged or other GB ROM
Flash NAMELESS kernel
Reboot
Click to expand...
Click to collapse
did these in this order even before you posted them but wondered 2 things will it matter if I used the first all ext4 format zip you posted and 2ndly how long are you supposed to experience the "boot loop"
If I'm on EE4 do I need to flash EP1F stock first?
Sent from my SCH-I510 using Tapatalk
I know its made for gingerbread but can i flash this on froyo because i really want to try this but gingerbread isnt stable enough
rami98 said:
I know its made for gingerbread but can i flash this on froyo because i really want to try this but gingerbread isnt stable enough
Click to expand...
Click to collapse
I wouldn't use this on froyo, it's a kernel specifically for EP1F Gingerbread, you'll just get yourself caught in a boot loop.
ZeppelinJ0 said:
I wouldn't use this on froyo, it's a kernel specifically for EP1F Gingerbread, you'll just get yourself caught in a boot loop.
Click to expand...
Click to collapse
You up and running now?
navenedrob said:
Install process:
Use EXT4 Formatter (ALL version)
Flash Gummy Charged or other GB ROM
Flash NAMELESS kernel
Reboot
Click to expand...
Click to collapse
This worked. Thanks a bunch.
Sorry but what is ext4 formatter?
Edit: found it
Thanks for all the hard work!
I use my charge for a lot of tethering and when using the builtin hotspot it shows up as
Insert SIM for using Mobile Hotspot included tethering
Nice effects and looking smooth! Great work!
Are you planning to include the ability for a custom boot animation?
Sent from my Xoom using XDA Premium App
So I followed the steps outlined above, and now whenever I restart my phone, the initial Android setup wizard starts. All of my settings are intact, and even a new launcher is not stopping this. Any ideas?
NotATreoFan said:
So I followed the steps outlined above, and now whenever I restart my phone, the initial Android setup wizard starts. All of my settings are intact, and even a new launcher is not stopping this. Any ideas?
Click to expand...
Click to collapse
So are you saying that your settings are not being saved or old settings are not being updated?
Does anyone know why it wont boot past the screen with the white samsung logo the logo just flickers on then off?
I Tried:
Use EXT4 Formatter (ALL version)
Flash Gummy Charged 1.5
Flash NAMELESS kernel
Using CMR 4.0.0.8
MIUI 2.4.20
// HTC Dream:G1
// 2.3.7
// Based on Tvall's CM7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Attention
Always do a backup before flashing, responsibility lies with the operator of the device ultimately
Features
All the standard MIUI features
Known Issues
- Unknown!
Instructions
1. Download the rom, kernel, and gapps to your sdcard.
2. Make sure you are in recovery mode with a custom recovery.
3. Full Wipe!
4. Flash the rom
5. Flash the kernel.
6. Reboot.
Download
MIUI: 2.4.20 RC2
Kernel: Ezgb Kernel
Misc. Notes
This is MDPI based, and I followed procedure properly so everything should work here, but if anything is broken please let me know.
Also take note that DL'd themes do not work unless modified for MDPI use
Important
On first boot things may look garbled, after a reboot everything should be fine.
There may appear to be errors on install but everything should straighten out after a reboot.
What is the best gapps to use with this ROM and where can I get them from?
looks like gapps are packed with the rom so dont flash any separately
Everything is working as intended?
As of right now I am getting stuck on the green mytouch screen. The checksum of my downloads are correct. I know the problem isn't the kernal as I have used it before.
This has enough DLs for me to ask If your bootloop problem is isolated or not, is anyone else experiencing this?
wont install on a g1, tried two downloads (md5 for both 5F48EAFF996F2FA6BC7CC1F9195F7AA4) if you want to confirm
i dont have time to trouble shoot right now but at first the error appears to be missing a ringtone (romancingTheTone.ogg) and install is aborted, havent tried to adding it to test but someone else did (has only a couple of posts so he pm'd me as he cant post in this thread) and said the same. he tried replacing the file and then got another error that wouldnt let him flash, certinstaller error i think, but dont know why that would cause it not to instal. ill test tomorrow when i have more free time just giving you a heads up
Would that work on 32A devices with old radio?
This is my first time doing an MDPI MIUI port, It's strange for it to not work but I will compile a new build soonish
Ok, Uploaded RC2 and stripped the rom of potential breaks, so here goes folks!
anyone actually tested this?
tass0s said:
anyone actually tested this?
Click to expand...
Click to collapse
The first was non-functioning due to services and Framework, the second should probably work fine but If not I'll have to go the diffing route.
Either way I can for sure get this to be functional but I need feedback :s
Second Copy is smashed as well, It looks like I'm going to have to mess with code I'll have a new and hopefully proper build this time!
I hope you get this fixed! I love MIUI!
Just one thought; check system parition size, it may need to be bigger as MIUI is fairly big rom
Sent from my Desire HD using xda app-developers app
Okay my G1 stay alone without work and I preform test of yours rom. But my feedback is negative.
1. You have missing ogg melody and instillation was aborted because zip dont match with signature. I was able to install when disable signature verification. Thansk frankey
2. The rom dont boot. I try with RA/CWM recovery result was same. Are you sure this rom dont have need from custom MTD ??? My Logcat
From that logcat, audioflinger is dying. It isn't opening the files /system/etc/AudioPara_TMA.csv and /system/etc/AudioPara4.csv
Check to see if those are there. If not, get them then try.
Also, second post of my roms thread http://forum.xda-developers.com/showthread.php?p=31653323. If you use stuff I compiled, it states that you should at least send me a pm about using my work.
And the name is tvall. that's a lowercase "t".
Edit: still haven't downloaded yet. Just looking at file size, looks almost certainly like its too large for stock partition sizes. Try slimming it up, or moving some apps to /data, or just using custom mtd
i flashed it thru RA but it wont flash
just downloaded and looked. this rom is ~140mb. the /system partition on the g1 is 90mb. see the problem? trying to slim it up. got it down to 120mb by removing livewalpapers and apps that we are not allowed to distribute (including gapps isnt allowed). still have to free up ~30mb for this to be even usable. youll probably just have to use custom mtd.
edit:
have not tested this. /system size is 88mb, so no gapps yet. http://www.mediafire.com/?i3bsba3sgbf4e49. it may or may not boot. i have not tested. i just fixed the first obvious major issue with this rom, thats all.
tvall said:
just downloaded and looked. this rom is ~140mb. the /system partition on the g1 is 90mb. see the problem? trying to slim it up. got it down to 120mb by removing livewalpapers and apps that we are not allowed to distribute (including gapps isnt allowed). still have to free up ~30mb for this to be even usable. youll probably just have to use custom mtd.
Click to expand...
Click to collapse
Including gapps isn't allowed? Since when I use miui with them merged into the ROM
Take custom mtd up to 120 and then delete anything else we really don't need? Slim down ring tones to maybe 3 or 4
Good luck dude!
Sent from my HTC Desire HD using xda app-developers app