TouchWiz-4.4 ROM FIXER for Developer Edition devices
WARNING: These files are for Developer Edition devices ONLY. Kernels cannot be flashed on the retail VZW Note 3 devices!
THIS PROCESS ALSO SETS KNOX 0x1
Own a DevEd? Flashed the firmware/modem bits to the new TW4.4 in hopes of seeing some of the improvements or running a stock-modded ROM?
FIRST: Big shout out to @Imoseyon who has a VERY nice kernel for unlocked devices here:
http://forum.xda-developers.com/showthread.php?t=2488082
Go over there and tell him thanks, because I had spent a day or so trying to fix up a boot.img but wasn't having much luck due to a crash in TIMA memory. But, then I read that someone had gotten the leak booted w/ Imoseyon's kernel and was able to rip it apart and pull just the absolute minimum changes to get a VERY close to stock kernel / ramdisk setup for the 4.4 leak.
WHAT IS THIS?
Several issues were noticed immediately on DevEd devices due to the fact that we can't flash certain portions of the updated ODIN files (aboot, sbls, etc):
Play Movies won't stream
External SD card won't mount
Lockscreen settings don't work
Imoseyon's kernel was the only boot.img which would run 4.4 leak due to aboot/devicetree changes and TIMA crashes
The files below fix these issues and provide a VERY close to stock boot.img for use on DevEd devices.
FIX FILES: 2 flashable .zip files (for use in recovery):
1st flash file: flash-vzw-de-4.4-kernel-v1.0.zip
This is a rebuilt boot.img containing:
New NC2 stock-based kernel with CONFIG_TIMA disabled
Rebuilt dt.img using 1st gen dtbTool for use with our 4.3 aboot
Ramdisk has default.prop changes for disabling TIMA, KNOX and securestorage (Credit: @Imoseyon / leanKernel 2.4 ramdisk)
This file only needs to be flashed once (as long as you don't swap to AOSP ROMs). You can also use leanKernel by @Imoseyon if you like his work. The difference between this kernel and his are: I used the identical settings as the stock NC2 kernel (Kernel modules are enabled, etc) in an attempt to eliminate as many differences between the DevEd and the retail device. His kernel has a TON of tweaks and updates. But, could in theory have issues running the stock NC2 VZW leak.
Kernel source: https://github.com/Hashcode/android_kernel_samsung_hlte/tree/hlteatt-kk-nc2
2nd flash.zip file: flash-tw44-sys-files-fixes-v1.0.zip
A set of system file changes which fix the issues noted above (this file should be flashed after EVERY TW-based ROM is flashed)
Downloads:
Mirror 1 (Goo.im)
Mirror 2 (Crackflashers)
Instructions:
Download the above files and place them on your device's storage
Reboot into recovery
Flash flash-vzw-de-4.4-kernel-v1.0.zip if you need to fix kernel (coming from AOSP)
Flash flash-tw44-sys-files-fixes-v1.0.zip after ANY flash of TW-based 4.4 ROMs to fix system files
Reboot, no need to wipe cache, etc
XDA:DevDB Information
[DEVED/TW-ROM FIX] Developer Edition TW-4.4 ROM Fix Files, a Tool/Utility for the Verizon Samsung Galaxy Note 3
Contributors
Hashcode
Version Information
Status: Beta
Stable Release Date: 2014-04-27
Created 2014-04-27
Last Updated 2014-04-27
Reserved
Nice!
The sdcard fix worked but the screen security and play movies remains the same in captions of screen security it looks like this.
Edit: options not available due to device administration: screen lock security, encryption, credential storage type=backedup to hardware.
Great! Quick test results:
I can see my exFAT 64GB external SD card.
Cut and paste works with my password manager.
I still cannot set a screen lock PIN.
Sent from my SM-N900V DevEd using Tapatalk
I just received a PM from @oah2010 with the following fix for the screen unlock PIN/Password problem. He says:
Hi,
I don't post enough to reply to the thread in beans new dev edition kernel, but I wanted to let you and the other guys know about how I got the pin and password unlock to work for me.
I found it on a random xda thread:
In build.prop,
security.mdpp.result=None, changed to #security.mdpp.result=None
This let's you use the pin unlock as well as the other options that are currently greyed out.
This works for me with the deodex 4.4 rom and leankernel even before applying the fixes in beans new thread.
Please post this in the thread so other people will know.
Hope this helps.
Click to expand...
Click to collapse
I have not tested this yet since I have done very little file editing. Must backup first. Then I will test.
DavidFlory said:
I just received a PM from @oah2010 with the following fix for the screen unlock PIN/Password problem. He says:
I have not tested this yet since I have done very little file editing. Must backup first. Then I will test.
Click to expand...
Click to collapse
I tested this. It booted the phone up into a safe mode and reset my wallpaper/widgets. Still no luck with the lock screen.
I revered the change.
---------- Post added at 10:08 AM ---------- Previous post was at 10:05 AM ----------
Big thanks to @Hashcode! SD Card (EXFAT) is working great!
I have been getting a couple lock ups/random reboots a day while on leanKernel. Going to run with this kernel for a while to see if that still happens.
stargzrr11 said:
I tested this. It booted the phone up into a safe mode and reset my wallpaper/widgets. Still no luck with the lock screen.
I revered the change.
---------- Post added at 10:08 AM ---------- Previous post was at 10:05 AM ----------
Big thanks to @Hashcode! SD Card (EXFAT) is working great!
I have been getting a couple lock ups/random reboots a day while on leanKernel. Going to run with this kernel for a while to see if that still happens.
Click to expand...
Click to collapse
worked perfectly here you have to open it with text editor after mounting system r/w and delete the old copy of build properties after the new one is generated when you click save and exit, then mount the system r/o and reboot. Now get play movies going and I`m golden
mount r/w, change with text editor to #security.mdpp.result=None, click save and exit, mount r/o then reboot. Also verify that permissions are identical to the original. I hope I explained that better the second time sorry. Now I believe encryption will work too since a passcode can be set. Thanks @oah2010 and @DavidFlory .
Thepooch said:
worked perfectly here you have to open it with text editor after mounting system r/w and delete the old copy of build properties after the new one is generated when you click save and exit, then mount the system r/o and reboot. Now get play movies going and I`m golden
mount r/w, change with text editor to #security.mdpp.result=None, click save and exit, mount r/o then reboot. Also verify that permissions are identical to the original. I hope I explained that better the second time sorry. Now I believe encryption will work too since a passcode can be set. Thanks @oah2010 and @DavidFlory .
Click to expand...
Click to collapse
Thanks for the additional information.
I tried it again - I must have goofed up my build.prop somehow.
Regardless, it booted back up fine, but the swipe/pattern/pin lock options are still grayed out (just like the screenshot in the thread above). I tried wiping cache/dalvik without luck. Also tried re-applying Hashcode's sys-files-fixes zip - didn't make a difference.
I do see there is also a "security.mdpp" line in the build.prop a few lines above. Wonder if that needs commented out too.
---------- Post added at 11:39 AM ---------- Previous post was at 11:17 AM ----------
Thepooch said:
The sdcard fix worked but the screen security and play movies remains the same in captions of screen security it looks like this.
Edit: options not available due to device administration: screen lock security, encryption, credential storage type=backedup to hardware.
Click to expand...
Click to collapse
Play movies is working for me...
If it's still busted for you, try going into "Application Manager", "All", find "Google Play services" and click "Uninstall updates". Once you uninstall it, Hangouts should immediately popup saying you need to update Google Play services. Re-apply this update. Try play movies again...
Question folks: Will flashing this + Beans' kk Rom update the DE's modem to the current kk from MJE? I don't plan on running touchwiz on my DE but I'm wondering if I should just flash it to get the new modem (baseband) and then go back to AOSP.
TSman74 said:
Question folks: Will flashing this + Beans' kk Rom update the DE's modem to the current kk from MJE? I don't plan on running touchwiz on my DE but I'm wondering if I should just flash it to get the new modem (baseband) and then go back to AOSP.
Click to expand...
Click to collapse
No firmware update in this. Just ROM and kernel.
As far as I know there isn't a flashable modem firmware for that yet.
Sent from my SM-N900V using Tapatalk
I should say for my device, I'm not 100% sure if I flashed @BeansTown106's ROOT/ROM or whether I flashed the leak's system.img.ext4 file via heimdall (I remember flashing SuperSU initially to get root tho).
And I literally have no extra mods installed other than these.
So, I'd like to keep track of who has the following working and what users are doing to fix their issues:
- SD card (seems like it's fixed for most)
- Play Movies (@ThePooch it's not working -- possibly need to remove the updates / re-install?)
- Lock screen settings (Seems like I'm still the only one with working settings :/ -- possibly need a build.prop fix)
I have a theory that something in the ROOT ROM is causing the lock screen issues. My stock ROM was a direct flash of the system.img from the leak. But on rom-slot1 I installed Beans ROM. I have working lock screen setting on stock and the issues as everyone else on rom-slot1.
I'm researching the differences.
Sent from my XT1060 using Tapatalk
Thank you!
Hash,
I assume that we need to be on twrp 2.7 ( 4.3 edition).
Several people were complaining about the sd card not mounting -but fat32 wokrs.
here is a small donation 5W64555......
Thank you for keeping these devices up and running.
Hashcode said:
I have a theory that something in the ROOT ROM is causing the lock screen issues. My stock ROM was a direct flash of the system.img from the leak. But on rom-slot1 I installed Beans ROM. I have working lock screen setting on stock and the issues as everyone else on rom-slot1.
I'm researching the differences.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Rom slot ??? Wow now that is a difference I'm using TWRP 2.7.0.0 never once thought to use SS on a DE. Hmm I wonder could SS be the fix? How about running SS along side a native recovery? So your stock slot is not rooted and your running beans KK in Rom slot 1? This opens up many curious questions.
Thepooch said:
Rom slot ??? Wow now that is a difference I'm using TWRP 2.7.0.0 never once thought to use SS on a DE. Hmm I wonder could SS be the fix? How about running SS along side a native recovery? So your stock slot is not rooted and your running beans KK in Rom slot 1? This opens up many curious questions.
Click to expand...
Click to collapse
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
abe_cedar said:
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
Click to expand...
Click to collapse
Not a special edition, I'm debugging the retail version of Safestrap using the new leak setup.
abe_cedar said:
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
Click to expand...
Click to collapse
Do note that the kernel @Hashcode put up fixed the SD card problem. Exfat works fine with that kernel... I formatted my card back to Exfat.
Sent from my SM-N900V using Tapatalk
Dev Roms
Is there somewhere else we can put the Dev Roms and whatever else Dev there may be?
stargzrr11 said:
Do note that the kernel @Hashcode put up fixed the SD card problem. Exfat works fine with that kernel... I formatted my card back to Exfat.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Agreed. Are you using SS?
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
abe_cedar said:
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
Click to expand...
Click to collapse
I'm looking into it also thinking of the possibility of a special Odin package for the DE straight from the leak minus bootloader and plus Hashcode kernel so it will actually boot proper.
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
Latest Builds Here
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.[/QUOTE]
Links are up enjoy the light show
Twrp now has haptic feedback.
Wow...first post. I thought this would explode...Lol.
Great job dev.
Like the haptic... Thanx!
Sent from my SPH-D710
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.
HighxVoltage said:
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.
Click to expand...
Click to collapse
It works to flash jb+ I first built twrp when I was on stock then I flashed jb and went to 4.4
Sent from my SPH-D710 using Tapatalk
This is a repost of the twrp from a while back right?
sent from tumblr
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
I've used an older version of twrp. I install it through Odin then upgrade to this one.
sent from tumblr
@Linux guy this is a new build hint why it has haptic feedback.
Sent from my SPH-D710 using Tapatalk
Working great on my E4GT. Thanks
☞"And on the eight day the Lord made a backup"☜
Any chance for v2.7.0.0 in the near future?
CrimsonKnight13 said:
Any chance for v2.7.0.0 in the near future?
Click to expand...
Click to collapse
This is 2.7 basically I wait for major changes but probably in a week
Unjustified Dev said:
This is 2.7 basically I wait for major changes but probably in a week
Click to expand...
Click to collapse
Thanks! I look forward to your next release.
Any updates regarding 2.7 being compiled & released?
How does one flash this?
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"
os2baba said:
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"
Click to expand...
Click to collapse
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk
dirtyhewr said:
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?
os2baba said:
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?
Click to expand...
Click to collapse
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk
Surj138 said:
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.
os2baba said:
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.
Click to expand...
Click to collapse
This device is different because the recovery comes bundled with the kernel. This particular recovery is only for kk aosp ROMs... It overwrites the recovery those ROMs come with (CWM).
There are custom kernels for stock ROMs that come with a custom recovery. If you're on stock JB I recommend Agats 1.3
Trolling from my SPH-D710 using Tapatalk
This is for people who know how to debug to troubleshoot and correct issues in the jf tree, or at least provide relevant info.
Every post in the discussion thread should include your build string and variant, or you will be ignored.
I am not supporting your end user needs, but you can take that to the Q&A thread.
rom: https://www.androidfilehost.com/?w=files&flid=13420
use this gapps: https://www.androidfilehost.com/?w=files&flid=21354
do not flash another kernel
do not bring kk /data
known jf issues:
some overlays disabled
double tap home = camera is not working
swype on google keyboard not working
kernel source: https://github.com/CyanogenMod/android_kernel_samsung_jf
since nightlies are enabled, this thread wont be watched/updated anymore.
thanks for helping with the bringup.
Alright alright alriiiiiiiiiiight
Up & running, have cell and sound. Maybe NFC not working. GPS is, WiFi is. Thank you!
ROM is not able to access the SD card in my phone. Only the internal storage of the device is available. WIFI, GPS, and LTE are all able to connect without a problem. Camera is also working without issue.
hoffreaper said:
ROM is not able to access the SD card in my phone. Only the internal storage of the device is available. WIFI, GPS, and LTE are all able to connect without a problem. Camera is also working without issue.
Click to expand...
Click to collapse
what filesystem is it using?
hoffreaper said:
ROM is not able to access the SD card in my phone. Only the internal storage of the device is available. WIFI, GPS, and LTE are all able to connect without a problem. Camera is also working without issue.
Click to expand...
Click to collapse
Exfat isn't working yet I believe, fat32 does tho
How did you guys install it? I took a look inside the zip and found a lot of stuff missing, there's not even a build.prop, most of the bulk of the zip is on a file called system.new.dat
To the people who have this running What gapps are you using?
archangeles said:
How did you guys install it? I took a look inside the zip and found a lot of stuff missing, there's not even a build.prop, most of the bulk of the zip is on a file called system.new.dat
Click to expand...
Click to collapse
install zip in cwm as always
https://source.android.com/devices/tech/security/dm-verity.html#block-otas
Gapps
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
---------- Post added at 05:40 PM ---------- Previous post was at 05:32 PM ----------
dcd1182 said:
For testing...
Most stuff is working.
You tell me whats broken.
https://www.androidfilehost.com/?fid=95784891001613232
Click to expand...
Click to collapse
Did a test on making a call to my VM.while calling works ,trying to hang up it says hanging up but never does and VM lady just keeps talking til VM cuts off due to not entering anything
ShinySide said:
Gapps
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
---------- Post added at 05:40 PM ---------- Previous post was at 05:32 PM ----------
Did a test on making a call to my VM.while calling works ,trying to hang up it says hanging up but never does and VM lady just keeps talking til VM cuts off due to not entering anything
Click to expand...
Click to collapse
same here on 1st call, but 2nd+ call hung up fine. same for you?
dcd1182 said:
install zip in cwm as always
https://source.android.com/devices/tech/security/dm-verity.html#block-otas
Click to expand...
Click to collapse
I'm actually running twrp, do you recommend switch to cwm to install the zip?
I used CWM. No problems with 1st call for me, and good since
dcd1182 said:
same here on 1st call, but 2nd+ call hung up fine. same for you?
Click to expand...
Click to collapse
Na Tried 4 times, refuses to hang up. Acts like it hangs up visually but in call screen stays on saying hanging up and vm just keeps talking
archangeles said:
I'm actually running twrp, do you recommend switch to cwm to install the zip?
Click to expand...
Click to collapse
shouldnt matter
dcd1182 said:
install zip in cwm as always
https://source.android.com/devices/tech/security/dm-verity.html#block-otas
Click to expand...
Click to collapse
dcd1182 said:
shouldnt matter
Click to expand...
Click to collapse
I get an error executing updater binaries in zip
archangeles said:
I get an error executing updater binaries in zip
Click to expand...
Click to collapse
try cwm then
i use philz 6.58.7, works here
edit: were not bringing back file based flashing, so if the recovery doesnt support block based, recovery needs updating
archangeles said:
I get an error executing updater binaries in zip
Click to expand...
Click to collapse
There's something wrong on your end then. I've flashed both builds with twrp 2.8.0.1 without issue
ShinySide said:
There's something wrong on your end then. I've flashed both builds with twrp 2.8.0.1 without issue
Click to expand...
Click to collapse
I know there is, I had a similar problem updating to 4.4.4 from 4.4.2 tw custom rom, and fixing permissions seemed to fix that, but this time it does nothing, could the bootloader be a problem in any way? I'm still on 4.4.2 because 4.4.4 tw never installed properly, but pac-man 4.4.4 worked just fine. Any pointers?
archangeles said:
I know there is, I had a similar problem updating to 4.4.4 from 4.4.2 tw custom rom, and fixing permissions seemed to fix that, but this time it does nothing, could the bootloader be a problem in any way? I'm still on 4.4.2 because 4.4.4 tw never installed properly, but pac-man 4.4.4 worked just fine. Any pointers?
Click to expand...
Click to collapse
not bootloader
try to format system
Q&A for [ROM]-I317UCUCNJ1 ButtNaked Post #1 AlmostNaked Uploaded - Post #2 11/28
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM]-I317UCUCNJ1 ButtNaked Post #1 AlmostNaked Uploaded - Post #2 11/28. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Great rom!
dicksteele said:
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Build number: KOT49H.I317UCUCNJ1
ROM is NE5 patched with the NJ1 OTA. Rooted, Deodex'd, and Zipaligned
Thanks and Credit to @Zen Arcade for his Auto-deodexer
Added Tethering patch, Screenshot edit, and Quad-MultiWindow
No N3, N4 or S5 stuff. No Theming. Not sure if I'll go there on this ROM.
ButtNaked I317UCUCNJ1
https://www.androidfilehost.com/?fid=95784891001615960
MD5: d969d68f31c7ddb0d4b45292ada4a7a3
Almost Naked ROM IS POSTED BELOW. It has the stuff removed from ButtNaked.
Like Books, Flipboard, Magazines, SVoice, etc. All ATT crap will be stripped out.
I'm still learning what the changes were on NJ1. The camera feels like it takes pictures faster, a little quicker to respond for the next pic.
INSTALLATION
Instructions are the same as any other Custom ROM.
If you are on stock kernel it will probably hang. It should not if you are on AGNi kernel.
Download for AGNi kernel
http://forum.xda-developers.com/devdb/project/?id=2368#downloads
PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip
IT IS NOT RECOMMENDED TO FLASH Version 4.3.0 YET ! So use the 4.2.8 listed above
Great information is located here. Section 7 is How To Guides and References
http://forum.xda-developers.com/showthread.php?t=1987541 Credit @Bajanman
Custom Recovery
TWRP (TeamWiinProjects)
http://techerrata.com/browse/twrp2/t0lteatt (Zip is flashable, Tar is ODIN)
PhilzRecovery
http://forum.xda-developers.com/showthread.php?t=2159652
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/ (Latest version looks like 6.48.6. I have 6.41.6 on my phone. I will test with that) Either one should work fine.
Install instructions: Credit: ATT DN5 Team @sawdoctor and @Bajanman
You need to have Samsung 4.3 Bootloader or newer.
Make sure you have the latest TWRP/CWM recovery installed.
Next, remember to backup your apps and your efs folder. That's something that you always should do before flashing anything.
Go to TWRP/CWM recovery via pressing home + power + volume up button at the same time.
Make a Nandroid backup of your working system, if you haven't done so.
Its best to do a clean install for any new Rom (clean installation recommended includes internal storage)
In TWRP Recovery hit wipe, and slide to factory data reset system. (Internal won't be touched fyi)
In PHILZ Recovery Format Internal SDCard (in mounts and storage) and do Factory reset (I will install a new ROM option in PhilZ)
(Reminder) Remember that everything you flash you do it at your own risk so do your research before flashing anything!!
Now find the location of the Rom on your external and install it.
Flashing the Rom zip.
It should take less than 10 minutes till it boots...
[/QUOTE
ButtNaked is running good with the agni kernel 4.3.0 and added the viper4audio.
Click to expand...
Click to collapse
[email protected] said:
dicksteele said:
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Build number: KOT49H.I317UCUCNJ1
ROM is NE5 patched with the NJ1 OTA. Rooted, Deodex'd, and Zipaligned
Thanks and Credit to @Zen Arcade for his Auto-deodexer
Added Tethering patch, Screenshot edit, and Quad-MultiWindow
No N3, N4 or S5 stuff. No Theming. Not sure if I'll go there on this ROM.
ButtNaked I317UCUCNJ1
https://www.androidfilehost.com/?fid=95784891001615960
MD5: d969d68f31c7ddb0d4b45292ada4a7a3
Almost Naked ROM IS POSTED BELOW. It has the stuff removed from ButtNaked.
Like Books, Flipboard, Magazines, SVoice, etc. All ATT crap will be stripped out.
I'm still learning what the changes were on NJ1. The camera feels like it takes pictures faster, a little quicker to respond for the next pic.
INSTALLATION
Instructions are the same as any other Custom ROM.
If you are on stock kernel it will probably hang. It should not if you are on AGNi kernel.
Download for AGNi kernel
http://forum.xda-developers.com/devdb/project/?id=2368#downloads
PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip
IT IS NOT RECOMMENDED TO FLASH Version 4.3.0 YET ! So use the 4.2.8 listed above
Great information is located here. Section 7 is How To Guides and References
http://forum.xda-developers.com/showthread.php?t=1987541 Credit @Bajanman
Custom Recovery
TWRP (TeamWiinProjects)
http://techerrata.com/browse/twrp2/t0lteatt (Zip is flashable, Tar is ODIN)
PhilzRecovery
http://forum.xda-developers.com/showthread.php?t=2159652
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/ (Latest version looks like 6.48.6. I have 6.41.6 on my phone. I will test with that) Either one should work fine.
Install instructions: Credit: ATT DN5 Team @sawdoctor and @Bajanman
You need to have Samsung 4.3 Bootloader or newer.
Make sure you have the latest TWRP/CWM recovery installed.
Next, remember to backup your apps and your efs folder. That's something that you always should do before flashing anything.
Go to TWRP/CWM recovery via pressing home + power + volume up button at the same time.
Make a Nandroid backup of your working system, if you haven't done so.
Its best to do a clean install for any new Rom (clean installation recommended includes internal storage)
In TWRP Recovery hit wipe, and slide to factory data reset system. (Internal won't be touched fyi)
In PHILZ Recovery Format Internal SDCard (in mounts and storage) and do Factory reset (I will install a new ROM option in PhilZ)
(Reminder) Remember that everything you flash you do it at your own risk so do your research before flashing anything!!
Now find the location of the Rom on your external and install it.
Flashing the Rom zip.
It should take less than 10 minutes till it boots...
[/QUOTE
ButtNaked is running good with the agni kernel 4.3.0 and added the viper4audio.
Click to expand...
Click to collapse
Happy you like it. The Shift kernel works well also. Not trying to take anything away from AGNi, just pointing out another great solution.
Click to expand...
Click to collapse
dicksteele said:
[email protected] said:
Happy you like it. The Shift kernel works well also. Not trying to take anything away from AGNi, just pointing out another great solution.
Click to expand...
Click to collapse
I know shift 3.8.1 and 3.8.3 work. Is their anything that works that's higher than those.
Click to expand...
Click to collapse
[email protected] said:
dicksteele said:
I know shift 3.8.1 and 3.8.3 work. Is their anything that works that's higher than those.
Click to expand...
Click to collapse
I don't think so. He's been working on CM12 Lollipop kernels. He has one working.
Click to expand...
Click to collapse
dicksteele said:
[email protected] said:
I don't think so. He's been working on CM12 Lollipop kernels. He has one working.
Click to expand...
Click to collapse
Thanks for your quick reply.
Click to expand...
Click to collapse
No mobile connection after flashing
I've flashed PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip, Buttnaked-NJ1.zip, ATT-I317UCUBMJ4-Modem.zip (per instructions after flashing Buttnaked-NJ1.zip), and AlmostNakedFix.zip, in that order, but I get no mobile connection. I'm using CWM 6.0.4.1 and the phone is rooted. I also tried flashing CWM-I317UCUCNJ1.zip, but it didn't make any difference. I'm on AT&T.
When I go to view mobile networks, it says I need to insert a SIM, even though it is already inserted. There is no IMEI number listed, even though my SIM is inserted and mobile worked before flashing. Any help will be appreciated.
--Michael
---------- Post added at 03:34 PM ---------- Previous post was at 03:08 PM ----------
smartbean said:
I've flashed PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip, Buttnaked-NJ1.zip, ATT-I317UCUBMJ4-Modem.zip (per instructions after flashing Buttnaked-NJ1.zip), and AlmostNakedFix.zip, in that order, but I get no mobile connection. I'm using CWM 6.0.4.1 and the phone is rooted. I also tried flashing CWM-I317UCUCNJ1.zip, but it didn't make any difference. I'm on AT&T.
When I go to view mobile networks, it says I need to insert a SIM, even though it is already inserted. There is no IMEI number listed, even though my SIM is inserted and mobile worked before flashing. Any help will be appreciated.
--Michael
Click to expand...
Click to collapse
Also, in "About device" it says baseband version is "Unknown"
smartbean said:
I've flashed PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip, Buttnaked-NJ1.zip, ATT-I317UCUBMJ4-Modem.zip (per instructions after flashing Buttnaked-NJ1.zip), and AlmostNakedFix.zip, in that order, but I get no mobile connection. I'm using CWM 6.0.4.1 and the phone is rooted. I also tried flashing CWM-I317UCUCNJ1.zip, but it didn't make any difference. I'm on AT&T.
When I go to view mobile networks, it says I need to insert a SIM, even though it is already inserted. There is no IMEI number listed, even though my SIM is inserted and mobile worked before flashing. Any help will be appreciated.
--Michael
---------- Post added at 03:34 PM ---------- Previous post was at 03:08 PM ----------
Also, in "About device" it says baseband version is "Unknown"
Click to expand...
Click to collapse
I'm running DS_AN Rom with AGNi N7105 4.3.1r2 with no issues. Also ran on AGNi v4.2.8.... however, when I tried upgrading AGNi to v4.3.7, ran into the no SIM no data issue. See my post 2340 in the N7105 AGNi kernel thread here: http://forum.xda-developers.com/showpost.php?p=58511272&postcount=2340
Try reflashing kernel (like AGNi v4.2.4) or previous last known working boot partition from a backup if you have one. I was able to fix my issue by just reflashing last known working boot partition. .. then IMEI and SIM were again recognized. Good luck.
DoctorQMM said:
I'm running DS_AN Rom with AGNi N7105 4.3.1r2 with no issues. Also ran on AGNi v4.2.8.... however, when I tried upgrading AGNi to v4.3.7, ran into the no SIM no data issue. See my post 2340 in the N7105 AGNi kernel thread here: http://forum.xda-developers.com/showpost.php?p=58511272&postcount=2340
Try reflashing kernel (like AGNi v4.2.4) or previous last known working boot partition from a backup if you have one. I was able to fix my issue by just reflashing last known working boot partition. .. then IMEI and SIM were again recognized. Good luck.
Click to expand...
Click to collapse
Thanks for the reply.
I found (somewhere) that flashing CM10.2 would fix this, and it worked in my case. I have no clear idea why. After that, I was able to flash another Android 4.4.X ROM and it continued to work, but after flashing Buttnaked again, it stopped working again. Maybe I'll try again next week if time permits.
smartbean said:
Thanks for the reply.
I found (somewhere) that flashing CM10.2 would fix this, and it worked in my case. I have no clear idea why. After that, I was able to flash another Android 4.4.X ROM and it continued to work, but after flashing Buttnaked again, it stopped working again. Maybe I'll try again next week if time permits.
Click to expand...
Click to collapse
I found this on the Galaxy Y GT-S5360 forum thread (so don't flash the zips in the OP on the ATT Note2!)... but found it interesting and perhaps a reason a few folks are seeing "no SIM" and "unknown IMEI" issues after flashing the newer versions of the AGNi N7105 kernel on the stock (NE5 or NJ1) ATT rom.
http://forum.xda-developers.com/showpost.php?p=52952880&postcount=1
Something to do with the RIL files being mis-matched. Not sure, but perhaps the RIL files are missing/corrupted causing the problem... just not sure where to obtain the latest RIL files for the ATT stock firmware or which RIL files should be loaded on the ATT firmware to get it to work.
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
dl12345 said:
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
Click to expand...
Click to collapse
Will this need me to unlock the bootloader?
Sent from my E6533 using XDA Free mobile app
angvil said:
Will this need me to unlock the bootloader?
Sent from my E6533 using XDA Free mobile app
Click to expand...
Click to collapse
Yes
Does it add anything over flashing the rom and then the rooted boot.img posted in the general forum?
ChrisJ951 said:
Does it add anything over flashing the rom and then the rooted boot.img posted in the general forum?
Click to expand...
Click to collapse
Yes, it's deodexed, zipaligned, SELinux in permissive mode, RIC disabled, busybox installed, write-enabled external SD card, adb insecure. I'll probably add some other things soon - Xposed is top of the list.
Does you think this can fix the over heating problem with some Z3+ devices? I hope so
dl12345 said:
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
Click to expand...
Click to collapse
Got my Z3+ last night and about to unlock the bootloader so happy to give it a test and report back. I've seen the command line twrp link but might need some additional guidance on flashing your ROM, if you wouldn't mind.
lilloscar said:
Does you think this can fix the over heating problem with some Z3+ devices? I hope so
Click to expand...
Click to collapse
I doubt it. I've made no bug fixes. If there's a problem in the base ROM, the problem will exist in this ROM.
dl12345 said:
I have successfully created a stock rooted ROM based on 28.0.A.8.251 Generic HK firmware
The ROM has the following features
Stock ROM with MyXperia app removed
Rooted with SuperSU on the /system partition
Custom kernel from latest 28.0.A.7 kernel- copyleft sources with SELinux in permissive mode and Sony RIC disabled
Deodexed and zip-aligned
Writeable external sdcard
Busybox
This ROM can be flashed using @ChrisJ951's command line TWRP.
I'm not yet ready to release it publicly but I am looking for a couple of beta testers. If you're a sophisticated user and you're willing to give it a go then send me a PM and I'll let you have a link to the download and some instructions for installation. The installation doesn't touch the userdata partition, so it's a non-wipe install, although I strongly recommend you update to the base firmware before installing the custom rom.
Click to expand...
Click to collapse
OK, so far, everything seems to be working fine including LTE, WiFi, Bluetooth and NFC transferring of files between devices, Location, Sync, Google Play, System RW (ES File Explorer and AdAway worked), ExternalSD RW (Titanium Backup and SMS Backup & Restore worked), Camera and all other Sony apps seem to be working fine. I haven't made any phone calls yet though. TWRP also worked great - backup, wiping and installing all worked great.
Only slight niggles I've found so far are: Google Drive keeps popping up a blank grey/white screen for a split second - when trying to sync or access Play Store - and disappears and when setting up a Google account, a message pops up saying Google Play Services has stopped - even thought it works just fine. Oh and Google Maps didn't connect the first time but forcing a continue worked. Other than those 3 items, everything else seems to be working fine. However, once all apps are updated, they all work fine.
Currently testing 4K recording and it's just gone past 11 minutes .
Xposed also working as well as Greenify Experimental Features and it seems the 20MP Superior Auto is working. Xperia Xposed didn't work - I believe this is a general incompatibility matter and not restricted to this ROM - haven't tried anything else though
Thank you very much @dl12345 for your hard work. If you need any more testing, let me know.
My first initial thoughts are perfect. I haven't had any issue whatsoever. No problem with root, works with every app. Appreciate the work.
Skickat från min E6553 via Tapatalk
rjhellel said:
OK, so far, everything seems to be working fine including LTE, WiFi, Bluetooth and NFC transferring of files between devices, Location, Sync, Google Play, System RW (ES File Explorer and AdAway worked), ExternalSD RW (Titanium Backup and SMS Backup & Restore worked), Camera and all other Sony apps seem to be working fine. I haven't made any phone calls yet though. TWRP also worked great - backup, wiping and installing all worked great.
Only slight niggles I've found so far are: Google Drive keeps popping up a blank grey/white screen for a split second - when trying to sync or access Play Store - and disappears and when setting up a Google account, a message pops up saying Google Play Services has stopped - even thought it works just fine. Oh and Google Maps didn't connect the first time but forcing a continue worked. Other than those 3 items, everything else seems to be working fine. However, once all apps are updated, they all work fine.
Currently testing 4K recording and it's just gone past 11 minutes .
Xposed also working as well as Greenify Experimental Features and it seems the 20MP Superior Auto is working. Xperia Xposed didn't work - I believe this is a general incompatibility matter and not restricted to this ROM - haven't tried anything else though
Thank you very much @dl12345 for your hard work. If you need any more testing, let me know.
Click to expand...
Click to collapse
Which version of Xposed did you use? All the ones I tried only resulted in bootloops.
I used official xposed v73 sdk21 arm64.
Little note: You have to wipe dalvik cache before or after installing Xposed to prevent bootloop.
Latest Xposed has auto-wipe feature, but to make sure...
Could I test, just unlocked my bl last night
hello all this rom have lte band 38/2600 ? Or can be added? thx
Having a e6533 Dual. 266 firmware with unlocked bootloader. Would like to downgrade and test this rooted 251 ROM. Thank you.
I used to use xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929.zip as from some post. Facing random reboot from time to time.
Last week, I need to reflash, I tried official xposed-v79-sdk21-arm64.zip. It works ... and the phone stay "no reboot" for one day. Then it starts again. I wipe cache and seems back to be more stable. My own feeling is thsi v79-sdk21 has less reboot issue, but still does.
---------- Post added at 16:35 ---------- Previous post was at 16:29 ----------
BTW, Sony has new update in Asia ...
28.0.A.8.272 Release: 1/9/2016 Still 5.0.2
I could not find anywhere to download full rom. Also not sure existing root/xposed will work or not.
[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.