yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] eyeballer:
This is actually a specific issue with Savaged-Zen kernels only, not Kernel Manager. Savaged-Zen are aware of it, and were supposed to be working on a fix, may want to check with them as to status.
[EVO 4G Android Development] mrfyisms:
Went into recovery and kept looping (like several others were reporting) and had to flash a nandroid backup. Was trying to flash Tiamat_evo. What kernel would you recommend for best battery life? My workday is 10 hours minimum and i usually listen to music all day.
[EVO 4G Android Development] mrfyisms:
AHA I'm using this too so it's worth looking into the possibility...
[EVO 4G Android Development] mrfyisms:
This person also having same issue. Are you using the SD card speed fix?
[EVO 4G Android Development] EndlessDissent:
OK. I was finally able to use this to download a Tiamat update. It worked, but not flawlessly, on the latest MIUI update.

First thing: Well, I was a dumbass and forgot to connect to any sort of data network. When I started the app, it threw a null pointer exception, which confused me, because I didn't realize I wasn't connected to a network. I thought something happened with the app until I tried opening the market to reinstall it. Basically, what I'm asking is, can you put in a notification that a network connection is unavailable instead of throwing an exception? That way, dumbasses like me don't get confused and think there's something wrong with your app.

Second: The first time I chose to download and flash the kernel, the Downloading Kernel notification popped up, but it hung at 0% for several minutes. I closed and reopened the app, and it worked flawlessly. My concern is, some people might not give the app a second chance. If I find a way to duplicate this, I'll grab a logcat. I doubt many people will be seeing this bug, though.

Overall, this is a great app. It just needs to be slightly idiot-proofed for the forgetful types. I will be buying the paid version tonight. Thank you very much, Shinzul.
[EVO 4G Android Development] Mr.Shroom:
I have had the second issue as well, but was unable to do it twice. it doesn't seem to be a big issue. Thank you.
[EVO 4G Android Development] mrfyisms:
Wow, I thought I read that you have to submit your kernels for them to be included in the app. People were complaining because their favorite kernels weren't included and he said, "tell the dev to submit it." Can't we all just get along.
[EVO 4G Android Development] Shinzul:
Exactly... users were complaining that there weren't kernels available, so I posted 2 so that users could have some use for their particular device.

I don't understand what the big deal is tbh.
[EVO 4G Android Development] algirnavi451:
I tried running this App and I got an issue.

I was running the CM40 nightly with the stock kernel and tried flashing the Tiamat Kernel. After downloading and trying to install I got a message saying not enough memory I should restart and try again. After I restarted I ended up getting a bootloader screen. Restarted again, same screen. Went into recovery and rebooted from there nothing. Recovery again and flashed SZ 1.1.0 Kernel that i had on my SD card and that didnt work, bootloader again...Trying to reinstall CM7 zip that I have and that seems to have fixed the problem.

Thoughts? Anybody else see this?

Edit: nvm after updating to 1.1.0 of the app, the problem seems to be fixed
[EVO 4G Android Development] mrfyisms:
Yes we were all having the same problem before...

Well I tried again after update and it installed but market kept force closing while it was restoring apps then com.android.phone and .system kept force closing and I had to restore from recovery again. Is this an app issue or a kernel issue because the kernel forum thread has been pretty active lately too.
[EVO 4G Android Development] ModXMV:
This happens to me and I have to Nandroid back. I am still having the issues after the newest update.
[EVO 4G Android Development] xHausx:
GJ on this one

http://lifehacker.com/#!5793257/kernel-manager-makes-installing-custom-android-kernels-a-snap
[EVO 4G Android Development] cLOUDFAn:
same thing happened to me just now

was trying to flash sz 2.0 (with kernel manager 1.1.1)

had to reflash cm7
[EVO 4G Android Development] Semantics:
First off, I love the work that your team does. I do see what the issue would be for that dev who had his kernels uploaded to the app before he signed off on them. If you are posting to Devs to upload their kernel, and they decide not to, then just upload them anyway, why even ask in the first place? I understand that people want a varied selection of kernels, and they get pissed when they pay 4 bucks and can't find a kernel to use, but again, why even bother asking Devs to upload the kernels if their decisions are not going to be respected if they want to hold off and they get uploaded anyway?
[EVO 4G Android Development] Shinzul:
Well in this particular case, no one said not to do anything. I fully respect the wishes of a dev who doesn't want his kernel included.
[EVO 4G Android Development] shiftwig113:
Just Curious how much testing was done this....

Because this f***d up my phone.....yes i know i'm a aware that i'm responsible i just dont wan't to see the same happen to someone else.

As soon as it was done flashing my phone went straight into bootloader...never seen that before...

I made my fair share of mistakes with flashing zips when i was still new to the android scene, but i never had something stop and kick me into the bootloader that only had 4 options

Reboot Bootloader

Reboot

Power off

FASTBOOT

All 3 of those options took me back to the same thing...

it wouldn't even scan the PC36IMG that i put....

However FASTBOOT for whatever reason worked after a couple of battery pulls

Lucky for me i Have ENG HBOOT .76 and re-flashed amon-RA Recovery and sprint lovers IMG36 zip.

and i just glanced at my phone right now and MYN's RLS5 has just finished and booted.

Next step Erasing Kernel Manager.

About my phone

HW003. HBOOT .76. Radio 2.15.00.11.19. and PRI 1.77....

I advise anyone who has the same/very similar setup as my phone does to take extra precaution before you have Kernel Manager flash anything.

BTW before everyone gets uptight and starts ****ting themselves, I am not accusing team win or pointing the finger in any way. remember this was my experience, I'm betting most of you had a better experience
[EVO 4G Android Development] Shinzul:
Let me apologize for the issue! Do note that you can always just re-flash your ROM from the recovery menu to fix this issue.

That said, I have a new version coming out tonight that (REALLY hoping) completely eliminates this problem.

Kernel Manager has only been available for 6 days... growing pains! :)
[EVO 4G Android Development] sanjsrik:
Shinzul, I have to say, your responsiveness and ability to take criticism is awesome. Thank you for the great application.
[EVO 4G Android Development] shiftwig113:
maybe i had an isolated case but i couldn't access my recovery...just the bootloader....and it didn't even have recovery as an option.

But thanks.
[EVO 4G Android Development] algirnavi451:
Yeah this happened to me twice. For me I chose bootloader and then into reboot recovery. Then re-flashed ROM
[EVO 4G Android Development] mallman:
same thing happened to me. flashing the rom again got it booting again
[EVO 4G Android Development] nerozehl:
I love the program concept and I purchased the Paid version before I even tried the Lite (caveat emptor!). I was not, however, disappointed in the slighted. I easily found the kernel I wanted and it downloaded very nicely and flashed so quickly I didn't even notice it was done until I heard the boot animation. Kudos for you hard work.

I did read through the thread, and for the life of me can't seem to find this out: what is the difference, aside from the donation, between the paid and the lite version, i.e. any extra features? If not, that's ok, but I didn't see in the App Market any differences.
[EVO 4G Android Development] EndlessDissent:
You can filter kernels by features in the paid version.
[EVO 4G Android Development] Brandito:
I'm having the same problem getting booted into the bootloader.

except i'm using stock sense :/

i flashed the stock kernel because i've been having trouble with net's kernels (or at least that's what i think i've narrowed it down to) and now i do believe i'm mostly screwed.

my last nandroid is pretty old, i do have very recent titanium backups though.

any way out of this without nandroiding? i guess i could try flashing the stock sense rom for my evo, after i find it...

update: i did an advanced restore with CWM and only restored boot from the list and the phone booted. however now my wifi and 4g don't work. i get "error" for the status of wifi.
[EVO 4G Android Development] Shinzul:
Re-flash a normal kernel through recovery.

Can you try the latest market release of Kernel Manager and see if you still have the bootloader problem?
[EVO 4G Android Development] Brandito:
tried that actually, kept rebooting to the bootloader.

just restored a month old nandroid backup and all is well again.

apparently something got messed up in the bootloader? really not looking forward to restoring everything to the way i had it :/
[EVO 4G Android Development] barnacles10:
Yeah bro. Borkin my system too. Updated tonight as it prompted me in the market. Flashed a kernel. Bootloader. Wiping caches, flashing the kernel through recovery, none of that works.
[EVO 4G Android Development] Shinzul:
Blargh.

You just have to re-flash a rom through recovery and it'll be back up and running.

What ROM were you running?

What kernel were you running?

What revision phone do you have?
[EVO 4G Android Development] barnacles10:
Oh yeah, no worries.
[EVO 4G Android Development] Brandito:
what about those of us not running custom roms?

edit: so far this is what i did and it mostly has me back to normal, so far as i can tell...

did a full nandroid backup of my borked configuration, then did a full restore to my most recent nandroid before the borkage, THEN restored the data from the advanced restore option in CWM using the borked nandroid backup. i THINK everything is good.

i'd say YMMV though, those with custom roms need not apply it appears.
[EVO 4G Android Development] Shinzul:
You can flash the stock rooted rom. Basically it just replaces your boot image with the boot.img from the rom.
[EVO 4G Android Development] Brandito:
i was going to do that but the only image i found for the evo said it would wipe the phone in the process.

perhaps i'll flash back to my borked backup and see if that will somehow work? is there anyway to just flash the boot.img? or replace it i suppose?

right now i'm back to what i assume is 99% of where i was before the mishap. doing ba nand backup right now and going to try your app again.

i think it's a great app and am eager to have it working without any show stopping bugs!

should take some of the mundane aspects of kernel flashing out of the process.

update: tried your app again, so far so good, got passed the bootloader at least!
[EVO 4G Android Development] aka.karasawa:
Just want to give you a heads up that it finally works with warm z. Bought the pro version to show support. Thanks for being on top of it. Great support!
[EVO 4G Android Development] Biofall:
Having same problem.

CM nightly 40

Stock cm kernel going to savage

003

Flashing a kernel through recovery still gets me into bootloader screen, and when I try to flash a ROM I keep getting:

assert failed: write_raw_image("/tmp/boot.img"."boot)

E:Error in /sdcard 1 ROMs/cm_supersonic_full-40.zip

(status 7)

I don't want to nandroid..
[EVO 4G Android Development] deepred86:
Hi, just saw app thread i just sent you a mail reporting this:

When i start a download and the screen goes landscape or visa versa it forcecloses // When download finishes it says: error flashing kernel or smth w/o even rebooting to fastboot / recovery.

but as far as i can see .. i'm not the only one :)
[EVO 4G Android Development] TheDave1022:
Tried to flash on CM N41. Downloaded and extracted Tiamat from Kernel Manager and when trying to install I got an error for not enough disk space and to reboot.

On reboot, it booted into bootloader. I tried to reboot and just went back in. Tried to manually install Tiamat as I had on my SD card, same result.

I had to reflash CM7 N41 to get back into OS.
[EVO 4G Android Development] barnacles10:
At the time? Stock 3.70 sense. Rooted. Flashing stock htc kernel. Hardware 3
[EVO 4G Android Development] DonSolo:
To me this is better then Rom manager. Rom manager sometimes doesnt flash correctly. Kernel Manager flashes correctly errtime lol.
[EVO 4G Android Development] DonSolo:
What recovery are you using? Using Ra and never had a problem. When you flash from rom to rom, you have to install a fresh copy of KM. Yes yes!
[EVO 4G Android Development] barnacles10:
I don't think his issue pertains to not installing the kernel manger. He said himself he downloaded a kernel through it =P
[EVO 4G Android Development] ModXMV:
Feature suggestion:

Allow me to filter kernels based on flavor of Android. AOSP vs Sense.

Also the newest update fixed my flashing issue. Thanks Shinzul!
[EVO 4G Android Development] MitchRapp:
I get a java.nullpoint etc... exception error on the screen when starting. When trying to flash kernel zip from SD, I get a force close.

Moto XOOM Tiamat 1.1.6 (trying to flash 1.3.1)
[EVO 4G Android Development] Shinzul:
It actually flashed the kernel from SD card - reboot. I'm pushing a fix for the force close to the market now.
[EVO 4G Android Development] Shinzul:
I posted the official CyanogenMod kernel in Kernel Manager!

So if there aren't any kernel devs who have uploaded their kernels to KM yet, you can at least see the flashing process and if it's something you'd use .

Enjoy!
[EVO 4G Android Development] sxayarath:
If you get stuck in bootloader without the option of recovery, reboot while holding the volume button down. This worked for me. You can reflash a rom at this point.
[EVO 4G Android Development] jefbal99:
Trying to flash back to official CM kernel from tiamat and I keep getting an unknown error after the download. I check the SD card and there is nothing in kernel-manager\cyanogen. Any logs or details i can share to get this working?

Running CM7 N41, updated to the latest KM
[EVO 4G Android Development] Shinzul:
Delete your kernel-manager folder from your SD card and try again.
[EVO 4G Android Development] MCLFLN:
bootloader

Stuck in bootloader....

Running Mik 4.61

Amon RA 2.3

Was flashing latest Netarchy kernel.
[EVO 4G Android Development] jefbal99:
It ended up working after a couple of reboots and doing a backup. It almost seems like the KM folder on the sdcard was not writable
[EVO 4G Android Development] Simian Drugs:
I'm buying Pro tomorrow.
[EVO 4G Android Development] mrfyisms:
I tried this just for s&g and it worked after that. Folder contained a previous failed download. Only found one issue so far and pretty sure it needs to go to Tiamat thread. If I try to change any CPU settings it freezes and reboots phone.
[EVO 4G Android Development] Shinzul:
The previous failed downloaded bug has been fixed. Shouldn't fail to flash after downloading with market version 1.1.3.
[EVO 4G Android Development] detcup4evr:
Same thing here, I am running stock 3.70 with latest radio and driver, had to nandroid to week old nandroid, I then flashed the kernel manually from the directory.

worked great on my coworkers cm 7 but not so good on my evo

Sent from my Evo using the XDA app
[EVO 4G Android Development] Funkmon:
Got stuck in the bootloader like most other people. Evo hardware 4, flashing SZ CFS kernel from CM7 stable.

Fat fingered and did a full wipe accidentally. BAH. *restore*
[EVO 4G Android Development] lakers1624:
I'm trying to flash a tiamat SBC kernel and am getting the error unable to create new boot image.

I'm on cm7 with savage Zen kernel and hardware 002.
[EVO 4G Android Development] alaman68:
first use today installing tiamat 3.3.7 sbc on salvagemod nightly 16 with amon 2.3 and it was perfect. faster than the usual wipe method
[EVO 4G Android Development] Shinzul:
There is an error when you try to flash something if you are currently running a savage zen kernel. The savage zen developers need to fix it.
[EVO 4G Android Development] mmegalodon:
Upgraded to latest Tiamat (3.3.8) and worked beautifully. Love the app.

:D
[EVO 4G Android Development] reverepats:
+1

10char
[EVO 4G Android Development] sparkyryan:
Thanx shinzul for your excellent support, just to let you know km is now working perfectly with new cm release 7.0.2
[EVO 4G Android Development] Smurph82:
Don't know if it has been asked in the thread already but is there anyway to backup your current kernel before you flash the new one. That way you could roll back to your old kernel easily. Great app and yes I bought the pro version.
[EVO 4G Android Development] mmegalodon:
You could nandroid JIC.
[EVO 4G Android Development] eyeballer:
This is slated to be a Pro feature at some point soon(tm).
[EVO 4G Android Development] mmegalodon:
Niice, glad to hear! :)
[EVO 4G Android Development] sparkyryan:
Keep you old kernel zip on your sd card and it's a breeze to re-flash it through recovery or as has been suggested back up using something like clockwork mod.
[EVO 4G Android Development] rstuckmaier:
Bug report:

Flashed Tiamat Kernel through app

Flashed CM7.0.2 through recovery

After booted up (check for stability) went to re-flash Tiamat and app says it is already installed.
[EVO 4G Android Development] ereinhart:
Yep, same thing happened to me today

Sent from my PC36100
[EVO 4G Android Development] eyeballer:
Yeah, it's a bug. Go to manage applications and clear data for kernel manager, then you can re-flash tiamat.
[EVO 4G Android Development] rstuckmaier:
I just flashed CM kernel then Tiamat again, just wanted to point it out.
[EVO 4G Android Development] Smurph82:
Yes I know that but it would just be faster to flash your backup vs flashing the whole nand. I always do a nandroid backup before I flash something.
[EVO 4G Android Development] mmegalodon:
You also have your downloaded kernels stored in the Kernel Manager folder, so with that and the nand options - and until it's added, as mentioned, in the pro version - then that'll have to suffice. :)
[EVO 4G Android Development] RileyGrant:
This is in no way meant to insult TeamWin or their product as I realize everything I do is completely at my own risk, however, today when using kernel manager I selected the option to flash the latest tiamat (was running the latest MIUI). Tiamat downloaded and said flashing, but then threw the error, could not make new boot image, okay, ya thats fine and all, so I tried again. This time it flashes and says, not enough room on disk or whatever. So out of frustration I boot into recovery and flash it manually. I hit reboot and bam, it throws me into the bootloader, fastboot to be more accurate. Currently flashing something else. Hope I didnt screw myself.

edit: booting up now, appears as if my boot partition was just corrupted or possibly kernel manager just failed to repack it after replacing the zimage.
[EVO 4G Android Development] jdguggs10:
Hey, fairly experienced user here looking for some brief direction...

I was flashing tiamats new kernel with the kernel manager when I was returned the 'not enough space' error... after rebooting my phone, i was sent straight to the bootloader, where i am trying to enter recovery and failing... (selecting recovery simply jumps me back to the hboot screen)

i'm assuming i have a broken recovery?
[EVO 4G Android Development] smw6180:
Pull the battery, hold volume down and power on when you put it back in....then try going to recovery from the bootloader. That's what did it for me. You didn't happen to have the sz kernel installed prior to the tiamat kernel did you?
[EVO 4G Android Development] jefbal99:
Same issue, I just did a flash from SD card and picked the Tiamat kernel from the KM folder.
[EVO 4G Android Development] cb7tuner93:
It doesn't wipe though, Maybe implement it later. I flashed a kernel through this and it broke some things because it didn't wipe.
[EVO 4G Android Development] :
Saw a post on Twitter from Shinzul saying that he believes that he found the out of space error.

"Shinzul

I finally pinpointed the 'out of disk space' BUG OF DOOM in #kernelmanager! Fix will be in KM v1.2.0!"

http://twitter.com/#!/shinzul
[EVO 4G Android Development] cb7tuner93:
Forgot to say, Thanks for this app, And a good trial and error begining.:cool:
[EVO 4G Android Development] Shinzul:
I'm sorry to hear this! :o

I just last night pinpointed the nasty bug causing this issue, and I will have a fix that at least prevents it from happening in version 1.2.0.
[EVO 4G Android Development] rstuckmaier:
Did you select to wipe from the menu? It doesn't wipe by default.
[EVO 4G Android Development] RileyGrant:
Thank you very much kind sir! Not a big deal as everything was smooth sailing after booting into recovery. Gotta love those nandroids. :D
[EVO 4G Android Development] Shinzul:
If anyone was having issues with the "out of disk space" bug, please try the latest market version (1.2.0). It fixes this issue!
[EVO 4G Android Development] jefbal99:
Suggestions for next version:

Filter for AOSP vs. Sense

Have the app query the kernel currently installed. I have tiamat from the previous KM release, but the new app is giving me the download/install button
[EVO 4G Android Development] Shinzul:
I am planning to add a new filter option for the android flavor (aosp/sense) for the next version.
[EVO 4G Android Development] martuseich:
Is there a list anywhere of who's kernels are available. I I suppose I could download & find out but would be nice to know what will be available.
[EVO 4G Android Development] rstuckmaier:
Shinzul, probably a known bug but just in case:

Currently running godmode kernel

I got the notification that an update was available (love that, btw)

I went to app to update and it says it's already installed and won't let me redownload.

Temporarily fixed by deleting kernelmanager folder on sd and wiping app data.
[EVO 4G Android Development] EndlessDissent:
Same here for the Tiamat update.

Also, I pressed the Installed button anyway to see if it was a display glitch, and it started flashing the kernel, but said Unknown Error. I pressed the Send Report button, so hopefully you get that.
[EVO 4G Android Development] Mr.Shroom:
Love the the app. Just out of curiosity is there any chance of keeping old version of the kernels on the severs(say just the one prior to current), so if one want to roll back a version they don't have download it online. I know its easy enough to download and flash, but i get lazy.

Oh are any of the teamwin dev. going to get a evo 3d?
[EVO 4G Android Development] jefbal99:
I had this issue as well, also had a problem regarding the boot.img being created. I had to boot into recovery and manaully flash to Godmode kernel. After that, Kernel Manager still thinks that tiamat 4.0 is installed, even though the highest version i ever had was 3.3.8...

I deleted my kernel manager folder and relaunched KM, still doesn't read that I have godmode installed, still listing tiamat 4
[EVO 4G Android Development] einsteins:
I just had this same thing happen to me while trying to upgrade to tiamat 4.0

I also sent report

Einsteins
[EVO 4G Android Development] jefbal99:
Getting lots of notifications for the Tiamat kernel that KM thinks I have installed even thought I switched to godmode
[EVO 4G Android Development] jefbal99:
Updated to the latest and greatest release, but still getting unable to create boot image errors. I sent a report.

Thanks for the notification options

Sent from my gginggerfied EVO
[EVO 4G Android Development] einsteins:
This worked for me also....thanks for the workaround!!

eins
[EVO 4G Android Development] jefbal99:
I've switched back to Amon_RA 2.3 recovery from CWM 3.0.0.5 and i'm no longer getting the Boot Image error