Database Info

[Q] Why can I not install a new Kernel?

Hi All
Finally plucked up the courage to register and ask a question after lurking for the good part of 2 years.
I've an i9020A and have flashed CyanogenMod 9 v4.0.3 v1.0 which is great, however I wanted to try Steve Garon's kernel which just wont take.
I reboot into Recovery, wipe Dalvik Cache a couple of times, install Steve's kernel which apparently flashes no problem.
I reboot and get the optimising Android applications screen then check my kernel under settings.
It is still the original KalimochoAz kernel and I cannot turn on my wireless.
Now this has happened previously when trying to also update my kernel under CDTDroid's AndroidMe 1.2 which I could only fix by restoring back to 1.1.
Any idea on what may be wrong here guys?
Appreciation in advance.
Lally

Have you tried just flashing again? A bad flash often results in wifi not working and may be the cause of the about page showing the old kernel. Remember to wipe dalvik cache again, too.

Thanks for the reply Harbb, do you mean a re flash of the Kernel or ROM? If Kernel then yeah I have done, same scenario. I'll also try a re download of the Kernel to see if that improves anything but this is much akin to me trying to update from Speedy3 to Speedy4 under AndroidMe 1.2 which was unsuccessful.

Just the kernel, as you've already tried. Just remember to do a NANDroid backup (CWM --> backup & restore --> backup) when you have a stable, working ROM. Can save you alot of trouble if you don't have a relatively recent one.
Also, are you using CWM 5.0.2.0? And could it be that your phone isn't particularly happy about the 1100mhz OC with Steve Garon's kernel?

I'd suggest updating CWM recovery to the latest version.
Sent from my Nexus S using xda premium

Cheers for the help guys.
Yes, using 5.0.2.0, but something is not right cause I just tried to flash CWR again from within Rom Manager (4.8.1.3) and it gets to around 95% and the app gives 'Rom Manager is not responding.
Looks like I'll have to try a complete wipe and reflash.
Will report back the results.

Forget rom manager all together.
Download the recovery you want to use.
Flash it via fastboot
flash kernel.

I'd do what albundy said - flash a new recovery through fastboot and make sure the bootloader is unlocked (vol. up + power --> bootloader: unlocked)

Ok, downloaded CM9 1.1, redownloaded Steves kernel, reinstalled recovery from fastboot.
Wiped and formatted everything twice then installed from scratch.
So far everything is good, still getting errors on Superuser, but installing again via recovery seems to fix that issue.
Cheers chaps.

Good to know Lally, happy you got it sorted out.

Cheers Harbb, the test will be when I want to change the kernel again I suppose, one complete wipe and install a day is enough

[Q] TWRP Q&A

Dont want to muck up the CM7 thread and no thread was started.
FB Im wondering if twrp is fully wiping when you run the wipe option. I used the kj6 heimdall one-click to get back from a bad flash. However once I finally was able to get everything set back up I had restored some apps through Titanium Backup, but only app no data. Amazon app store was one and I had to delete the backup and uninstall the app, reboot clear cache and then re-install it to get it to work. The theme chooser app was fcing on me until I did the same thing.
After I did this I applied a theme apk that borked me. I was stuck on the team acid logo. No boot loop just stuck. I then one clicked to kj6 again, then used antonx kernel one click. Made a new backup of my efs, wiped everything including boot img. Flashed the twrpcm7 zip and followed the directions to finish.
I know anything is possible but is it likely that twrp is seeing something not wiped in the bml to mtd conversion and its causing conflicts?
If your not comfortable with the possibility of bricking your phone do not follow my steps and format everything. Formatting boot has the possibility to brick your device.

Hmm, well /data isn't getting wiped in R11. Bryan submitted a patch for updater.sh that should take care of this though I haven't tested it. I haven't tested a BML->MTD (cm7-twrp) flash though, but I'll have to look into it in the next few days. I'm running a rom build right now, so I'll probably test that out tonight.

I didn't wipe anything, I just flashed the twrp boot.img. I am running Team Kick Asses MIUI Revenge (MTD). After I flashed and the phone booted, wifi would not turn on, and it said error underneath the button. Pulled a logcat but all it said was wifi failed to initialize. Is that error due to the fact I didn't wipe anything or factory reset/fix perms?
Either way, it is super sweet recovery!

Max says its a driver issue. Ill find the post and link it.
m4xm4n said:
The reason wifi didn't work is because the wifi module needed to be from the same kernel build. I'm not sure how FB built the two builds, so I don't know if he included a module from a different kernel build or not.
Try the R11B with TWRP and then install R11(not B) with inject TWRP enabled.
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse

Now that you have twrp make a cwm zip for the r11 kernel, flash it via twrp and leave the "inject twrp" option enabled. You should get working wifi and twrp
Sent from my SGH-T959V

Like I said on cm thread the wifi module is different from the one Max used on his new boot.img which is why twrp and the new boot.img doesn't work with the current miui build ...the first release of dianxin os had the new boot.img fb sent me and that was the wifi issue.
sent from my batcave

I flashed miui on with twrp doing a wipe firs and it installed miui fine, with wifi and everything seems to be fully functional. Just to be safe I wanted to test out twrp on miui, however the only way I could get to it was volume up+down+ power. But that loads it right up, and I flashed a few different modems to see which gave me the best signal, and it worked each time. Btw, nice work fb twrp is great.
Sent from my SGH-T959V using xda premium

Which modems did you flash? If the modem flash DID work you should be able to go into Settings > About Phone and check under baseband version. I'm not sure if that's the exact menu on MIUI but there should be something very similar.

I just flashed kg4 and that's what it says under baseband version, I flashed kd1 earlier and that's what it said before I just flashed kg4. Just to make sure it was working. I think it says t959vuvkg4 or something to that effect, it definately just changed though from kd1
Sent from my SGH-T959V using xda premium

Hey guys just a progress report on this. I've been messing with a twrp injection cwm zip all evening. After some discussion with bhundven, the way we're going to go about this is to NOT include twrp by default in cm7. It's been really hard to get a working copy compiled and included with cm7 and if we can't do this automatically there's no point to doing it at all.
The CWM zip will (hopefully) allow us to give you the option of using TWRP even if you're using CWM at the moment. The benefits are the following:
You won't need to mess around with kernel features that don't work (wifi was broken, ffc was broken)
You only really need to inject twrp once via CWM since twrp comes with an inject option before you flash a CM7 update.
It'll make it easier on us since we'll have less releases and thus have to provide less support.
At the moment I'm trying to have something for you guys tonight, but the chances are slim for that happening.

FB
For some reason TWRP can't Flash Zip file like Mtd modem kd1. I try to make a nandroid bk and didn't work. Also I try to save error logs on sd card didn't work.
My english is not the best, sorry
Sent from my SGH-T959V using xda premium

Please post the logs here.
What errors did you get when trying to flash the kd1 modem or make the nandroid backup? I've tried making and restoring a nandroid backup using CM7 R11 with twrp injected by the zip and it's worked fine for me.
What rom/kernel combination are you using?

Error: Unable to open zip file
I try nandroid backup again and for some reason did work but wasn't working.
Am using CM7 R11B & CWM TWRP
Everyting else is working good thanks!!!!
Sent from my SGH-T959V using xda premium

NS 9020t - problem flashing marmite_v4.4 kernel to miui 2.9.7

I'm having a problem flashing marmite 4.4 to the newest miui build (2.9.7).
Basically in cwm recovery and flashed the kernel.
Will say "ununderstandable message 3" and "lid is licked"
Reboot the device and it will get stuck on the miui boot screen.
Tried installing both the "stock OTA" and "All other ROM" version of marmite.
Same message comes up.
Already tried performing a full wipe (actual full restore, format system, format boot), reload the ROM.
Tried wipe cache and dalvic (even though it is not needed)
Just wondering if there is something incompatible or not.
I was able to flash air kernel without issues.
I haven't tried an older version of marmite yet, but will try later.
I'm not blaming marmite, it could be miui as well, or it could be just me.
I'm certain I'm flashing correctly.
I read bedalus' marmite post and saw 2 others with this issue (not same version of kernel or ROM).
The suggestion was that they didn't use the correct kernel for ROM.
I would assume miui would not be categorized as "stock OTA", so I tried "all other ROM" version first"
Am I doing something wrong?

There is a new version 4.5 the message you get I believe is like a joke. It does show however that the installation was successful.
Never experienced boot loops flashing his kernels.
Sent from my Nexus S

Actually, I downloaded that one just now to try and same issue.
It will just stall at the miui (ROM) boot screen.
I am trying some other stuff right now as well.
Really want to use this kernel. :good:
I'll report back later.
Thanks for the help.

Good luck. His kernel offers great speed and stability!
Sent from my Nexus S

For marmite 4.5, did a full wipe again, even formatted the SD partition.
So flashed miui 2.9.7.
Booted to the ROM.
Made sure things seem normal in the ROM.
Restarted just to be sure.
Boot back to recovery.
Flashed marmite 4.5
And it is stuck on the miui loading screen again.
Only thing I haven't tried this time is to fix permissions. (didn't wipe cache or dalvic either)
I'll try it again. :laugh:

Since I formatted the SD partition, it should rule out that it was something on the SD card right?
It's time consuming to copy things back to the NS.
I'll try an older version of marmite afterwards and then an older version of miui.
It should tell me what is causing the lock up by then. I think. :silly:
.... yes I have a lot of time ....

I forgot to mention one thing.
I'm flashing the official Chinese version of miui 2.9.7.
Wonder if that's the cause.
I guess I will download the US or UK version to try as well.

Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S

kwibis said:
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
Click to expand...
Click to collapse
Took some time to test, but sort of found my answer.
It's the official Chinese miui that's causing the issue.
Well at least some component in the ROM.
I tested with the MIUI UK (miuiandroid) version 2.9.7 and it installed like a charm.
Before flashing the UK version, I tested with earlier versions of marmite (4.3 and 3.5) on the Chinese 2.9.7.
All failed at the ROM boot screen.
I should check with the miuiandroid team and see what they changed that made it different.
When I was testing I did a full wipe, installed ROM, booted ROM, boot to recovery and flashed the kernel.
I didn't even wipe cache or dalvic (which is not needed anyways).
I had to do a full wipe because the ROM just wouldn't boot back up afterwards.
I'm tempted to test with an earlier version of the official Chinese miui and see if it makes any difference.
... too much time and/or no life ... :laugh:

Lol, well it's good you found your answer So its not a waste lf time as you learn from this
Sent from my Nexus S

If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2

Articudos said:
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Not sure what the boot.img type is, but I'll look it up. Thanks.
I posted on miuiandroid forums and someone replied saying that the Chinese version is odexed and not busyboxed.
UK and US version is definitely deodexed, I downloaded them and checked. I haven't found out how to check busybox.
I have a few choices.
1. I can use the UK or US version, since I was able to flash marmite on them... easy way out.
2. Find out how to deodex the ROM and, I guess, how to add busybox (?)... I get to learn more stuff.
3. Use a way faster ROM (eg. Paranoid Android - great ROM by the way!) and flash marmite on it as well... but really want to use miui again.
Thanks guys for your help though. Really appreciate the information. :good:

Glad you found a solution

Cannot flash new kernel

Hi xda. I just installed (flashed) cyanogenmod 9 on my nexus s, after getting bored with the stock kernel so I flashed trinity ics kernel. Now when I try and flash a new kernel nothing changes, cwm recovery said it flashed successfully. The procedure I did when I installed it was:
1) install zip from SD card
2) choose zip
3) yes
4) reboot system
Is there anything I did wrong? Do i need to clean the cache and dalvik cache?
Sent from my Nexus S using xda premium

How are confirming that it did not flash?

Clockwork recovery said it was successfully installed. Also the version of the kernels are right for my rom (ics)
Sent from my Nexus S using xda premium

You missed understood me.
How are you checking/confirming that the kernels you flashed after trinity are not actually flashing/ booting/being used or how ever you want to phrase it?

cm changed their ramdisk(again). so now custom kernels without cm ramdisk wont boot cm. as always, cm likes to "break" things. complain to cm. i recommend other non cm based roms, like rasbean jelly. it doesnt have as much junk included and is a faster/smoother experience than cm. many kernel developers arent willing to cater to cm anymore because of these changes they constantly make. enough is enough.

Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.

albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
maybe so, bit i dont see a mention of a boot animation
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
ah, ok. i reread the op very slowly.
op, did you check the kernel version in your about phone? other kernels wont get rid of the boot animation unless they offer a boot animation or include a script to delete it.

Yeah. But he is saying he doesn't see a change. Implying the phone boots up as it did prior.
He is also on cm9 , not the new cm10 that botched things up again.
That is why I am trying to get him to confirm how he is checking if the kernel changed. Almost certain its the op just seeing the boot animation and thinking that it didn't change due to that.
Op. Go to settings /about phone and look at kernel version. Flash a different kernel again. Check again.

I am confirming that it did not flash by going to settings and then about phone. In kernel it still says Trinity kernel rather that matrix kernel or air kernel (2 roms I've tried flashing).
Sent from my Nexus S using xda premium

Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one

[/QUOTE]
albundy2010 said:
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
Click to expand...
Click to collapse
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.

I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.

I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.[/QUOTE]
albundy2010 said:
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
Click to expand...
Click to collapse
Ok ll try that

You can flash my cm compatible kernel.

Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2

p1gp3n said:
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I gave up and flash a new rom and kernel thanks for the help.

[Q] Can't Flash ANYTHING!!!!

Every time I try to flash something my tablet fails, and I have to revert back my backup. It doesn't matter if I download on PC or from the tablet itself. HELP!!!!
Galaxy Tab 2 7.0

Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,

bill_in_mtl said:
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
Click to expand...
Click to collapse
I'm running stock 4.0.4, Rooted, Clockworkmod recovery. I have tried to flash several different roms. Romswell, AOKP, CM nightlies thru ROM manager. all of them fail in recovery. I flash stuff all the time on my SIII so I'm not really a Noob to flashing and what not, but I can't figure this one out. Thanks for any help.

What are you using for recovery? When you say failed what is the error message? Sounds like you should prolly reflash a current official recovery. If by failing you mean it hangs on first boot then your not wiping system before flashing. Factory reset and wipe system before you flash.

Are you by chance running any scripts for sd card swap, etc ?
I am running this script, http://forum.xda-developers.com/showthread.php?t=1961097 which swaps my 32GB external sd for the internal sd, which runs great - no issues, except with rom manager and flashing from recovery.
I have to go back and de-activate the script, reboot, and then dowload - or transfer file from PC, and it flashes without issue
Otherwise, I have had no flashing issues of any kind - using CWM 6.0.1.5 for the p3113
Good luck,
Bill