Database Info

Help! Boot time very long when flashing kernel

Iv'e flashed every kernel i could find and used all different settings when installing but my phone stays on the HTC logo for about 3-4 minutes before starting up, even when rebooted 2-3 times its still the same iv'e tried wiping and installing rom again without flashing kernel an boot time is about 60 seconds so it must be the kernel messing up my device.anyone else have this problem?

ryanraven said:
Iv'e flashed every kernel i could find and used all different settings when installing but my phone stays on the HTC logo for about 3-4 minutes before starting up, even when rebooted 2-3 times its still the same iv'e tried wiping and installing rom again without flashing kernel an boot time is about 60 seconds so it must be the kernel messing up my device.anyone else have this problem?
Click to expand...
Click to collapse
if i was you i would try do a full wipe and then run an ruu, just to give yourself a fresh install. then place a custom recovery onto the phone again and install your rom of choice. if its still lagging then i dont know what it could be:/

heavy_metal_man said:
if i was you i would try do a full wipe and then run an ruu, just to give yourself a fresh install. then place a custom recovery onto the phone again and install your rom of choice. if its still lagging then i dont know what it could be:/
Click to expand...
Click to collapse
but doesn't RUU lock bootloader etc ?

ryanraven said:
but doesn't RUU lock bootloader etc ?
Click to expand...
Click to collapse
yea it does.as i see you are S-OFF so you do not need to flash the boot.img manually but give it a try to see if it works.if it is not then from recovery do format all partition(except sd card)and flash the rom again.best wishes

ryanraven said:
but doesn't RUU lock bootloader etc ?
Click to expand...
Click to collapse
it does, but since you are s-off you can just reflash the revolutionary/ jupuntobear hboots to have fastboot enabled ect

okay iv'e done all that installed RUU wiped everything etc install rom and installed kernel and still takes the same amount of time to start up so wiped again and left it with the kernel that came with the rom and it starts up much faster not sure why no kernel works properly with this rom. HyperSensation 3.1 CM

ryanraven said:
okay iv'e done all that installed RUU wiped everything etc install rom and installed kernel and still takes the same amount of time to start up so wiped again and left it with the kernel that came with the rom and it starts up much faster not sure why no kernel works properly with this rom. HyperSensation 3.1 CM
Click to expand...
Click to collapse
maybe its just the kernel your trying to flash doesnt like your phone ;P. which kernel is it?

heavy_metal_man said:
maybe its just the kernel your trying to flash doesnt like your phone ;P. which kernel is it?
Click to expand...
Click to collapse
ive tried a few and their all the same
XxXPachaXxX kernel aroma installer v2.53
Pyramid-ICS-XE-010b2-300-aroma
Bricked-3.0-v1.4-ics-maxkhz=1566000-minkhz=192000-maxscroff=486000 << Starts up the same time as ROM Kernel
3.0.40-TAMCORE-00689-gfe1a294

You do realize that different kernels are for either sense or aosp right?
Sent from my Sensation

blahbl4hblah said:
You do realize that different kernels are for either sense or aosp right?
Sent from my Sensation
Click to expand...
Click to collapse
yes but all of these kernels were recomended by other users to use with non sense roms

Change Kernel on JellyBam v4.1.0

As I said: I was wandering if it is possibile to change kernel, I tried this one, installed with aroma, but my Sensation is stuck in a bootloop.
I'm S-on, I tried to flash either with and without the 4ext smart flash with the same result.
Anyone has a solution?

Fulvio93 said:
As I said: I was wandering if it is possibile to change kernel, I tried this one, installed with aroma, but my Sensation is stuck in a bootloop.
I'm S-on, I tried to flash either with and without the 4ext smart flash with the same result.
Anyone has a solution?
Click to expand...
Click to collapse
flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1step)
otherwise flash another kernel
which kernel did you use?

rzr86 said:
flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1step)
otherwise flash another kernel
which kernel did you use?
Click to expand...
Click to collapse
Sorry! I forgot to past the link and then I had to wait five minutes to edit my post and, well, I forgot again.
This is the kernel: http://forum.xda-developers.com/showthread.php?t=1216197 I don't really need it but I would have tried some oc and the sweep2wake function and stuff, so, any other kernel (or even the rom one, if it's possible to set it) is the same to me.
Just to tell you: I flashed Jellybam after a full wipe, and it was working, then flashed the kernel, then, when I got stuck in the bootloop I flashed Jellybam again without wiping, right now all works properly.

Fulvio93 said:
Sorry! I forgot to past the link and then I had to wait five minutes to edit my post and, well, I forgot again.
This is the kernel: http://forum.xda-developers.com/showthread.php?t=1216197 I don't really need it but I would have tried some oc and the sweep2wake function and stuff, so, any other kernel (or even the rom one, if it's possible to set it) is the same to me.
Just to tell you: I flashed Jellybam after a full wipe, and it was working, then flashed the kernel, then, when I got stuck in the bootloop I flashed Jellybam again without wiping, right now all works properly.
Click to expand...
Click to collapse
That kernel is NOT designed for AOSP Jelly Bean ROMs like JellyBAM. That kernel is designed for Sense Ice Cream Sandwich ROMs, so it's to be expected that your phone won't boot after flashing that over JellyBAM. If you want a kernel to use with JellyBAM that has all the features that you just mentioned (Sweep2Wake, OC, etc.) then try my kernel (Sultan kernel). The thread is here: http://forum.xda-developers.com/showthread.php?t=2035897

android1234567 said:
That kernel is NOT designed for AOSP Jelly Bean ROMs like JellyBAM. That kernel is designed for Sense Ice Cream Sandwich ROMs, so it's to be expected that your phone won't boot after flashing that over JellyBAM. If you want a kernel to use with JellyBAM that has all the features that you just mentioned (Sweep2Wake, OC, etc.) then try my kernel (Sultan kernel). The thread is here: http://forum.xda-developers.com/showthread.php?t=2035897
Click to expand...
Click to collapse
Yeah well, I was looking at the title of that kernel thread while I realized which was the problem, I'm glad to tell you that I flashed your kernel last night (I'm Italian) and after a whole day using it I have to say that I really like it (even if I've to settle with all the differences between the governors and the best way to set them with aroma).
Thank you!

[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.

[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.

Webpages often turns all white after finishing loading

Hi guys and girls. Hope you can assist me here.
I flashed Android Revolution HD on my girlfriends HTC Sensation.
Now she has an issue on many webpages, both occurring with stock browser and Dolphin. When she for example enters ekstrabladet.dk (Danish news page) and opens an article, the whole article loads but then immediately after completion (or maybe 0.5 seconds later) the whole page turns white - the address bar is still there and I can scroll up and down the white page. I can even hold a finger down and go into selection mode as if the whole page was shown behind the white page.
I've tried Googling the issue. Some answers suggested changing the APN setup to not have a proxy address, which I've tried without success.
Then I've also seen one user reporting a similar issue where flashing a different radio helped.
I only flashed and rooted the phone without going to S-Off, so the Sensation is still S-ON, so I'd prefer not to play around with flashing radios, if that is not the cause of the issue.
Issue occurs both on 3G and on Wifi.
Any suggestions?
I haven't experienced anything similar with my previous HTC Wildfire or my current Samsung Galaxy R.
And this issue pretty much renders it 50% useless as a smartphone. The issue was never present on stock rom.
Flashed: Android Revolution HD 7.3 XE (with Beats audio)
Kernel: 3.0.16-v1.5.2, SebastianFM #1 SMP Preempt
Basebamd version 11.76A.3504.00P_11.24A.3504.31_M
Version 3.33.401.154 CL391535 release-keys
Browser version: Webkit/534.30
Edit: Regarding the option to use a different Radio, I just checked the ARHD 7.3 thread which states:
--- With 7.x ROMs I strongly recommend flashing 11.76A.3504.00P_11.24A.3504.31_M radio ---
--- Don't flash RADIO from ClockworkMod recovery! Extract downloaded file and read the guide inside! ---
so that doesn't really support the fact that another radio should be used.

In any case you are on S-ON so you can't flash another radio
Go to settings->apps->all and erase cache of the browser
If that doesn't work then reboot to recovery and do wipe dalvik-cache
See then how it goes
Sent from my HTC Sensation Z710e using xda premium

Exactly, that's why I hope not to have to flash a different radio as I would then have to get S-off.
I will try the cache thing. But since different browsers behave similar, I don't think it is sufficient clearing just the browser. Maybe Dalvik can help.
I also got to think that I choose SebastianFM kernel instead of Stock kernel or some third option because the guide I followed recommended a non-stock kernel.
Thanks for your help. Will give it a try tonight.
BR, Martin
Sent from my GT-I9103 using xda app-developers app

I've tried clearing first the cache of the apps but without luck.
I then tried clearing Dalvik Cache (Not Dalvik Cache + Cache) also without luck.
This issue doesn't happen initially. Usually I can go to 2-3 articles on http://ekstrabladet.dk before the white top-layer issue occurs.
It seemed like it may have been taking slightly longer before it occurred after flashing the Dalvik cache.
I did try flashing stock kernel but without success. Maybe because I'm not S-OFF.
However, the SebastianFM Overclocked 1.5.2 kernel seems rather popular.
I also just tried installing SetCPU to limit the max frequency to 1.242 instead of 1.5 GHz. No improvement.
Any suggestions? My girlfriend is of course pretty mad with the phone's ability to browse news pages.

my mistake
i meant wipe dalvik + cache
sorry
also you don't have to be on S-OFF for flashing different kernel

rzr86 said:
my mistake
i meant wipe dalvik + cache
sorry
also you don't have to be on S-OFF for flashing different kernel
Click to expand...
Click to collapse
I just tried Dalvik + cache this morning without improvements
Yeah, I know that I shouldn't need S-OFF for flashing a different kernel, but I for some reason did not succeed. I thought that maybe my method was not compatible with S-ON. Or maybe I am doing it all wrong, even if I had S-OFF. I just took a HTC_stock_somefilename.zip kernel file and tried flashing it via 4Ext recovery.
Also I tried flashing it via Kernel Update utility as recommended in ARHD thread. But after reboot, the kernel was unchanged.
I may go back to stock ROM, if I don't find a fix. But I would be very sad to do that as ARHD and SebastianFM kernel must be a great improvement to stock in my opinion. In particular because she also suffered out-of-RAM issues in stock, where custom ROMs are more optimized.

mhca said:
I just tried Dalvik + cache this morning without improvements
Yeah, I know that I shouldn't need S-OFF for flashing a different kernel, but I for some reason did not succeed. I thought that maybe my method was not compatible with S-ON. Or maybe I am doing it all wrong, even if I had S-OFF. I just took a HTC_stock_somefilename.zip kernel file and tried flashing it via 4Ext recovery.
Also I tried flashing it via Kernel Update utility as recommended in ARHD thread. But after reboot, the kernel was unchanged.
I may go back to stock ROM, if I don't find a fix. But I would be very sad to do that as ARHD and SebastianFM kernel must be a great improvement to stock in my opinion. In particular because she also suffered out-of-RAM issues in stock, where custom ROMs are more optimized.
Click to expand...
Click to collapse
what error did you have when you flashed the kernel?

rzr86 said:
what error did you have when you flashed the kernel?
Click to expand...
Click to collapse
It did not give any errors. With Kernel Updater it gave a message that now I could reboot and my phone would have the new kernel.
And in 4ext it just said "flashed kernel ... bla bla" without any errors.
Just didn't have any effect on the phone.

I realised that I forgot to enable SmartFlash in 4ext, which I need because of being S-ON.
(Described in step 3 in this guide )
I assume that I can enable SmartFlash and retry the kernel flashing before trying other ROMs or going back to stock.
I'm not sure this is kernel-related, but I would assume that ARHD is so close to stock that I don't know why this occurs.

mhca said:
I realised that I forgot to enable SmartFlash in 4ext, which I need because of being S-ON.
(Described in step 3 in this guide )
I assume that I can enable SmartFlash and retry the kernel flashing before trying other ROMs or going back to stock.
I'm not sure this is kernel-related, but I would assume that ARHD is so close to stock that I don't know why this occurs.
Click to expand...
Click to collapse
for flashing a different rom or kernel first you have to enable smartflash from 4ext(for S-ON devices only)

Flashing back to stock kernel didn't help.
I hope that she will allow me to try re-flashing ARHD maybe without the tweaks that I checkmarked during installation.
Or maybe I'll flash one of the below roms instead:
Elegancia (Blitz 3.6 version)
ViperS 3.1.2 (sense 4+)
Both seem like really nice ROMs and I believe she wants something with Sense.