Database Info

[Q] [i9020-T] bootlooping after flashing Trinity UV11

I've been trying to get morfic's Trinity UV11 kernel to work with both the Cyanogenmod 7.1-RC1 as well as reddev1's AOSP kernel. I've flashed everything through Clockworkmod as well as cleared the Dalvik-cache with the provided zip in the thread. The issue that comes up is that the phone boots into the sign-in screen fine but later on the touch response stops working and then the phone restarts. Is there something wrong with the roms/process that I'm using or is it just that my phone cannot handle the undervoltage of the ROM? Any suggestions would be welcome!

boredomkillz said:
I've been trying to get morfic's Trinity UV11 kernel to work with both the Cyanogenmod 7.1-RC1 as well as reddev1's AOSP kernel. I've flashed everything through Clockworkmod as well as cleared the Dalvik-cache with the provided zip in the thread. The issue that comes up is that the phone boots into the sign-in screen fine but later on the touch response stops working and then the phone restarts. Is there something wrong with the roms/process that I'm using or is it just that my phone cannot handle the undervoltage of the ROM? Any suggestions would be welcome!
Click to expand...
Click to collapse
update your cm7, rc1 is old and outdated. try the latest cm nightly or cm kang. flash the latest, your gapps, and the kernel. in that order, then reboot.

simms22 said:
update your cm7, rc1 is old and outdated. try the latest cm nightly or cm kang. flash the latest, your gapps, and the kernel. in that order, then reboot.
Click to expand...
Click to collapse
Do you have any suggestions for stable AOSP roms that would work with this kernel? I'm trying to avoid the CM7 nightlies just because of any possible stability issues.

boredomkillz said:
Do you have any suggestions for stable AOSP roms that would work with this kernel? I'm trying to avoid the CM7 nightlies just because of any possible stability issues.
Click to expand...
Click to collapse
na.. i run either nightly or kang as a daily. should be much more stable than rc1 in any case

Hmm I've done what you suggested (flashing the latest nightly, then gapps, then kernel) and still no luck getting past the sign in screen. I've also used the "battery pull" method of rebooting the phone that was noted in the thread and still have the same situation.

boredomkillz said:
Hmm I've done what you suggested (flashing the latest nightly, then gapps, then kernel) and still no luck getting past the sign in screen. I've also used the "battery pull" method of rebooting the phone that was noted in the thread and still have the same situation.
Click to expand...
Click to collapse
does it work with any other rom/kernel?

simms22 said:
does it work with any other rom/kernel?
Click to expand...
Click to collapse
I've done a CM7/Netarchy(BFS) as well as reddev1's/Netarchy(BFS) combination which have both worked well without a hitch.

[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] boot image

hi im currently on the hfp 2.2 rom. i just flashed the new faux cm kernel coming from trinity xlp kernel. im still getting the trinity boot image, is this normal? can it be change back to stock boot image or a faux boot image? thx... im pretty new at this. i would appreciate any help

mormoney said:
hi im currently on the hfp 2.2 rom. i just flashed the new faux cm kernel coming from trinity xlp kernel. im still getting the trinity boot image, is this normal? can it be change back to stock boot image or a faux boot image? thx... im pretty new at this. i would appreciate any help
Click to expand...
Click to collapse
You can reflash hfp 2.2 and then install the new faux cm kernel...or...get the bootanimation.zip from hfp 2.2 (located under /system/media) and push it to the same directory...
Sent from my LG-P999 using Tapatalk 2

how about rom tool box, can i use this to get a new boot img? will it mess up anything on my phone cuz its running amazing rite now. or do u recommend re-flashing? i just want some thing other then the trinnity boot?

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

[Q] Can't get Komodo kernel to boot

For the past few days now, I've been attempting to flash $droyd$'s unofficial AOKP and thicklizard's komodo kernel, with no success. I've fastboot flashed before and/or after, wiped everything, run wipe scripts, chanted voodoo prayers, but nothing has worked. It either hangs on the boot animation, or occasionally makes it to the welcome screen before freezing and rebooting. I've been flashing ROM's on this thing for a while, and have been using unofficial cm10.1 so far as my daily driver. What the hell am I doing wrong?

Not sure but you may also still want to flash the kernel zip and then fastboot flash. There may be kernel modules that the zip needs to install for the kernel to work well on 10.1
Sent from my HTC One S using xda premium

AKToronto said:
Not sure but you may also still want to flash the kernel zip and then fastboot flash. There may be kernel modules that the zip needs to install for the kernel to work well on 10.1
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Still no dice unfortunately, I guess it's just not meant to be. CM10.1 is running great so I don't have much to complain about.

Ok I think I've pinpointed the problem-it has something to do OC kernels. I just flashed your new Canuck kernel with PACman and I'm getting the same freezing and rebooting issue. Is my phone overheating somehow?

trathiang said:
Ok I think I've pinpointed the problem-it has something to do OC kernels. I just flashed your new Canuck kernel with PACman and I'm getting the same freezing and rebooting issue. Is my phone overheating somehow?
Click to expand...
Click to collapse
Are these kernels being flashed with arioma installer... If you go to my aokp thread 2nd post you will see a tweaked 4.2 version-- it already has komodo modules installed and komodo is the boot.IMG inside the zip... Do this no skipseys---download that rom-- fastboot the boot.IMG in my zip---boot to recovery and wipe every thing INCLUDING SD CARD..x3---- now mount your phone to PC and copy and paste the ROM zip to your SD card..it will look weird cause it will be the only thing on there. ----- now install ROM then wipe only the caches after that--- hit reboot----system
And enjoy aokp with komodo kernel... Now to explain---every time you re flash that kernel you are stacking modules that is why you won't boot and also why you now need to do the spring cleaning wipe.... If you follow those steps exact no skipseys you will get it done---
Sent from my Nexus 7 using xda premium

Eureka! Did adb bugreport while it was booting to see what was going wrong, and I saw that there was something up with the voltages. Set the clock speed to minimum and then turned up the voltages in kernel tuner and VOILA, working overclock! I guess my phone, for whatever reason, disliked the undervolted voltages.