Related
For two months I have tried to install Cm6 and currently shadow rom. Every time after install from clockwork or nandroid I get the same bootloop splash htc screen. I have installed other roms with no problem....there must be a common issue with cm6 & shadowrom. I have wiped full, cache, davlik and even formated system cache etc. I have a 2.x radio kouche kernel and newest hboot. I've tried changing sd cards etc. No avail......any suggestions would be appreciated.
SamuraiXDroid
I would try wiping dalvik/cache before the flash, flashing, then wiping dalvik/cache again before the first boot of the new rom. I would also suggest trying kings kernel or koush's test kernel by flashing them from cwm recovery directly after the rom.
Aside from that, I could only guess that you might have a corrupt area preventing a full install of your rom/kernel which isn't too uncommon but which I have no experience with. I've heard there are ways to get around this by building the kernel manually or by restoring it from another nandroid (say king's on a ruby nandroid? though I'd venture to guess Ruby would have the same problem), but it seems fairly difficult.
I'm not a developer, but I hope my suggestions can hope point you in the right direction. I'm using the latest nightlies of CM6 and they are awesome. I hope you get the chance to try it.
Thanks jaguox for such a quick reply. So I tried this.method on both cm6 and shadowrom. Wiped full wiped cache wiped davlik. Installed rom and gapp and kernel. Tried koush and kingkernal....wiped davlik...cm6 boot loop.....shadowrom brings me to android touch screen initial setup. I try to touch screen but my phone dosnt respond....screen freeze. Sussesful installs I've had are sky raider virtuous most.sense roms...the only froyo I have that works is ruby...my fav right now. I would love to have cm 6....I've posted on this forum a few times as well as cyanogen forum. I hope im not the only one with this.issue.......
SamuraiXDroid
Here are some more ways to potentially solve your problem. Again, I am not a developer so I am just mentioning a few solutions that might work, I am not entirely sure what is wrong with your device. I'm just trying to help you hammer away from all sides.
Are you wiping data manually too? People have noted success before where they had none before by wiping data/dalvik/cache twice before flash and once after. Not sure why this would solve anything but it is worth a try.
Try installing cyanogen without GApps (I do this anyways with the nightlies since it seems to be corrupt for some reason) and then installing them later if it boots correctly.
I use the Paid rom manager for the ease of use for nightlies, but here is a web link to the nightlies which you can try if you don't have paid: http://mirror.teamdouche.net/?device=inc They are more up to date and stable at this point than 6.0.2 was (for me at least). I am using build 100 and have tried the packaged in kernel, koush test 6, and adrynalyne's, and all work well.
Adrynalyne has another kernel for AOSP roms you can try: http://adrynalyne.us/?p=79
You can also try using the phone to reformat one of your SD cards just to eliminate that potential pitfall, though I don't think you would be getting that far anyways if it was not formatted correctly (Menu>Settings>SD card). This will wipe any data currently on your SD card.
Now, I would wait for someone else to provide confirmation that this should work since I haven't done it personally, but you could also try restoring boot.img from a Ruby Nandroid with KK1/2 installed (Install Ruby, install KK, make nandroid backup, install CM6 w/o Gapps, nandroid>advanced restore>select ruby nandroid>Restore boot). This should restore a working AOSP kernel for CM6/shadow to use however I am unaware if there are any other consequences. I also suggest KK or adrynalyne since I do not know what Ruby uses and KK and adrynalyne have both worked for me on CM6. The reason I think the kernel is not installing correctly is because your touchscreen is not working and AOSP roms use a different driver than sense roms for it. I could be completely off base however.
Also, out of curiosity, which radio version exactly are you using?
Hi Jaguox,
Thanks again for the help here is what I tried. I do own the market app ClockworkMod Revovery v2.5.0.5/rom manager. I came from Ruby 1.1.1 with the newest kouch Kernal and radio 2.15.00.07.28. I then wiped data, cache and dalvik twice. I then installed cm nightley 96&98/shadowrom (two seperate installs of course for each rom). I then installed Adrynalyne/Kingkernal kernals and wiped dalvik cache once more. I did not install gapps and let the rom boot. Interesting enough the roms bypassed the intial setup and booted to the home screen. But both roms with both kernals still would not let me have touch access to the screen. So I could see the roms but I couldnt touch them...aaaahhhhhhh the irony. I also tried a reformatted sd card.....same outcome. One time out of the hundred I have tried in the past two months allowed me to initiate my account in a cm nightly and access apps. I rebooted after a fix permission and got a boot loop. That was the farthest I have ever made it. Its strange that both these two roms that share the same dna give my phone the same effect. I appreciate anyones help in solving this mystery.
Thanks in advance!
?
SamuraiXDroid
Same issue on my Dinc. I have.wiped, rewiped and.still.the same out come on 2.1. I did not have this issue when I installed the first release of SR a while back. I have no other issues with other ROM's. Help?
Sent from my ADR6300 using XDA App
So shadow rom first release woked for you? There must be some common denominater for why our phones cannot take certain aosp roms? Ruby works but not cm6 or shadow......very strange.
So I think shadow rom found the fix to the issue I was having....hopefully this thread helps anyone in the same vote as me.
http://forum.xda-developers.com/showthread.php?t=808972
I was wondering if anyone could help me out please. I've tried searching the forums, but I haven't been able to find my exact issue. Basically, I feel as if my phone seems to have increasing issues with flashing through Clockwork Recovery; here's the details:
I originally rooted my phone using the Odin flash method. I flashed the Juggernaut available at the time, wiping data/factory, cache, dalvik, and battery stats through clockwork first, and letting it chill for 15 minutes with the first boot. I follow the same steps each time I flash another rom ( I've read that I should also wipe /system, but Juggernaut seems to do that itself, so I haven't ). A month and a half ago, I wanted to add a few things, so I wiped, then flashed the latest Juggernaut, rebooted, let it settle,and then flashed the ICS Ultimate Theme, no wipe, then after another settle, flashed the Pdroid zip ( no wipe ) I made with the v1.27 auto-patcher. Everything seemed to work flawlessly for a month or so, then I started having issues that just kept getting worse: phone freezing while installing market apps then unfreezing, camera lagging, random freeze & reboots, etc. I tried fix permissions, and no luck. I wiped and tried reflashing everything the way I had, and the phone kept freezing after the faux kernel loading screen. Installing Juggernaut or another rom by itself, or a nandroid restore, is the only thing that got it past boot. Not even themes flashed over roms that they're made for get past boot. I restored my phone to stock using this method, wiped both SD cards, and re-rooted then flashed Juggernaut again, but this time I used clockwork's wipes and darkside's super wipe before flashing, but I still can't flash anything but the rom itself without a boot loop, even with fix permissions. I had a similar issue on my old mytouch Espresso; consecutive flashes seemed to almost eat away at my phone and make things worse, but that phone also had hardware issues. I'm using a new MicroSD since then. Also, if it means anything, I tried flashing the new clockwork touch from the zip on these forums after these issues started, and it never took, however, flashing through Rom Manager's after I purchased it worked fine.
Sorry about the long post, but I wanted to detail everything I've tried that I could think of before bothering anyone here. Does anyone know what could be the issue? I would really appreciate some help, because this issue is really frustrating, and I have no idea what's causing it.
Could someone help me with this please? I can try and get a log cat if needed. I'm just really hoping to get to the bottom of these issues.
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
techfanatic9 said:
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
Click to expand...
Click to collapse
I'd like to point out that he does in fact use tdjs super wipe.
OP: have you tried other ROMs or kernels. In my past experiences, faux kernel did not meet my expectations so I moved along to another one. Give my configuration a go (refer to my signature) and let me know of the problem persists
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the replies!
techfanatic9 - I originally just wiped through clockwork ( before darkside superwipe was standard ), but now I use that too, and I'm still having those issues. I watched through the entire video just in case, and I'm doing it just like they say to.
iLeopard - I have tried Digital Warfare, but I still have the same issue when flashing things over it ( ICS Theme and/or PDroid ), even if it's supposed to be compatible, though I haven't tried kernels yet. I'll give your sig's setup a try and report back.
Meanwhile, could anything else be the issue? As you can probably tell, I've tried almost every mistake I could think of, and since my last phone had the same issue, a similar hardware issue seems unlikely.
All right, I've been running that ROM and kernel combo for a few days now. I don't seem to have any issues when I just flash the ROM and kernel, but I get stuck at the boot screen if I try to flash something else on top of it. Also, when I try to restore my text message backups through Gosms ( around 9800 texts that I want to keep ), the phone freezes halfway through the restore, and from that point on, the phone will freeze 5-10 minutes after rebooting, unless I reflash. I make sure I don't have the phone running and I leave it alone while restoring, and it doesn't help. I've only had this gosms issue since my flashing issue, and sometimes it restores fine.
Does anyone know what could be causing that?
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Gzerner said:
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Click to expand...
Click to collapse
K. The reason you aren't getting to the old version of CWM is because you flashed Codename. Codename is an AOSP ROM which has been known to cause bricks when flashing with Rogue. Because if the bricks the developers opted to but include CWM of any kind in the kernel. What you need to do is find a replacement ROM and download it. Once you've downloaded it you need to flash the EL26 stock CWM (you can find it in the OP of the link below) then use it to flash your new ROM.
http://forum.xda-developers.com/showthread.php?p=295021
Well you're at it is suggest reading the How Not To Brick Your Phone thread in general.
Good luck!
Codename rom is an AOSP rom so your external SD storage will be under /emmc and not /sdcard/externalsd. That's why it wasn't showing up. Same thing with CM9 and AOKP, not because it doesn't work. Also I wouldn't recommend flashing anything ICS related from rogue recovery, js.
And recoveries changed because with our phones, the recovery is packed into the kernel itself so when you flashed Codename, the recovery changed to the stock recovery included with the roms kernel. Hope that clears it up lol.
Sent from my SPH-D710 using Tapatalk
If you want a fresh install, the best way is to Odin the el29 kernal. From there, get into your recovery and wipe and flash away.
Sent from my SPH-D710 using XDA
so it seems that after I moved to an AOSP rom (and then came back) I have a lot of problems. One that is confusing is the fact that I have 2 animations (even after flashing factory ODIN stock rom).
I am getting the samsung swirly graphic animation followed by the sprint 4g lte animation. The funny thing is that the sprint music plays over the samsung animation and then the sprint animation is without sound. Why does the ODIN not clear that old animation?
Anyone else run into this? I cannot seem to clear it even after several factory resets.
P.S.... dont install an AOSP rom unless you want a lot of issues.
I'm not exactly sure what you're describing about the Samsung boot animation. Which aosp ruin did you install? We need to know so that we can have a reference and an idea on how to help, cause not all roms are created equal.
Secondly, the factory reset in recovery mode only clears user data. It doesn't reset your phone to out-of-the-box conditions. So factory testing a million times wouldn't change the boot animation (or the Rom, for that matter).
If you want to try to manually change the boot animation, there's a thread over in the themes and apps section of the Sprint s3 forums, or you can download Rom toolbox pro and they have the option in there.
Finally, most aosp roms are fairly stable. I've been running them exclusively for the past 5 months and they've gotten much more stable over that time. Yes, there are some inherit things that are less stable than on tw roms, but all-in-all, they're fairly stable. The good thing about nandroid backups is that we can flash any number of roms and always go back to something we love. That is, assuming you made a nandroid backup.
Sent from my SPH-L710 using xda app-developers app
edufur said:
so it seems that after I moved to an AOSP rom (and then came back) I have a lot of problems. One that is confusing is the fact that I have 2 animations (even after flashing factory ODIN stock rom).
I am getting the samsung swirly graphic animation followed by the sprint 4g lte animation. The funny thing is that the sprint music plays over the samsung animation and then the sprint animation is without sound. Why does the ODIN not clear that old animation?
Anyone else run into this? I cannot seem to clear it even after several factory resets.
P.S.... dont install an AOSP rom unless you want a lot of issues.
Click to expand...
Click to collapse
I would suggest doing a FULL Wipe before Flashing when switching from AOSP, to TW. Or vis versa. It sounds like you have a bad flash.
What I do is :
DALVIK CACHE
CACHE PARTITION
FORMAT SYSTEM
FORMAT SD:EXT
FORMAT DATA
FORMAT CACHE
THEN WIPE ALL USER DATA/FACTORY RESET
I guess I should have been clear. I did a full wipe both ways... full wipe before installing AOSP (CM10 Stable), and a full wipe when I came back... and factory restore after odin. Even cleared internal storage. Nothing restores the original boot animation. Is there a way to make this thing fully stock out of the box?
Even since the CM10 flash (stable build), my battery now drains faster and GPS locks slower and drifts... it used to not drift.
You can flash freeza's Stock Rooted Rom. The link is below.
http://forum.xda-developers.com/showthread.php?t=1910947
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
You can flash freeza's Stock Rooted Rom. The link is below.
http://forum.xda-developers.com/showthread.php?p=2586
Click to expand...
Click to collapse
Could you explain to me how a stock rooted rom is closer to out of the box than the shipped rom which has been factory reset?
Does his stock rooted ROM guarantee to remove the double animation and return the ROM to the original single sprint animation?
And will his rom somehow fix the anomalies that started after I flashed CM10? If so, how does it accomplish what the shipped ROM wont?
edufur said:
Could you explain to me how a stock rooted rom is closer to out of the box than the shipped rom which has been factory reset?
Does his stock rooted ROM guarantee to remove the double animation and return the ROM to the original single sprint animation?
And will his rom somehow fix the anomalies that started after I flashed CM10? If so, how does it accomplish what the shipped ROM wont?
Click to expand...
Click to collapse
What exactly do you mean by "shipped rom" from out of the box? What Android version was it? I know our phones originally shipped with Android 4.0.4, so if you're flashing a "true" out-of-the-box Rom, it'd be 4.0.4. Please help me understand what you've done so that I can help you fix it.
Was the "out-of-the-box" Rom a TAR file that you flashed via Odin? Where did you get it from? I'm getting a little confused when you say you did a "full wipe" (which is typically done in Recovery), but then flashed a Rom through Odin. Typically, people only use one or the other. It's making it more difficult to understand exactly what you did, and therefore it's making it difficult for me (and others) to help you.
As far as your most recent questions: I can't guarantee anything. I'm just a guy who has done a lot of work on his phone who is trying to help you out here. At the end of the day, I have about a 90% passing rate when I give people help (and they actually follow it). And when my directions don't work, I typically stick around and keep helping until they do get their phone working (or until someone else, like Ed or CNexus, picks up the case).
I can say that Freeza's stock rooted rom works exactly like a stock phone (with all updates), but just with Root. It should give you back the stock boot animation and reset everything to stock. The file you want is:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMD4
MD5: 77262D9D6CF1A6AF30A8981A95A75D57
Click to expand...
Click to collapse
You might as well flash the latest baseband/modem. That file is:
MD4 Firmware:
MD4 Firmware/modem/baseband update
MD5: EEEAFDBE59CF9C5B492B1A591EC92D02
Click to expand...
Click to collapse
Well then I appreciate your attempt to help, but that doesn't resolve my problem. I'm sure it can resolve other people's problems (if their problem isnt a double animation problem).
To answer you questions, there are 2 stock roms available that are considered "shipped" ROMS... as in... what the ROM was shipped with. Those ROMS can be flashed via odin and are featured in many of the threads here. When a person flashes these ROMs with odin, it covers everything... recovery, radio, kernel, etc. It removes custom recovery and root. After flashing, one would do a factory reset, either in the rom after it boots, or from the stock recovery. This brings you as close to "out-of-the-box" as you can get... "out-of-the-box" means the way it was when you bought it and opened the box. The problem I am having... is that even after this process, I still have a double boot animation. The samsung with a swirl, and the sprint 4g with flying wires.... and the sprint music plays out of sequence with the sprint part of the animation.
I hope this clears things up for you.
I dont need a new rooted or custom rom... what I do need is to get back 100% to out-of-the-box state. I am close, but the animation is obviously not covered when flashing a shipped rom.
edufur said:
Well then I appreciate your attempt to help, but that doesn't resolve my problem. I'm sure it can resolve other people's problems (if their problem isnt a double animation problem).
To answer you questions, there are 2 stock roms available that are considered "shipped" ROMS... as in... what the ROM was shipped with. Those ROMS can be flashed via odin and are featured in many of the threads here. When a person flashes these ROMs with odin, it covers everything... recovery, radio, kernel, etc. It removes custom recovery and root. After flashing, one would do a factory reset, either in the rom after it boots, or from the stock recovery. This brings you as close to "out-of-the-box" as you can get... "out-of-the-box" means the way it was when you bought it and opened the box. The problem I am having... is that even after this process, I still have a double boot animation. The samsung with a swirl, and the sprint 4g with flying wires.... and the sprint music plays out of sequence with the sprint part of the animation.
I hope this clears things up for you.
I dont need a new rooted or custom rom... what I do need is to get back 100% to out-of-the-box state. I am close, but the animation is obviously not covered when flashing a shipped rom.
Click to expand...
Click to collapse
When Flash, or ODIN the Stock Rom it should include the Stock bootanimation. But since the issue still persists. You can go to THIS thread and get the Stock bootanimation. Also you can use a File Explorer to navigate to system / media to make sure that the permissions are set, and that you only have one file in there.
prboy1969 said:
When Flash, or ODIN the Stock Rom it should include the Stock bootanimation. But since the issue still persists. You can go to THIS thread and get the Stock bootanimation. Also you can use a File Explorer to navigate to system / media to make sure that the permissions are set, and that you only have one file in there.
Click to expand...
Click to collapse
That's the animation that is currently on my phone and is followed by the sprint (Original) animation. The animation you link is not the one that is supposed to be on the phone... only the sprint one should be. The is the problem I am having... I have both on there. I need to figure out how to remove the other one.
edufur said:
That's the animation that is currently on my phone and is followed by the sprint (Original) animation. The animation you link is not the one that is supposed to be on the phone... only the sprint one should be. The is the problem I am having... I have both on there. I need to figure out how to remove the other one.
Click to expand...
Click to collapse
Using a File explorer navigate to system / media. Then delete the one you do not want, and reboot. It should be back to normal.
TEAM MiK
MikROMs Since 3/13/11
What's up everyone? I am having a strange problem when trying to flash just about any kernel on my N7. While I'm not a developer or anything, I'm not new to flashing ROMs or Kernels by far. In fact, my love affair with smartphones began when I got an HTC Apache with Windows Mobile 5. Anyway, every time I try to flash a kernel, it will show successful, and then the phone will boot into a fuzzy/pixelated light blue screen. Eventually, this screen will go away and my device will be pretty much locked up. All the images will have turned blue and orange, and the only way for me to get back into recovery will be to hold volume down + power, until the phone shuts off. The only kernel I have had any success with is Glitch, and I have even had this happen with it a couple times.
I always make sure to read through the instructions, and have done lots of searching here, and via Google. After I flash a rom, I will make sure the N7 boots up, and works properly, then reboot into recovery, do a full wipe, and flash the zip from TWRP. My most recent attempt was with Buttered AOKP w/Aroma installer. It walks you through the steps in a manner that should make this easy for anyone. It give you the option to wipe cache and kernel, which I always do, but no go. The only way I can get Glitch to run on it, is to complete the whole process twice.
Sorry if the answer is right under my nose, but I couldn't take it anymore and had to ask. I've never once bricked a device, nor have I had issues flashing kernels on any device before. Somebody please restore my sanity!!! I didn't have much to begin with.
yamus08 said:
What's up everyone? I am having a strange problem when trying to flash just about any kernel on my N7. While I'm not a developer or anything, I'm not new to flashing ROMs or Kernels by far. In fact, my love affair with smartphones began when I got an HTC Apache with Windows Mobile 5. Anyway, every time I try to flash a kernel, it will show successful, and then the phone will boot into a fuzzy/pixelated light blue screen. Eventually, this screen will go away and my device will be pretty much locked up. All the images will have turned blue and orange, and the only way for me to get back into recovery will be to hold volume down + power, until the phone shuts off. The only kernel I have had any success with is Glitch, and I have even had this happen with it a couple times.
I always make sure to read through the instructions, and have done lots of searching here, and via Google. After I flash a rom, I will make sure the N7 boots up, and works properly, then reboot into recovery, do a full wipe, and flash the zip from TWRP. My most recent attempt was with Buttered AOKP w/Aroma installer. It walks you through the steps in a manner that should make this easy for anyone. It give you the option to wipe cache and kernel, which I always do, but no go. The only way I can get Glitch to run on it, is to complete the whole process twice.
Sorry if the answer is right under my nose, but I couldn't take it anymore and had to ask. I've never once bricked a device, nor have I had issues flashing kernels on any device before. Somebody please restore my sanity!!! I didn't have much to begin with.
Click to expand...
Click to collapse
Flashing a CAF kernel on an aosp Rom or a aosp kernel on a CAF Rom. What Rom are you on? (cynanogen based roms are CAF)
Sent from my Nexus 7 using Tapatalk 4
xfrancis14 said:
Flashing a CAF kernel on an aosp Rom or a aosp kernel on a CAF Rom. What Rom are you on? (cynanogen based roms are CAF)
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Currently on: [ROM] Buttered Flo AOKP 4.3.1 [+Aroma] [2013-10-12]
It has all the kernels built into the aroma installer, so I would assume they are all compatible. Some more than others.
I got 3.4.1 Glitch-Flo to run on it, but had to return phone to stock, and flash twice, to get it to work. The aroma installer also has the option to use Faux Kernel in one of three flavors. I tried the "Ultra CCCCCCOMBO" first, and then the "Enhanced Stock", but no go.
When I go to the thread for both kernels, it says they are CAF kernels, but it's kind of strange they they would be included as an option in the rom. I have tried a few other roms, with various kernels too, and not had any luck. I want to get a log to post, but I'm not sure if I will be able to pull it via ADB, when the device is pretty much unresponsive.
Thanks for your response, and let me know if what you think about the CAF kernels being inlcuded with the AOKP rom.
Thanks,
Yam
Sooooo..... Isn't aokp based of the cm kernel? If that's the case, any of the kernels I am trying should work. I would post this in the ROM thread, but its happened with just about every ROM kernel combination in have tried. What's the dealio
Any update on this? I am having the exact same problem with my Nexus 4 running ProBAM 2.0 ROM. I have tried flashing every kernel and every version possible and it either freezes before boot (Google logo) or I get the blue screen... help anyone? I really want to flash a kernel with FauxSound, that's really all I want. Thanks so much!