Develop Bugs

Flashing a ROM won't work

So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?

When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?

cupfulloflol said:
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
Click to expand...
Click to collapse
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.

CheesieOnion said:
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
Click to expand...
Click to collapse
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.

CheesieOnion said:
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
Click to expand...
Click to collapse
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.

cupfulloflol said:
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
Click to expand...
Click to collapse
I got the rom from the topic here on XDA. It is the build from 19 november.
simms22 said:
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
Click to expand...
Click to collapse
In the instuctions in the ROM-topic it says it needs them and I also need them to use.

CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
Click to expand...
Click to collapse
install the gapps from the play store. you can flash without them, besides the ones that you cant get from the play store are included. you can try it, or just stay in your bootloop, its your call.

CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
Click to expand...
Click to collapse
Ah, my bad I didn't realize it was picked up by someone else, I see that now (which I thank you for the heads up that it is back in production). I was just making sure you weren't flashing something that wasn't ready for public use, and that it was a real ROM.

[Q] CM Nightly Doesn't update recovery

I'm not sure if this is intentional or not, and I couldn't find an answer with a search, but is updating Cyanogenmod with the zip files from get.cm supposed to also update the recovery in the phone at the same time?
I came from using Captivate before, and it updated the recovery as well with the updates, but so far I have not had a recovery update that has come trough a ROM update on my Galaxy S III. I can manually update the recovery trough ROM Manager if I need to, but I was not expecting to need to update recovery with it.

Metal_Koola said:
I'm not sure if this is intentional or not, and I couldn't find an answer with a search, but is updating Cyanogenmod with the zip files from get.cm supposed to also update the recovery in the phone at the same time?
I came from using Captivate before, and it updated the recovery as well with the updates, but so far I have not had a recovery update that has come trough a ROM update on my Galaxy S III. I can manually update the recovery trough ROM Manager if I need to, but I was not expecting to need to update recovery with it.
Click to expand...
Click to collapse
I've flashed cyanogenmod with twrp and it was flawless. Nothing went wrong. Twrp doesnt need much updates like CWM constantly does. but hey your choice!
Now to your question. I have flashed cyanogen mod with twrp and before i had twrp i flashed it with CWM i have never seen it update my recovery. Are you sure that was a feature on that nightly build?

amzi said:
I've flashed cyanogenmod with twrp and it was flawless. Nothing went wrong. Twrp doesnt need much updates like CWM constantly does. but hey your choice!
Now to your question. I have flashed cyanogen mod with twrp and before i had twrp i flashed it with CWM i have never seen it update my recovery. Are you sure that was a feature on that nightly build?
Click to expand...
Click to collapse
Well, I skim trough the patch notes, and I see patch notes about the recovery and how it's being updated in the github, and I was wondering why it wasn't being pushed to the devices at the same time as I update. But if they stopped including the CWM recovery with CM, it would make sense.

Metal_Koola said:
Well, I skim trough the patch notes, and I see patch notes about the recovery and how it's being updated in the github, and I was wondering why it wasn't being pushed to the devices at the same time as I update. But if they stopped including the CWM recovery with CM, it would make sense.
Click to expand...
Click to collapse
While I cannot answer your question myself, I can help elaborate with the hope you get a better response. The question posed here pertains to the recovery image for the ROM that holds the fresh boot image of all the system files ('factory reset')
I haven't spent any time researching how Android recoveries function - but when you update CM through the OTA updater, I believe it only patches modules in the system rather than updating the entire boot image itself - if they updated the whole package daily that would be terribly taxing on the person packaging and distributing the ROM, not to mention ISP bandwidth (I have never tried CM myself, so I couldn't tell you for certain if this is the way it works or not).
In any case, the OP is asking about the ROM image in recovery not the recovery itself (i.e. - TWRP, CWM, etc.) . Hopefully someone with a better understanding of Android can chime in for you.
Sent from my SGH-I747

I've been flashing CM roms for years, for different phones, and have never seen it include a recovery.

marinierb said:
I've been flashing CM roms for years, for different phones, and have never seen it include a recovery.
Click to expand...
Click to collapse
Alright, it might have been special for my Captivate then. Thanks for letting me know.

[Q] HTC One V (CDMA) continuously boots after flashing ROM

Any resolution to this problem? This has been reported in several threads (link 1, link 2, link 3, need I give more?)
I'm also experiencing the same problem. I installed Paranoid Android (per instructions here) and am now experiencing the same problem. After flashing, the phone continuously reboots. I am using an HTC One V (CDMA) from the US. I also flashed the JB 4.1.2 gapps with the ROM flash process.
When it boots, I receive two errors: "Unfortunately, android.process.acore has stopped working" and "Unfortunately, Contacts has stopped working". When I lock the screen, it reboots. When I try using it, it reboots after 30 seconds. If I just leave it alone, it reboots.
I have also tried several kernels with this same ROM (kernel that comes with the ROM, SuperSick [found here], and stock CM10) and they all just produced the same behavior.
I've looked all around. Some possibilities are: bad kernel, memory (RAM or otherwise) running out, bad install of ROM, or something no one has yet to define. I don't think its a bad kernel because this happens in 3 different ones. I don't think it's a memory issue because I lowered the CPU clockspeed and the phone has plenty of storage memory, and I've also flashed AOKP with the same results which rules out a bad ROM install.
I've wiped cache, system, data, and dalvik and followed all instructions as given to get a completely fresh installation. No avail. I realize that the One V isn't very popular, and there is only a limited amount of support for it but could anyone shed some light as to what the problem could be?? Perhaps some of the original devs who made the ROMs can help out us lowly fools who can't get it to work? I thank anyone in advance for being awesome and at least trying to help.

You may have to flash the old RUU. Look in the General subforum for a thread about phone rebooting after one minute.

sounds like you did the OTA update and have the new radio version, you need to RUU back to stock and dont get the OTA.

I'll try.
Thanks both of you! I will try flashing the RUU and I'll make sure to not install the OTA update. I'll post later with my results.

...
So... I flashed the RUU on the phone again. I again carefully followed instructions on how to flash ROMs (AOKP and Paranoid) and it simply doesn't boot. AOKP's ROM only starts up to a black screen. Paranoid boots to the boot screen animation and just hangs... I've used stock kernels, and tried the SuperSick kernel with both. No progress. Any other ideas?

Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.

Awesome!
riggerman0421 said:
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
Click to expand...
Click to collapse
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.

htc one v
filoxo said:
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
Click to expand...
Click to collapse
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?

lytesson said:
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
Click to expand...
Click to collapse
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.

filoxo said:
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
Click to expand...
Click to collapse
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?

I've got a similar issue (virgin mobile HTC One V)
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.

The OTA update reboots were fixed in the latest 4.2 SickleKernels.
Sent from my One V using Tapatalk 2

bheadrick said:
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
Click to expand...
Click to collapse
I think I'm having the same problem. The phone boots, gets as far as the "this build is for development purposes..." and then hangs for a few minutes and restarts, over and over. The flash with fastboot seemed to work fine and reported no errors.

EpicLordPhone said:
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
Click to expand...
Click to collapse
Yes. Do NOT install the update if you want to flash another ROM onto your device. Use the RUU to get the device back to factory; this will restore the original radio version. Then go through the steps to unlock the bootloader, root, and flash your ROM as desired. There are other forums which explain the mentioned processes better.
BeyondExistence says that this is fixed with a "4.2 SickleKernel", but as far as I'm aware there are no JB 4.2 ROMs for the HTC One V. Maybe a little more information would be in order?

Bheadrick:
I'm not quite sure what you mean when you say you flashed the stock recovery. The One V doesn't have a recovery when everything is stock.
You will have to RUU your device back (have you read any of the posts in this and other forums??). The process will reinstall the stock rom, relock your bootloader, remove the recovery, etc.
I recommend that you use Paranoid android's rom with the latest SuperSick kernel. Its been my favorite and most stable build I've used.
Sent from my Nexus 7 using xda app-developers app

So I found what BeyondExistence might have been talking about (for those of you who care/are currently having the bootloop problem and would rather go with this route). Its called RhythmicRom. This is a 4.2.2 ROM and it has some cool things for users switching from Sense to a more-pure Android [Link here]. Its based off of CM10.1 for the One V and it includes the BeatsAudio app (which most ROMs don't, as far as I know).
The reason I think that this is worth mentioning is because whoever runs into this bootlooping problem can simply SKIP the RUU process and just move onto this ROM. Hit thanks if this helped!

Newest OTA update.
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.

filoxo said:
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.
Click to expand...
Click to collapse
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.

tallnproud said:
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
Click to expand...
Click to collapse
Did you flash stock recovery and lock bootloader before running RUU?

Lsesp said:
Did you flash stock recovery and lock bootloader before running RUU?
Click to expand...
Click to collapse
I had flashed my stock recovery (although it was still boot-looping), and I did re-lock the bootloader before running the RUU.
I used the instructions found here.

[Q] How to (Re)Root Nexus Toro on KitKat 4.4

I update to Shiny's AOSP 4.4 ROM on the Verizon (Toro) nexus, and so far, I really like what I see. However ... I did something stupid .. I did not include the root update while in recovery, and now while my device boots KitKat AOK .. I cannot get into recovery.
So It looks like I need to re-root the device to be able to install recovery.
Since this process seems to be unique for every version of Android, would anyone have any tips on how to do this on KitKat? I did some searching, but did not come up with much.

dblml320 said:
I update to Shiny's AOSP 4.4 ROM on the Verizon (Toro) nexus, and so far, I really like what I see. However ... I did something stupid .. I did not include the root update while in recovery, and now while my device boots KitKat AOK .. I cannot get into recovery.
So It looks like I need to re-root the device to be able to install recovery.
Since this process seems to be unique for every version of Android, would anyone have any tips on how to do this on KitKat? I did some searching, but did not come up with much.
Click to expand...
Click to collapse
1. Wrong forum, this goes in Q&A.
2. Shut off the phone.
3. Hold both volumes and power and boot into the bootloader.
4. Use volume up/down to get into recovery, and hit power to select.
5. Recovery should still be there, flash SU.zip or whichever superuser you downloaded.
6. Reboot into rooted kitkat.
7. Read the full instructions next time.
If this doesn't work, go back and update recovery (if you haven't already), wipe, reflash and reflash root in the same step.

This did the trick ... THANK-YOU!

idefiler6 said:
1. Wrong forum, this goes in Q&A.
Click to expand...
Click to collapse
At least the title was descriptive and the post well written and to the point. Best newb post I've seen in a while. And for the record I would have just asked in the rom's thread not Q&A.

Mod please move this.?! THANK YOU!
♦ToroNex-Vanir

hotrodwinston said:
At least the title was descriptive and the post well written and to the point. Best newb post I've seen in a while. And for the record I would have just asked in the rom's thread not Q&A.
Click to expand...
Click to collapse
Why does that suddenly make it OK?

Magisk Manager Keeps Closing

Hey, folks.
I have a two day old Pixel 2 XL. I have unlocked it and an running the stock ROM (latest factory), but I have rooted it by installing Magisk (flashed a zip file).
I still have the stock recovery, I flashed by booting to twrp via fastboot command.
I keep getting an error that Magisk Manager Keeps closing.
Is there a known issue that I just have not read about yet?
I only rooted so I could use AdAway, but when I tried to check a few settings in Magisk today, this kept coming up.
I'll reboot and see if I can get into it again, but if there is a known "proper" fix, I'd appreciate some gentle assistance.
Thanks

Seems to open up fine after a reboot and passes safety net check.
No clue what causes the issue, but I can live with an occasional reboot.

myk.robinson said:
Seems to open up fine after a reboot and passes safety net check.
No clue what causes the issue, but I can live with an occasional reboot.
Click to expand...
Click to collapse
Are you on stock or custom kernel?

Badger50 said:
Are you on stock or custom kernel?
Click to expand...
Click to collapse
Stock. You and Az Biker helped me with unlocking, and I not flashed the Magisk zip. Still stock kernel and stock bootloader, and I flashed the latest factory image.

myk.robinson said:
Stock. You and Az Biker helped me with unlocking, and I not flashed the Magisk zip. Still stock kernel and stock bootloader, and I flashed the latest factory image.
Click to expand...
Click to collapse
Maybe flash a custom kernel, followed immediately by flashing magisk ???

Badger50 said:
Maybe flash a custom kernel, followed immediately by flashing magisk
Click to expand...
Click to collapse
I mistyped my response, i ONLY flashed the Magisk zip file.
Same prescription, though? Try a different kernel with Magisk again, after taking a backup, of course?

myk.robinson said:
I mistyped my response, i ONLY flashed the Magisk zip file.
Same prescription, though? Try a different kernel with Magisk again, after taking a backup, of course?
Click to expand...
Click to collapse
While backups are always good practice, you'd be fine without one for flashing a kernel+magisk. Unless of course you want to, which is never a bad thing

Badger50 said:
While backups are always good practice, you'd be fine without one for flashing a kernel+magisk. Unless of course you want to, which is never a bad thing
Click to expand...
Click to collapse
You probably already know what my next question will be
I'll read some kernel threads and check out the pros and cons. My main concern is that I retain the features and stability of the stock kernel. Just have bad memories of certain kernels on my Moto G4 Plus breaking the fingerprint reader and messing up the screen saturation
Thanks

myk.robinson said:
You probably already know what my next question will be
I'll read some kernel threads and check out the pros and cons. My main concern is that I retain the features and stability of the stock kernel. Just have bad memories of certain kernels on my Moto G4 Plus breaking the fingerprint reader and messing up the screen saturation
Thanks
Click to expand...
Click to collapse
The past is the past my friend. I will unequivocally just say that whatever custom kernel you choose, they are all extremely good and reliable. I haven't run the stock kernel since the custom ones came out. My battery life is excellent, and functionality is just perfect. Not to mention, that if you use the EXKM app, there's a few extra perks that you may like. If you want the latest Linux changes and updates go with Flash kernel. If you want to stay closer to stock Linux/Google code, then go with Snoke or Ex kernel. I'm not going to try and convince you on what to do, I'm just relaying personal experience my friend ??