I'd like to use kernel manager to flash kernels, since its easier to do it from within android, with a GUI. I've downloaded imnuts' 100uv voodoo kernel, and after unzipping, it says "failed to create new boot image", so I guess the zimage is failing. Any help is appreciated.
Sent from mah Fascinate using XDA Premium App
I had the same problem. I just used kernel manager to download the kernel. Then manually booted to cwm recovery and flashed it manually. Worked fine.
Just apply zip and point it to your sdcard / kernel-manager / imnuts
Related
Okay, so tried the Vibrant OC UV Kernel so I can overclock my Vibrant, but I get stuck in boot loop everytime. This is what I did;
-Installed Eugene's ROM 2.2 JK2 using Odin3 v1.7- Worked fine.
-Installed ROM Manager
-Flashed Recovery using ROM Manager
-Download "Vibrant OC UV Kernel v1.0"(which is a zip file) on PC and moved it to root of SD card
-Reinserted SD card into Vibrant and used ROM Manager to Reboot in Recovery Mode
-In Recovery I, selected reinstall packages, selected choose zip from sd card, selected external sd, selected "Vibrant_OC_UV_Kernel_v1.0.zip"
Now I don't know what I'm doing wrong but every time it finishes it gets stuck in a boot loop. The only thing I can think of is what JAC said about kernels:
NOTE:For compatibility with all phones this does not automatically OC to 1.2Ghz per Unhelpfuls idea as not everyone can handle 1.2Ghz. Use a user script in the init.d folder with
Code:
#!/system/bin/sh
echo 1200000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
or setCPU to OC the Kernel to 1.2Ghz. 9.8MFLOPS is about what these CPU's average in Linpack at this speed. I've had it in the 10's and that may be coming back as another option.
Download the Overclock script here and make sure you put it in the /system/etc/init.d folder (right click and save with no extension for Windows users)
Anybody have any ideas?
dverrette said:
Okay, so tried the Vibrant OC UV Kernel so I can overclock my Vibrant, but I get stuck in boot loop everytime. This is what I did;
-Installed Eugene's ROM 2.2 JK2 using Odin3 v1.7- Worked fine.
-Installed ROM Manager
-Flashed Recovery using ROM Manager
-Download "Vibrant OC UV Kernel v1.0"(which is a zip file) on PC and moved it to root of SD card
-Reinserted SD card into Vibrant and used ROM Manager to Reboot in Recovery Mode
-In Recovery I, selected reinstall packages, selected choose zip from sd card, selected external sd, selected "Vibrant_OC_UV_Kernel_v1.0.zip"
Now I don't know what I'm doing wrong but every time it finishes it gets stuck in a boot loop. The only thing I can think of is what JAC said about kernels:
NOTE:For compatibility with all phones this does not automatically OC to 1.2Ghz per Unhelpfuls idea as not everyone can handle 1.2Ghz. Use a user script in the init.d folder with
Code:
#!/system/bin/sh
echo 1200000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
or setCPU to OC the Kernel to 1.2Ghz. 9.8MFLOPS is about what these CPU's average in Linpack at this speed. I've had it in the 10's and that may be coming back as another option.
Download the Overclock script here and make sure you put it in the /system/etc/init.d folder (right click and save with no extension for Windows users)
Anybody have any ideas?
Click to expand...
Click to collapse
are you using the unnofficial rom? or the old froyo that doesent brick?
if your using the old one (Froyo that doesent brick) you might consider updating to Macnut R13 or The Unofficial.
and you might want to use a more up to date kernel as well.
I'm not familiar with the kernel you posted either... thats not Jac's kernel is it?
if so, it wont work with 2.2 roms.
I'd try one of eugene's if your on his rom. (make sure its a 2.2 kernel first though)
you may want to re-odin beforehand though just in case.
Im still fairly mew to this so how would I know if I have The Unofficial or Froyo that does not brick? This is what's in my settings,
Firmware 2.2
Sent from my SGH-T959 using XDA App
Baseband: T959UVJK2
Kernel: 2.6.32.7
Build: FROYO.UVJK2
Sent from my SGH-T959 using XDA App
Also this is the MD5 file I use with Odin, "Eugene_2E_JK2_Froyo.tar.md5"
So the question remains if this is the unofficial or the froyo that doesn't brick?
Hey guys! Now I know some of you have been asking for an Odin version of CWM 3.x seeing as we are all starting to phase out amend scripting. And I know you guys don't want it in a flashable zip form because then you'd have to flashed CWM 2.x and then flash the zip to 3.x or hacked 2e recovery and use Koush's cwm 3x and then flash the zip to Voodoo 3.x.
Well here it is the CWM 3.x with Voodoo options ODIN package:
http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5
MD5 sum: (CWM3_Voodoo.tar.md5) = 914b57882405cecda4f5590e48789d35
SHA1 digest: (CWM3_Voodoo.tar.md5) = 9794f6b3532af19e8f3621e0eb4d8b945930b127
http://dl.dropbox.com/u/36791/CWM3_Voodoo-blue.tar.md5
MD5 sum: (CWM3_Voodoo-blue.tar.md5) = 2f3898feb98cff85eab4d66c94ef626f
SHA1 digest: (CWM3_Voodoo-blue.tar.md5) = 03769dae411207ed3f77807cda6e768a7d7c56f9
http://dl.dropbox.com/u/36791/CWM3_Voodoo-purple.tar.md5
MD5 sum: (CWM3_Voodoo-purple.tar.md5) = 87a5be1e61720ea2a7e5f025cf845462
SHA1 digest: (CWM3_Voodoo-purple.tar.md5) = 04312731c65501a766c8b4ef0ac14b62628fa0a6
You guys know the rules:
Flash with Odin
Boot straight into recovery
Flash kernel of choice if needed if on stock
*NEW*
Flashable Zip version:
http://dl.dropbox.com/u/36791/CWM3_Voodoo.zip
MD5 sum: (CWM3_Voodoo.zip) = 6838cd1efea6c0489dab02db2154d9c1
SHA1 digest: (CWM3_Voodoo.zip) = b84d427096debede74b8ff56275718efca7ca936
http://dl.dropbox.com/u/36791/CWM3_Voodoo-blue.zip
MD5 sum: (CWM3_Voodoo-blue.zip) = f673dbe60eb6418179de02b86fc3a8e2
SHA1 digest: (CWM3_Voodoo-blue.zip) = 1a712a8b63fc12849dd35c6942ed7542d62b113a
http://dl.dropbox.com/u/36791/CWM3_Voodoo-purple.zip
MD5 sum: (CWM3_Voodoo-purple.zip) = fc110b27f95d2cd859e61b07d3ad1299
SHA1 digest: (CWM3_Voodoo-purple.zip) = 20b404f80510d1e4d5aaf1142a34e6da813af3f8
NOTICE:
If you are nonvoodoo and plan to stay nonvoodoo make sure you have a disable-lagfix file in the voodoo folder on your sdcard
For some reason, even though this is a recovery it's still doing the voodoo conversion.
So from here on out, I am not responsible for your spontaneous voodoo conversions.
YOU'VE BEEN WARNED
NOTICE 2:
So for the people that don't think recovery is wiping batterystats.bin it actually is.
If you boot into recovery after seeing there's a batterystats.bin in /data/system
and then you wipe batterystats and then mount data before or after you run the wipe battstats command
and you adb shell into /data/system you will see that batterystas.bin IS NOT there.
So just to make everyone feel better, batterystats wiping DOES work.
For those who only need to update their recovery from an existing version of CWM that aren't coming from stock.
Hopefully amend will be dead here and everyone will fall in line properly and start using edify.
Enjoy!
EDIT: as far as I know. ADB does work while in recovery with this. If someone wants to test please post saying whether or not it does. Or I'll just test later and let everyone know.
TODO:
Add Format boot option to recovery as requested.
This will go into the advanced menu, since it's not integrated originally into CWM3.x
*************************************************
EDIT 4.24:
Updated to latest recovery included in jt's kernel source.
Should fix the RFS errors when trying to wipe anything
The only not found error you'll get is sd-ext, because we don't have one.
ADB *DOES* work in this one too.
EDIT 4.25:
Recompiled to make sure I catch any changes that jt made
Added link to a flashable zip version see above.
EDIT 4.26:
Added notice about voodoo conversions
EDIT 4.29:
http://forum.xda-developers.com/showpost.php?p=13309766&postcount=71
Some insight about why battery stats wiping isn't working.
EDIT 4.29 2:
See notice #2
EDIT 5.3:
Rebuilt recovery from source using Nemesis2all's recovery tree
Added Reboot Download Mode in Advanced menu
Added batterystats wipe success output.
EDIT 5.6:
Fixed stupid SD-Ext error when wiping dalvik cache
Fixed USB Mass Storage in recovery with some help from jt.
EDIT 5.8:
Got bored and added two more recoveries, now in new colors! Blue and Purple!
thank you sir
Coming through in the clutch! Nice!
Sent from my SCH-I500 using XDA Premium App
Nice. I didn't even think to make it an ODIN file. Then again some of us don't want to always use odin so sometimes having it in a flashable zip is useful.
Apologies but will this wipe data? If we are on TW kernel and SC we just Odin this and reboot?
Thanks for the work!
Sent with my thumbs.
BeeDubs said:
Apologies but will this wipe data? If we are on TW kernel and SC we just Odin this and reboot?
Thanks for the work!
Sent with my thumbs.
Click to expand...
Click to collapse
This is just recovery, not rom. Odin this baby
You've just been Fascinated
Thank you! Will do.
Sent with my thumbs.
Updated OP
Sent from my SCH-I500 using XDA App
This week keeps getting better and better
Thanks man, just what i was looking for
x 1/0,
Confirmed adb does work while in recovery.
gdnl
yup works in recovery
I've heard word in the "other" CWM3 thread that 3.x has trouble flashing themes sometimes (the OP's OP). This true or are themes good to go?
Syn Ack said:
I've heard word in the "other" CWM3 thread that 3.x has trouble flashing themes sometimes (the OP's OP). This true or are themes good to go?
Click to expand...
Click to collapse
if themes have edify scripts in them its fine....i believe the real issues are with roms if the issues exist at all
Is this the latest version of CWM? Will it work on the Mesmerize?
Why do I get this error when cleaning cache:
E:mount -t rfs -pllow,check=no.nosuid.nodev /dev/
block/mmblk0p1 /data
E:unkown volume for path [/sd-ext]
Ya will it work on mez
Sent from my SCH-I500 using XDA App
Yes it works on the mez
Sent from my SCH-I500 using XDA Premium App
Cool is this the very latest cwm that works on the mez? Currently I have the 3/30 cwm from jt. Can I just flash over it with Odin?
Updated OP.
Now that we have a CWM image that works with the Flyer, has anyone started working with @koush to get our CWM image on the Rom Manager list?
I would like to be able to use Rom Manager, but it requires CWM to be installed by the app.
Honestly I think he should support multiple recoveries. Why only cwm?
Sent from my PG86100 using XDA App
Express/Flyer Rom Manager Workaround
I have the View (Express) and I used a little workaround until its recovery is listed. I copied and edited the .settings file from my 3d's clockworkmod directory changing the detected_device from "shooter" to "express". Then, I overwrote the original .settings file in my View's clockworkmod directory with the edited one, rebooted and Rom Manager recognizes recovery and allows me to peform all functions except Flash ClockworkMod Recovery. I've pasted the contents of that file below and I've also included a zipped copy. Try changing "express" to "flyer" and see how it goes.
{"paypal_transaction_id":"","is_clockworkmod":true ,"current_recovery_version":"3.0.0.5","detected_de vice":"express","flash_recovery":"","readonly_reco very":false,"recovery_timestamp":1312091378056,"re boot_recovery":""}
Awesome mate!
Could you patch that also for the flyer, then I could add the patched version to my rom? (I have so many things to do..)
That would be great
spankaroo said:
Now that we have a CWM image that works with the Flyer, has anyone started working with @koush to get our CWM image on the Rom Manager list?
I would like to be able to use Rom Manager, but it requires CWM to be installed by the app.
Click to expand...
Click to collapse
I would also like to see this on the Rom Manager list.
dhearns said:
I have the View (Express) and I used a little workaround until its recovery is listed. I copied and edited the .settings file from my 3d's clockworkmod directory changing the detected_device from "shooter" to "express". Then, I overwrote the original .settings file in my View's clockworkmod directory with the edited one, rebooted and Rom Manager recognizes recovery and allows me to peform all functions except Flash ClockworkMod Recovery. I've pasted the contents of that file below and I've also included a zipped copy. Try changing "express" to "flyer" and see how it goes.
{"paypal_transaction_id":"","is_clockworkmod":true ,"current_recovery_version":"3.0.0.5","detected_de vice":"express","flash_recovery":"","readonly_reco very":false,"recovery_timestamp":1312091378056,"re boot_recovery":""}
Click to expand...
Click to collapse
Works great with my Flyer 3G/Wifi. I just started a backup using Rom Manager - Very nice.
I used your .settings file and modified "express" to read "flyer" as you suggested. I simply replaced the existing .settings file in /sdcard/clockworkmod with the new one attached.
Cheers!
Please disregard this post.
strange as i have just installed rom manager onto my flyer and clicked reboot into recovery and it did this just fine, no work around needed.
is this needed for backing up etc as i already did this in the recovery menu not via rom manager
madnlooney said:
strange as i have just installed rom manager onto my flyer and clicked reboot into recovery and it did this just fine, no work around needed.
is this needed for backing up etc as i already did this in the recovery menu not via rom manager
Click to expand...
Click to collapse
You may or may not need it, but it's fixed these problems for some: When selecting "Download ROM", "Check for ROM Updates", "Install from QR Code", "Manage and Restore Backups", "Backup Current ROM", "Partition SD Card", or "All ClockworkMod Recoveries" most people encounter the error "You must have ClockworkMod Recovery installed before continuing! Install the recovery through ROM Manager first". When "Install ROM from SD Card" is selected a warning is displayed "Flashing an update package on a recovery other than ClockworkMod Recovery may not work properly. Proceed?
Yeah it restarts to recovery fine but in Tom manager it didn't allow to backup or manage until I changed settings
In ROM Manager, press menu, then 'manual flash override'
How do I remove dual core scripts... Or whatever is enabling them... I tried a couple kernels and still activated. Running eternity 1.4.2
Sent from my PG86100 using xda premium
Check your init.d folder for a file called 98dualcore, delete that. If you don't see anything, then your going to have to flash an unmodified stock kernel. Freeza has an explanation for that in his thread.
ceyo14 said:
How do I remove dual core scripts... Or whatever is enabling them... I tried a couple kernels and still activated. Running eternity 1.4.2
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
DDiaz007 said:
Check your init.d folder for a file called 98dualcore, delete that. If you don't see anything, then your going to have to flash an unmodified stock kernel. Freeza has an explanation for that in his thread.
Click to expand...
Click to collapse
Example: Ziggy's dual core kernel flash .zip file modifies thre system binaries in addition to the init.d script it adds. Kernel .zip files, imo, should not modify system binaries. System binaries should only be modified by ROMs. Of course, there is no official standard and this is just my opinion based on experience.
One main reason would be, majority of other kernel .zip files do not modify those same system binaries. So the only way to "undo" the files changed by Ziggy's kernel flash, would be to reload a ROM which replaces the three system binaries Ziggy changes.
Essentially, if you want to undo the changes made by Ziggy's kernel flash, you'll need to replace all files modified by his kernel flash. Flashing another kernel will not replace those files, but loading another ROM *should*.
Hope that helps!
Are there any known issues with using the latest CWM recovey for the Evo View running Honeycomb? I have just downloaded cwm 5.8.1.5 and was going to flash it but I wanted to make sure there aren't any known issues first.
Is anybody else using cwm 5.8.1.5? If so, what improvements did it bring from the default 4.x version?
it recognize both internal and external memory so you can flash roms or files from the internal memory if you don't have an sd card ..
it's best to post any questions on the original thread to get better respond
Thanks for the info. To install it did you just take the recovery-clockwork-5.8.1.5-express.img file you downloaded and rename it to PG41IMG.zip and then let the fastboot detect it to install it? Or is there a zip version that is flashable from the older cwm recovery?
NP.. I used ROM Manager to flash it
It also can be flashed using fastboot command
Sent from my PG41200 using xda premium