Related
I have a GSM Galaxy Nexus and I am currently using 4.2.2 Cyanogen Mod released in April 2013.
It has the following Kernel
3.0.31-cyanogenmod-g64e9296
I have flashed ROMs many times mostly CM ROMS.
I want to try changing kernel to improve battery life and check what kernel changes actually is all about.
Since I havent done it earlier, I want answers to following questions:
1) Is it safe to change my kernel to another one? I want to install http://forum.xda-developers.com/showthread.php?t=2115590 or maybe someone can tell me a better one with focus on improved battery life.
2) What if the above kernel screws up? can I recover the old kernel back?
3) Is kernel flashing Permanent or any ROM I flash will have it's own kernel?
4) Just in case my kernel screws up, I have a full TWRP backup as well, would flashing that change my current kernel to old one that came with cyanogenmod last ROM?
Thanks.
You can pretty much flash any kernel you want. Just make sure the kernel is made for the version of Android you are on. If something goes wrong, you should be able to flash your ROM again and get back to normal. ROMs come with their own kernels so every time you flash a ROM, you will get the kernel that comes with it. But the best way to recover from a screw up is to restore a nandroid from your recovery.
jsgraphicart said:
You can pretty much flash any kernel you want. Just make sure the kernel is made for the version of Android you are on. If something goes wrong, you should be able to flash your ROM again and get back to normal. ROMs come with their own kernels so every time you flash a ROM, you will get the kernel that comes with it. But the best way to recover from a screw up is to restore a nandroid from your recovery.
Click to expand...
Click to collapse
Advanced restore should work, no need to restore the whole thing, just system.img and boot.img should do the trick.
Sent from my Nexus
Hi,
I am considering to flash ElementalX kernel and CleanRom on my stock nexus 7 2013 wifi. Is it correct if the steps I take are:
1. Rooted with Toolkit (i. unlock bootloader and ii. root?)
2. Flash CleanRom
3. Flash Stock kernel (is this step necessary?)
4. Flash ElementalX
Please let me know if there are other steps or things that I need to be aware. Thanks!
For step one you have to unlock boot loader in order to root. You also need to flash a custom recovery such as twrp or clockworkmod.
Also step 3 is unnecessary. After you flash cleanrom, you should just flash ElememtalX. Have fun
Sent from my Nexus 7
The toolkit will do it for you, I recommend TWRP recovery.
After that just flash the kernel.
Remember always to follow instructions.
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
DoczuPL said:
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
Click to expand...
Click to collapse
That means you're flashing the incorrect version of the kernel, from now on if you are flashing a rom see if its CAF-based or AOSP-based, for example CM is CAF-based, so you'll need to flash the correct version of the kernel, look in the kernel threads for the CAF kernel download, I know that Glitch and ElementalX have kernel compatible for CAF -based roms
DoczuPL said:
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
Click to expand...
Click to collapse
ElementalX kernels newest build is 4.4.2 not 4.4.1 and also a good tip stated above to see if you need a CAF of AOSP kernel.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Thanks for the advice, i'll try to flash it again when i'm back home. Cheers guys!
Probably not the first, won't be the last. I rooted my N7 with WugFresh root toolkit. But I can't choose a ROM. I would prefer close to vanilla with the advanced power menu that includes reboot and bootloader if possible. I have TWRP for recovery.
I've looked at Kangakat, CleanROM and Sinless. If one of them is better over the other that would be fine. Or another ROM. I want the latest build (KOT49H) and OTA potential.
scottad said:
Probably not the first, won't be the last. I rooted my N7 with WugFresh root toolkit. But I can't choose a ROM. I would prefer close to vanilla with the advanced power menu that includes reboot and bootloader if possible. I have TWRP for recovery.
I've looked at Kangakat, CleanROM and Sinless. If one of them is better over the other that would be fine. Or another ROM. I want the latest build (KOT49H) and OTA potential.
Click to expand...
Click to collapse
Everyone's taste is different. You should flash them all to find out which one suits you best.
Sounds like all you need is xposed and 1 module.
I did install Xposed and a few modules. Also added a different kernel. Elemental-X
Sent from my Nexus 7 using Tapatalk
i'd recommend OmniROM, close to stock, stable, nice features, OTA support, latest build (KVT49L) not (KOT49H) check out this thread: http://forum.xda-developers.com/showthread.php?t=2626831
Or if you want a clean build which your only requirement is the advanced shutdown menu, CleanRom has it with no add-ons. Its clean, fast and stable.
Sent from my LG-P880 using xda app-developers app
The author of cleanrom said its abandoned now :/
But its still my favorite rom . Fast and stable
Sent from my Nexus 7 using xda premium
scottad said:
Probably not the first, won't be the last. I rooted my N7 with WugFresh root toolkit. But I can't choose a ROM. I would prefer close to vanilla with the advanced power menu that includes reboot and bootloader if possible. I have TWRP for recovery.
I've looked at Kangakat, CleanROM and Sinless. If one of them is better over the other that would be fine. Or another ROM. I want the latest build (KOT49H) and OTA potential.
Click to expand...
Click to collapse
You don't need another rom for that, just Xposed and the GrafityBox plugin
.
Ed V said:
You don't need another rom for that, just Xposed and the GrafityBox plugin
.
Click to expand...
Click to collapse
That's pretty much what I did XPosed and then a plugin. Didn't use Gravity but am considering it!
Personally I've Installed Cyanogenmod Nightlies, with ElementalX Kernel. CM ROMs are close to stock, but with some cool stuff. you can activate advanced power menu in CM in Developers section. The latest Nightlies are stable and smooth, and the battery life is correct.
Don't forget, unlocking your device will do a full wipe :laugh:
Sincerely
Speaking of CM11, what isn't stable? Like what problems have you came across? If any that is cx
Sent from my Nexus 7 using Tapatalk
vparres said:
Personally I've Installed Cyanogenmod Nightlies, with ElementalX Kernel. CM ROMs are close to stock, but with some cool stuff. you can activate advanced power menu in CM in Developers section. The latest Nightlies are stable and smooth, and the battery life is correct.
Don't forget, unlocking your device will do a full wipe :laugh:
Sincerely
Click to expand...
Click to collapse
CM is about as far from stock as one can get.
BioDesigner48 said:
Speaking of CM11, what isn't stable? Like what problems have you came across? If any that is cx
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I experienced some bootloops, lags, even some fonctions broken (Wifi, proxymity sens, etc) in some nightlies. I experienced it on my friend's Galaxy S2, but i never experienced something like that with my N7 on "stock" CM11. In fact, i bought my N7 recently
look into omnirom...
I am not going to say any ROM is better than others because all ROMs have their pros and cons. To find out which ROM you like best you will have to try and experiment for yourself.
Nexus devices have a wonderful recovery manager which is TWRP which stands for Team Win Recovery Project. Nexus devices also have a great tool which works with TWRP recovery manager, this tool is call MultiROM manager. What multirom manager does is it allows you to install multiple ROM's on your Nexus device without harming or altering your stock ROM.
In order to use multirom you need to first patch your stock ROM with the kexec-hardboot patch. That can be done very easily. First thing you need to do is root your device. If you are going to root your device i would also recommend unlocking the tablets bootloader. This can all be done with WuGFresh's NRT (nexus root toolkit). Here is a link for NRT -> http://www.wugfresh.com/nrt/
After you have your tablet rooted and bootloader unlocked then install TWRP recovery, again all of this can be done with the Nexus Root Toolkit.
After that you can go to the google play store and download the app MultiROM Manager. This is the easiest way to install multirom. Here is the link for multirom manager -> https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Again, if you don't have your stock kernel patched with the kexec-harboot patch you won't be able to boot multiple roms. You can patch your stock kernel with the kexec-harboot patch from multirom manager.
So once you have unlocked bootloader + root + twrp recovery manager + kexec harboot patch for stock kernel (from stock rom) + multirom manager you have the freedom to do whatever you want to your tablet without harming or modifying your stock rom.
As for a custom ROM i would recommend that you look into OmniROM. It has gotten good reviews and i personally love it. I find it very stable and it also has a really nice feature with multi-windows and split screens.
Another thing you might be interested in is look into "xposed framework" that allows you to customize your stock or custom rom by adding things like multi-windows or advanced reboot menu for example.
I hope this has been helpful...
If you get stuck on anything there is great documentation on rooting + twrp recovery manager here on xda or you can find great videos on youtube.com.
-droidshadow
droidshadow said:
I am not going to say any ROM is better than others because all ROMs have their pros and cons. To find out which ROM you like best you will have to try and experiment for yourself.
Nexus devices have a wonderful recovery manager which is TWRP which stands for Team Win Recovery Project. Nexus devices also have a great tool which works with TWRP recovery manager, this tool is call MultiROM manager. What multirom manager does is it allows you to install multiple ROM's on your Nexus device without harming or altering your stock ROM.
In order to use multirom you need to first patch your stock ROM with the kexec-hardboot patch. That can be done very easily. First thing you need to do is root your device. If you are going to root your device i would also recommend unlocking the tablets bootloader. This can all be done with WuGFresh's NRT (nexus root toolkit). Here is a link for NRT -> http://www.wugfresh.com/nrt/
After you have your tablet rooted and bootloader unlocked then install TWRP recovery, again all of this can be done with the Nexus Root Toolkit.
After that you can go to the google play store and download the app MultiROM Manager. This is the easiest way to install multirom. Here is the link for multirom manager -> https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Again, if you don't have your stock kernel patched with the kexec-harboot patch you won't be able to boot multiple roms. You can patch your stock kernel with the kexec-harboot patch from multirom manager.
So once you have unlocked bootloader + root + twrp recovery manager + kexec harboot patch for stock kernel (from stock rom) + multirom manager you have the freedom to do whatever you want to your tablet without harming or modifying your stock rom.
As for a custom ROM i would recommend that you look into OmniROM. It has gotten good reviews and i personally love it. I find it very stable and it also has a really nice feature with multi-windows and split screens.
Another thing you might be interested in is look into "xposed framework" that allows you to customize your stock or custom rom by adding things like multi-windows or advanced reboot menu for example.
I hope this has been helpful...
If you get stuck on anything there is great documentation on rooting + twrp recovery manager here on xda or you can find great videos on youtube.com.
-droidshadow
Click to expand...
Click to collapse
Thanks I was thinking bout omni ROM lol
sent from my LG Optimus L9 P769 v20h
I'm on YouTube (aSuperSaiyanG0D)
So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.
Bootloop
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
slysurfer said:
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Click to expand...
Click to collapse
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
peltus said:
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
Click to expand...
Click to collapse
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Angdvl089 said:
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Click to expand...
Click to collapse
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
peltus said:
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
Click to expand...
Click to collapse
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Angdvl089 said:
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Click to expand...
Click to collapse
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Angdvl089 said:
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Click to expand...
Click to collapse
Glad to be of help. Have fun with your phone!
First of all make sure you're on the correct firmware for whatever rom and kernel your wanting to use or it will not boot. It will bootloop if on say a Marshmallow build amd your trying to install a Nougat rom.. Now if all matches you can proceed.. This is how I've installed roms for 5-6 years: in twrp wipe: data, system, cache, delvik cache, flash rom, flash gapps (open gapps mini is what I use) flash either SuperSu zip or PHH superuser, next reboot. Some roms (example: DU and AICP) come with SU already inside so no need to flash it.. You can tell because in twrp during flash process you'll see SU being installed If rom comes with it. If you choose to use PHH Superuser you'll need his app from Google play store. Just grab it (search PHH Superuser) and open it and you should be good to go. I use SuperSU as I've had issues using other SU with ARISE sound which is also something i use. Hope that's not confusing. Hmu on hangouts if you need help and I'll help when I'm available: [email protected]
Sent from my LG Nexus 5X using XDA Labs
Need any help
Hi mate, i have now unlocked bootloader, installed twrp and installed pure nexus rom. Did not use the toolkit, i used adb and fastboot using commands... It was easy. If you need a hand with anything give us a yell . [quoter=Angdvl089;68875927]So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.[/QUOTE]
[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.