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] Cant install new kernels

Hi guys, I'm using the CM9 ICS with my transformer and I was trying to install a different kernels without any success at all. I've booted into CWM (V5) and installed from sd card but when I restart the machine, It's always with the same kernel. Can someone suggest how to make it work?

How long does the install take? That should give some insight onto what it is doing

yosi199 said:
Hi guys, I'm using the CM9 ICS with my transformer and I was trying to install a different kernels without any success at all. I've booted into CWM (V5) and installed from sd card but when I restart the machine, It's always with the same kernel. Can someone suggest how to make it work?
Click to expand...
Click to collapse
Just to be sure, CWM v5 will not read external uSD card, only the internal storage /sdcard. May I know the kernel you are installing?

It takes about a minute to install.
I've tried a few:
TesteyMeh ICS 0.7
Blades
Others...
All of them seem to install fine but when rebooting I see the same kernel version and I cant OC.

have u tried wiping the cache and dalvik before flashing them?

scottyf79 said:
have u tried wiping the cache and dalvik before flashing them?
Click to expand...
Click to collapse
Yes I have... no good

yosi199 said:
It takes about a minute to install.
I've tried a few:
TesteyMeh ICS 0.7
Blades
Others...
All of them seem to install fine but when rebooting I see the same kernel version and I cant OC.
Click to expand...
Click to collapse
A minute is way too long. Kernels only take like 3 seconds cuz they are small.
Try mount /system under mounts and storage before flashing the kernel.

yosi199 said:
It takes about a minute to install.
I've tried a few:
TesteyMeh ICS 0.7
Blades
Others...
All of them seem to install fine but when rebooting I see the same kernel version and I cant OC.
Click to expand...
Click to collapse
Flashing a new kernel takes a few seconds. After reboot please pay attention to the blue indicator below the Android figure. It this not appears something went wrong with the first stage of the flashing process, invalid image/zip file etc.
Please use the customized CWM version, just not the flashed one from the Rom manager. I'v good experiences with the R2 (internal sdcard only) as well with the R1 (external micro-sdcard only). I preferred the R1 version.
Btw I'v have the best experiences with my TF101G with the CM9 build of March 29 combined with the quevor-test8 (just NOT from the guevor thread but ONLY from the thread of Richard because it's compiled for CM9) kernel, no reboots and no deep sleeps anymore while 3G and Wifi is working fine. Please do not wipe or clear something before flashing the new kernel to prevent Wifi problems. And I'v the best experiences not using the reboot system now from CWM but using power down and switch on the TF manually.

antond57:
i too have been having trouble getting kernels to allow overclocking...i flash one, all looks ok but when i get to tablettop the kernel info appears unchanged and setcpu wont clock past 1000.
could you maybe please post links to the rom and kernel you used? im having trouble locating the Richards R1 and R2 versions. i would like to see if i can repeat your success w/ these versions.
much appreciated.

I have same issue except worse yesterday. I'm on latest CM9. I tried to flash guevro test 9 and I did wipe both cache. Using roach 2 recovery. Just stayed on Asus screen. Blue bar did pop up and take a second or so but nothing. Checked md5 and all was good.
I had to totally flash ROM again after a full wipe because even a restore from recovery wouldn't go past very first Asus screen. I'm not sure what happened but I'm definitely now worried about trying a new kernel again
Sent from my Transformer TF101 using xda premium

eminembdg said:
I have same issue except worse yesterday. I'm on latest CM9. I tried to flash guevro test 9 and I did wipe both cache. Using roach 2 recovery. Just stayed on Asus screen. Blue bar did pop up and take a second or so but nothing. Checked md5 and all was good.
I had to totally flash ROM again after a full wipe because even a restore from recovery wouldn't go past very first Asus screen. I'm not sure what happened but I'm definitely now worried about trying a new kernel again
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Yap, I have the same problem. Nandroid restore did not restore to the previous state. For me, re-flash the ROM fixed the problem (no full-wipe).

Try Using clockwork recovery
I have just flashed guevor kernel as well with no problems. I'm using clockwork mod recovery. Have you tried it?

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] Changing Stock kernels

Hi,
I have managed to put on a kernel that's not working. Is there a way to revert back to the original kernel? I do have a nandroid backup, but re-installing that didn't put on the old kernel.
I am using Liquidsmooth ROM. Any help would be appreciated.
Thanks.

if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.

DvineLord said:
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
Click to expand...
Click to collapse
I did exactly that, presuming that it was working... But I have been facing issues. The phone restarts every once in a while and I have managed to get to this condition after multiple wipes and restoring a backup. Anyways I don't know what the issue is I was just wondering how to revert back to the original kernel.

im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.

DvineLord said:
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
I do not have s-off does the flashimagegui works even without it?

strommer666 said:
I do not have s-off does the flashimagegui works even without it?
Click to expand...
Click to collapse
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.

DvineLord said:
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
Click to expand...
Click to collapse
Thanks I'll make sure I do that..

also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.

DvineLord said:
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
Click to expand...
Click to collapse
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.

strommer666 said:
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
Click to expand...
Click to collapse
you need everything. you don't need to extract the kernel. just load the whole zip file.

DvineLord said:
you need everything. you don't need to extract the kernel. just load the whole zip file.
Click to expand...
Click to collapse
I did load the full file and the flash gui image extracted the kernel. The thing is I have the kernel now, but still I can't seem to be able to install the new version of the LiquidSmooth build. I am doing a nandroid backup of this thing and try installing it again.

well new liquidsmooth is nice, im using cwm now as recovery since ive had tons of issues with twrp since version 2.2.2.0

[Q] PAC-man ROM not booting anymore

hi,
so as i can not post in the android development subforum i'll have to try it here..
I have: HOS with TWRP 2.4.4.0 (goo manager) with HBOOT 2.15 (S-ON) running PAC-man ROM 22.1 (the newest update)
also i have bubba v4 installed and everything was working really perfectly. (s2w and some kernel tuner settings)
yesterday i played a bit with UI settings, nothing that i thought would stop my device from booting..
today i woke up, the battery was empty so i plugged in, turned on and left, after a while i came back and it was still at the boot
animation (PAC is loading...).
now i have tried to reflash bubba, PAC (cache+dalvik wipe) and the boot.img via fastboot. still it is stuck on that loading screen.
now i'd really like to use this rom with the bubba kernel.
any clues how i could get it out of this boot cycle?
thanks
-t.

2.4.4.0 is kinda crap in certain things. Flashing roms is one of them. Please use 2.3.3.0 as this will work.

why do you think that twrp version is the problem?
flashing this rom with 2.4.4 has worked well, so flashing over the same ROM with it shouldn't be problem...?
when flashing or wiping everything seems to work normally.
also, i am not sure how to downgrade twrp!?
best,
-t.
edit: okay i found out, fastboot flash recovery .. should work. i'll let you know if it works afterwards *fingers crossed*
edit2: reflashing the ROM it takes much longer (maybe thats good?) i just hope it finishes at some point...
edit3: okay, so re-flashing with twrp 2.3.3.0 did'nt work either, it is still stuck at the "PAC loading..." stage
(yes, i flashed the boot.img too)
any more clues?
finally i had this phone set up just the way i wanted, it was perfect and then this. why couldn't it just keep working
makes me sad, i want to use my phone damnit

okay, so i flashed and wiped and flashed and wiped a few times, system, cache, dalvik whatever, suddenly it started working... i also flashed some different kernels (as i thought some bubba stuff might still be there)
soo IDK what it was but now it works again, thank god..
maybe its worth mentioning that i flashed an older PAC rom (v22.0.1_20130324-230044) though i am not sure if that was the problem...

Sorry, I was off for some time from this forum.
If your bootloader version is > 1.09 you'll have to flash the kernel separately due to some restrictions in the higher bootloader versions.
If e.g. you flashed boot.img only from the 'bubba.zip' you're missing some of the modules needed for working coming with that flashable zip. Just have a look inside the zip file and you'll see some different content besides the boot.img. So you need to flash the complete zip file (to get the modules) and separately again the boot.img (to get the kernel itself).
The point about 2.4.4.0 / 2.5.0.0 is, that some installer scripts for some roms don't work as they should.
:good:

Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Well nevermind I guess I learned something from this little action that cost me most of my precious Saturday...
Also I now tried flashing twisted 3 and bulletproof kernel neither of them worked for pac rom, maybe someone could explain to me which kernel works for which rom? I thought they are completely interchangeable as long as they are compatible to the hardware..
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Well, appreciate the help.
Best,
#t.
Sent from my One S using xda app-developers app harhar

Bulletproof is for sense
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2

Aha okay, I thought sense is like any app running ontop of any kernel...alright.
Sent from my One S using xda app-developers app

tehtomi said:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Click to expand...
Click to collapse
Usually the installer script should set the right permissions already. Nah, modules shouldn't go lost this way ( system/lib/modules/*.ko).
tehtomi said:
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Click to expand...
Click to collapse
In short: boot.img = kernel
It's stored in an own partition (block) on the phone, That's why you have to use 'fastboot flash boot boot.img'. Same for radio: 'fastboot flash radio radio.img' and so on. The bootloader will load them first from this block. But search Google if you'd like to know more. lol
Usually there is a boot.img file in any rom.zip that can be extracted and flashed also it's supposed to be flashed with the rest of rom.zip in one go. Blame htc for their bootloaders which prevent you from this. That's why we talk about htc's half assed bootloader unlock.
To come to an end: There are sense based roms, AOSP and AOKP based roms. Whereas AOSP and AOKP based kernels could be interchangeable, sense based kernels are only compatible to htcs sense UI. That's why you can't mix them up with all the roms out there. Sense is deeply integrated into kernel.