The latest kernel, R1.8, is for Shield experience 9.1. Supported Shield TVs include all 2015 and 2017 models. The 2019 models are not supported. Enjoy the kernel and leave any feedback that you may have
Install Instructions:
- Download and extract Kernel_R1_8.zip
- Flash Kernel_R1_8.img in fastboot using fastboot flash boot Kernel_R1_8.img
- You could also fastboot boot the kernel before flashing it to make sure everything is working correctly
- Once your shield has booted up again install the latest magisk app if you haven't already
- Open the magisk app and update / reboot if necessary
- I've seen the shield fail to boot when rebooting right after updating Magisk. If this happens, just unplug your shield tv and plug it back in and everything should work fine
- Install Shield_Tools_V1_4.apk and tune the kernel to your liking. By default, all settings are stock
- If you need exfat / ntfs support, then install the attached Vold9_0 Magisk module
Kernel R1.8 Features:
- Based on the kernel sources for shield experience 9.1
- 2.22 Ghz CPU overclock
- 1.23 GHz GPU overclock
- 1866 Mhz RAM Overclock
- Fully customizable fan settings
- The touchpad on the 2015 controller (blake) is enabled and works correctly
- The blake touchpad cursor speed is adjustable
- One of the the top triggers on the blake controller can be selected to act like a mouse button. This can be used along with the touchpad to scroll fairly conveniently
- The kernel version has been updated from 4.9.141 to 4.9.324 using the upstream android 4.9-q branch. Some changes have also been integrated from Linux for tegra
- Compiled with the latest aosp prebuilt clang, clang-r445002 version 14.0.2
- Compiled with -O3 speed optimizations and link time optimization (LTO)
- CFI is enabled for additional security
Note: The cpu throttles to around 2.0Ghz at 66C. Keep this in mind when setting fan speeds if you're trying to maximize performance. Also, regardless of what you set, the fan will always turn off when the temperature falls below the lowest value. I'll probably change this in a future shield tools release.
Old Changelogs:
R1.1:
Prerooted with magisk
Selinux is permissive by default
R1.2:
GPU Overclock up to 1.23 GHz
Boot frequencies are default and must be adjusted manually (using my app) to overclock
Ondemand and interactive governors added. Interactive is default
(debug feature) Serial console over ttyUSB0
First release of shield tools, an app to help tune this kernel. Shield Tools does not work with earlier releases
R1.3
First release for pie
Fully customizable fan settings
Shield tools updated to V1.1 with fan controls and changes needed for pie
Vendor and system verity are disabled
System as root is removed to support Magisk.
R1.3.1
Use kernel modules again to fix some bugs such as USB issues.
R1.4 / Shield Tools 1.2.1
Kernel updated from 4.9.140 to 4.9.162
1866 MHz RAM Overclock (Improves graphics performance significantly)
Power throttling added by Nvidia in the pie release has been removed
RAM control added to Shield Tools
Shield Tools saves settings and applies them on boot now
Shield Tools 1.2.1 fixes fan settings for 2017 shields.
R1.5 / Shield Tools 1.3
Kernel updated with Nvidia's latest rel-32-r7 sources
Many more selectable RAM frequencies
RAM voltage is slightly increased at frequencies above 1725 MHz
New installation method that doesn't modify the system or vendor partitions
Standby frequency reset issue fixed (actually fixed in Shield Tools 1.2.2)
Kernel version is 4.9.140 again, but the sdcard bootloop issue is gone
R1.6 / Shield Tools 1.4
First release for android 11
Kernel version updated from 4.9.141 to 4.9.309
Touchpad on blake controller is enabled by default and a problem with the cursor jumping on initial touch has been fixed
Blake touchpad speed can be adjusted
Either the top right or top left trigger on the blake controller can be selected to act like a mouse button. This makes scrolling using the touchpad fairly convenient
When setting fan speed values the same speed can now be repeated
The speed and temperature dialogs now automatically scroll together
Fan hysteresis is now set when changing temperatures to fix potential problems with the fan speed not decreasing properly
All security features are left enabled. I'll disable them if there's actually a need for it
Magisk's root directory overlay feature is used to load kernel modules
R1.7
Changes from the 9.0.2 release have been merged
Kernel version updated to 4.9.311
Werrors preventing compilation with clang 14 have been fixed
Several CFI failures have been fixed allowing enforcing CFI to be used (at least on 2015 shields)
Clang is now used to compile the kernel with LTO and CFI enabled
Debug tracing has been disabled to save some memory
In previous releases the voltage was too low on some shield tvs to reach a 2.22 GHz CPU overclock. This has been fixed.
Changelog for the latest release R1.8:
Changes from the 9.1 release have been merged
Kernel version updated to 4.9.324
CFI failure in the realtek ethernet driver that caused the 2017 shield to bootloop should be fixed
Big thanks to Magisk.
Standard Disclaimer: You're responsible for what you do to your devices, so don't blame anyone else if something goes wrong.
Kernel Sources: https://github.com/rootfan/
Always great to see development on the Shield devices. Thanks for your contribution.
Sent from my SHIELD using Tapatalk
Would love if someone could show a vid with the differences with this mod
anyone else try this, I couldn't get it to flash, says invalid zip. I installed the boot.img through fla**** but it wasnt a clean install and became unresponsive. My next step is to try it on a clean install.
flashed on darcy android 8 - wifi broken
I tried this kernel on the android 8 AOSP that was floating around a few months back, which I use because the adoptive storage works (unlike 7.2.3).
Anyway, it booted, seems noticeably faster, but wifi radio is piffed, which is a dealbreaker, so I restored back with TWRP.
Are there any alternate flashable radios for darcy?
thanks for your efforts
Hi, I flash this kernel on my Shield TV 2017, but USB slot does not work, everything else is fine.
imoldchen said:
Hi, I flash this kernel on my Shield TV 2017, but USB slot does not work, everything else is fine.
Click to expand...
Click to collapse
Can anyone else confirm this?
Since op states only cpu clock, selinux mode and magisk is added, this shouldn't break usb right?
Also, right now I'm on 7.2.3 rooted.
Can I just do fastboot boot steel01's twrp and then flash the zip and done?
No bootloop no reflashing anything in bootloader? No dm-verity issues?
trohn_javolta said:
Can anyone else confirm this?
Since op states only cpu clock, selinux mode and magisk is added, this shouldn't break usb right?
Also, right now I'm on 7.2.3 rooted.
Can I just do fastboot boot steel01's twrp and then flash the zip and done?
No bootloop no reflashing anything in bootloader? No dm-verity issues?
Click to expand...
Click to collapse
I use developer firmware to disable dm-verity via adb root, Yes, the Sheild TV 2017 version of USB does not work, And it can't into twrp, only flash boot.img in boodbloader mode.
If anyone has done this can you post some benchmark testing results?
rootfan said:
This kernel is only for the latest shield TV software version, 7.2.3. Do not flash it on older versions or lineage OS. The only major addition to this kernel is the 2.22 GHz overclock. The ramdisk is from the shield developer release, so adb root is available. The twrp flashable zip is below. It works with Steel01's latest experimental twrp. I've only tested it on the shield pro, but it "should" work on other variants. Please make a backup of boot before flashing to be safe. As usual, the standard disclaimer applies. Your warranty will most likely be void, and I can't be held responsible for any damages flashing or overclocking may cause your device. Full sources can be viewed and / or downloaded at https://github.com/rootfan/nvidia-4.9-kernel. I hope this kernel works well for you. If it does, please give the thanks button a press
Changelog:
R1.1:
. Prerooted with magisk
. Selinux is permissive by default
Click to expand...
Click to collapse
Have you tested this on the new Pie release?
bum2kev said:
Have you tested this on the new Pie release?
Click to expand...
Click to collapse
R1.1 only works on shield experience 7.2.3. I'll make an updated version for pie / 8.0 once Nvidia releases their sources.
rootfan said:
R1.1 only works on shield experience 7.2.3. I'll make an updated version for pie / 8.0 once Nvidia releases their sources.
Click to expand...
Click to collapse
Thank you for the reply. Have you done any benchmark testing? How are the temperatures?
Please tell me what is the fastboot command to flash the kernel. thanks
marvinsi said:
Please tell me what is the fastboot command to flash the kernel. thanks
Click to expand...
Click to collapse
Thanks for adding GPU overclocking, The issue of GPU overclocking on github was submitted by me. :highfive:
The 2017 and PRO versions compare the extra files：
lib/firmware/tegra210b01_xusb_firmware
lib/firmware/tegra21x_xusb_firmware
sbin/slideshow
Add these files to the kernel, and USB will work on the 2017 version.
About the APK app, I hope to provide a complete language XML file.
This makes it easy for users to submit translations in other languages.
What are the steps to flash this kernel please
marvinsi said:
What are the steps to flash this kernel please
Click to expand...
Click to collapse
fastboot flash boot boot.img
But I highly recommend you not to do it, because as you weren't able to figure it out your own, indicates you are lacking basic knowledge about adb/fastboot and problem solving you should have in case something goes wrong in that process. I don't want to shame you for not knowing this, but every tempering with your shield on this level has the potential risk of bricking it, so you should know exactly what you are doing and how to fix problems, which I honestly doubt if you need to ask something that you could have found out with a 10 seconds Google search
imoldchen said:
Thanks for adding GPU overclocking, The issue of GPU overclocking on github was submitted by me. :highfive:
The 2017 and PRO versions compare the extra files：
lib/firmware/tegra210b01_xusb_firmware
lib/firmware/tegra21x_xusb_firmware
sbin/slideshow
Add these files to the kernel, and USB will work on the 2017 version.
About the APK app, I hope to provide a complete language XML file.
This makes it easy for users to submit translations in other languages.
Click to expand...
Click to collapse
can you add this info to the github issues? This is the one thing that is stopping me from doing this. Have you run any benchmarks with the CPU/GPU overclock?
@rootfan, BTC address to send tip?
@bum2kev, @imoldchen, and anyone else who's interested, here's something to try that should fix the 2017 shield USB issue, if it boots. It's a Magisk zip that replaces the installed kernel with my modified version. The magisk installer is set to preserve dm-verity and this kernel should disable dm-verity, so hopefully it'll work on the 2017 shield. You can install it with this twrp I put together: https://drive.google.com/open?id=1BCfXg9pUpFm_3sPXp_nEwBlkNU9nelkg Make sure you're on a stock boot.img before flashing the kernel. Let me know if it boots and be prepared to restore your shield (just the boot.img) if it doesn't
The attached file is only for 7.2.3
rootfan said:
@bum2kev, @imoldchen, and anyone else who's interested, here's something to try that should fix the 2017 shield USB issue, if it boots. It's a Magisk zip that replaces the installed kernel with my modified version. The magisk installer is set to preserve dm-verity and this kernel should disable dm-verity, so hopefully it'll work on the 2017 shield. You can install it with this twrp I put together: Make sure you're on a stock boot.img before flashing the kernel. Let me know if it boots and be prepared to restore your shield (just the boot.img) if it doesn't
Click to expand...
Click to collapse
Tried it on my Shield 2017 version and I can confirm that it works. Shield booted up fine and the USB ports are now working! Thank you for the work you have done!
My shield 2017 (16gb) is still on fw 7.1.0 with working trwp and magisk rooted already.
Since I don't have PC around to do fastboot method, is it possible to upgrade to pie and root it with this guide by using only exiting trwp. If so, how?
Thanks.
Related
Read First: This method is relatively drastic, and will hurt device performance some. You should only use this as a last resort, if the more basic methods of fixing a soft brick didn't work (e.g, factory reset, flash stock firmware, etc.)
*Update 8/22: Android O is working with 4 Cores now! Big thank you to @xls654 for finding out how to get Android O to work.
*Petition:
I made a petition for Google to officially release and sign modified boot.imgs, so that people with locked bootloaders can fix their devices too. Check it out here. (I apologize for dumbing it down so much, I wanted to make sure everyone could understand it)
*Changelog:
8/25 - EX kernel for Android O added.
8/22 - Android O DPR6 boot.img and source added.
8/16 - Started making this fix open-source, source code section added in OP. Also uploaded modified Franco and Flash kernel & source.
8/10 - Added PA 7.2.2 and DarkROM boot images.
8/08, 2nd change - Uploaded modified boot.img for firmware 48C.
8/08 - Updated EX kernel to version 4.1.2. This updated zip adds the CPU utilization patch to the init.elemntalx.rc, instead of removing the old init.angler.rc and copying the new init over. That should mean more compatibility with Roms/kernels that modify the init.angler.rc. I also modified the camera-daemon to use cpus 0-3 instead of 0-2, so hopefully this should make the a camera bit faster too.
8/07 - Added boot.img that only uses 1 core. Someone suggested I make a boot.img that only uses 1 core, just to see if it works for devices that didn't work with the 4 Core fix.
7/30 - Added universal EX zip, this zip should modify your kernel to use only 4 cores, and it should modify it to utilize all 4 cores. You can flash this over most ROMs and it should work. Also added a donation url, and this changelog.
7/29, 2nd change - Added Pure Nexus and PA dev version boot images, modified to use 4 cores, and utilize all 4.
7/29 - Updated this fix to greatly improve performance. Before this fix, the device was only using 1 core for foreground tasks, now it will use all 4 cores. Also revamped OP.
7/21 - Fix created, stock boot.img, TWRP image, and EX kernel modified to use 4 cores.
*What this fix does, and how to apply it:
The problem:
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit. However, I am continually working on ways to improve the device's performance.
The update: If anyone remembers device performance with the first fix, it was hurt a lot, however, after finding out that the device was only using 1 core for all foreground tasks, I modified the ramdisk to utilize all 4 cores more effectively, and it helps a lot.
Requirements: For this fix to work, you need:
A brain
A computer
A bootlooping 6P with an unlocked bootloader/OEM unlocking enabled
The modified files of your choice
Fastboot on your computer (preferably installed system wide). If you do not know what this is, or do not have it, look at this post. Answer yes to all of the prompts to install it.
How to apply the fix:
Boot your phone into bootloader (hold power and volume down).
Connect your phone to the computer.
Go to the folder where you have the modified files, then hold shift and right click in a blank space, click on "open command prompt here" in the menu that pops up.
In the command prompt: type "fastboot flash boot [name of the file here]" and then press enter. If you're flashing TWRP, replace boot with recovery. (Linux users, make sure you're running as root)
Edit: With the new EX zip, you shouldn't need to flash the boot.img anymore, you can just flash twrp, and then flash EX in twrp.
Boot up your phone, and hopefully it should work!
*If your phone is bootloader locked/OEM locked:
You can try to get your phone to boot long enough to enable OEM unlocking. Some users have reported success by freezing their phone for a bit, then booting it. Others have let their battery drain all the way, and then tried to boot their phone, but the most successful method seems to be heating up your phone (a lot).
If you do attempt any of these methods, make sure you have time and patience, as it will take a long time.
To enable OEM unlocking and unlock bootloader:
Go to settings.
Go to developer options, if you do not see that, go to "about phone", scroll to build number, and then tap it 7 times. You should now see developer options in settings.
Once you're in developer options, click on "OEM unlocking" and accept the prompt.
Now reboot your phone to bootloader, connect your phone to the computer, and type "fastboot flashing unlock" Your bootloader should now be unlocked.
*Downloads:
Boot.img from stock 6.17, 8.0 firmware: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. It also disables forced encryption as a bonus. Thank you to @xls654 for figuring out how to get Android O to work.
Boot.img from stock 48C, 7.1.2 firmware: Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
Boot.img from stock 48B, 7.1.2 firmware: Download |Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
EX kernel version 5.03: Download | Mirror. EX kernel 5.03 works with android 8.0.0. This zip applies the 4 cores patch, but you will need to flash it over an already modified boot.img to work.
Elemental X kernel version 4.12, universal zip: Download | Mirror. This zip is EX kernel, modified to use only 4 cores. Update: I modified it to apply the CPU utilization patch too, so now this is a universal zip, flash it over almost any ROM, and you should now have the BIG cores disabled fix, and the little core utilization fix.
Flash kernel version 2.5: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.
Franco kernel r55: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.
You will most likely not need these images. It will be much easier, and much more universal to flash one of the custom kernel zips above ^^^
PA boot.img from PA version 7.2.2, build 8/10: Download | Mirror. Uses only 4 cores, and has core utilization patch.
PA boot.img from PA version 7.2.1: Download | Mirror. Boot.img from PA dev preview 7.2.1, uses only 4 cores, and is modified to utilize 4 cores more effectively. Flash it after you flash the PA zip, either with fastboot, or TWRP image flash.
Pure Nexus boot.img from Pure Nexus 7/25 build Download | Mirror. This image is modified to use only 4 cores, and it has a tweak to utilize the 4 cores more effectively. Flash it after you flash Pure Nexus, either with fastboot, or TWRP image flash.
DarkROM boot.img from 7/21 build: Download | Mirror. This image is modified to use only 4 cores, and has the utilization patch.
Boot.img modified to use only 1 Core. Some people were reporting that the 4 core images weren't working for them, someone suggested that I make a 1 core version to see if that helps at all. Edit: seems not to help unfortunately. Here it is: Download | Mirror
Unfortunately, I have not been able to get Android O working yet, but I am working on it right now.
If you have a favorite custom ROM or kernel you want to ported over to use 4 cores, let me know, and I'll put it up.
*Source code:
Flash kernel: source | Flash ramdisk/AK2: source.
Franco kernel: source | Franco ramdisk/AK2: source.
Android O boot.img: source.
p-0000000000000000000000000000007 (sorry that was my kitten)
*Tested custom ROMS/kernels
I have used Pure Nexus by flashing the modified EX zip over it, it has notably better performance than the stock ROM, and very good battery life. It's a clean, stable ROM, with plenty of good features that are actually useful.
I have also used Paranoid android dev preview, very good performance, definitely my favorite as of now. Battery life leaves something to be desired, but I have not tried a custom kernel yet. Also, 7.2.1 seemed smoother to me than 7.2.2.
If you have a custom ROM/kernel that worked for you, let me know and I'll put it up here.
*To improve performance slightly:
Flash a custom kernel. I will upload more kernels as I test more, so stay tuned.
Overclock the little cores. It can slightly help offset the lost performance, on my 6P, I have mine overclocked to 1632MHz, and it works perfectly for me. Edit: I actually recommend not overclocking. Many people have reported their Little cores failing, so I would go for longevity on this device, and keep it at stock clocks, or even underclock it. The speed difference you get from overclocking is negligible anyways.
Disable animations in developer options. Seriously, as soon as I found out about this tweak, I've used it on ever single device I've owned, it helps a ton.
Turn resolution down to 1080p. On a small screen, the difference in between 1080p and 1440p is not very noticable. To do this, first get root access, then download a terminal emulator. In the terminal, type "su" and grant it root access, then type "wm size 1080x1920", and finally, change the density "wm density 400". Personally, I like my density at 400, but you can expieriment with it. Lower density=Smaller items and text, Higher density=Bigger items and text. Also @Adithya FRK mentioned that you also want to put density in build.prop so apps display correctly. Change ro.sf.lcd_density=560 to your density, if you changed it.
*Credits:
@rchtk, His post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
@tr1gg3r.man, He made the the PA kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
@BeansTown106, He made the Pure Nexus kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
@Dark_Eyes_, He made the DarkROM kernel, I just added a couple modifications to it. In no way am I trying to steal and/or discredit his work.
@[U][COLOR="Purple"]The Flash[/COLOR][/U], He made The Flash kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work. His posts have also helped me a lot with learning how to build a kernel from source, understanding how to use git more, etc. I recommend you check them out if you are interested in getting started with android development.
@[B]franciscofranco[/B], He made Franco kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work.
@xls654, He found out how to get Android O working with 4 cores.
FAQs
What's the password for TWRP/Why is TWRP asking for a password? - In android 7.0, Google added forced encryption to the data partition. To get around this, click cancel when TWRP asks you for a password, and then factory reset the device. Then you can flash EX kernel/Magisk to disable forced encryption.
Why am I getting an error when I try to flash the images? - Your bootloader is probably not unlocked, try running the command "fastboot flashing unlock", If you get an error there too, then you will have to enable OEM unlocking before you can continue.
It's not working for me, how do I fix it? - My only advice for that is: "Flash the stock firmware for whatever version image you're trying to flash, then reflash the images again" If you're stuck on the boot animation, wait at least 20 minutes before you declare it's not working. If none of that works, chances are your device may have a different problem.
Does EX kernel have the new speed fix? - Yep, you can flash this over just about any ROM, and it should patch it to use only 4 cores, and use them well.
I would like to help as many people as I can, however, I am much more likely to be able to easily help you/reply to your post if you clearly state your problem and the steps you attempted to fix it. I will be much less likely to reply to posts such as "omggg i flashed the image and my phone won't boot helppp" Please read through post first, I did not spend time typing up this OP for no one to read it. If I can see that you read through the OP and have attempted all the steps, then I will be much more willing to help you.
I set up donations on my profile, for those of you who want to donate. I have spent countless hours modifying, flashing, testing, and helping, don't get me wrong, I love doing this and helping y'all out, but donations really keep me motivated to keep going, and donations also will help me fund new equipment and devices that will help further my android development. Every single donation is appreciated Donate to me here!
If this guide helped you, please click thanks, it means a lot to me
flashed modded TWRP then flashed modded EX Kernel and I'm back up and running... thanks so much!!
How the fuuuuuuuu man you save me, how do you make this.
Really work for my Nexus 6p thank you man, is there any way to send a cup of coffe.
worked for my brick - can enter TWRP again
Hello man is there any way to can use this with Android O ????
You are god!
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Today it suddenly happened to my device too. I flashed your img and the device booted again, thank you! However, seeing you disabled some cores, would it be caused by a bad core in the device? So, a hardware failure? Or is the boot.img simply corrupted in some sort of way? I'm trying to pinpoint the issue here.
edit: flashed the stock boot.img and the device was back into loop. So it's probably is a hardware defect.
@nabears101 you are AMAZING! Outstanding job.
My phone has life again (even though I already bought a OP5 to replace it)
NeoS said:
Today it suddenly happened to my device too. I flashed your img and the device booted again, thank you! However, seeing you disabled some cores, would it be caused by a bad core in the device? So, a hardware failure? Or is the boot.img simply corrupted in some sort of way? I'm trying to pinpoint the issue here.
edit: flashed the stock boot.img and the device was back into loop. So it's probably is a hardware defect.
Click to expand...
Click to collapse
That would be my guess, I'm trying to figure out if there's a way to debug the bootloader so I can pinpoint the problem with the BIG cores.
javitomen said:
Hello man is there any way to can use this with Android O ????
Click to expand...
Click to collapse
I'll go ahead and upload a version for android O later today
javitomen said:
How the fuuuuuuuu man you save me, how do you make this.
Really work for my Nexus 6p thank you man, is there any way to send a cup of coffe.
Click to expand...
Click to collapse
To anyone who wants to make a boot.img with 4 cores: It's actually fairly simple, you need to get abootimg tools on linux. Then unpack the boot.img with abootimg -x (name of your boot.img) Once the image is extracted, there should be a file named bootimg.cfg, edit that file and put in maxcpus=4 in the line that starts with cmdline =. Then repack the image with abootimg --create myboot.img -f bootimg.cfg -k zImage -r initrd.img And viola! You have a (half) working kernel.
XCnathan32 said:
I'll go ahead and upload a version for android O later today
Click to expand...
Click to collapse
Thanks man you dont know how thankfull i am, i hope your release of the android O to test it, thanks again for your work :good:
javitomen said:
Thanks man you dont know how thankfull i am, i hope your release of the android O to test it, thanks again for your work :good:
Click to expand...
Click to collapse
Just uploaded boot.img and EX Kernel for Android O, check OP. And no problem, I'm always happy to help a fellow android fan.
XCnathan32 said:
I'll go ahead and upload a version for android O later today
Click to expand...
Click to collapse
XCnathan32 said:
Just uploaded boot.img and EX Kernel for Android O, check OP. And no problem, I'm always happy to help a fellow android fan.
Click to expand...
Click to collapse
Hi man i just flash it, but after Android logo just return bobootloader
javitomen said:
Hi man i just flash it, but after Android logo just return bobootloader
Click to expand...
Click to collapse
Oops I'm getting that problem too, working on it now...
XCnathan32 said:
Oops I'm getting that problem too, working on it now...
Click to expand...
Click to collapse
lol thanks man, i hope you can fix it
I don't have this bootloop issue but it is extremely reassuring to know there is a fix even though it means limiting performance and such an easy fix too. Making the modifications seems very easy which makes me wonder why it's taken so long for someone to do a modification like this.
NeoS said:
Today it suddenly happened to my device too. I flashed your img and the device booted again, thank you! However, seeing you disabled some cores, would it be caused by a bad core in the device? So, a hardware failure? Or is the boot.img simply corrupted in some sort of way? I'm trying to pinpoint the issue here.
edit: flashed the stock boot.img and the device was back into loop. So it's probably is a hardware defect.
Click to expand...
Click to collapse
If you're interested, I made a post here https://forum.xda-developers.com/nexus-6p/help/dev-help-debugging-ramoops-bootlooping-t3640826 that semi-identifies the problem, I'm trying to get help on how to fix it.
I'm still downloading your imgs but the response of people to this thread/guide is already making me feel like I've arrived at the end of the Amazing Race (filled with awful challenges of unlocking, rooting, flashing, discharging, waiting, and just. literally. staring.)
Thank you, BLOD SLAYER!
XCnathan32 said:
Oops I'm getting that problem too, working on it now...
Click to expand...
Click to collapse
Hi man, did you found the fix for Android O?
SamFail presents...
PartCyborgActiveRom
ARA1
A Rooted Custom Rom
For SM-G892A/U on V1 and V2 Bootloaders
FAQ
What is my Bootloader Revision?
Your bootloader revision is part of the baseband build number of the firmware you are currently running. For example, let's consider this firmware version: G892ASQS2BQL1
Start from the right and count 5 characters back. See that 2? That is the bootloader revision for the firmware that came with this rom. All Samsung firmware follow this formula for all devices.
Using this formula, What is the bootloader version for G892UEU4GHK1?
Answer: Bootloader revision is 4
Updates
Please see below for a a new update to both the V1 and V2 releases.
It is a new BL "part 2" tarball that contains a fix for the issues reported by
many of you with the finger print and other various sensors. It has replaced
the original firmware Part2 link in the following post .
Featured Modifications
Deodexed
Deodexed for all devices.
I found a way that works!
It should continue working as long
as we care about nougat
Xposed Preinstalled
Forget that extra flash, PCR now comes out of the flasher with xposed pre-installed.
NOTE: Xposed Installer may crash on first boot. It will not crash after setup finishes and you reboot
New Custom Boot Animation
Another great one from @rayan-refoua himself.
This one is my favorite so far.
JamesDSP
I added another DSP style audio mod. JamesDSP is similar to V4A in how it operates and what features it has, but it has some really awesome features that have gotten me using it for a while. Specifically it has a better convolver (IRS processing) implementation, and its bass boost is WAY better than v4a. However you can use both at the same time to get the best of both worlds.
ITYBP Modded YouTube
A last minute addition, this is a really nice youtube mod brought to you by XXXXXX ADD SOURCE XXXXX. It features some cool features like native adblocking (no more xposed module), override your max youtube resolution (so you can watch 4k videos on your phone), and, not as important to us, spoofing different device types to get true hdr videos. I have been using it for a while and really like it. A big thanks to them for letting me include it with PCR
Improved Debloating
I did a lot more digging this round, and was able to add back a few things that I had taken out without loading the system more. This rom feels snappier than any before it. As usual, if you find something missing that you want back, pull it from the stock rom and install it in /system.
Improved Battery Life
Thanks to some fine battery sleuthing work by @TheMadScientist, this release comes with a nice big bump in efficiency. With just some very minor tuning using amplify and a service disabler, I can get around 1%/h drain.
Performance Improvements
That increased battery life does not come at the cost of performance. In fact performance is better too. Part of that is due to a large batch of personally tested build.prop tweaks make the ui a lot more responsive. Part of that is the data optimisation scripts that now run at boot to make sure things are cleaned up and in tip top shape. You wont notice those, but they are there doing their thing.
Other Features
- Pre-Rooted with SuperSU installed
- CSC OYN pre-installed. Tested working on several carriers
- RCS and VoLTE icons removed from status bar.
- High quality audio mods, including
- Viper Audio (V4A)
- Dolby Atmos from the Axon 7
- Pandora hifi audio framework
- Native Google Dialer & Contacts support, including local search, spam call blocking
- Oreo 8..1 Emoji Icon Set
- Custom Lockscreen Clock font
- Stock system display fonts replaced with Apple's original San Francisco Font
Special Thanks
- @ahiron and @Zackptg5 for the killer sounds from V4A and Dolby Atmos Mods!
- The Aiur crew for Pandora (now a legacy mod but works great on the s8)
- @syndre for the Google Dialer and Contacts framework mod
- @rayan-refoua for the beautiful Tech Lines Custom boot and shutdown animations!
- Last but not least, my new friend @laura almeida, along with @Razerman amd @ZaneZam for letting me include the iYTBP - injected YouTube Background Playback Mod
- everyone who tested
Warnings/Disclaimers/Known Issues
- 80% Battery life like every other rooted US snapdragon device
- Flashing on a USB 3.0 port will likely cause corruption in your flash that can cause kernel panics, loss of root, and occasionally very strange other errors. If you get something like this, its not the rom its a hardware conflict that can only show up with larger images like are used in SamFail flashing. See the section below on Kernel Panics for more.
- If there is an app or apk from the stock rom that you wish you had installed, the best solution is to extract it from your stock rom image and copy it to the same place in /system using a root file manager. If a large number of people want something back, I will include it in the next version, but by now I think we have covered all those possibilities and now the list will only get shorter. No I will not put Bixby back
SamFail Rooting Process
and Rom Installation
WARNING: THE FOLLOWING WILL ERASE YOUR WHOLE PHONE
If you have a SDCard, remove it from your device. Occasional firmware incidents have wiped SDCards in the past. Better safe than sorry.
Prepare the Following:
- complete stock rom at your bootloader rev in case things dont work
- Everything backed up (see above)
- Both Prince Comsy Odin, and Regular Odin for flashing stock
- A USB 2.0 Port. If you attempt to flash with a USB 3.0 port it may work, but if you get kernel panics, or unexpected bad behavior and/or crashes your usb3 is absolutely to blame. some people get lucky and suceed after a few tries, YMMV. If you can not acquire a machine with a usb2.0 port, get a usb2.0 hub and run your phone into that & that into your machine. Reports are that has made things work for some, but we get few reports back.
[/size]
Steps to Root
1) Download and unzip AP Part 1 and BL Part 2 zip files.
2) Download and unzip Prince Comsey Odin and start it up
3) Reboot device into Download mode, connect to your pc
4) Open Comsy Odin and add ONLY the AP Part1.tar.md5 file. Select the following options only:
- "Auto-Reboot"
- "F-Reset Time"
- "Nand Erase All"
NOTE: Odin will freeze while checking the AP tar.md5 hash.
Be patient, it will come back.
5) Click "Start" and wait for the system.img.ext4 file to flash fully to your device. This will take a while too.
ATTENTION:
When the flash finishes, this is when the SamFail magic happens. Instead of saying "Failed (Auth)" like it should, the device will crash into upload mode with "Unknow Error".
If your device does not do this, and just says "Failed (Auth)" or something similar and stays in download mode, you need to start again from the beginning, but using a different set of ub ports as you have suffered from the usb3 corruption.
When you see the upload mode page, use the 3 button reboot to go back to download mode.
WARNING: When you reboot from upload mode, your phone will show an error instead of download mode.
When you reboot back into download mode, your screen will say that you had a failed update and you need to do emergency repair or take your device to a service center.
Rest assured, your phone is actually in download mode, and Odin will have recognized it and said "Added!" along with the com port lighting up underneath the progress bar.
It is safe to continue
6) Close and re-open Comsy Odin or hit the reset button, and add BL_PartCyborgRom-BootLoopEdition-<version>.tar.md5 to the BL section.
7) Leave the default checkboxes for "F Reset Time" and "Auto Reboot" checked. Click "Start" and flash the BL (part 2) to your device.
8) Wait for the flash to finish . It won't take very long at all all the files are small.
9) When it has finished, Odin will say PASS and your device will reboot into recovery.
Warning: Failure to follow this step could lead to a corrupted instance with no cell coverrage
10) When in recovery issue a factory reset. This ensures that your device has a userdata partition that is valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.
All done!
Donations/Root Bounty
Pledged a donation for the root bounty? Send it here. Thank you!
IF YOU GET A BOOT LOOP:
If you get a boot loop or your device hangs at boot, try the following:
1) Reboot to recovery and factory reset again.
To get to recovery hold power+vol-down until screen goes black, then wait till upload mode (press power key for 7+ secs) comes up. Then press vol-down+power again and hold it till it reboots and as SOON as the screen goes black switch to holding vol-up+power+bixby. Hold it for 5-7sec then let go and you will wind up in recovery mode.
Kernel Panic, Invalid Argument
Start the process over
Go back to the beginning and do everything again. If it fails in a new way this time, you may have hardware caused corruption, or maybe you missed a step. Change hardware, and keep trying.
Help
If you get stuck, some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Come Check it out.
Enjoy!
XDA:DevDB Information
PartCyborgRom, ROM for the Samsung Galaxy S8
Contributors
partcyborg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: TouchWiz/Samsung Experience
Version Information
Status: Stable
Current Stable Version: BQL1
Stable Release Date: 2017-12-10
Created 2017-12-11
Last Updated 2018-2-10
Downloads
V1 Bootloader Revision
PartCyborgRom.G892A-ARA1.Part1.zip
[Alternate Mirror]
PartCyborgRom.G892A-ARA1.Part1b.zip
[New: Fingerprint/Sensors all working]
V2 Bootloader Revision
PartCyborgRom.G892A-2ARA1.Part1.zip
[Alternate Mirror]
PartCyborgRom.G892A-2ARA1.Part2b.zip
[New: Fingerprint/Sensors all working]
(New!) V3 Bootloader Revision
SM-G892A: PCR_G892A_BLV3.7z
SM-G892U: PCR_G892U_BLV3.7z
Odin
Prince Comsy Odin
One more time
I'm gonna celebrate it
Oh boy I'm first in the thread lol. No bagsssss.
I'm outa thanks for the day but they is comin
How to I know what version of Bootloader I have?
Yu-Ra said:
How to I know what version of Bootloader I have?
Click to expand...
Click to collapse
What is your baseband version
Mine has the u2 in it means I'm v2 look in pic
Can't unzip part 1, re DLed it multiple times can only extract 518mbs then crc error.
Pjs187 said:
Can't unzip part 1, re DLed it multiple times can only extract 518mbs then crc error.
Click to expand...
Click to collapse
I will let him know this was a issue the other day as well
That would be the AP part right
TheMadScientist said:
I will let him know this was a issue the other day as well
That would be the AP part right
Click to expand...
Click to collapse
Yes sir. TY.
Pjs187 said:
Yes sir. TY.
Click to expand...
Click to collapse
He may be busy I dropped him a note It happened a while back while he did the reg s8 betas also something with the zip file is corrupt
The downloads worked for me, no issues. If you're on a tmobile variant this rom will work fine also if you're on BL 1 att you'll be fine not sure about sprint, my fingerprint scanner, iris scanner & face recognition don't work but everything else running perfect.
Purest said:
The downloads worked for me, no issues. If you're on a tmobile variant this rom will work fine also if you're on BL 1 att you'll be fine not sure about sprint, my fingerprint scanner, iris scanner & face recognition don't work but everything else running perfect.
Click to expand...
Click to collapse
Hmmm the download extract was broken for me as well. But should be fixed sometime soon.
TheMadScientist said:
Hmmm the download extract was broken for me as well. But should be fixed sometime soon.
Click to expand...
Click to collapse
What mirror did you use? Some of the mirrors were giving me issues, the Texas mirror was the only one working properly for me.
Purest said:
What mirror did you use? Some of the mirrors were giving me issues, the Texas mirror was the only one working properly for me.
Click to expand...
Click to collapse
Lol that's the one I used
Purest said:
What mirror did you use? Some of the mirrors were giving me issues, the Texas mirror was the only one working properly for me.
Click to expand...
Click to collapse
TheMadScientist said:
Lol that's the one I used
Click to expand...
Click to collapse
Pjs187 said:
Can't unzip part 1, re DLed it multiple times can only extract 518mbs then crc error.
Click to expand...
Click to collapse
Sorry for the trouble folks! The zip extracts fine on my end, so it must be an AFH issue. Ill do what i can as im s paying customer, but we will see. In the meantime, i posted another link under "Alternate Mirror", so download from there if you are having issues.
ill reupload it to afh as well
Bootloader V2 support is now up in the OP!
Hey what version of xposed did you use, note 8 xposed isn't working wondering if you used a modified version or what you might have used?
partcyborg said:
Sorry for the trouble folks! The zip extracts fine on my end, so it must be an AFH issue. Ill do what i can as im s paying customer, but we will see. In the meantime, i posted another link under "Alternate Mirror", so download from there if you are having issues.
ill reupload it to afh as well
Click to expand...
Click to collapse
Awesome work OP thank you very much, got everything up and running now very nice, let me know where to send money for the bounty.
Pjs187 said:
Awesome work OP thank you very much, got everything up and running now very nice, let me know where to send money for the bounty.
Click to expand...
Click to collapse
I knew I forgot something!!!
https://www.paypal.me/partcyborg is the link. I will add it to the op too.
INTRODUCTION
I posted my configuration before inside a couple of threads. After that, I have received a lot of questions about the same issues. I have also been asked to create a thread so newbies could have an easy way of having an Oreo system up and running in the Axon 7. So I am doing it. Newbies will have an easy entry point to the world of custom Oreo ROMs and a single point to clarify any question. We have a healthy and active Axon 7 scene here at XDA. This guide provides a path to have a custom Oreo system with the latest features available for this device requiring a minimum effort. It applies to any of the 3 Axon 7 flavors: A2017 (China), A2017G (Europe) and A2017U (Americas) with any memory and storage capacity. At this time there are 3 groups of ROMs depending on the Bootstack and GSI support:
1. B32+B10 ROMs use the reliable Nougat bootstack. They are very stable and battery efficient. On the other hand, none of them support dual SIM or HDR+ camera. However they support HDR and Camera2 API.
2. B12 without GSI support ROMs use the Oreo beta B12 bootstack. Full support for Camera2 API and HDR+ but very poor battery performance and stability issues.
3. B12 with GSI support ROMs also use the same Oreo beta B12 bootstack. They also require a separated vendor partition. They share the same benefits and limitations of the previous group. So far they are experimental and the Treble ROMs don't support yet all the Axon 7 Hardware when using them along with a GSI image. They are examples of a Work-In-Progress that is yet to be finished.
WHAT THE HECK IS TREBLE AND GSI?
Since Oreo, all the new devices must have a separated vendor partition to fulfill Google's Treble project requirements. This way the OS is structured in two parts:
1. Treble ROM: includes all the device drivers and vendor related files in the vendor and boot partitions. The Treble ROM is owned and updated by the device vendor or a custom ROM developer.
2. Generic System Image (GSI): Includes the Android OS, it is controlled by Google and allow generic and frequent security and system feature updates directly from Google. It uses the system partition.
So far, custom Android distributions such as LineageOS, Resurrection Remix, AOKP, Dirty Unicorns, AEX, etc... had to create specific ROMs for each supported device. This was painful and it all was depending on the willingness of a developer to maintain a version for each device. Thanks to Treble project, now Android distributions just release a single GSI able to be installed in any device using a Treble ROM. This way they can properly maintain all the devices with a single GSI image by focusing on frequent updates of a single GSI. These custom distributions will also deliver the security and feature updates by Google. So a fully Treble ROM for the Axon 7 will open the door to virtually all the Android distribution out there.
@NFound in the AEX ROM thread) is the only one working in developing a Treble ROM for our device. He has released some incomplete Treble ROMs coupled with non-generic system images. Others like @Kranoner in the Hellsgate Kernel thread or @OrdenKrieger in the LineageOS 15.1 are building and kindly sharing unofficial releases of several custom Oreo 8.1 ROMs that are used in the EDL packages below.
@Victor13f has also created guides on how to install the leaked Stock Oreo 8.0 Beta B12 ROM. I really advise to upgrade to any of the current Oreo ROMs since the current unofficial releases work way better than the previous Nougat versions. The custom AOSP Oreo 8.1 ROMs offer a wider spectrum for tweaking for better performance and battery. Custom kernels are adding full featured and optimized drivers for custom ROMs. They support almost everything, including backported drivers from the latest Linux 4.xx official kernel sources.
BACKUP:
Please note that a dirty flash won't work when coming from any non Treblerized Axon 7 (Axon 7 without the vendor partition). So, if you want to keep your information, then you should do a backup of your data before continuing with this guide. You can use the file manager to move your Documents, Downloads, Music, Pictures, Videos, etc... from your internal storage to an external SD card. You can upload them to a cloud service such as Google Drive, One Drive, MEGA, DropBox, etc. Or use the USB connection to move your information to your PC.
DEVICE UNLOCK:
Unlocking your bootloader will trigger a factory reset, and will delete the internal storage along with all the information in your phone. If your Axon 7 bootloader is still locked, you have to follow this guide before proceeding to the rest of this guide. It works for Marshmallow and Nougat stock phones. Please use that thread to ask any question related to unlocking your device.
INSTALLATION INSTRUCTIONS:
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES YOUR DEVICE TO BE UNLOCKED, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
In case you get stuck at any point in this guide, do not panic! There is a straightforward way to go back to stock. Just follow this Unbrick/Restore guide. I've tried to make things as easier as possible for everyone, specially newbies not used to deal with the Axon 7. So, I have created stable custom EDL packages. In order to reduce the risk and complexity, this one Stop ROM Shop performs all the following actions in a single flash:
- installs TWRP custom recovery
- installs my customized Bootstack
- removes unlocked bootloader annoying warning message.
- installs custom Oreo ROM.
- installs google apps.
- installs custom kernel.
- installs magisk root
- creates vendor partition to treblerize your phone, this way it will be futureproof.
- formats vendor partition as ext4 filesystem to complete the previous task.
- And the guide also helps you to format data and cache as f2fs in case you haven't done it already. It provides better battery, performance and extends the lifespan of the internal flash.
I provide here 2 basic EDL package options. Both of them include the vendor partition so you won't have to perform any additional formatting and backup when upgrading to treble roms. Both options are this way future proof, just choose one of them:
OPTION 1: B32+B10 based EDL Package if you prefer stability. It includes:
- N+O custom Bootstack (B32+B10)
- TWRP 3.2.1-7 recovery by NFound
- Resurrection Remix Oreo 6.0.0 2018.05.11 ROM By Kranoner
- Google apps (ARM64, 8.1, micro)
- HellsGate v3.0 Kernel by Kranoner
- Magisk root 16.7
OPTION 2: B12 based EDL Package If you require dual SIM or full support for HDR+ camera apps. It includes:
- O custom Bootstack (B12)
- TWRP 3.2.2 recovery
- AEX 5.7 20180711 ROM by NFound
- Google apps (ARM64, 8.1, micro)
- HellsGate X12 GClang Kernel by Kranoner
- Magisk root 16.7
Once you had chosen your preferred option then proceed with these steps:
Download and Un7zip the chosen package to a folder in your computer, ensuring there are no errors. I have an A2017U, so the American modem is the package default. If you have an A2017 or A2017G just copy your modem firmware, from the corresponding provided modem subfolder, to the main folder. Just overwrite the default American modem file.
Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest Qualcomm drivers.
Enter EDL mode using one of the following options:
by pressing VolUp+VolDn+Power until the power led flashes briefly
Installing a terminal app and typing reboot edl at the app prompt.
connecting your phone to your PC and typing adb reboot edl at your computer's command prompt.
While your phone is completely off, press VolUp+VolDn while connecting your phone to your PC.
If you haven't done yet, it's time to connect your phone to your computer.
Open MiFlash in your computer.
Click Browse button and select the folder you created with the firmware files.
Click Refresh button and your device will appear listed as virtual COM port.
Click Flash button and wait for a few minutes until it finishes. Note the bottom options are not applicable.
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery. Go to Advanced > Terminal and now type: reboot "dm-verity enforcing"
Press VolUp+Power until the phone vibrates to enter into recovery, then release both buttons. Go to Advanced > Terminal and type: reboot disemmcwp
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery for a 3rd time. To ensure everything is clean you should format the DATA partition, including internal storage. Go to settings and ensure "Use rm -rf instead of formatting" option is not selected. Then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Select F2FS and confirm action. Do the same to apply F2FS to the Cache Partition. Now, from the main menu > Wipe, select and clean dalvik.
NOTE: If you receive an error while formatting data, then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Format DATA as EXT4 first and, without leaving TWRP do it again as F2FS. That will fix the issue.
Go to main menu and reboot system.
Complete the setup process so you can continue with the rest of the customizations not included in the basic package:
SOUND EXPERIENCE:
The following steps will provide you with Dolby ATMOS and Viper4Audio pre-processors along with the HiFi DAC output. Please note that the activation of these features will drain your battery faster since both will use your CPU. Nonetheless the benefits are evident. if you want to fully enjoy the audio capabilities of the Axon 7 you should go ahead and use them. The steps are:
Download Mixer_AK4490.zip and Dolby-Oreo.zip to your phone.
Open Magisk Manager app, go to the Download section and Download (do not install yet) Ainur Sauron, Viper4Android FX and Audio Modification Library.
Reboot to recovery the same way you did during System installation, press install, navigate to /sdcard/MagiskManager folder and install Ainur Sauron, Viper4Android (I prefer 2.5.0.5 and traditional interface, however it is all up your personal preference) and Audio Modification Library zip files in that order. Do not reboot after flashing these files, just navigate now to the /sdcard/Download folder and flash Dolby-Oreo.zip and Mixer_AK4490.zip
SCREEN COLOR ENHANCEMENT:
Download and install KCAL Color Calibration/enhancement app. I only modify the Saturation to 62 to get amazing vibrant colors from this AMOLED screen, nonetheless this is a very personal configuration. At the end this has to please your own eyes. . This app optional since Kernel Adiutor and EX Kernel Manager apps can also configure Qualcomm SoC Color Control.
AVOID BATTERY DEGRADATION:
Install Battery charge Limit [ROOT] app. Open it and set Limit charge to 85% and recharge below 79%. Do you want to avoid your battery to wear as the time go by? do not miss this guide to understand why this step is so important for the health of your device.
BETTER CAMERA:
+ Snap Camera App
I am using, and heavily recommend the paid version of Snap Camera HDR. It supports Camera2 API with full manual and HDR support. Find recommended settings here.
Testing now GCAM v4.0. Nonetheless so far I am just starting testing.
Bacon Camera is another Camera I am now actively testing.
The next level of this guide will provide with instructions on how to change recovery, ROM, kernels and all the details and options you have. It is late today so I'll finish it later.
Hope it helps. I will be updating this guide in the future as soon my configuration changes or I find new technologies, apps or patches. If you know about a better option just post your suggestions!
Thanks and credits go to @NFound, @Kranoner, @Infy_AsiX, @roisuke, @Skrem339, @djkuz and you too for bringing up issues and valuable solutions.
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
kitcostantino said:
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
Click to expand...
Click to collapse
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
This was actually why:
NFound said:
TWRP Exclusive™
For "U" models pacth cleaning inscriptions bootloader NO BET!
Warning! "Del Inscription" - only for A2017 and A2017G !!!
Click to expand...
Click to collapse
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
kitcostantino said:
This was actually why:
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
Click to expand...
Click to collapse
Well NFound just tried to say that his solution was not tested at that time in an A2017U. Actually the 2017U is unbrickable thanks to the hardware EDL mode of the Qualcomm SOC.
By the way, I have updated the OP. Now it matches my current configuration. I have also mentioned my current testing efforts in the battery and camera areas.
Regards
Hi. Any fix for Dual Sim? I read through XDA and it seems dual sim is still not fixed. I am getting tired with nougat ROMs but without dual sim I have to stick with it...
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Dave_XDA said:
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Click to expand...
Click to collapse
Yes, the guide is valid for any Axon 7 flavor: Chinese, Euro and Americas.
marcdw said:
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Dave_XDA said:
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Click to expand...
Click to collapse
There is no problem as long you have an Oreo Bootloader. Since you are already running a custom Oreo ROM it means you already have a valid bootloader. Thus, you only need to flash the RR-O ROM. Should you find any problem you can just flash the latest bootloader I link in the OP or go back to AEX. It is important to do a clean install when switching Oreo flavors, as you plan, otherwise you will face problems.
Thanks for this. Been running stock since I got the phone, but missing the old phone days where I used to flash something new like once a week. Gonna try this out tonight I think. Really appreciate the concise directions
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
amphi66 said:
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
Click to expand...
Click to collapse
No issues, you can always go back to B35.
Oki said:
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Click to expand...
Click to collapse
Thanks for the info.
Never used/explored TWRP Exclusive's extras really. In my environment I might break something [emoji39] but cool that everything is there.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
How long does the first boot after flashing the bootloader take? I don't seem to get past the ZTE powered by android screen.
Never mind. Just hold Power + Volume Up at boot.
Thanks !! Oreo AND RR together !!
I will flash it tomorrow on my A2017G !!
(maybe you should write the A2017G compatibility on the first page because this :
RR-O-v6.0.0-20180422-axon7-Unofficial.zip
for the ZTE Axon 7(2017U), by Kranoner
on androidfilehost almost made me missed it )
EDIT : Does this ROM+kernel have the dualsim problem ?
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
ashishv said:
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
Click to expand...
Click to collapse
What have you really done my friend? This guide requires a complete cleanup so it is impossible that you had any locksettings after a clean install. If you follow all the steps and follow the guide then you shouldn't have any problem.
The lock settings get corrupted after migrating to f2fs, and you can also find that problem when dirty flashing some roms or kernels. For that reason, to take care of that step, in the f2fs migration link, there is a link to a very detailed way to cleanup the lock settings. You can find that guide here: https://forum.xda-developers.com/axon-7/how-to/guide-access-locked-axon-7-how-to-t3525403 but, it shouldn't happen when following the steps of this guide. By the way, this guide requires RR Oreo ROM, and you mention you are using AEX Oreo...
I might have found a quick and dirty Method to Port TWRP to the newest 7.2 shield experience. It's not guaranteed, but it's a chance im going to try. But as I didn't upgraded my own shield yet, I need some files from someone who has rooted his shield already.
1. Is an recovery.img
2. The build.prop
If I can get hands on these files I might be able to bring up a testing version asap
Enough. Seriously.....
Keep it clean, and on-topic... The rules are there for a reason. Don't remember them? HERE you go.
Adromir said:
I might have found a quick and dirty Method to Port TWRP to the newest 7.2 shield experience. It's not guaranteed, but it's a chance im going to try. But as I didn't upgraded my own shield yet, I need some files from someone who has rooted his shield already.
1. Is an recovery.img
2. The build.prop
If I can get hands on these files I might be able to bring up a testing version asap
Click to expand...
Click to collapse
If you want the files
Then can you please update your Sheild tv to the latest firmware for us 7.2.2
An back up the recovery.img
An back up your build.prob
Because I can't help you! I refuse!
Thx again have a great day
i hope you can port the twrp to nvidia sheild tv thx
Foster_e (Shield TV 2015 16GB) - 7.2.2 (30.7.130.7)
recovery.img + build.prop
https://drive.google.com/open?id=18E_u8as1E9dstmRtRwPb97hALdmsrdsc
The recovery is dumped directly from
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS -> /dev/block/mmcblk0p16
No offense but quick and dirty does not do it on the new kernel.
You can port as much as you like and it might work for the older models but certainly not for the 2017 model.
And if you have no clue how to get the required files by simply exctracting the firmware files that you can download then I wonder how you will be able to actually modify the recovery image.
People with quite some experience tried and failed, so unless you compile TWRP from source he proper way it won't work (at least not on the 2017).
And even if compiled correctly there is no garantee it will be usable with the secure boot restrictions still in place.
You need a fully rooted device to fully use TWRP and you can not root the 7.2 in the simple way anymore.
Fully rooted the normal TWRP will work just fine.
Downunder35m said:
No offense but quick and dirty does not do it on the new kernel.
You can port as much as you like and it might work for the older models but certainly not for the 2017 model.
And if you have no clue how to get the required files by simply exctracting the firmware files that you can download then I wonder how you will be able to actually modify the recovery image.
People with quite some experience tried and failed, so unless you compile TWRP from source he proper way it won't work (at least not on the 2017).
And even if compiled correctly there is no garantee it will be usable with the secure boot restrictions still in place.
You need a fully rooted device to fully use TWRP and you can not root the 7.2 in the simple way anymore.
Fully rooted the normal TWRP will work just fine.
Click to expand...
Click to collapse
So if I understand you correctly the only way that a recent version of TWRP would work on 7.21 and above are if you have a "rooted" developer image? I have stayed with 7.1 (rooted with a flashed TWRP recovery) My expectation is that Ill stay with it until a stable version is released.
Odd thing is every OTA notification I get refuses to install. It just boots to TWRP without updating. I even opted in for the 7.2.2 beta updates and the shield refuses to update. Kinda thankful as others seem to have so many issues, just not worth it until 7.3 is released perhaps?
Any decent update is worth applying.
But if you ask if it is worth it for those really needing full root access then the answer is no.
The cummunity behind the shield might not be as big as behing Samsung devices but I am sure something will be figured out sooner or later.
@Downunder35m : As I mentioned in a deleted Post, I know how to get these Files from the recovery images. But they are Still 7.2.1 and as 7.2.2 already I didn't see a point in starting with already Outdated Files.
What kind of Things have you been trying already? My Approach was, that maybe TWRP hangs itself, because it can't find the Vendor and system Partition. After unpacking the recovery.img i found out, that the partitions still get mounted, but not over over the fstab anymore but single commands in some init scripts. So my Idea was to patch the kernel of the recovery image with a proper fstab and then use that to build a twrp around it, with the modified boot image. But sadly the resulting TWRP exceeded the Partitionsize. But i didn't set up the Source Tree to compile correctly, because I assumed that with such a breaking approach nvidia did at least moved onward to Android 8.1 ..
A real life job sadly limits my time far more than what I would like.
So maybe my failures are of use to you...
Lets start with the basics:
(All for the 2017 model!)
Firstly, the bootloader has changed and now enforces basically everything Google has on offer.
This means you can not just boot into a custom recovery because the bootloader does not accept it as genuine.
Lets say you get around this problem by, dor example, compiling TWRP from source and with the not yet realesed NVidia 7.2 sources.
There might be other ways but right now I think we can't get around compiling it from scratch.
Once you are able to somehow properly boot into TWRP there is more problems:
A lot if not all special rights and permissions are now handled almost exclusively by the DTB, or to be precise the DTS, which is compiled during boot.
By default TWRP does not make any use of the DTB but instead relies only on the FSTAB configuration.
And since TWRP is not an authorised service, task or app the bootloader won't provide the required rights.
The system partition stays invisible, the vendor part locked and since TWRP is required to copy or store at least some things somewhere this is detected as a possible intrusion.
As that the bootloader now marks the entire system as compromised - the dreaded corrupted system message appears and the system fails to boot.
You could tweak the init files, get the complete FSTAB info from the plat - and nonplat_file_contexts and even fiddle with the rest.
Then you get this happy feeling of a booting TWRP, pull a backup and think all is fine.
That it until you try to reboot and nothing works anymore.
The backup is useless as firstly you can not write it back and secondly it will be encrypted or otherwise corrupt.
To be able to use TWRP ADBD must be able to run in root mode, this is not possible by default on a user or release build, which NVidia now provides as a "developer" firmware.
A bootloader set to enforce all SeLinux and DM-Verity funtions will not allow any vital modifications to any vital part of the system.
In theory you must first at least free the bootloader (we can not do that) or destroy the safety, like by using a modified DTB.
Then you must make sure that you modifiy the prop files so full ADB and ADBD rights are available where they are needed.
After that TRWP will run just fine but it creates a cricle that first needs to be broken somehow
No root rights means no TWRP, no TWRP means no mods to the system.
Magisk currently fails to help us as it does not make use of DTB features at this stage.
And if you ask me then messing with the DTB can backfire badly.
Unlike normal firmwares we won't get a DTB partition included in the boot image or kernel image.
So once the dTB is stuffed too much it will be hard to impossible to install a genuine or custom firmware.
Once Pie comes out this will be worse.
Here the DTB too will be protected and generated/checked during boot.
Unless NVidia wakes up and removes these restrictions from the developer firmwares we will be locked out until someone finds a way to restore full root rights.
Right now I am hopin they will still release the full sources one day.
With a massive effors one could then just compile a normal userdebug firmware and all is fine once more.
Any luck yet? I upgraded one of my Shield TV to 7.2.2 from 7.2.1 dev root and want to install Magisk....
Thanks!
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
UPDATE: Boots but not working correctly so removed links
leezaal said:
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
https://www.androidfilehost.com/?fid=6006931924117905072
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
https://www.androidfilehost.com/?fid=6006931924117905072
Click to expand...
Click to collapse
Every time i open recovery it works, but after trying to reboot it bootloops at nvidia. I flash-all and it works again until i enter recovery (then botloops again on reboot). Am i missing something? (shield 2017 7.2.3 dev edition)
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1BCfXg9pUpFm_3sPXp_nEwBlkNU9nelkg/view?usp=sharing
rootfan said:
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1REnehReTaA5BamUBDe8XmBMyZG6zQkFB/view?usp=sharing
Click to expand...
Click to collapse
there is always the bug for 4k screen display?
rootfan said:
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1REnehReTaA5BamUBDe8XmBMyZG6zQkFB/view?usp=sharing
Click to expand...
Click to collapse
Many thanks i renamed this to recovery.img and renamed magisk boot img to boot.img reflashed both as part of the whole 7.2.3 dev OS shield tv 2017 image.
booted into TWRP via adb from my pc it loads up fine on my LG 43" 4k tv no problem rebooted and got back into 7.2.3 also without any issues
UPDATE: TWRP will not let me wipe system / data or anything else or mount any partitions in order to wipe before trying to install anything making this sadly kinda useless right now
twrp seems complicated to be functional lately, the same on my mi max 3, but orange Fox might be better on Shield
leezaal said:
UPDATE: TWRP will not let me wipe system / data or anything else or mount any partitions in order to wipe before trying to install anything making this sadly kinda useless right now
Click to expand...
Click to collapse
Well that makes sense because I was overwriting the emmc fstab with the sata one. I've updated my original post with a link to a new twrp that should have this problem fixed. If you're still having issues please click on the menu button to the right of the home button in twrp and tell me what the log says. Do this when first booting into twrp before doing anything else. It should say something like the following with no mounting complaints if everything is working right.
Shield Debug: Hardware variant is darcy
Shield Debug: Using emmc fstab
Shield Debug: Found required fstab
rootfan said:
Well that makes sense because I was overwriting the emmc fstab with the sata one. I've updated my original post with a link to a new twrp that should have this problem fixed. If you're still having issues please click on the menu button to the right of the home button in twrp and tell me what the log says. Do this when first booting into twrp before doing anything else. It should say something like the following with no mounting complaints if everything is working right.
Shield Debug: Hardware variant is darcy
Shield Debug: Using emmc fstab
Shield Debug: Found required fstab
Click to expand...
Click to collapse
Thanks for the great feedback will DL the updated TWRP and give it a go will report back shortly
UPDATE: 100% working ! Amazing work all partitions mount etc no problem FULLY working TWRP on my 4k TV too
it's harder to pin down clear decisive info on this box than I thought.
can someone confirm whether using magisk manager (an older version 7xx or 8xx) will successfully flash magisk onto this box without bricking it ?
I've seen a TV Box Stop video on this box that stated messing with the included SuperSU bricks the box...
can it be done via TWRP or patching a downloaded update zip ?
all knowledge welcome
The amlogic boxes, magisk does not work unless you hexedit your boot image. It will install, but not function.
There is a video tutorial on 4pda (russian site)on how to do so, and I'm writing up a visual tutorial at some point soon.
I did the process myself one time, and it works.
The issue I am currently having is my Amlogic Box is also a new "mystery" box.
Repacked by a company called "CONCEPTUM" for the greek market here.
The Model is X96 Air Extreme. I have disassembled it and got the specs on it and photos, and will make a post soon.
Have you gotten yet photos of your internals?
This particular box is somewhat compatible with the
X96Max_Plus_Q2_20201209-1446.img (I had to flash it with that.. long story), everything internal works but the wifi only connects at 54 mbps, not sure if its because of a firmware driver mismatch or its a POS.
I'm looking to flash slimbox pie eventually, I'd rather not open my box if I can avoid it.
Ex Kernel manager reports:
• available ram @ 3794mbs
• max clock speed @ 1908mhz and 4 cores
• GPU mali-G31 with OpenGL ES 3.2
for testing which box you have slimhouse wrote this:
First of all, you should look at the system information in the settings, it will be displayed there: Plus, Plus2, Plus100, etc. However, crooks can fake this and stickers.
Using Device Info HW, you can determine whether there is a 1000Mb LAN and which radio module (turn on WiFi!). If the device was flashed with firmware for another modification, then the information may be missing or unreliable - you need to open and check the presence of the LAN 1000 chip and which radio module is installed.
#
The radio module can be identified by the marking on the chip or by the sticker on the board
X96 Max Plus2. Availability Of 1000Mb Ethernet RTL8211F. You can make sure by connecting 1Gb-supporting devices to the equipment or using Device Info HW, or visually by the presence of a chip on the board. There are 2 antennas. RTL8822CS Radio Module
#
X96 Max Plus2
There was a modification of Plus2, but 2GB of RAM, only the 202009 flash and the special flash for 2GB RAM from JAW are sewn. Photo
And there is also a Plus2 version with the RTL8822BS radio module (Fn-Link 6222B-SRB), there is a problem with the radio module on the ports of Yugos.
Device Info HW says my box has a Wi-Fi chip numbered RTL88x2cs, that's not exactly the same as listed above...
I flashed slimbox pie on this box yesterday and all is more less well with the rom, but this box has no ramdisk and even though TWRP flashed successfully according to he official TWRP app i cannot boot into it.
the box tries 2 or 3 times and boots back to the system. without TWRP that i can get to there's no chance of magisk.
any thoughts or advice welcome
3mel said:
I flashed slimbox pie on this box yesterday and all is more less well with the rom, but this box has no ramdisk and even though TWRP flashed successfully according to he official TWRP app i cannot boot into it.
the box tries 2 or 3 times and boots back to the system. without TWRP that i can get to there's no chance of magisk.
any thoughts or advice welcome
Click to expand...
Click to collapse
you need to find a firmware to flash, you can then modify it with magisk and flash it, i made a guide here on the process
aidanmacgregor said:
you need to find a firmware to flash, you can then modify it with magisk and flash it, i made a guide here on the process
Click to expand...
Click to collapse
thanks for the response
will this work on any rom suitable for the box ?
I'll have get YouTube to slow down the video a little so it's easier to follow what you're opening but I think I get the general unpack repack idea.
if you know of a TWRP image that's flashable via flashify or TWRP official app and that works on this box, can this technique be shortened by just patching that image pre-flash ?
I dropped back down to this boxes stock image, Slimbox couldn't keep magisk running and at random times root just stopped working. I tried Aidan's rom but the UI is not for me and there's no sideloading allowed ?? and it couldn't see my memory card anyway.
with the help of Aidan's guide above I got magisk working on the stock rom but I still have a default su binary that came with the box and has no visible root switch. if anyone knows of a way to deactivate it please share.
thanks