[Q] KozmiKKernel Flash Question - HTC Vivid, Raider, Velocity

Hi,
I just downloaded the Beta 5 release of the kernel and need some help. I'm using the latest WCX rom and performed the following steps to flash this kernel:
1. Downloaded the S-OFF version of Beta 5 as I'm S-OFF
2. Copied file to my SD-Card
3. Rebooted to Recovery
4. Flashed the kernel file
5. Recovery flash process showed as being successful
6. Rebooted phone
Now when the phone boots back, it still shows the WCX kernel as being installed. I don't see any sign of the Kozmik kernel and the freq remains at 1512 instead of the 1782 in this kernel.
Am I doing something wrong? Any help would be appreciated. Thanks.

N/M...figured it out. Not sure why I thought I was S-OFF, but I'm not. Flashed through bootloader and works great now. Feel like an idiot.

Related

[Q] Issues loading Darlington Kernel with CM7

I'm struggling with trying to get the dalingrin loaded on my nook color, followed instructions here: http://forum.xda-developers.com/showpost.php?p=11535969&postcount=151 to flash my nook from stock. Running CM7 build 14 and everything is working as expected, however i can't seem to load the kernel update. Regardless of the file i load using clockworkrecovery 3.0.0.6, the following sequence appears every single time:
Install .zip from card, installed successfully. Removed sd card, rebooted:
"touch the future of reading"
Nook symbol
Install Failed / Please power off and back on to try again...
Power off / on
Boots into CM7 normally, but under setting -> about -> 2.6.29-omap1 [email protected] #22 which I believe indicates that dalingrin kernel was not loaded, right?
Sounds like something isn't overwritten properly in the boot record..
Any help would be most appreciated. Thanks!
installed this file:
update-CM7-dalingrin-OC-sd-030811.zip repeated with cm 7 release 12, 13 and 14. same issues.
Bump... can someone please help. I must have missed something trivial or boot loader didn't overwrite properly. Very strange. Any advice would be most appreciated.
My suggestion is to check out this thread http://forum.xda-developers.com/showthread.php?t=987735 and update you sdcard to CWR 3.0.1.0. I've had serious issues the past week when trying to use the 3.0.0.6 CWR with some of this newer stuff going around.
yarink said:
Bump... can someone please help. I must have missed something trivial or boot loader didn't overwrite properly. Very strange. Any advice would be most appreciated.
Click to expand...
Click to collapse
Updating to new recovery may work. May also try this if you haven't already. If you are using the CM governor or setcpu, try setting it to boot at 800. I am not sure if the fail to install is a speed issue or what. If it boots you can tweak the speed.
I updated my boot sd-card to CWM 3.0.1.0 and installed the latest kernel again. I don't believe any changes were made. Same sequence: install, reboot, i get nook symbol and failed to boot, reboot and cyanogenmod gingerbread loads as expected. Under Kernel I see: 2.6.29-omap1 [email protected] #3. Mod version Cyanogenmod-7-03112011-NIGHTLY-encore
Did the latest kernel install despite the first reboot issue?
Thanks!
Are you wiping the devlik-cache in the advanced menu of Clockworkmod after flashing the kernel?
Yes, wiping both devlik cache and well as standard cache, but before flashing kernel. Does it matter if I flash before vs after flashing? I can overclock to 1.1ghz using setcpu, not sure if that means install was successful. Still trying to figure out it the kernel version i posted reflects the latest kernel. thanks
Hi,
In your first post, you mention using this file:
"installed this file:
update-CM7-dalingrin-OC-sd-030811.zip repeated with cm 7 release 12, 13 and 14. same issues."
That appears to be the file for CM7 version that will run from an SDcard.
I believe you want the version that runs on CM7 installed to the internal memory
or emmc:
update-CM7-dalingrin-OC-emmc-031311.zip
Settings->about tablet reports kernel version: "2.6.29-omap1 [email protected] #4"
The Settings->CyanogenMod settings->performance->CPU Settings->MaxCPU freq
can then be set to 1100MHz. The stock CM7 kernel can be set to 9xxMHz.
Sounds like you may have solved it already, otherwise, hope this helps!
Peter

[Q] Help With Custom Rom installation.

Hi there,
Since gingerbread with most probably be the last update for SGS i would like to install a custom mod.
Now i have been trying to do this (darky 10 RC4) for the past 2 days.
I followed Darky's instructions then i had a problem with the CWM only accepting "edified" script.
So i downloaded rom manger and tried to downgrade ta 2.5 but as soon as i tap on the 2.5 it immediately comes up with an error, "an error occured while flashing your recovery."
this is done on a 2.3.3 JVB SGS with CWM 3 installed (orange text).
Are there alternate routes? maybe downgrading to android 2.2 installing an older version of darky and than upgrading the darky rom?
any help is much appreciated.
thanks
Download the rom CWM-zip and put it in your internal sdcard.
Download some froyo-kernel (yes, froyo) with CWM 2.5. Speedmod for example. Then flash it with Odin repartition and auto-reboot unticked. When the flashing process is completed, pull the battery and then boot to recovery (3 button combo). Now you have CWM 2.5 and you can flash the CWM-zip from there.
thanks, i wil try that.
Now you have CWM 2.5 and you can flash the CWM-zip from there.
Click to expand...
Click to collapse
just 1 question, why do i need t flash CWM-zip if i am already on CMW 2.5?
jan-sgs said:
thanks, i wil try that.
just 1 question, why do i need t flash CWM-zip if i am already on CMW 2.5?
Click to expand...
Click to collapse
Sorry. With CWM-zip I meant the Darky's Rom.zip, which can be flashed through CWM.
it didnt work, u just gave up.
hopefully some new rom update that is edified will show up in a couple of months
Install supercurio hacked kernel, it has recovery 2.5 instead of 3.0.0.5. From there you should be able to install darky's rom. If the new version of his kernel is recovery 3, tell me i'll send the old one just for the purpose.
Hi,
ok last attempt
i flashed ( odin PDA, no pit and no repartition) with this link:
Kernel Download:
Gingerbread-GT-I9000-stock-kernel+hacks.tar
http://forum.xda-developers.com/showthread.php?t=975349
while i was on
PDA_I9000XWJVB - PHONE_I9000XXJVK - CSC_I9000XEEJV3
rooted with root CF-Root-XX_OXA_JVK-v3.1-CWM3RFS
and lag fixed with CF-Root-ext4-v1.2
and it forking worked red text 2.5 THANKS A BUNCH!
edit just a problema. it is only booting in CWM.
reattempting this without the lag fix.
2nd attempt with PDA_I9000XWJVB - PHONE_I9000XXJVK - CSC_I9000XEEJV3
and without lag fix not rooting.
phone stuck looping at booting with strange sound on each boot loop
3rd attempt with rooting, but no lagfix
If you are only rebooting in recovery, did you flash the new kernel, then reboot recovery ? if yes, the easy way to get out, is to reboot in download then reflash the wanted kernel (Since your rom is installed, you can install any kernel (GB of course)) then, it will reboot in recovery again and just reboot system now. This should fix your problem.
edit : Dont forget to get CF-root 3.1 for JVB and not JVK.
chadouming said:
If you are only rebooting in recovery, did you flash the new kernel, then reboot recovery ? if yes, the easy way to get out, is to reboot in download then reflash the wanted kernel (Since your rom is installed, you can install any kernel (GB of course)) then, it will reboot in recovery again and just reboot system now. This should fix your problem.
edit : Dont forget to get CF-root 3.1 for JVB and not JVK.
Click to expand...
Click to collapse
ok, i couldnt do that before because i had deleted the rom form the internal SD.
and also thanks for pointing out that i had the wrong root (i worked by you never know if it could case problems)
ok so
PDA_I9000XWJVB - PHONE_I9000XXJVK - CSC_I9000XEEJV3
root CF-Root-XW_XEE_JVB-v3.1-CWM3RFS
lagfix CF-Root-ext4-v1.2-Addon
and
Gingerbread-GT-I9000-stock-kernel+hacks
and the zip is in progress.
ps it wasnt stuck the previous time, i was pressing the middle key as the selection while i should have been pressing the power button.
thanks for your help very much appreciated.
if i get some free time i will write at tutorial since i could not the solution.
This isn't development, moved to Q&A

Entering recovery phones stuck HTC Logo

Whenever I try to enter recovery on my HTC vivid all I get is the HTC Logo. I can press buttons, they vibrate, but nothing changes.
I've rooted and unlocked the bootloader. Everything else on the phone seems fine and works properly.
I was reading somewhere it might be due to having version 5 of clockwork. It wasn't the same phone though. Is anyone else running into this issue with the HTC Vivid At&t?
I had this happen once , and it seems like relocking the bootloader and running the stock ruu file is almost a fix for every thing I've ran into .
So that's what I would try .
I've used ClockWorkMod v5.5.0.4 (it's non-touch) since I got my phone (about 2 months now?) and I have flashed a few roms (and backup/restored many times) without any issues. Is that the version you are using? (Or is yours the newer touch-style one?).
If you want to try manually flashing 5.5.0.4 via fastboot....
Filename: CWM-beta2.img (inside the below zip)
http://www.4shared.com/zip/tAZgjz25/CWM-beta2.html
I have the phone that's completely touch. I'm using version 5.0.2.7 of ClockworkMod. I'll try using the version you posted and if that doesn't help I'll re-lock the bootloader and run the stock ruu file.
For some reason when I installed the Rom Manager it chose to install that other version of Clockwork Mod which was giving me issues I assume. I reflashed Clockwork Mod recovery with the version you mentioned 5.5.0.4, and I'm able to boot into recovery now :] Thank you both for helping.
Sweet!

Rooted and Unlocked, but need help install ROMs

Hello there fellow XDA members,
I just got a Nexus One and it is giving me quite a headache right now...
I am unlocked (using fastboot) and rooted (SuperOneClick) but cannot get into recovery / flash roms.
I have tried:
1.) Installing ROManager,4EXT, etc. apks, but get parsing errors in android
2.) Install CWM through fastboot, but get stuck on the logo when I boot into recovery
3.) Install ROManager, 4EXT, etc through adb, but get "INSTALL_FAILED_OLDER_SDK" error.
About my phone:
Firmware 2.1-update 1
Baseband: 32.240.22U_4.03.00.21_2
Kernel: 2.6.29-01117-g4bc62c2
Build number ERE27
If anyone could offer some help in getting me to a working ICS rom, I would be very grateful.
EDIT: Was able to use ARMONs recovery just aye okay, guess I freaked out too early. Just flashed an ICS ROM, time to see if it works okay!
EDIT 2: ROM doesn't seem to be rooted, but so far so good
Do you have Blackrose installed?
And I can safely say that *every* custom ROM you will find here is rooted.

Can't catch a break - need help! DM-Verity Verification Failed.

Trying to flash my Note 4 (Canadian version - N910W8) with either the AllianceROM 1.1 or TEKXodus 3.6 ROMs. Can't seem to get it done and I'm so incredibly frustrated.
Chronologically-speaking, here's what I did.
1. Rooted with appropriate Auto-Root file with Odin 3.09
2. Used Flashify to flash the latest TWRP files (2.8.7)
Most of the time, I just reboot onto "dm-verity verification failed." I've tried everything I can think of.
Sometimes, I get lucky and boot into TWRP. When I flash using TEKXodus 3.6 ROM, it proceeds to do everything but then, the screen goes black and I can never boot. I've read it can take 15 min for it to boot. I've waited 30 min with nothing. Only thing I could do is boot back into Download mode to reflash it with a stock ROM through Odin.
I don't understand why this doesn't work and I've flashed a bunch of phones before without any issue! Help? Anybody? UGH!
need help
Strat-Mangler said:
Trying to flash my Note 4 (Canadian version - N910W8) with either the AllianceROM 1.1 or TEKXodus 3.6 ROMs. Can't seem to get it done and I'm so incredibly frustrated.
Chronologically-speaking, here's what I did.
1. Rooted with appropriate Auto-Root file with Odin 3.09
2. Used Flashify to flash the latest TWRP files (2.8.7)
Most of the time, I just reboot onto "dm-verity verification failed." I've tried everything I can think of.
Sometimes, I get lucky and boot into TWRP. When I flash using TEKXodus 3.6 ROM, it proceeds to do everything but then, the screen goes black and I can never boot. I've read it can take 15 min for it to boot. I've waited 30 min with nothing. Only thing I could do is boot back into Download mode to reflash it with a stock ROM through Odin.
I don't understand why this doesn't work and I've flashed a bunch of phones before without any issue! Help? Anybody? UGH!
Click to expand...
Click to collapse
i m also having the same problem
did u find any solution
Strat-Mangler said:
Trying to flash my Note 4 (Canadian version - N910W8) with either the AllianceROM 1.1 or TEKXodus 3.6 ROMs. Can't seem to get it done and I'm so incredibly frustrated.
Chronologically-speaking, here's what I did.
1. Rooted with appropriate Auto-Root file with Odin 3.09
2. Used Flashify to flash the latest TWRP files (2.8.7)
Most of the time, I just reboot onto "dm-verity verification failed." I've tried everything I can think of.
Sometimes, I get lucky and boot into TWRP. When I flash using TEKXodus 3.6 ROM, it proceeds to do everything but then, the screen goes black and I can never boot. I've read it can take 15 min for it to boot. I've waited 30 min with nothing. Only thing I could do is boot back into Download mode to reflash it with a stock ROM through Odin.
I don't understand why this doesn't work and I've flashed a bunch of phones before without any issue! Help? Anybody? UGH!
Click to expand...
Click to collapse
So i see your posting about your flashing but what about your wipes..
Nandroid backup ext sd.
Then reboot twrp.
Wipe sys/dal/cache/data..
Include the internal if after what i posted above doesnt work.
Check the md5 sum of your downloaded rom..
Nav to your ext sd were you should have the rom stored..
And flash the rom..
Curious as to why you used flashify to get twrp.. it comes in a tar and flashes easy in odin..
You might wanna try that as well twrp may not be installed 100% corectlly.
Ok..[emoji41] [emoji106]
Last but not least you need to use bishock kern in your flash after the Rom flash, in the same session before reboot.
Or it will never work.
You booting problem more than likely kernel related..
Flashvetrin

Categories

Resources