Root Help! Stuck in bootloop after kernel flash

[k2buckley]

Okay, I did a search and found no information on a similar situation. Here's what happened. I recently rooted via unrevoked 3.21, then flashed a stock rooted rom, by OMJ, his most recent ROM. I ran the phone for a day with that ROM and kernel that it came with, and everything was working good, battery life seemed good for the day. Well, I decided to flash the 4.19 netarchy kernel this evening, and after doing so, the phone got stuck in bootloop, and I had to do a battery pull. TO flash the kernel, I did this : flashed from clockwork recovery to RA 1.8. Wiped cache, wiped dalvik cache, flashed kernel from SD card, rebooted phone. Then it was just stuck in bootloop, endlessly rebooting. I pulled battery after about 25 minutes, and rebooted into Recovery, which was RA at this point. I wiped all data, cache, davlik. flashed the OMJ ROM again, flashed the netarchy kernel, rebooted. same thing. Pulled battery again, rebooted to recovery, wiped data, cache, davlik. Flashed ROM, no Kernel this time. Booted fine. went into ROM manager, flashed back to clockwork. booted to recovery. wiped data, cache, davlik. restored nandroid backup from earlier today. That is where I'm at now, my EVO is back to the way it was a couple hours ago, which is sweet. (sorry for spelling it out, but figure the more info about what I did, the easier it will be for someone to help me) So I'm wondering what to do now, or if I did something wrong while flashing the kernel. Should I just try a different one? I would still like to try a different kernel, i want to experience the fps uncapped. Thanks in advance for any help.

BTW: I thought i had read on here, that when flashing from clockwork to RA, via ROM manager, that after a reboot it would be back to clockwork. Is that incorrect? because after I flashed from clockwork to RA, it definitely did not boot back into clockwork, I had to flash clockwork again. Thanks

kyle

 

[k2buckley]

So I did the same exacty thing with BFS # 9, and it worked. Things seem to be running smoothly thus far. Fantastic. The only thing that I've noticed so far is that my 3g data connection was dropping out sporadically while in the market, and it wouldn't let me DL any apps, kept getting an error. I rebooted and it's working okay now. My question is, was I supposed to flash a radio update with that kernel? I didn't see anywhere that it required one. Thanks in advance.

kyle

EDIT: I've been reading through an insane amount of threads, and from various places, have found that the problem I was having was most likely due to me having the leaked ROM 3.28. There were reports of the same problem. Kings BFS #9 seems to be working okay so far. we shall see what happens.

 

[tsipa]

BTW: I thought i had read on here, that when flashing from clockwork to RA, via ROM manager, that after a reboot it would be back to clockwork. Is that incorrect? because after I flashed from clockwork to RA, it definitely did not boot back into clockwork, I had to flash clockwork again. Thanks

kyle

If you flash an alternate recovery through ROM manager, it will permanently stick unless you flash a different recovery. What you were reading about was a temp flash done through recovery. You need to put the alternate recovery in a zip file on the root of your sd card and then install through recovery. This will instantly give you access to the features of the alternate recovery and you will be back to your permanent one after a reboot.

 

[tsipa]

So I did the same exacty thing with BFS # 9, and it worked. Things seem to be running smoothly thus far. Fantastic. The only thing that I've noticed so far is that my 3g data connection was dropping out sporadically while in the market, and it wouldn't let me DL any apps, kept getting an error. I rebooted and it's working okay now. My question is, was I supposed to flash a radio update with that kernel? I didn't see anywhere that it required one. Thanks in advance.

kyle

EDIT: I've been reading through an insane amount of threads, and from various places, have found that the problem I was having was most likely due to me having the leaked ROM 3.28. There were reports of the same problem. Kings BFS #9 seems to be working okay so far. we shall see what happens.

You only have to flash a radio & wimax update if you are coming from 2.1 and have never done so before.

 

[kegacide]

how is kings BFS #9 i was going to try that, but i just rooted and have to NAND update first, but when i get a chance im gonig to give it a shot...

 

[tsipa]

how is kings BFS #9 i was going to try that, but i just rooted and have to NAND update first, but when i get a chance im gonig to give it a shot...

BFS #9 is solid and fast. NAND update?

 

[kegacide]

unrevoked 3.21 has it in there already i believe, i used simple unrevoked 3 and need to use unrevoked forever to NAND update

 

[tsipa]

unrevoked 3.21 has it in there already i believe, i used simple unrevoked 3 and need to use unrevoked forever to NAND update

Oh, you mean NAND unlock.

 

[exclamation_mark]

Try flashing the kernel with out wiping the data. Just wipe the chache and the Dalvik. I has a similar issue in this thread. I had to re-flash the ROM or restore my nandroid to get the boot loop to stop. Then I flashed the kernel after only wiping the cache's and not the data. It worked after that.

 

[exclamation_mark]

how is kings BFS #9 i was going to try that, but i just rooted and have to NAND update first, but when i get a chance im gonig to give it a shot...

I really like Kings #9. I have been testing out Netarchy's 4.1.9 for a few days and haven't noticed a huge difference but personally it felt like Kings #9 was a bit snappier. Of course i have yet to prove it

 

[k2buckley]

So the kings # 9 feels to be spectacular so far. I have only had it for a short while, but it seems pretty quick. Battery barely drained at all over night, about 3 percwnt over 6 hours it seems. I'm noticing as I type this that the keyboard is a little laggy. I read that other people were having issues with this kernel starting out quick and then. Slowing down. We will see. Thanks for the replies.

Kyle