Develop Bugs

[GUIDE] 2e recovery and Tegrak's kernel !!!BACKUP BEFORE PROCEED!!!

THERE WERE AT LEAST TWO REPORTS OF SYSTEM FAILURE AFTER THIS UPDATE, BOTH HAD LAGFIX ENABLED.
!!!BACKUP BEFORE PROCEED!!!
This guide is to help those who would like to test tegrak's kernel but have dowbts about losing ability to flash zip files from CWM. This will also help those who would like to have simple root solution, and 2e recovery on froyo.
a) If you want to have simple root solution, one click lagfix and 2e recovery. Tested with Doc's v9.1.4 but should work on any rom including stock
1. flash tegrak's kernel found here http://forum.xda-developers.com/showthread.php?t=920711 using Odin (all instructions in tegrak's thread)
2. install Tegrak lagfix app from the market and install root from the app's menu
3. download attached file
4. extract this file saving directory structure and copy it's system folder into /sdcard/tegrak/update/00/ (If this path doesnt exist, create those folders) so your path should look like /sdcard/tegrak/update/00/system/...
5. reboot your phone into tegrak's recovery (simply reboot your phone and press home button when you see tegrak's kernel introduction)
6. (before proceed with this step backup your system partition from the same tegraks recovery) choose update from sdcard and select 00 folder
7. Install Rom Manager from the market and flash CWM from it. Now you have tegrak's kernel and CWM to flash all types of zip files.
a) If you already rooted your phone
1. flash tegrak's kernel found here http://forum.xda-developers.com/showthread.php?t=920711 using Odin (all instructions in tegrak's thread)
2. install Tegrak lagfix app from the market
3. download attached file
4. extract this file saving directory structure and copy it's system folder into /sdcard/tegrak/update/00/ (If this path doesnt exist, create those folders) so your path should look like /sdcard/tegrak/update/00/system/...
5. reboot your phone into tegrak's recovery (simply reboot your phone and press home button when you see tegrak's kernel introduction)
6. (before proceed with this step backup your system partition from the same tegraks recovery) choose update from sdcard and select 00 folder
7. Install Rom Manager from the market and flash CWM from it. Now you have tegrak's kernel and CWM to flash all types of zip files.
All this process replaces your 3e recovery with 2e recovery image and as tegrak's kernel does not overrides original recovery image your CWM will be untouched by tegrak's kernel, and you will successfully have combination of two recoveries (CWM and Tegrak's) To access CWM you can chose "reboot in recovery" from the Rom Manager menu or from Tegrak lagfix menu, and to access tegrak's recovery, press home button when you see tegrak's kernel introductory window while booting up your phone.

Brack11, thanks for the guide, but you should be posting this over to the general subforum.
Sent from my GT-I9000 using XDA App

g00ndu said:
Brack11, thanks for the guide, but you should be posting this over to the general subforum.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I think it's too advanced and dangerous for novices that mostly visit general. Also both described things 2e recovery and tegrak's kernel are from the area of development, this is all about customizing rom. I dont agree that it should be in general.

Thanks a lot!!

I also fail with barebone rom with incorporated tegrak kernel in 3e recovery,**** m8 spend all day to fix it & get back to insanity rom
10ks m8 for your efort

hensk said:
I also fail with barebone rom with incorporated tegrak kernel in 3e recovery,**** m8 spend all day to fix it & get back to insanity rom
10ks m8 for your efort
Click to expand...
Click to collapse
As I understand this fix didn't work for you, could you share to others what and how has failed?
Sent from my GT-I9000

no, no mate, just did not know that there is
thread like this,with fix solution

hensk said:
no, no mate, just did not know that there is
thread like this,with fix solution
Click to expand...
Click to collapse
Glad to hear that this works for you, thanks are accepted
Sent from my GT-I9000

brack11 said:
Glad to hear that this works for you, thanks are accepted
Sent from my GT-I9000
Click to expand...
Click to collapse
Point to note, this may even be only me.
The CWM does not reside in the kernel. Rebooting through recovery will only bring back to 2e. I need to apply update.zip again, reboot through recovery to get CWM. This happens everytime when going to recovery.
Sent from my GT-I9000 using XDA App

g00ndu said:
Point to note, this may even be only me.
The CWM does not reside in the kernel. Rebooting through recovery will only bring back to 2e. I need to apply update.zip again, reboot through recovery to get CWM. This happens everytime when going to recovery.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You are right, this has nothing to do with tegraks kernel or with recovery, I has this issue when I has rooted phone without custom kernel. It would always go to standard recovery and then I would have to apply update. I believe thoa is some special feature of the device.
Sent from my GT-I9000

brack11 said:
You are right, this has nothing to do with tegraks kernel or with recovery, I has this issue when I has rooted phone without custom kernel. It would always go to standard recovery and then I would have to apply update. I believe thoa is some special feature of the device.
Sent from my GT-I9000
Click to expand...
Click to collapse
Iirc, when I use Rom Manager the last time, it wasn't like that at all. Reboot let me goes directly to CWM. I only need to download it and apply it once.
Sent from my GT-I9000 using XDA App

g00ndu said:
Iirc, when I use Rom Manager the last time, it wasn't like that at all. Reboot let me goes directly to CWM. I only need to download it and apply it once.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Well, the tegraks kernel doesn't really replaces kernel, and if the kernel is stock you get thesame behaviour as you should have with the stock kernel, as I say, I never had rommanager be as default recovery, always either through update.zip or custom kernel (which is not custom in tegraks case)
Sent from my GT-I9000

brack11 said:
Well, the tegraks kernel doesn't really replaces kernel, and if the kernel is stock you get thesame behaviour as you should have with the stock kernel, as I say, I never had rommanager be as default recovery, always either through update.zip or custom kernel (which is not custom in tegraks case)
Sent from my GT-I9000
Click to expand...
Click to collapse
I understand, back in the days before the speedmod, voodoo or even the oc kernels, i installed the ROM manager and had made CWM as the default recovery. Anyway, it is still okay, I guess. Btw, using tegrak's kernel, have you tried using update zips via cwm?
I have not tried it yet, since I find that updating via tegrak method works very well for me.

g00ndu said:
I understand, back in the days before the speedmod, voodoo or even the oc kernels, i installed the ROM manager and had made CWM as the default recovery. Anyway, it is still okay, I guess. Btw, using tegrak's kernel, have you tried using update zips via cwm?
I have not tried it yet, since I find that updating via tegrak method works very well for me.
Click to expand...
Click to collapse
Yes, I used a few times to flash different modems and r64 theme.

Unfortunately this did not work for me (XWJS5), got stuck on initial splash screen, luckily Dean-O's post http://forum.xda-developers.com/showpost.php?p=10562493&postcount=80 saved my ass.
I've been unable to get 2e recovery working on a bear-bones kernel since XXJPY.

fomofo said:
Unfortunately this did not work for me (XWJS5), got stuck on initial splash screen, luckily Dean-O's post http://forum.xda-developers.com/showpost.php?p=10562493&postcount=80 saved my ass.
I've been unable to get 2e recovery working on a bear-bones kernel since XXJPY.
Click to expand...
Click to collapse
Did you have lagfix enabled? As I can say from my own experience.now - this hack is DANGEROS if you have lagfix enabled. To say more any manipulations with recovery while on onenand fix - DANGEROUS AND LEAD TO LOOSING ALL PARTITIONS
Sent from my GT-I9000

brack11 said:
Did you have lagfix enabled?
Click to expand...
Click to collapse
No, I have used the "hack" recovery 2e method with success right up until JPY, but JS3, and now JS5 does not work.
It seems to me (just learning Android), that it doesn't have write permissions to the /sbin directory, which is what the recovery script needs.
Recovery 2e works with CF-root, but I already have root, and rather not overwrite the stock kernel.

Ok, yesterday I have thoroughly tested my workarounnd for installing rom. I hade Doc's 9.6 downloaded 9.8 reboot into recovery using rommanager option, wiped cach partition, wiped dalvik, wiped data, flashed 9.8, wiped data again, and flashed again, rebooted, restored titanium backups, flashed tegrak's kernel, flashed update for recovery 2e from within tegrak's kernel, then rebooted into 2e recovery, flashed new modem (JVE) and flashed theme r64, rebooted, everything works as it should no errors no hangs no loops.

Does this still work?

The Best Kernel To Flash On ParanoidAndroid?

Hi all, I'm searching the best kernel to flash it on the latest version of ParanoidAndroid. What kernel do you suggest me?

Frenix27 said:
Hi all, I'm searching the best kernel to flash it on the latest version of ParanoidAndroid. What kernel do you suggest me?
Click to expand...
Click to collapse
With ParanoidAndroid being a modded version of CM9, I'd say stock CM or whatever PA runs.

Using Fanco Kernel with Linaro 194 10pc 512
The speed is amazing and also the battery backup.
you can also use AirKernel 1.9 from here
http://forum.xda-developers.com/showthread.php?t=1663332
its compatible with PGM2 Nexus

gautam_nexus said:
Using Fanco Kernel with Linaro 194 10pc 512
The speed is amazing and also the battery backup.
you can also use AirKernel 1.9 from here
http://forum.xda-developers.com/showthread.php?t=1663332
its compatible with PGM2 Nexus
Click to expand...
Click to collapse
Thanks very much, I think I'll try Franco kernel with Linaro.
Bye!

Oh no, I have flashed Linaro and my phone doesn't work! It go in bootloopand can't turn on it! Help me! How can I do??
P.s. Fortunately I can go in recovery and I remember I have an old backup! Problem solved (I think)

Frenix27 said:
Oh no, I have flashed Linaro and my phone doesn't work! It go in bootloopand can't turn on it! Help me! How can I do??
Click to expand...
Click to collapse
Enter your recovery, then either flash another kernel if you have one, or reflash whatever ROM you're using to get back the kernel or reapply your nandroid backup if you have one.
Back cover off
Battery out
Battery in
Press and hold the power button and volume up + down
In the fastboot menu, scroll to "recovery" with the volume keys and then finally press the power button to boot into the recovery.
The matter is most likely that your phone cannot handle the 10% static board overclock as in the kernel gautam_nexus had attached.

Just a question: when I am in recovery, can transfer some files from pc to nexus??

Frenix27 said:
Just a question: when I am in recovery, can transfer some files from pc to nexus??
Click to expand...
Click to collapse
Currently, no. USB mass storage doesn't exist on the Nexus, and I have yet to see an option to enable MTP through clockworkmod.
EDIT: Wait, you can send stuff through ADB for sure provided you have ADB set up and working.
EDIT2: Say you wanna send file.txt (just an example), then you would do the following:
adb devices (to see if you actually have adb access)
adb push path-to-file.txt /mnt/sdcard/
EDIT3: Check my sig for drivers or how to set up something called knives and forks.

Ah ok, so I can't through recovery but there is another way. Ok thanks. So, coming back to my question, a GOOD kernel I can flash on Paranoid??
Please don't give me a dangerous kernel

I've been running it with the stock CM9 kernel for a few weeks (since before it changed to come with that in 1.4), and it was smooth, responsive, and good battery life. I have just (literally 30 minutes ago) decided to try CM-plus. No troubles so far....

Frenix27 said:
Ah ok, so I can't through recovery but there is another way. Ok thanks. So, coming back to my question, a GOOD kernel I can flash on Paranoid??
Please don't give me a dangerous kernel
Click to expand...
Click to collapse
I'd say GLaDOS kernel gets the job done on just abut any ROM.

Can't Install or Update Apps on CM10

Anyone else running CM10 on their Dinc2 having problems installing updates from Google Play? Even after force stopping the Download Manager [4.1.1-eng.evan.20120730.150512] and clearing its data...updates stall while attempting to download.
Phone: Droid Incredible 2
OS: Jelly Bean 4.1.1
ROM: aeroevan CM10 7/30 build
Kernel: aerovean ICS v12

Kingsley1 said:
Anyone else running CM10 on their Dinc2 having problems installing updates from Google Play? Even after force stopping the Download Manager [4.1.1-eng.evan.20120730.150512] and clearing its data...updates stall while attempting to download.
Phone: Droid Incredible 2
OS: Jelly Bean 4.1.1
ROM: aeroevan CM10 7/30 build
Kernel: aerovean ICS v12
Click to expand...
Click to collapse
I haven't seen this problem, or heard of it on this rom, but...it was common on a lot of ICS roms. If the download never starts try this:
1. Open Terminal Emulator
2. Type "su" and hit enter
3. Type "killall drmserver" and hit enter
4. Close Terminal Emulator and try installing the app update again.
If it is a problem actually seeing your apps in play, there is a different workaround, but it doesn't sound like this is your issue.

gtdtm said:
I haven't seen this problem, or heard of it on this rom, but...it was common on a lot of ICS roms. If the download never starts try this:
1. Open Terminal Emulator
2. Type "su" and hit enter
3. Type "killall drmserver" and hit enter
4. Close Terminal Emulator and try installing the app update again.
If it is a problem actually seeing your apps in play, there is a different workaround, but it doesn't sound like this is your issue.
Click to expand...
Click to collapse
Thank you so much! Everything is actually downloading!

Kingsley1 said:
Thank you so much! Everything is actually downloading!
Click to expand...
Click to collapse
Glad it helped, and you probably want to memorize that sequence. You may have to do it every reboot. It's pretty hit or miss, and some roms have it and others don't.

gtdtm said:
Glad it helped, and you probably want to memorize that sequence. You may have to do it every reboot. It's pretty hit or miss, and some roms have it and others don't.
Click to expand...
Click to collapse
Is there anyway I can make this change permanent?

Kingsley1 said:
Is there anyway I can make this change permanent?
Click to expand...
Click to collapse
I don't think anyone has discovered a way, except that down the line it will likely be fixed in the rom.

It seems to happen pretty infrequently, it hasn't happened to me yet.

It happens to me every time I have to reboot my phone. The code helps, and is thankfully easily memorized.
EDIT: I wonder if this is related to downgrading HBOOT from 98? I'm not too savvy how all that stuff works, but I know that was an unusual circumstance. Kinglsey1, did you downgrade?

nymthiriel said:
It happens to me every time I have to reboot my phone. The code helps, and is thankfully easily memorized.
EDIT: I wonder if this is related to downgrading HBOOT from 98? I'm not too savvy how all that stuff works, but I know that was an unusual circumstance. Kinglsey1, did you downgrade?
Click to expand...
Click to collapse
Yeah, I downgraded my Stock Gingerbread ROM so I could root my phone. Then flashed CM9, and eventually CM10. What makes you suspect downgrading is the cause of the drmserver running afowl?

Hboot has nothing to do with it, everyone who is S-OFF had to downgrade it. I'm sure you could make an init.d script to do it on boot, or use script manager to run a script on boot. I'd do it but I'm not at my computer right now.
Sent from my Incredible 2 using Tapatalk 2

Kingsley1 said:
Yeah, I downgraded my Stock Gingerbread ROM so I could root my phone. Then flashed CM9, and eventually CM10. What makes you suspect downgrading is the cause of the drmserver running afowl?
Click to expand...
Click to collapse
As I said before, I don't really know how all of it works, but I just thought that it may have since when I was looking to get S-OFF, downgrading HBOOT from 98 to 97 wasn't a usual thing to do, and neither was having this error.

Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1610741

Is there another option other than the killall drmserver? I've tried that and the problem still persists. I'm able to open the store and see my apps. When I attempt to download I get an error.
---------- Post added 18th August 2012 at 12:01 AM ---------- Previous post was 17th August 2012 at 11:41 PM ----------
stnkyminky said:
Is there another option other than the killall drmserver? I've tried that and the problem still persists. I'm able to open the store and see my apps. When I attempt to download I get an error.
Click to expand...
Click to collapse
I was able to get apps to load by just flashing the ROM and not the JB apps img. Seems to be working now.

upgrade gapps
hi , i installed cm10 and the gapps from the bootmenu after some use i found them buggy so i downloaded a difrent newer version how do i upgrade them is it just matter of installing them from the boot menu? or shoud i do something else thanks
ps.
the original file is 60mb
the new is 80 mb
would this make a diffrence

migueldefy said:
hi , i installed cm10 and the gapps from the bootmenu after some use i found them buggy so i downloaded a difrent newer version how do i upgrade them is it just matter of installing them from the boot menu? or shoud i do something else thanks
ps.
the original file is 60mb
the new is 80 mb
would this make a diffrence
Click to expand...
Click to collapse
1.) You should be able to install these new gapps from CWM Recovery:
Reboot your phone and start Recovery
>>install zip from sdcard >> choose zip from sdcard >> Choose your new gapp zip file >> Choose Yes
2.) This thread is dead.

CWM Problem

Hi Folks,
long away since my DHD and now back with an Galaxy Nexus. On first day manually changed to an yakju (instead of yakjuxw) to have 4.1.1 installed. And on this way flashed CWM and Radio too. Now i have a big problem: With CWM 5.5.0.2 (latest in the Tutorials) all works fine (Backup needs a lot of time and have a believable size after it). When i use my ROM Manager License and install 6.0.0.1 (touch or not) the Backup runs for about 1 minute and it has a size of about 20MiB (witth CWM 5.5.0.2 over 700 MB). When i watch the files in the backup i see only two images (boot, recovery) and the rest has an ending with .ext4.up and has little filesize. It seems 6.0.0.1 cannot save the partitions like system & data . Anyone else ? In the meanwhile i flashed backup to the old CWM (via fastboot) and this works fine.
Thanks a lot!
Stefan

It's not a problem, it's the new feature.
Read more here
https://plus.google.com/103583939320326217147/posts/L5aVZe7C9vg

To be honest, I dont like to use ROM Manager. I think it's useless.

lutyz said:
To be honest, I dont like to use ROM Manager. I think it's useless.
Click to expand...
Click to collapse
This thread is not about Rom Manager, it's about ClockworkMod recovery. However, I don't like to use Rom Manager either

buzzcomp said:
It's not a problem, it's the new feature.
Read more here
https://plus.google.com/103583939320326217147/posts/L5aVZe7C9vg
Click to expand...
Click to collapse
this
I personally hate the new way, but of course, my opinion.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

kyokeun1234 said:
this
I personally hate the new way, but of course, my opinion.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
I don't like it either. I like the good old school

[ROM+Kernel][MAY 16, 2020] AOSP direct, Marshmallow 6.0 & NEW kernel, version 3.4.99

[ROM+Kernel][MAY 16, 2020] AOSP direct, Marshmallow 6.0 & NEW kernel, version 3.4.99
****UPDATE****
As of May 16, 2020, If you already have this ROM installed, please see this link for an updated kernel to version 3.4.99 with other various editions and Extras. If you are downloading and installing this ROM for the first time download the ROM and Flash it, and finish setting up your device before updating the kernel. You will have to flash Superuser or Magisk again (or whatever your root preference is) after installing the ROM or boot image regardless of whether you're coming from a fresh installation or updating the kernel.
The number of ROMS for the Nexus 10 has dwindled, and those that do remain, have too many bugs and not everything works. I spent a couple weeks looking for a good ROM and finally found one. I did NOT build this ROM, however I DID build the kernel from scratch.
What you get:
- Android 6.0, Marshmallow ROM built directly from the AOSP source code. (built by Dmitry.GR)
- Freshly updated kernel from 3.4.67 to 3.4.99, built by Me from source. I used the Manta kernel source (3.4.67) from Omnirom's android-6.0 branch and applied the official kernel patches 3.4.67-68 through 3.4.98-99. SELinux in the boot image provided by the ROM is disabled. Standalone updated kernel/boot image is permissive). Kernel in its original form, would not allow for a permissive selinux so the only option was to disable it.
- In the updated boot image, ADB is insecure (ro.adb.secure=0 and ro.secure=0). This allows for an automatic root shell when running 'adb shell'. It also allows you to remount the filesystem RW through ADB, using the command 'adb remount'.
- No swap or zram options on the original kernel because it was not performing properly. This is fixed on the standalone upgrades to the kernel I have been doing.
What doesn't work:
- Location services may or may not work. If they don't, let me know as I do have a fix for that. For some reason, com.google.android.gms was removed from the framework-res (android system apk). Some apps won't recognize the device GPS and may tell you location is turned off when it actually isn't.
- The camera work however oh, there is an issue with the flash. Every time you use flash the camera will crash after snapping the photo. This wouldn't be a problem except the photo doesn't get saved. I don't know what's causing it and until I can figure that out you can't use the flash on your camera.I have a suspicion or two but I haven't looked into it because I don't use the camera often enough and when I realized the problem I'm never at home to look.
Installation requirements and instructions:
Required:
1. Unlocked bootloader
2. TWRP custom recovery
3. PC with either Windows or Linux
Instructions:
1. You need to wipe the device completely. Boot to recovery, select wipe, format data and type yes and confirm. When done, tap home, wipe, advanced wipe, select all and swipe to confirm. Tap home, reboot, reboot recovery.
2. Once booted back to recovery, plug your tablet into your PC. It should be recognized.
3. Download Open Gapps, ARM, 6.0, Pico and place it on the tablet's internal storage.
4. Download the TWRP flashable zip that contains the ROM and place it on internal storage.
5. Download the boot.img which contains the new Kernel, place in storage.
6. Download SuperSU zip and place in storage.
7. Once done, tap the home button then install. Select the TWRP flashable ROM zip and install it. When done tap home again, install, install image and select image-new.img and install.
8. When finished tap home and install and install Open Gapps. When finished install SuperSU then reboot system when finished.
Kernel installation and updates ONLY
1. Download and extract the zImage from the provided zip at the end of the post.
2. You need to unpack the boot image from the ROM above. You can do this on Windows Linux or your own Android device with the Android image kitchen by XDA developer @osm0sis. After unpacking the image, open the folder named 'split image' and locate boot.img-zImage. make a copy of it and put it somewhere safe, then delete it from the split image folder.
3. Now take the zImage you extracted earlier and put it into the split-image folder, and rename it to boot.img-zImage. Repack your boot image which when done, will be default named to image-new.img.
4. Reboot the device into TWRP or the bootloader and flash your new boot image and reboot.
Screen shot below. You now have an awesome Marshmallow ROM and brand new Kernel for your Nexus 10!!
****Change Log****
February 10, 2020: Updated kernel version from 3.4.69 to 3.4.71. kernel patches not fully cooperating with the disabling of SELinux so I had to re-enable it. Simply placing a small script into /system/su.d (or locate wherever your su folder is and inside will be a su.d folder) to set selinux permissive on boot works perfectly. Create a text file called permissive.sh and copy and paste text below and save it to that folder with permissions: 777. If no su.d folder exists, create one in /system with permissions 755.
Code:
#!/system/bin/sh
setenforce 0

Can I dirty flash this with LineageOS15?

ong14 said:
Can I dirty flash this with LineageOS15?
Click to expand...
Click to collapse
I am going to take a guess and say no. Partition layout changes in Android 8 and 9 so probably won't work. I compiled the kernel with AOSP 6.0 gcc toolchain and I have no idea if this kernel can even support 8 or 9. I have to read further on updating the kernel as this is as far as I can update it for now. Any further patches say they're already added so I have to figure out what I am doing wrong. Also need to figure out how to update security patches.

ong14 said:
Can I dirty flash this with LineageOS15?
Click to expand...
Click to collapse
I am testing out another option. I will know soon enough whether or not it will work.

ong14 said:
Can I dirty flash this with LineageOS15?
Click to expand...
Click to collapse
No luck on the other option. Drats!

I'm charging my nexus right now and I'm gonna try this. I'll report in a few hours.

Update:
February 10, 2020: Update kernel from 3.4.69 to 3.4.71.
Download the zip, extract the zImage. use any one of the various tools in existence to unpack the boot image for the device and in the split-image folder delete boot.img-zImage and replace it with the zImage file and rename it to boot.img-zImage. Repack the the boot.img and flash in twrp or reboot to bootloader and flash in fastboot.
Sent from my Google Nexus 10 using XDA Labs

So I've been using this for a day now and I gotta say I'm loving it. It is stable no crashes or reboots. So thank so much for bringing this out. I've attached some screenshots for those curious.View attachment 4946929View attachment 4946931
Sent from my AOSP on Manta using Tapatalk

Kaleshwar said:
So I've been using this for a day now and I gotta say I'm loving it. It is stable no crashes or reboots. So thank so much for bringing this out. I've attached some screenshots for those curious.
Click to expand...
Click to collapse
Glad to hear. I have tried numerous ROMs on that device and all of them have some kind of flaw or another on a serious level. Either random reboots would occur, random shutdowns, extreme loss of memory and various other things. I got quite excited when I found this one online, with a working download link. Honestly it's exactly what I was looking for straight from AOSP. The stock ROM is also quite good, but it needs to be a bit more recent than lollipop. Because I was so used to stock AOSP on it already I was glad I can continue using AOSP. Never have been a big fan of lineage since they took over cm.and as the days go on it seems I like them less and less.
On a side note once I I'm able to update the kernel to a more recent version, then I will start experimenting with adding features. With that having been said I found it very hard to do so with this kernel. However I'm sure it can't be any more difficult then having to go through failed patches to remove commits and differences that screw up the build. Cherry picking on a whole new level. The only way I can figure out what patches do not work are by patching it and seeing which ones fail. That makes the process very timely.

Kaleshwar said:
So I've been using this for a day now and I gotta say I'm loving it. It is stable no crashes or reboots. So thank so much for bringing this out. I've attached some screenshots for those curious.
Click to expand...
Click to collapse
PS I just caught your screen shot. Awesome home screen! I've also included mine as well as a screenshot of the device has info for the kernel version. In the meantime, kernel auditor works awesome on this device. Especially the entropy settings. This tablet seems to pay on it a bit and increasing the read and write variables a bit, does give this device a new feel.
Sent from my Google Nexus 10 using XDA Labs

I had been using LOS for a long time thinking it was the most "stable" option, but after trying this... WOW, I feel that my Nexus has been reborn. It is fluid, the boot is quite fast, battery performs quite well and so far I have not had any unexpected reboot issues, which in LOS it was a every day thing.
The only thing I miss is being able to use Magisk, but I will survive.
Thank you!

ThePx said:
I had been using LOS for a long time thinking it was the most "stable" option, but after trying this... WOW, I feel that my Nexus has been reborn. It is fluid, the boot is quite fast, battery performs quite well and so far I have not had any unexpected reboot issues, which in LOS it was a every day thing.
The only thing I miss is being able to use Magisk, but I will survive.
Thank you!
Click to expand...
Click to collapse
The saying goes they don't make them like they used to. I have found myself consistently returning to older devices and finding new means to bring brand new life into them. It's not often I get to get a case like this where the difference is so drastic. I literally turned a technically ancient device into what will soon be my new daily driver tablet. Best $50 investment ever.

One thing: the selinux script is working fine, but when I patch the new kernel it get stuck in a boot loop. I have followed your instructions using the Android image kitchen without luck, any idea?
BTW I've noticed that your configuration screen is dark, which theme engine are you using?

ThePx said:
One thing: the selinux script is working fine, but when I patch the new kernel it get stuck in a boot loop. I have followed your instructions using the Android image kitchen without luck, any idea?
BTW I've noticed that your configuration screen is dark, which theme engine are you using?
Click to expand...
Click to collapse
Not sure I'm using the same z image. I'll test it when I get home and see what happens it's the same one I pulled off of mine so I know it works. I don't believe it'll work on the stock ROM so I'm pretty sure you have to be on the marshmallow ROM in the OP. Other than that I'll have to test it and see what happens. You could also use any other tool that unpack and repack boot images, that just happens to be the one I use.
If you look at APK mirror, you can grab an APK for substratum that works on marshmallow ROMs. You're pretty limited in the theme number of themes for it, and there are a few good ones that still exist but are still quite limited. I use PureZ material dark. It won't turn every app into dark mode, including some Google apps, so just download 'dark mode' from the play store which takes advantage of accessibility services to darken most every other app.
Sent from my Google Nexus 10 using XDA Labs

ThePx said:
One thing: the selinux script is working fine, but when I patch the new kernel it get stuck in a boot loop. I have followed your instructions using the Android image kitchen without luck, any idea?
BTW I've noticed that your configuration screen is dark, which theme engine are you using?
Click to expand...
Click to collapse
Sorry it took so long. Busy time at work these days. I honestly don't know what was wrong everything work fine on my end so here's what I did. Instead of using the actual zImage I went ahead repacked it to the stock boot.img from the ROM in OP. That should work but you will have to reflash SuperSU or magisk if you have systemless root.
Managed to add a few features but it's nothing much yet. Added all governors such as powersave, ondemand and userspace, etc. Disabled SELinux again, added debug info and options for GPU, and kernel same page merging (can be deactivated at boot by using kernel auditor or Franco kernel). Also deactivated the option that told the kernel it was using a "fake platform GPU". trying to get some kind of GPU options selectable inside one of the kernel applications. Let me know if it works and I will update the OP with the updated file. Just backup your current boot image and flash the new one in TWRP or push it in fastboot.
Sent from my Google Nexus 10 using XDA Labs

DragonFire1024 said:
Sorry it took so long. Busy time at work these days. I honestly don't know what was wrong everything work fine on my end so here's what I did. Instead of using the actual zImage I went ahead repacked it to the stock boot.img from the ROM in OP. That should work but you will have to reflash SuperSU or magisk if you have systemless root.
Managed to add a few features but it's nothing much yet. Added all governors such as powersave, ondemand and userspace, etc. Disabled SELinux again, added debug info and options for GPU, and kernel same page merging (can be deactivated at boot by using kernel auditor or Franco kernel). Also deactivated the option that told the kernel it was using a "fake platform GPU". trying to get some kind of GPU options selectable inside one of the kernel applications. Let me know if it works and I will update the OP with the updated file. Just backup your current boot image and flash the new one in TWRP or push it in fastboot.
Sent from my Google Nexus 10 using XDA Labs
Click to expand...
Click to collapse
3.4.71 working with the new image, thanks!
No problems so far, I'll update if I find something.

While unpacking boot.img I don't get split-image folder!! Seems the procedure described needs some clarity

ranandi said:
While unpacking boot.img I don't get split-image folder!! Seems the procedure described needs some clarity
Click to expand...
Click to collapse
See this link https://forum.xda-developers.com/showpost.php?p=81747927&postcount=15 flash boot image in TWRP or in bootloader mode. reboot your device then reboot back to recovery and flash magisk or whatever superuser you use. This is a clean boot image from stock so it is not rooted.
Sent from my Google Nexus 10 using XDA Labs

DragonFire1024 said:
See this link https://forum.xda-developers.com/showpost.php?p=81747927&postcount=15 flash boot image in TWRP or in bootloader mode. reboot your device then reboot back to recovery and flash magisk or whatever superuser you use. This is a clean boot image from stock so it is not rooted.
Sent from my Google Nexus 10 using XDA Labs
Click to expand...
Click to collapse
Yes, I could flash new boot image, following two issues:
(1) Camera sometimes shows 'not connecting', but sometimes it works fine.
(2) In clock when trying to set times of mother international zones, clock is not working error.

ranandi said:
Yes, I could flash new boot image, following two issues:
(1) Camera sometimes shows 'not connecting', but sometimes it works fine.
(2) In clock when trying to set times of mother international zones, clock is not working error.
Click to expand...
Click to collapse
1) I can look into the camera. I may know why that happens, though I never had a problem.
2) you may need to install another clock. I didn't stick with the one on the ROM. But try going to /data/used/0 and deleting the folder com.google.androud.deskclock (com.androis.deskclock?) and the contents and reboot and try again. I discovered while I've been testing kernels, that when flashing gapps, it doesn't always update the data files for Google related apps in that directory and causes some of the applications to force close, or not function at all. Also check the SD card Android/data as well and do the same.