Hello, XDA family. This is my issue today. I didn't read all that there was to know about rooting and flashing in the EVO LTE, because I did my share of flashing on the OG. However, when I couldn't boot into AOSP roms, I started my research and found out different stories about how to go about doing so.
I saw somewhere that I had to flash a specific boot image first, then flash the Rom. That didn't work, and it also crashed my WiFi.
After even MORE research, I found that the phone has to be S-Off, and I am not.
After trying to flash an updated IMG to save my WiFi, the phone didn't boot to the animation. It showed the splash screen, then went blank. And this happened for all of the custom roms that I tried to flash. It only booted to a rooted version of the stock Rom.
It also corrupted my TWRP 2.1 recovery, and the recovery kept restarting. I solved the issue by flashing TWRP 2.3
I even tried flashing the stock recovery and.installing the OTA update, and it did nothing but perform a data reset, and cleaned my internal sd. So I'm stuck on the software version that doesn't have a remappable Multitasking button.
What do I do?
______________________________
HTC Evo 4G LTE
Did you try using Flash image GUI to flash the kernel first?
Sent from my EVO using xda app-developers app
Yes, and I suspect that it was the incorrect kernel altogether. Not was one from Komodo...rls one, I believe. My phone did a factory reset, so I can't tell you.
ASUS Transformer TF300T
Stock Rom - Unrooted/Unlocked Bootloader
Okay, so I found a thread on themikmik that has a boot img for the rom that I am using.
http://themikmik.com/showthread.php...oted-Based-on-Latest-OTA-(Odexed-and-Deodexed)
Let's hope that this works out in my favor.
ASUS Transformer TF300T
Stock Rom - Unrooted/Unlocked Bootloader
Quick update: Wifi doesn't work. I'm going to try flashing a custom rom and see what happens
ASUS Transformer TF300T
Stock Rom - Unrooted/Unlocked Bootloader
I forgot to mention in my first post that when I flash custom sense roms, I wouldn't see the disclaimer in red letters with the splash screen, and then the phone would go blank.
Now, after flashing the new img, and flashing a custom rom (Sinister LTE V4), I STILL didn't see the red letters, which I thought that it would fail. HOWEVER, it actually DID boot, with Wifi working and everything. So...what the he'll happened? I don't really care at this point...but I'm laying of flashing for a little bit until I do a lot more research, since my new EVO different in subtle ways from its predecessor, but those same "subtle" differences almost bricked my phone. I blame it on my negligence.
ASUS Transformer TF300T
Stock Rom - Unrooted/Unlocked Bootloader
I don't think you nearly bricked your phone. You don't need to be s-off buy it does make things easier. The fact that your Wi-Fi was not working probably means you flashed a version of komodo that wasn't up to date with your rom or visa versa.
My advice would be to read the "don't panic" thread stickied in the Q&A section
Sent from my EVO using xda premium
Here's exactly how I flash my ROMs. Haven't had an issue since I started using this method:
Download ROM I want, adb push it to my INTERNAL sd card.
Open Flash Image, select "flash kernel" and select the entire .zip of the ROM I downloaded. It will find the kernel file for me.
Flash the kernel.
Reboot into TWRP.
Select "Wipe System" and wipe the whole system.
Flash ROM.
Boot.
Once my phone has booted, go into TWRP again and flash gapps, then reboot.
I ALWAYS ALWAYS ALWAYS have an issue if I try and flash ROM and GAPPS without booting in between. Or if I try and flash the rom and my TiBu update.zip at the same time. I have to flash ROM, reboot, then reboot again into recovery and flash GAPPS/update.zip.
Hope that helps.
Ahhh...interesting. As I mentioned before, I am not S-off. I am not sure if I will become S-off at some point, but right now, I am very happy to be on Sense 4. That's the main reason I chose this phone over the GS3 when I was upgrading from my OG Evo.
I like Sense roms, and when the ONE series was released, my entire theme became Sense 4.
However, if I ever decide to begin flashing AOSP roms, I will certainly keep your advice in mind.
______________________________
HTC Evo 4G LTE
Related
I have been flashing roms for at least a year now with no problems. For some reason, recently I can flash some roms fine and some roms only boot loop or boot freeze. I am currently using Bamf SoaB v1.0. when I tried to flash iBolt v0.90 the most I can get is to the MUIU boot screen and it either boot loops or freezes. I can boot OMFG roms and others fine as well and have ran into other roms that boot loop and freeze also. I have even had an issue with recovery boot looping in the middle of trying to load a rom or wipe. I have tried different Recoveries with no luck. I am wiping everything every time I flash. I even returned to stock Ruu with S-on and rerooted and no luck. Does anyone have any ideas?
Did you check the md5 of the file? Maybe it was a bad download
Update to newest CWM and use newest recovery or use 3.0.2.5 that was always a great one for flashing with no issue or boot loops.
If I helped you in any way please use the thank you button.
1) you aren't wiping (probably not the case since you've done this b4)
2) bad/corrupt rom download (check md5 as suggested)
3) recovery borked causing failures (reflash newest recovery)
4) recovery outdated and those roms require an updated version (reflash newest recovery)
5) your phone doesn't like the kernel and/or default clock speeds of the rom you are flashing (use different rom or flash a different kernel immediately after the rom *YMMV*)
.
.
.
15) hardware failure (get new phone) *not really failure, just not living up to potential*
All that is meant by the dots is to indicate that there are a few other things to check before settling on it being a hw problem but I can't think of any right now.
After eliminating the likely causes described above, you may want to check your recovery log immediately after you flash. Export the log to the sd card, then examine the log file from your computer.
I am a frequent rom flasher, and I have had issues with bad nand blocks only being a problem to me with select roms and not others. Little bit of weirdness.
I have not received my thunderbolt yet, so I am only assuming that htc designed the internal and sd memory in your phone in a similar manner to my sexy nexy. Please correct me if I am wrong!
Sent from my Nexus One using xda premium
Thanks for all the help. The issue seemed to be a kernal problem. At least with ibolt it was. Sad thing after all that work and time and losing everything on my SD I ended up not caring much for the rom. lol At least I know what to try if the problem happens on other roms.
Alright, after bricking my phone yesterday and spending hours finally unbricking it, I've decided that I'm just not quite ready to play around with ROMs on the Transformer Prime. At least, not until they get a little more stable.
However, I'm finding myself unable to get my Prime back to stock ICS...
What I'm currently running is a Cyanogenmod 9 nightly build from 3/4/12. Through Rom Manager I was able to install the latest CWM (5.8.2.0) BEFORE the whole bricking incident. Now I can't even get my WiFi turned on...so I suppose any further changes via Rom Manager are halted.
Anyway, I used Vipermod's tool and was able to unroot successfully. I then went into settings and attempted to perform a factory reset. However, my tablet booted up with the same, Cyanogenmod boot screen and brought me back without any changes.
So then I tried using ADB....plugging my Prime in and typing "adb reboot recovery". But I get the message "adb server is out of date. killing..." then on the next line * daemon started successfully *. My device resets...but same thing...cyanogenmod...no CWM...no changes.
I thought maybe ADB wasn't working because I had unrooted. So I re-rooted, again using Vipermod. I see superuser again now...but ADB reboot recovery is still not working.
So now I'm stuck... I seemingly can't perform a factory reset with my build of cyanogenmod, and I can't find any way of getting back to recovery (I've tried selecting recovery reboot after pushing the power button, tried selecting recovery from within Rom Manager and tried with ADB...all failed). Again, all I want to do is factory reset, and get my stock ICS back. Can anyone please help me out?
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Diamondback said:
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Click to expand...
Click to collapse
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
scaryslocuda said:
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
Click to expand...
Click to collapse
My warning only applies to STOCK blobs (like the ones in the official asus updates from their website).
The guide you posted seems to be fine.
Great! I'll give it a shot tonight.
One last thing... If I find that Virtuous isn't the best fit for me, would you advise AGAINST installing the stock firmware posted over at Android Soul? Is this what you would consider a "stock blob" or is this something different? Here is the link:
http://www.theandroidsoul.com/trans...h-cwm-recovery-on-unlocked-bootloader-primes/
That's a zip, not a blob, you can flash that
Diamondback said:
That's a zip, not a blob, you can flash that
Click to expand...
Click to collapse
Worked perfectly! Thanks so much for your help Diamondback...again!
Hi all - the weirdest thing is happening to me and it is definitely something I've done but I haven't the slightest what it is.
I've got CMX right now, and I've tried to go to a couple of ICS ROMs (Task, Sonic). They flash just fine, but on the new system if the screen goes to sleep the video flickers on screen wakeup. I have tried to remedy this by flashing an ICS kernel but haven't had any luck whatsoever. So today I thought I'd go back to my Nandroid backup that I took on CWM 5.0.2.7 way back on the 1st before I rooted my tab. I was on (and prefer) TWRP so I used Odin to re-flash the original recovery, wiped everything (including format /system from the Mounts menu to wipe the ROM) and restored the backup. Everything seemed fine. But to my horror, I locked the screen and woke it up to find the same flickering!!!!
I rebooted back into recovery and flashed TWRP back on so I could restore my CMX backup and I'm back to normal again. But now I feel like I'm stuck here, and the only way I'm going to be able to fix this issue is by using Odin to flash a stock firmware package. I really don't want to have to do that if I don't have to but will if I need to of course...
The one thing I haven't been able to get an answer on is before blowing everything away is what I'm asking now...in thinking about it, I had taken the backup before flashing a bootloader to fix my "rolling recovery screen" issue. Could the cause of this type of problem be a bootloader that the ROM doesn't like, or is this a crazy assumption?
OK I'm going to bump this thread with a simple to-the-point question - hoping for an answer as I work out my theories.
For those of you who have flashed ICS and custom recovery with no "rolling/flickering" issues - are you using an unlocked bootloader?
For the bootloader you just hit the point my friend,the bootloader that we use to fix rolling recovery problem has issues with most kernels except Pershoot's HC or CM9...
For your problem you should think of grabbing the official ICS or HC(just for getting rid of screen flicker),and in addition to flashing it you should extract it's stock bootloader,make a. tar.md5 out of it and keep it for future similar problems...
Note that the bootloader can only be flashed using Odin in PC and CWM or even stock flashing using MobileOdin can't make changes to it(or recover it)
For now there is not a proper fix for that but I think the best way is to have the stock bootloader and use ROMmanager or MobileOdin for flashing(since the recovery rolls with stock bootloader)...
Yeah I flashed stock ICS and rooted yesterday. I am just going to fight through the rolling recovery for now and stick with ICS until we can do more.
Thanks for the response!
some trick:you can rename the zip files you're going to flash so that their name starts with "Z",it's then easy to navigate to them(just press vol down twice)
Yep! That works, and you can also rename files as update.zip and use that option I believe. It's time to think outside of the box a bit with regard to flashing some ROMs...thats the bottom line. i am sure there are a few devs on this site that would appreciate it if we did more of that lol!
guys im really getting the same problem now... and i dont know what to do
would you be able to help me please?
I can't find clear cut instructions anywhere but I am sure there is a post on it already... I looked through the CM10 thread in original development but didn't see anything. I am totally stock on 1.22.651.3.
Well, you root using regawmod, you flash the ROM, and then you fastboot flash the kernel
Instructions for each of those are strewn about the forums
My write-up for Installing kernels with H-boot 1.15
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
Rooter:
http://forum.xda-developers.com/showthread.php?t=1690919
Sent from my EVO using Tapatalk 2
Skullmonkey said:
I can't find clear cut instructions anywhere but I am sure there is a post on it already... I looked through the CM10 thread in original development but didn't see anything. I am totally stock on 1.22.651.3.
Click to expand...
Click to collapse
The process is fairly similar to most other devices, with the one unusual quirk being HTC's unlock method does not allow the kernel portion of a ROM to be loaded from the custom recovery.
Assuming you have to use the HTC unlock method, this quirk will apply to your process.
There are multiple ways to approach working around the quirk, but I'll provide two common methods.
1) After unlocking the device, which can be done with packaged up software or by directly using HTC's software at htcdev.com, you'll want to make sure you have the RUU (method to revert back to stock) handy in case of any issues.
2) At a high level, a ROM consists of two portions, the kernel and the system. The system will almost always be loaded through the custom recovery and the kernel, due to HTC's quirk in their unlock method, can be loaded via the command line using the fastboot command, or through the phone using my app, Flash Image GUI.
If a mistake is made or something does not load properly, a computer and the command line will be the only option, thanks to HTC's quirk.
3) The order of loading the ROM depends on the method. I would recommend either one of two methods:
1) Flash Image GUI, select the ROM .zip from the sdcard, and FIG will flash the kernel portion.
2) Reboot into the custom recovery, select the same ROM .zip from the sdcard, and the custom recovery will load the system portion.
3) Reboot and everything should work.
Another available method:
1) Reboot into the custom recovery, load the ROM .zip from the sdcard, the custom recovery will load the system portion.
2) Reboot into the bootloader/fastboot mode, extract the kernel file from the ROM .zip, and using fastboot and this command: fastboot flash boot c:\downloads\boot.img, load the kernel.
3) Reboot and everything should work.
If something doesnt work, you'll gain some experience in troubleshooting, which isn't too difficult, but takes more time. If you're new to the process, I'd plan for more time learning the ins/outs.
Hope that helps!
Thanks Joey! Not new to the game but I like to know the process before actually going through with it. I had to flash 2 times and unlock manually but I an now running Jelly Bean! Now to figure out why my WiFi is nothing even being 2 feet away from the router...
Don't forget to wipe dalvic, cache and factory reset before flashing a new ROM or you will have problems.
Sent from my EVO using xda premium
I did. Wiped cache x2, dalvik x2, factory x2, superwipe x5. Should be squeaky clean!
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
NoClemency said:
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
Click to expand...
Click to collapse
S-OFF is really the way to go if it's still an option for you it's the only way to get the new firmware without relocking and taking the OTA then unlocking and rooting again read post 2 in the lazypanda thread found here http://forum.xda-developers.com/showthread.php?t=1737123 just go down the list and verify everything works before running lazypanda there are plenty of members that subscribe to that thread so there is plenty of help availiable
Also, rerooting won't do anything. You're already rooted? Think the problem is in the rom u installed. Possibly a bad download. Try downloading from a good connection and install it again. If it is close to stock like flex's stock w goodies just clear cache and dalvik in recovery.
And what do u mean u tried a few recoveries? Cwm doesnt work well with the evo LTE. Try twrp 2.2 and leave it alone until its updated again.
What is your hboot? What rom did you try flashing?
Sent from my lair.
Im also getting this issue and i know its not anything to do with rooting and all that since ive been rooted since i picked this up from best buy on preorder release day and ive been flashing and running the same rom and mods forever now also i was using wifi yesterday soooo yea lol
Recognized Hooker Killer
First, I don't believe I can make my phone S-off, because it has software version 2.13.651.1 710Rd on it and even though I do have a nandroid back on 1.13 hboot, for the default rom from a long time ago with my old HTC EVO LTE, I can't flash back a hboot to 1.13 so I believe I'm stuck S-On for now. Let me know if I'm wrong.
I've attempted several different roms including fresh rom 5.1.1, viper4G_1.0.0, and a jelly bean rom (cm-cfX-20120904-OFFICIAL-jewel all with the same problem. As for recoverys, I should have said I've tried restoring back to several different nandroid backups that I created in the past that were working just find with my old HTC EVO LTE.
Right now my phone is unlocked and rooted. I am running H Boot-1.19.000, I am S-On, and Radio-1.12.11.0809.
I know this problem has something to do with flashing new roms, because when I do a nandroid back up to the default rom, I don't have this problem, and the wifi is working great, I only have this problem if I try to flash any custom rom or use a nandroid backup that I made with my old HTC EVO LTE.
Again, this is not my first time around the track with an HTC EVO LTE, this just happens to be a new phone that I recently got from Sprint when they were thinking my dropped calls were caused by my phone when in fact they figured out they had a tower down. Since then, the tower is back up, so that is why I just rooted this new phone they gave me.
Let me know if you have any suggestions or if you need anymore information.
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Please Help
NoClemency said:
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Click to expand...
Click to collapse
Hey im having the same exact issue I however went back to my stock backup from right after I rooted. The issue I had was I flashed a CMX nightly. I had been running them fine and suddenly everything went haywire i was bootlooping but only after about 30 seconds after the rom would load up. I'd have just under a minute to fish around and the it would reboot again. it was in this short window that I saw the wifi error and that it would not connect to the sprint network at all for voice or data. Im S-On Hboot 1.15 Evo LTE. I used Flash GUI to go from Stock sense to CMX as im sure youve figured out you have to do. Since i had backups of previous CMX nightlies I tried to just restore But none of my nandroids would fix the looping issue I managed to flash the boot img from the CMX rom i was previously on through adb/fastboot and it took but still my device kept looping. Finally i found this http://forum.xda-developers.com/showthread.php?t=1917106 but I didn't have any Sense Based Roms only my Stock Nandroid back up. So i used the Boot Image Flasher Tool, it took, then Instead of rebooting the system I went straight to my custom recovery and restored my Stock Sense BackUp since the tool flashes the stock sense kernel. To my relief the phone booted right up no problem connected to the network and all but to my dissmay the wifi is STILL broken somehow it says error and will not switch on. Everything else seems to be working fine though. This is crucial there is no way I can go without wifi on my phone. I don't want to ruin anything further or permanitely but i do plan to move forward. My plan is to download a sense rom (MeanRom) which im doing now but it's taking forever on 3G. Wipe everything (using TWRP 2.2) Data Dav rom and use super wipe, and try to install MeanRom. If anyone has any other suggestions Im all ears. Also im alittle confused on the Hboot kernel limitations I know I have to use Flash GUI if Im going from a sense Rom to Aosp and vise versa but do I have to use it when say Going to a nandroid backup of a sense rom while currently on a Aosp rom because I couldnt find a boot.img file in my backup file when i used the tool to extract it. I hate S-On HTC really screwed us with this. And I hate my original evo which had S-Off for dying on me on the 15th day and me having to get this replacement with 1.15 im sorry guys I love this phone but it has become a nightmare and the Evo 3D was no walk in the park either. I apprectiate any comment from anyone this is the first time in almost 8 years of hacking I've been truely worried I may not be able to fix something.
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
You also might want to try a different rom with its corresponding boot img. I'm currently running Venom rom with its boot img file and its working great. Right now, it sounds like your kernel is what is giving you problems like mine, so flashing the correct boot img should fix it.
vel7wil said:
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
Click to expand...
Click to collapse
Thank you I'll be sure to try this out quick update, in TWRP recovery I had (force MD5 check on all zips?) checked now I don't remember checking it or if it came checked by default but as soon as I unchecked it I was able to run superwipe and flash MeanRom which both failed multiple times when it was checked on. Not sure if this was the cause of my problem but I agree I think I got a bad kernel in the CMX nightly. Either that or the Flash GUI app didnt exract the boot image properly. Either way I haven't been brave enough to try another AOSP rom man I hate having S-On my first Evo was perfect then I get stuck with this locked down replacement. One question though is that boot image for a stock/sense rom just wanna be sure.
vel7wil's advice worked for me I was having the same issue. Download the zip he recommends. Use flash image gui to flash the kernel and clear dalvik and cache. I just did a standard reboot after that and it said "android updating... apps x of xx" then everything was back to working.