At first I thought my issue was isolated to the 8.x snap kernels but now I am also having issues with KingX bfs 8 and netarchy's 4.1.9. I clear cache, and dalvik, flash the kernels and I either get a bootloop or the phone will load and just freeze after a minute or two. Flash an older kernel (kx bfs #6) and everything is fine again.
Is there something else I need to be doing aside from clearing cache and dalvik? What could be causing this?
hm i personally do not clear dalvik and cache when flashing kernels some roms i find i have problems when i do such as on Evio rom. you may try flashing the kernel with out wiping the data and see if it helps any.
also if you are using CM6 which i assume you are since you were using snap. not all kernels are compatible with CM since it is asop. this could also cause your boot loops. if it does not specifically say CM compatible i would assume it isnt.
lastly if you use setCPU make sure it is reconfigured to the new kernel. i normally get force close issues and not freezes but am trying to throw out anything can think of that might help.
The only kernels I tried with CM were the snap kernels. I gave up on CM and went back to Evio and tried the other kernels. I also delete SetCPU beforehand and reinstall it after the flash.
Gonna try flashing kx bfs 8 without clearing data....
EDIT: Still didn't work. It never gets past the "hTC EVO 4G" screen. Just hangs on it for a while and then reboots and repeats.
let us know i have the same problem flashing after clearing on evio. i believe it has to do with how the dalvik is moved to the cache partition so i never wipe when flashing kernel with it.
hopefully that works also the new evio 1.2 has king 8 presintalled
I noticed my phone acting a little funny with Kings #8, so I reverted back to #6 and my phone has been back to normal since doing so.
I'm going to flash VirusROM carbon as soon as he gets it up. It's packaged with #8 too so we will see what happens.
When I first flashed CM6 I repartitioned my SD card, maybe I need to do that again when going back to a sense rom/kernel? Going to clear everything in my phone and repartition SD card before I flash virusROM Carbon. Maybe that will clear it up.
Nope, that didn't work either.
Does anyone have any ideas why this is happening?
Could it be my recovery that's doing it? I'm using AmonRA.
Bump.
I just tried kingx bfs9 and once again- bootloops.
Does anyone have any ideas what could be causing this?? Please?
Related
I do not know the reason for the following Situation.
I once had Fresh 3.2 installed, for no reason the phone one day stayed at the boot screen after a restart.
I tried Installing CYANOGEn but never could o I installed NONSENSE, this is all usong RA recovery.
I tried installing the latest Fresh and Myns and no luck, I decided to go Closckwork, I was finally able to istall the new FRESH. YAY SO HAPPY... NOT I cant install anythig from the market or any apks. it reboots to bootscreen saying FRESHHHHH. AHHHHH, so I tryed reinstallyng, nothing then tried Myns, wont install in closckwork.
AHHH
then I go and reinstall RAs recovery, Im able to install Myn Ota supersonic, the rom runs perfectly I can install apps on the market, it wont reboot. so Now I install Myns warm twopointtwo. and yess it installs YAY, lets go install an app.. NOOOOOOO it restarts phone to boot screen.
WHY?????????????????
is there a problem witth my phone?
Did you wipe before flashing? If you dont, it might cause the problem you are describing.
i heard psoting in the right forum helps fixs problems too (see Q&A)
You're not wiping. If you are, you're doing it wrong. If you wipe wrong, it leaves sh*t behind. Same rule applies to the men's room.
Sent cuz I like boobies
Not sure if you are doing complete wipes and disregard my answer if you are, but I used Amon RA and wipe EVERYTHING twice whenever I install a new ROM or do a nandroid restore. I wipe data, cache, dalvik cache, ext, battery, and rotation twice. I have never had a problem flashing ROMs. It might be overkill, but it works.
I have done everything
I have Wiped EVERYTHING even changed the SD card,
now Im able to Flash Fresh and Warms rom but
now I cant install any apps from the market or SD
everytime I try to install something it reboots.
Hey guys, I feel like I have ran out of options on this problem so I figured I would post and see what you guys think. I am currently running Myn's RLS 2 and ever since I flashed the first version I have not been able to get past running the HTC Stock Kernel. If I flash any other Kernel my phone runs for a bit and then will freeze up and randomly reboot. Even during reboots sometimes it will reboot again. Do I need to be running SetCpu at all to help with this, or is it another problem? Any suggestions would be greatly appreciated. Thank You.
Depends on which kernel you want to run ... some play better with certain roms. I notice that you mention Netarchy's kernel in your signature ... have you tried his universal 4.1.9? Anyway ... whenever I install a different kernel, here's the procedure I use ...
Boot into recovery (I use RA) ... wipe cache and dalvik cache twice each ... flash the kernel ... wipe cache and dalvik again ... reboot.
so im trying to get MIUI on my evo, but when i flash it it sticks at the sprint bootloader. i got the rom from MIUI. anyone help?
Did you wipe everything before flashing? Have you tried other kernels?
i have wiped data and cache. and im sorry but im new at this, what is a kernel
first of all, try also wiping data ( i kno its hard, just back up with titanium backup), system, boot, and battery stats. that should boot right up.
Did you wipe dalvik? You need to wipe data/cache/dalvik when switching ROMs.
If you don't know what a kernel is then I HIGHLY suggest you spend a little time reading up on all this because that is Android 101. You should have known what a kernel is before attempting to flash anything. A kernel is basically the interface between the software and hardware of your phone. It has all the drivers and instructions that tell your hardware what to do. They are flashed the same way ROMs are flashed and can affect performance dramatically. Different kernels perform differently on different EVOs so you need to find one that works well for your device. Sometimes the kernels that come packaged with ROMs don't work well on some EVOs and can cause booting and performance problems.
Mas wipey before flashy! Wipe all data, save for sd card, twice before flashing this rom. The savaged kernel that comes with the rom is just fine. Also, I would avoid titanium backup like the plague, especially if you are going to use MIUI.
Swyped from my CM7 EvO
I recently decided to update the look on my Evo and went with the MikFroyo v4.5 Rom. I was running Netarchy's Burnt Rom, and had the toastmod kernel. After updating the radios, as they suggested, I proceeded with flashing with the MikFroyo rom. The MikFroyo Rom comes with stock HTC #15 Kernel, which I just left alone until my wifi stopped working.
I read on a few threads that some people were flashing a different kernel and were able to fix wifi, so I tried a couple of different ones. I've listed the kernels I used below. Additionally, I updated profile in system updates, and it still didn't fix anything.
[KERNEL]
Stock HTC #15 Kernel (came with MikFroyo v4.5)
4.3.1 netarchy-toastmod-cfs-nohavs-nosbc-universal
4.3.4-cfs-havs-less-nosbc (Less Aggressive HAVS) - This kernel is currently on my phone.
I'm just grasping at straws at this point, and I have no idea what else to do. I love the Rom, but I need the wifi to work.
Does anyone know a kernel that is supposed to resolve the wifi issue?
Are there perhaps some file location changes that were made when the new Rom was installed?
You stated that you kept the HTC 15 until wifi stopped working. This infers that wifi was working with MikFroyo and then something happened. What mods did you make to your phone just before wifi stopped working?
Hi, thanks for the reply. I meant to say I didn't start trying new kernels until I noticed the wifi wasnt working. The MikFroyo rom suggested updating the radios before flashing it, so I did.
The wifi problem surfaced after updating the radios to the current ones. I reverted the ROM back to Netarchy Burnt Droid 1.4.2 to see if it was the ROM that was causing the issue, but the wifi still can't scan for networks. I also always wipe the dalvik and cache before flashing.
Which radio did you flash.
I would suggest doing a full wipe, and then re-flashing the rom.
Khilbron said:
Which radio did you flash.
Click to expand...
Click to collapse
I did the combo and the boot update found here. I don't know which piece effects the wifi though.
teh roxxorz said:
I would suggest doing a full wipe, and then re-flashing the rom.
Click to expand...
Click to collapse
I also always wipe the dalvik and cache before flashing anything. Are you saying I need to wipe something else?
aerobic1 said:
I also always wipe the dalvik and cache before flashing anything. Are you saying I need to wipe something else?
Click to expand...
Click to collapse
I'm saying backup your rom and apps. Then do a full wipe, factory/data, cache, and your dalvik, then re-flash your rom. That should clear up your issues.
teh roxxorz said:
I'm saying backup your rom and apps. Then do a full wipe, factory/data, cache, and your dalvik, then re-flash your rom. That should clear up your issues.
Click to expand...
Click to collapse
Wooohooooo!!!! I wiped everything, and it's working PERRRRRRRFECTLY!!
Thanks a bunch teh roxxorz
Anytime man.
I tried to flash HONO Full Throttle V2, cleared cache, dalvik cache.
Now my phone keeps rebotting loopping. I tried to access ROM manager but it reboots before it can do it. I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Do i have to unbrick?
Any help is appreciated, thank you
When that happened to me, with a different ROM, I went ahead and pressed power again at that screen and it continued to CWM, didn't wipe/reset my phone.
neuty said:
I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Click to expand...
Click to collapse
That is what you are supposed to see. Press power button twice to "accept" the factory reset. It won't actually reset anything -- instead it will boot directly to CWM.
Oh, okay thanks so much RealyPssd and Drumist! Got a bit scared for a second there. Was able to flash back
Edit: I might have found the problem:
I tried installing HONO's P930 CM9 Kernel V5 and it did the same thing but worse, it didnt even let me past the CM boot guy.
Went through the same thing
I tried flashing HO!NO!'s CM9 Full Throttle this morning and went through the same thing. Sometimes it would boot into the OS, other times it wouldn't get past the CM9 guy, and even sometimes it wouldn't get past the HO!NO! logo. I even had a hard time getting into CWM via the factory hard reset method (I kept getting just a blank screen, but the phone was still on. I pressed the volume down button and that seemed to get it into CWM, although it could have just been a coincidence).
I tried re-flashing the ROM but still no change. So I then flashed CM9 RC-1 and haven't had an problems since.
From what I've read in the Full Throttle thread, the HO!NO!'s ROM already comes with HO!NO!'s kernel. I've also read that the instability is due to the undervolting that's taking place in the ROM (and I'd have to agree based on my experiences with overclocking).
If you really want CM9 go with the RC-1 (or even the nightly). I find it to be incredibly fast so far. Maybe HO!NO! can make a ROM compiled with the linaro toolchain that has a slightly less aggressive undervolting settings
To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.
Wiped everything but had a backup
HO!NO! said:
To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.
Click to expand...
Click to collapse
I was coming from a stock ROM that I had rooted with SuperOneClick, and installed CWM using Rom Manager from the market. When I went to install your ROM I first made a backup of the current ROM (i wanted to having something to fall back to). I did a wipe data/factory reset, wipe cache, wipe dalvik, then flashed your ROM. I also flashed gapps as well (could that have caused a problem?)
Does it sound like anything is off? I would really like to be running your Full Throttle ROM (it's the only reason why I tried to flash my phone in the first place)