Develop Bugs

Q? About HONO Full Throttle

I tried to flash HONO Full Throttle V2, cleared cache, dalvik cache.
Now my phone keeps rebotting loopping. I tried to access ROM manager but it reboots before it can do it. I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Do i have to unbrick?
Any help is appreciated, thank you

When that happened to me, with a different ROM, I went ahead and pressed power again at that screen and it continued to CWM, didn't wipe/reset my phone.

neuty said:
I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Click to expand...
Click to collapse
That is what you are supposed to see. Press power button twice to "accept" the factory reset. It won't actually reset anything -- instead it will boot directly to CWM.

Oh, okay thanks so much RealyPssd and Drumist! Got a bit scared for a second there. Was able to flash back
Edit: I might have found the problem:
I tried installing HONO's P930 CM9 Kernel V5 and it did the same thing but worse, it didnt even let me past the CM boot guy.

Went through the same thing
I tried flashing HO!NO!'s CM9 Full Throttle this morning and went through the same thing. Sometimes it would boot into the OS, other times it wouldn't get past the CM9 guy, and even sometimes it wouldn't get past the HO!NO! logo. I even had a hard time getting into CWM via the factory hard reset method (I kept getting just a blank screen, but the phone was still on. I pressed the volume down button and that seemed to get it into CWM, although it could have just been a coincidence).
I tried re-flashing the ROM but still no change. So I then flashed CM9 RC-1 and haven't had an problems since.
From what I've read in the Full Throttle thread, the HO!NO!'s ROM already comes with HO!NO!'s kernel. I've also read that the instability is due to the undervolting that's taking place in the ROM (and I'd have to agree based on my experiences with overclocking).
If you really want CM9 go with the RC-1 (or even the nightly). I find it to be incredibly fast so far. Maybe HO!NO! can make a ROM compiled with the linaro toolchain that has a slightly less aggressive undervolting settings

To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.

Wiped everything but had a backup
HO!NO! said:
To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.
Click to expand...
Click to collapse
I was coming from a stock ROM that I had rooted with SuperOneClick, and installed CWM using Rom Manager from the market. When I went to install your ROM I first made a backup of the current ROM (i wanted to having something to fall back to). I did a wipe data/factory reset, wipe cache, wipe dalvik, then flashed your ROM. I also flashed gapps as well (could that have caused a problem?)
Does it sound like anything is off? I would really like to be running your Full Throttle ROM (it's the only reason why I tried to flash my phone in the first place)

What is the issue with the Poweroff / Reboots not working.

I have almost tried ALL the ICS custom roms. Besides the default, T-Mo ICS rom, none of the other custom ICS roms that is based on 4.0.3 UVLE1, does not shutdown or reboot.......it just sits there.
All the instructions that I came across refers to 'Cache, Dalvick Cache and Permissions reset" - but this does not make a difference.
Even the software apps available to reboot.poweroff, does not work anymore.
Any ideas? Am I missing something?
It almost seems like something was messed up somewhere and all the ROM mods are based on that?
Thanks

Have you tried that Darkside Cache Wipe? it usually clears up that problem.
Sent from my SGH-T989 using xda app-developers app

bert269 said:
I have almost tried ALL the ICS custom roms. Besides the default, T-Mo ICS rom, none of the other custom ICS roms that is based on 4.0.3 UVLE1, does not shutdown or reboot.......it just sits there.
All the instructions that I came across refers to 'Cache, Dalvick Cache and Permissions reset" - but this does not make a difference.
Even the software apps available to reboot.poweroff, does not work anymore.
Any ideas? Am I missing something?
It almost seems like something was messed up somewhere and all the ROM mods are based on that?
Thanks
Click to expand...
Click to collapse
What recovery are you running? Have you tried the darkside super cache wipe? Cwmr 5.0.2.7 (i believe that's the version) the hard recovery doesn't clear caches correctly. Never had a problem with with ics roms not rebooting or power issues, been running cm9 stable since release and haven't had a problem.
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!

EnigmaticGeek said:
What recovery are you running? Have you tried the darkside super cache wipe? Cwmr 5.0.2.7 (i believe that's the version) the hard recovery doesn't clear caches correctly. Never had a problem with with ics roms not rebooting or power issues, been running cm9 stable since release and haven't had a problem.
Click to expand...
Click to collapse
Yes. I used the Darkside Cache wipe everytime before I flash the ROMs, This is my process:
Backup, wipe data, Wipe cache, ADvanced+wipe Dalvic, mount+Format /system, flash Darkside EXT4 wipe, Flash Darkside Cache wipe,
Flash rom, reboot, let is sit 10mins, reboot (well hold power in for 10seconds until it buzz and then boot up)
Afterwards powerbutton brings up menu, it even brings up the T-Mobile shutdown logo (if the rom has it) and just sits there......FOREVER.
I have even reflashed the Darkside Cache wipe - still the same.
I'm on CWM Touch recovery 6.0.1.1
Very annoying.
Caboose13 said:
Have you tried that Darkside Cache Wipe? it usually clears up that problem.
Click to expand...
Click to collapse
THanks - yes I have.

bert269 said:
Yes. I used the Darkside Cache wipe everytime before I flash the ROMs, This is my process:
Backup, wipe data, Wipe cache, ADvanced+wipe Dalvic, mount+Format /system, flash Darkside EXT4 wipe, Flash Darkside Cache wipe,
Flash rom, reboot, let is sit 10mins, reboot (well hold power in for 10seconds until it buzz and then boot up)
Afterwards powerbutton brings up menu, it even brings up the T-Mobile shutdown logo (if the rom has it) and just sits there......FOREVER.
I have even reflashed the Darkside Cache wipe - still the same.
I'm on CWM Touch recovery 6.0.1.1
Very annoying.
THanks - yes I have.
Click to expand...
Click to collapse
Yeah, that is very annoying. Have you looked into the potential that it could be a kernel issue? And also, have you flashed back to stock and done completely clean install without resorting data to anything?
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!

EnigmaticGeek said:
Yeah, that is very annoying. Have you looked into the potential that it could be a kernel issue? And also, have you flashed back to stock and done completely clean install without resorting data to anything?
Click to expand...
Click to collapse
Thanks....
I'll flash back to stock this evening when I get back home and see how it goes.....will report back.
Thanks
PS. I normally ONLY restore my apps-data - NO system data accept SMS/MMS & Bookmarks - that's all system data I EVER restore.
But I'll try the 'back to stock' and report back.
THX

I was having the same problem. The ds scripts did not fix it for me. I also tried updating cwm5.0.2.7 to cwm 6.x. still it did not work. Tried using ROM toolbox pro, titanium backup pro and ROM manager, they would all freeze while trying to power off the phone or trying to reboot to recovery. Finally I flashed twrp2.2, that has seem to fixed it.
Sent from my SGH-T989 using xda premium

Don't use CWM to wipe cache at all.
1. Flash super wipe
2. Flash Rom
3. Flash cache wipe
4. Reboot
5. Let sit for 10 mins
6. Reboot
Follow those steps and you will have no problems.
Sent from my SGH-T989 using xda premium

Towle said:
Don't use CWM to wipe cache at all.
1. Flash super wipe
2. Flash Rom
3. Flash cache wipe
4. Reboot
5. Let sit for 10 mins
6. Reboot
Follow those steps and you will have no problems.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Honestly, I don't see the point of wiping cache after a fresh install. Unless I'm mistaken, there is no cache yet? I do that except no cache wipe after flash ROM. With Darkside in particular, it installs apps during the first boot up. Of yet to have out of the norm issues.
Sent from AOKP Goodness

LoopDoGG79 said:
Honestly, I don't see the point of wiping cache after a fresh install. Unless I'm mistaken, there is no cache yet? I do that except no cache wipe after flash ROM. With Darkside in particular, it installs apps during the first boot up. Of yet to have out of the norm issues.
Sent from AOKP Goodness
Click to expand...
Click to collapse
Must do something because the only way my reboot and power off will work is if I flash the cache wipe after the rom.
Sent from my GT-P7510 using xda premium

You need to flash the cache wipe after flashing and rebooting
Sent from my SGH-T989 using xda app-developers app

I must be the only one with this issue when i use superwipe for some odd reason my phone will not boot unless i do a cwm recovery no matter what i do. i am not too sure why this happes, and btw i am stock...., but it does and i cannot figure it out i am scared to use it. The only other way i was able to get my phone to boot past the quick load up bar which it stops at about 90% for some odd reason is if i do a nandroid restore...any reason why this happens???

You're supposed to use the darkside cache script after flashing the rom and after flashing any other mods and themes, but I have also notice that the script does not work correctly when using twrp. So when using twrp clear the caches and fix permissions with the options in recovery after the rom.

Bert, dont use that cache wipe again.. i think it depends on the phone or something. After i use that cache wipe zip, the phone is STUCK on goodbye. Does not reboot correctly after that.. i have to battery pull. If your phone hangs "normal" time length, put it in your pocket meanwhile.. who cares, **** happens.. no dev is perfect. Thats why theres so many updates all around..

try remove everything from yr phone, sd, sim, battery, use different ones if possible. format emmc etc..... am i being unclear？ nvm, recovering from a bad cold.
Sent from my SGH-T989

skyfolly said:
try remove everything from yr phone, sd, sim, battery, use different ones if possible. format emmc etc..... am i being unclear？ nvm, recovering from a bad cold.
Sent from my SGH-T989
Click to expand...
Click to collapse
probably the cold, because that has nothing to do with a cache wipe...

i mean the problem with reboots..... lol
Sent from my SGH-T989

noodles2224 said:
Bert, dont use that cache wipe again.. i think it depends on the phone or something. After i use that cache wipe zip, the phone is STUCK on goodbye. Does not reboot correctly after that.. i have to battery pull. If your phone hangs "normal" time length, put it in your pocket meanwhile.. who cares, **** happens.. no dev is perfect. Thats why theres so many updates all around..
Click to expand...
Click to collapse
Why are you pulling the battery? If for any reason the phone does get stuck all you have to do is hold down the power button for about 10 seconds for it to reboot. All you're gonna get pulling the battery so much is probably a broken back cover from removing it so much, only time you should pull the battery is if the phone isn't responding even to the power button or stuck in a boot loop where holding power til it reboots and then immediately holding down both volume rockers to get into recovery doesn't work.

lol nvm i was surfing on epic fail dot com.......
Sent from my SGH-T989

rastlin said:
I must be the only one with this issue when i use superwipe for some odd reason my phone will not boot unless i do a cwm recovery no matter what i do. i am not too sure why this happes, and btw i am stock...., but it does and i cannot figure it out i am scared to use it. The only other way i was able to get my phone to boot past the quick load up bar which it stops at about 90% for some odd reason is if i do a nandroid restore...any reason why this happens???
Click to expand...
Click to collapse
I'm surprise no one caught this but... Dude when you super wipe you're wiping everything! Of course your phone won't boot lol. You should cache wipe..
Sent from my SGH-T989 using xda app-developers app

[HELP] My GS3 hates customs kernels

Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin

You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'

dntesinfrno said:
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
Click to expand...
Click to collapse
Thanks man, will try your method and report back.

once you flashed your ROM(aokp) you need to reboot and let the phone fully boot into android... after that reboot to recovery and try flashing your Gapp + kernel
don't forget all the wiping and fixing permission for each steps
edit: wow this tab was open for a long time i guess. there was no other answer when i wrote this browsing through my opened tabs.

dingrn said:
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
Click to expand...
Click to collapse
Kevin my phone is exactly having the same problem did you come to a resolution

Especially on aosp roms it might help to flash the rom, let it boot once, then boot into recovery and flash kernel, wipe cache & dalvik, and fix permissions.
Also i've heard that some people will have alot of reboots before the kernel starts running smooth and stable. Or you could just have a bad phone that doesn't like to be tweaked. If i were you i'd take advantage of that warranty and try to get a replacement.

sorry for being a newbie....but what do you mean by fix permissions? =/

ohaai said:
sorry for being a newbie....but what do you mean by fix permissions? =/
Click to expand...
Click to collapse
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.

jefferson9 said:
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
Click to expand...
Click to collapse
ive tried so many different methods of flashing kernels and all of them result in huge problems with crashes and random reboots all methods posted earlier are a gigantic fail. Im returning this refurbished phone for another refurbished and will report back

droidfta said:
Kevin my phone is exactly having the same problem did you come to a resolution
Click to expand...
Click to collapse
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.

dingrn said:
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
Click to expand...
Click to collapse
hey had the same exact problem. Got a new phone under warranty cpu temps run lower and stable under current kt747 kernel I'll wait a few more days before underclocking but it's defiantly the phone you just got a weak cpu like I did

[Q] Boot Loop, Need help!

i have been running the kiss kernel for a while now, last night i tried to flash the hellboy kernel and retern to my pacman rom. but it still boots, i have cleared all my caches formated everything but my sd card, have tried flashing all kiss kernels and multipul hellboy kernels, but never gets passed the boot screen.. any ideas?

i managed to get it to the android is upgrading.. starting apps thing, but it gets stuck there.

Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?

lilrob1213 said:
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
Click to expand...
Click to collapse
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement

JARR3DF15CH3R said:
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
Click to expand...
Click to collapse
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?

lilrob1213 said:
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
Click to expand...
Click to collapse
yeah i installed it after, pacman http://forum.xda-developers.com/showthread.php?t=1948770&page=12
im with telus gsm. the rom was working fine, but i went to change the kernel to hellboy cause i herd it was a bit better and now im in this bootloop

also not running the newest version of that rom, i am running v15a

Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?

lilrob1213 said:
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
Click to expand...
Click to collapse
thanks anyways, ill be sure to give that a try:silly:

Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!

bahubali67 said:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
Click to expand...
Click to collapse
yeah i always wait a little while, i have chosen latest kernel, has not made a difference, i have gotten better results using an older one of the titanium kiss, hellboy doesnt seem to work with my phone for some reason

Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.

mihirengg19 said:
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
Click to expand...
Click to collapse
i am using the all in one tool kit to flash my kernel, yes i am in fastboot, a window pops up runs through code and my phone reboots, i have changed the kernel on it before, but for some reason this time it wont boot properly at all, the phone is currently at the " android is upgrading" screen, it was the starting apps box with the spinning circle

if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.

1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
thank you so much 1ceb0x! my phone has been in this bootloop for an entire 24 hours,

1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel:
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!

chikuera said:
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
Click to expand...
Click to collapse
Thats the old version.... See the changelog code and flash dat in future..... Right now.... Here u go....
http://www.mediafire.com/?waggdha1ir1lxz0

Stuck at HTC welcome screen after flashing kernel

Hey,
I used the 18.5 version of Shpongle with the 14.5 version of HELLBOY kernel until today.
I tried to update only the kernel today to the latest HELLBOY (21.5), so what I did I booted into recovery (TWRP), erased only cache and dalvik, and flash the new version of the kernel using cmd, with these two commands:
Code:
Fastboot flash boot boot.img
fastboot reboot
After my One V rebooted, it got stuck on the HTC welcome screen (with the red development purposes warning) and I can't get out of it, all I can do is reboot then it comes back to that screen.
What did I do wrong? Can I fix that somehow? I can't seem to go back to recovery so it feels lost...
Thank you for any help.

Might be a bad flash. Wipe everything and reflash, then try to reboot.

MameTozhio said:
Might be a bad flash. Wipe everything and reflash, then try to reboot.
Click to expand...
Click to collapse
How do I wipe everything? My PC doesn't recognize the SD and I can't go to recovery...

amiregelz said:
How do I wipe everything? My PC doesn't recognize the SD and I can't go to recovery...
Click to expand...
Click to collapse
Turn off the phone and quickly press volume down and power on to try to get into bootloader otherwise it will turn itself back on (happened to me before when I got a bad flash). Try to get into recovery from there.

MameTozhio said:
Turn off the phone and quickly press volume down and power on to try to get into bootloader otherwise it will turn itself back on (happened to me before when I got a bad flash). Try to get into recovery from there.
Click to expand...
Click to collapse
Thank you! that's what I was looking for. I was hopeless. Thanks again!
Is there something wrong with what I did to update the kernel? I kept the ROM and just deleted the cache and dalvik and then flashed the new kernel. I just don't want to lose all the data so I'm hoping to fix it without wiping everything.

amiregelz said:
Thank you! that's what I was looking for. I was hopeless. Thanks again!
Is there something wrong with what I did to update the kernel? I kept the ROM and just deleted the cache and dalvik and then flashed the new kernel. I just don't want to lose all the data so I'm hoping to fix it without wiping everything.
Click to expand...
Click to collapse
No there was nothing wrong with what you did to update the kernel, you were just unlucky and got a bad flash. If it still gets stuck try reflashing the ROM, without wiping data.

MameTozhio said:
No there was nothing wrong with what you did to update the kernel, you were just unlucky and got a bad flash. If it still gets stuck try reflashing the ROM, without wiping data.
Click to expand...
Click to collapse
Thank you for your help, it was the wrong HELLBOY version - the HELLBOY kernel MediaFire library is very confusing. I picked the CM9 kernel instead of the 42 one. Now everything's working

amiregelz said:
Thank you for your help, it was the wrong HELLBOY version - the HELLBOY kernel MediaFire library is very confusing. I picked the CM9 kernel instead of the 42 one. Now everything's working
Click to expand...
Click to collapse
That's good , and you're welcome btw!

Help
How can i flash kernel under Ubuntu 13.04???