Develop Bugs

[ROM][12/7/10] Stock w/root, odex and deodex post-OTA, *updated instructions (v1.1)

ya ya, this should have been first. but we all wanted to play. but anyway here it is now.
this is the stock rom post OTA. added root (su and superuser.apk) as well as modified ramdisk (ro.secure=0) and busybox. Also zip aligned apps to optimize ram usage. there is odex (stock) and de-odex versions.
*i no longer see the reason for needing the pre-OTA rom. if you have a reason post up and we'll see what happens...
if you are upgrading from previous version of THIS rom you should not have to wipe, however you will still need to redo any system changes you have made, i.e. trackpad wake or notification lights.
Stock OTA kernel is now INCLUDED in rom flash. however if you want to flash an oc/uv/whatever kernel follow that post's instructions after this rom is up and running. i suggest pershoots kernels. been using his since the g1, awesome work. his g2 one has great performance AND battery life.(for me anyway)
These roms are g2 and dz compatible.
Cwm recovery recomended for ease and function.
1. Place stock rom of your choice on root of sdcard.
2. Boot into recovery
3. Do a nandroid backup.
4. Do a full wipe. (if coming from different rom)
5. Select flash zip from sd and select stock rom.
6. Once its finished, reboot and enjoy.
OTA odex: http://www.4shared.com/file/XlIDy7SV/ota_odex_V11.html
OTA de-odex: http://www.4shared.com/file/vi77pxvT/ota_deodex_v11.html
OTA bootv2 (kernel): http://www.4shared.com/file/y2NVlbJm/ota_boot_v2.html
*(only needed if you flashed a different kernel after the version 1.1 rom and want to go back to stock kernel. includes wifi module.)
pershoots's kernel:
http://forum.xda-developers.com/showthread.php?t=847672
theme template: http://www.4shared.com/file/VwINHT_r/theme_template.html
*theme template is for theme dev's only. it should be universal for any rom. just place the themed framework and/or apps in corresponding folders. i have a .txt file in the folders as a place holder, delete it after you add your themed stuff. take a look at the update script to see how it works, and to add or remove anything you need to...
change log:
v1.1:
fixed permissions and mismatched symlink issue w/busybox. (thanks to Mikey1022 for bringing this prob to my attn.)
v1.0:
initial release

Awesome thanks!! Do we have to flash a separate kernel if coming from Sense, and if so, do you have the stock kernel in a flashable .zip? Thank you in advance,
Russ

Nice work! good to have a base Rom to fall back on but why do we need three Roms for stock? why not just deodex the stock Rom with the OTA applied and be done with it? less work for you, right? I know this is quicker and will help folks who have boot looped/ soft bricked their phones. either way, good job and thanks!

Can I just remove the odex files along with the bloatware apk files from my current rom? I know they are both located in the systems/app folder.
Sent from DynamikD's R00t3d & OC G2

rUsTyRuSs said:
Awesome thanks!! Do we have to flash a separate kernel if coming from Sense, and if so, do you have the stock kernel in a flashable .zip? Thank you in advance,
Russ
Click to expand...
Click to collapse
question 1: yes.
question 2: damn im an idiot and half asleep. its gonna give u same error at end of flashing as others. ignore and take boot img from zip and flash with fastboot. "fastboot flash boot boot.img"
ill have to update later on to updater-script. i have to get up for work in 1hr 45min!!!!!

rUsTyRuSs said:
Awesome thanks!! Do we have to flash a separate kernel if coming from Sense, and if so, do you have the stock kernel in a flashable .zip? Thank you in advance,
Russ
Click to expand...
Click to collapse
Yes, just flash Coolbho3000s OCed kernel.

fastludeh22 said:
question 1: yes.
question 2: damn im an idiot and half asleep. its gonna give u same error at end of flashing as others. ignore and take boot img from zip and flash with fastboot. "fastboot flash boot boot.img"
ill have to update later on to updater-script. i have to get up for work in 1hr 45min!!!!!
Click to expand...
Click to collapse
Lol! dude, slow down... get some sleep! you're as crazy as I am going to work the next day with only 2 hours of sleep! Good work though!

sino8r said:
Nice work! good to have a base Rom to fall back on but why do we need three Roms for stock? why not just deodex the stock Rom with the OTA applied and be done with it? less work for you, right? I know this is quicker and will help folks who have boot looped/ soft bricked their phones. either way, good job and thanks!
Click to expand...
Click to collapse
we dont need 3, but this is what i had to work with right now. i did odex cause thats true stock, and de-odex as a base for theamers. after patching the ota in ill update this post, not gonna make a new one.
dynamikd said:
Can I just remove the odex files along with the bloatware apk files from my current rom? I know they are both located in the systems/app folder.
Sent from DynamikD's R00t3d & OC G2
Click to expand...
Click to collapse
NOOOOO! nothing will work! the odex file is part of the apk. de-odex'ing act joins them...
edit: wait if u mean just the ones that you are compleatly removing, yes, just dont go removing all the odex files, lol

sino8r said:
Yes, just flash Coolbho3000s OCed kernel.
Click to expand...
Click to collapse
yes, this or bacon bits SHOULD work till i have a chance to fix op...

Im viewing this with xda app an I dont see a m5d is there one?
Sent from my T-Mobile G2 using XDA App

I must be doing something wrong... I flashed the boot img in fastboot, then went into clockwork recovery to write the deodexed rom, but keep getting
"E:Can't find BOOT...
E:Failure at line 334:
Write_raw_image PACKAGE:boot.img
BOOT:Installation aborted
I'mma keep trying and hopefully update this before anyone has slap me...

HELP PLS!!
I have a G2 which is S-off'd
Loaded the HTC Sense ROM on it yesterday but it kept messing up my SMSs (any SMS app incl. stock would freeze when sending SMSs)
Wanted to come back to the stock ROM and found this post
Flashed the ROM but now am stuck in the "HTC Quietly Brilliant" booting loop (i.e. phone won't progress past that splash screen)
Can someone pls help me in figuring out how to get out of this mess
I used to have Open Recovery but that's gone now. Have to rely on the stock recovery
I am not a pro at ADB etc so would appreciate step-by-step instructions pls
Thanks a million!! Appreciate it

i think u can download the stock rom, rename it to PC10IMG.ZIP, and reboot into hboot, but iono, i cant get anything right this morning

tommyxd said:
I must be doing something wrong... I flashed the boot img in fastboot, then went into clockwork recovery to write the deodexed rom, but keep getting
"E:Can't find BOOT...
E:Failure at line 334:
Write_raw_image PACKAGE:boot.img
BOOT:Installation aborted
I'mma keep trying and hopefully update this before anyone has slap me...
Click to expand...
Click to collapse
Did you try booting? Ignore error, till i can get home from work and fix it. I usually do it in differeent order though. Full wipe, flash rom, get error, ignore. Reboot into fastboot and flash boot.img OR flash one of the aosp flashable kernel zip.
adp21 said:
HELP PLS!!
I have a G2 which is S-off'd
Loaded the HTC Sense ROM on it yesterday but it kept messing up my SMSs (any SMS app incl. stock would freeze when sending SMSs)
Wanted to come back to the stock ROM and found this post
Flashed the ROM but now am stuck in the "HTC Quietly Brilliant" booting loop (i.e. phone won't progress past that splash screen)
Can someone pls help me in figuring out how to get out of this mess
I used to have Open Recovery but that's gone now. Have to rely on the stock recovery
I am not a pro at ADB etc so would appreciate step-by-step instructions pls
Thanks a million!! Appreciate it
Click to expand...
Click to collapse
You need to wipe when going from rom to rom. Get cwm recovery and follow my instructions above.

lmao, i think i did that, just in reverse order. Don't worry man, I think you need to get some rest when you get home. Thanks for the quick response btw

fastludeh22 said:
Did you try booting? Ignore error, till i can get home from work and fix it. I usually do it in differeent order though. Full wipe, flash rom, get error, ignore. Reboot into fastboot and flash boot.img OR flash one of the aosp flashable kernel zip.
You need to wipe when going from rom to rom. Get cwm recovery and follow my instructions above.
Click to expand...
Click to collapse
Thanks for the quick reply
I have already wiped via stock recovery - both data/ settings and cache
I can't boot into the phone (ie the part where u have the home screen etc). Keep getting stuck at the htc quietly brilliant screen. Phone will keep looping here
Can I still install clockwork recoverY (cwm)? If yes, how? If no, what can I do to get my phone back to normal
I'm goin' crazy here lol

I need clearer instructions. What do I rename this file to? When I go into hboot how do I load said file up?
I renamed it pc10img.zip, didn't work.
Sent from my T-Mobile G2 using XDA App

adp21 said:
Thanks for the quick reply
I have already wiped via stock recovery - both data/ settings and cache
I can't boot into the phone (ie the part where u have the home screen etc). Keep getting stuck at the htc quietly brilliant screen. Phone will keep looping here
Can I still install clockwork recoverY (cwm)? If yes, how? If no, what can I do to get my phone back to normal
I'm goin' crazy here lol
Click to expand...
Click to collapse
Also I tried to flash boot.img from fast boot but no cigar. Am I trying to flash from the wrong place?
Should I be naming the file something else? I think I left the name as is and/ or may have tried to flash by calling it PC10IMG

Thanks buddy, got it figured out, iono why but I was using "fastboot flash..." instead of "fastboot boot..." all good now.

J
tommyxd said:
Thanks buddy, got it figured out, iono why but I was using "fastboot flash..." instead of "fastboot boot..." all good now.
Click to expand...
Click to collapse
Wait so it worked for you? What did you rename the file to and how did you load it in recovery?
Sent from my T-Mobile G2 using XDA App

Cant't flash any roms

First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.

just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.

scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.

lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?

drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.

lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.

scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download

lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.

lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).

drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.

If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem

drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.

lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)

drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...

hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.

lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.

[DEVED/TW-ROM FIX] Developer Edition TW-4.4 ROM Fix Files [2014-04-27]

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.

[05-15-17] Debloated-Deodexed-Rooted N910PVPS4DQC1

Attention! I've just noticed some activity here. Thanks to all the members for answering questions.
I haven't had this sprint device for awhile now so I don't keep track of this thread so much. For those of you needing help with gsm support, I'll try to offer assistance, since that's how I always used this device. I'll try to post a universal gsm fix script that'll modify any CDMA rom to work with gsm! Thanks!
DeBloated, DeOdexed N910PVPS4DQC1​Now with Rom Control! ​GSM ROM! (See Post 2)​
First Off About Me:
First off, Let me state, I'm a full-time construction worker and also a full-time Dad. I'm not a Dev, like the peeps I learned from. So don't expect this Rom to get massive updates or often updates. I no longer have a N910P, so this might be it for me!
About ROM
Warning: This ROM is ONLY for the Sprint SM-N910P!!! DO NOT FLASH THIS ROM ON ANY OTHER MODEL!!! If you do then you are on your own! Know what you are doing before flashing and modifying your phone!!! You have been Warned!! I am not responsible for your phone breaking or blowing up!!
This Rom is a debloated, deodexed, slightly modded Stock Rom! It is pre-rooted! And I removed a handful of non essential apps. Plus I added a handful of mods!
I really wanted to add some more useful apps and a custom aroma installer but just wanted to get this out for the people asking for it. Hope you like the debloat and included mods.
Version: 1.0
This is based on stock with some custom mods!
Fully deodexed framework and system apps
Debloated-Deodexed-Rooted
Basic Mods (Power menu, hotspot, etc)
Added a few useful apps!
Su.d support
Removed Knox
Removed ItsOn
Zip-Aligned
Slightly Modded Stock Kernel
Software Base version: N910PVPS4DQC1
Kernel Base: Official Samsung N910PVPS4DQC1
ROM Features
Mods added: CSC edits, Hotspot mod, Only Once/Always, All apps multi window, remove permanent notification, remove USB plug/unplug awake screen, removed high volume notice, added Advanced Power Menu.
Added app: YouTube adblock&background playback & AdAway!
Changelog
v1.0 - Released 05/15/2017
ADD-ON Features!
Rom Control by @ROBERT CM !
Flashing instructions:
Before you flash this rom you should be on the N910PVPS4DQC1 firmware. Specifically the bootloader and modem. (Uploading Now)
Heres QC1 firmware for anyone needing!
Full ROM - https://www.androidfilehost.com/?fid=529152257862726726
Firmware / Modem - https://forum.xda-developers.com/showpost.php?p=72341335&postcount=16
***Before you flash this rom, please make sure your battery has at least 30% charge***​
OK... Lets begin!
1. Download the rom and all the other mods you want!
2. Check the MD5!!! Use a MD5 checksum tool on your pc or phone (Google is your friend)
3. Copy the downloaded files to your phone's internal storage or micro-sd card
4. Backup anything you need to backup from your internal storage and copy it to your pc or sd-card
5. Reboot to TWRP custom recovery. Do "Advanced Wipe" options and wipe Dalvick-Cache, System, Data, and Cache. I also advise deleting /Android directory from Internal storage and SD card!
6. Install the rom!
7. REBOOT!!
8. The initial boot process will take around 12 minutes. Please be patient. It WILL boot. The phone might reboot once from SuperSU.
9. Once you reach the setup wizard proceed as usual and setup your phone.
10. Once phone is setup, Now Install Rom Control!
11. You're done! Enjoy!!
Credits
Without the following people NONE of this would be possible. Period.
In no particular order!
@SuperR. for his awesome kitchen, @Chainfire for root and SuperSU, @iBotPeaches for apktool, @JesusFreke for smali/baksmali tools, and @asc1977 & @edzamber & @tdunham for all their amazing collection of guides!
Also @tx_dbs_tx, @carlosggb, @SaintZ93, @hsbadr, @osm0sis, @freeza, @ianmb, @LMMT, @samep, and @wantedman76 for all their work that I've learned much from! And SO Many more here at XDA!
Thank You All !!​
DOWNLOADS
Fixed Zip Uploaded!!!
DeBloated, DeOdexed N910PVPS4DQC1-Fixed
MD5: 617f196041c2d8c9a330d783438cf0f8
GSM Rom! See Post 2
MODS
Rom Control
See Post 3!
Contribited By: aaron74
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N910PVPS4DQC1_N910PSPT4DQC1_N910PVPS4DQC1_HOME
Based On: Stock N910PVPS4DQC1
Created 05-15-2017

GSM ROM!
Gsm Rom:
Fyi, If your using this phone for gsm, I found its just easier and better to install a Tmobile rom. I don't believe you need a data fix with it. (Sorry it's been awhile). Never use a tmobile odin firmware though!
You can also install any other international rom but you will need a data fix and kernel!
https://mega.nz/#!t510lCoI!qqK8Wr-ttM5VJvAG8zo86KldSW7_2tMNUlxM_zQRuX8
Gsm fix patch from old rom: (Not needed for above rom! Only to flash over sprint rom in post 1)
https://forum.xda-developers.com/attachment.php?attachmentid=4134974&d=1493690641
Thread: https://forum.xda-developers.com/showpost.php?p=71301823&postcount=2

Rom control!
A great Dev @ROBERT CM made a Rom Control for our stock roms.
Goto his Thread below to Download and don't forget to Thank him and leave him a reply!
Here's his Main Thread!
You must Download both zips and flash consecutively.
Setup Rom first!, before flashing!
Thank you, & Enjoy!

Just in case!

Magnifiquè!!!!

Thanks for this!
Sent from my SM-N920P using Tapatalk

Excellent! Thank you!
Sent from my SM-N920P using Tapatalk

Please let me know if any problems! I usually never post unless i personally flash. But this time, i couldn't flash. I didnt do anything crazy, so all should be fine! But please let me know.

aaron74 said:
A great Dev @ROBERT CM made a Rom Control for our stock roms.
Goto his Thread below to Download and don't forget to Thank him and leave him a reply!
Here's his Main Thread!
Thank you, & Enjoy!
Click to expand...
Click to collapse
This weekend update my rom control and mods
I trying adapted more mods for n4 stock
This motivate me a development and keep it up and I know what more more persons and devs enjoy of this mod :laugh:

​
ROBERT CM said:
This weekend update my rom control and mods
I trying adapted more mods for n4 stock
This motivate me a development and keep it up and I know what more more persons and devs enjoy of this mod :laugh:
Click to expand...
Click to collapse
Thanks bro. I know the note 4 is dying out with devs. So it's always nice to have people keeping us alive. Take your time bro, i know how it is!

I flashed, and this is what I came encountered:
I was not rooted, so I Odin flashed TWRP, wiped everything but SD Card (Deleted SD Card Android folder) and flashed ROM followed by Rom Control 1, then 1.1.
First thing I noticed is that the top bar (not sure of its proper name) was missing, and when I swiped down, nothing happens. So, I cannot see any type of activity (i.e. new email icons, new text messages icons, notices, etc..). With that, I could not see my battery level, time, date, etc...
Second, I did not have root. I flashed SuperSU via twrp and still did not have root.
Third, when pressing the Power button to awake the device, it takes a few seconds to turn on. At first, I thought it wasn't turning on, so I kept pressing the power button... so the phone screen would not turn on. I eventually found out that I needed to wait a few seconds after pressing it the first time.
Fourth, pressing the "Recent" app button does nothing.
At this point, I think I am going to re-flash but without ROM control to see if these problems still exist. I'll report back.

Aloupha said:
I flashed, and this is what I came encountered:
I was not rooted, so I Odin flashed TWRP, wiped everything but SD Card (Deleted SD Card Android folder) and flashed ROM followed by Rom Control 1, then 1.1.
First thing I noticed is that the top bar (not sure of its proper name) was missing, and when I swiped down, nothing happens. So, I cannot see any type of activity (i.e. new email icons, new text messages icons, notices, etc..). With that, I could not see my battery level, time, date, etc...
Second, I did not have root. I flashed SuperSU via twrp and still did not have root.
Third, when pressing the Power button to awake the device, it takes a few seconds to turn on. At first, I thought it wasn't turning on, so I kept pressing the power button... so the phone screen would not turn on. I eventually found out that I needed to wait a few seconds after pressing it the first time.
Fourth, pressing the "Recent" app button does nothing.
At this point, I think I am going to re-flash but without ROM control to see if these problems still exist. I'll report back.
Click to expand...
Click to collapse
Yes, i had that problem with Rom Control once but it was on a N7 port rom.
When i last tested this rom control with stock. It worked but i also already had the rom up and running. I wonder if that has anything to do with it.
Thanks for reporting. Please let me know how just my rom works without it.

aaron74 said:
Yes, i had that problem with Rom Control once but it was on a N7 port rom.
When i last tested this rom control with stock. It worked but i also already had the rom up and running. I wonder if that has anything to do with it.
Thanks for reporting. Please let me know how just my rom works without it.
Click to expand...
Click to collapse
I just re-flashed. Other than root, all the other issues are gone.

Aloupha said:
I just re-flashed. Other than root, all the other issues are gone.
Click to expand...
Click to collapse
You have no root?
I'll have to pull file and check. I must have rushed.
Thanks for letting me know.
Also check the SU Hide app? Maybe that's messing it up. I've never used it before but included it, as some are interested in it.

aaron74 said:
You have no root?
I'll have to pull file and check. I must have rushed.
Thanks for letting me know.
Also check the SU Hide app? Maybe that's messing it up. I've never used it before but included it, as some are interested in it.
Click to expand...
Click to collapse
@aaron74 can you please provide ODIN files for only modem and bootloader
My internet connection is slow here
Thank you

natibongo said:
@aaron74 can you please provide ODIN files for only modem and bootloader
My internet connection is slow here
Thank you
Click to expand...
Click to collapse
Warning!! I am not Responsible for Brick!!!!
This is the first time I made a firmware and modem package!! Maybe someone can verify my commands below, before trying to Flash!!
Without going in detail, Heres my commands, If anyone wants to verify anything wrong!!
tar -H ustar -c modem.bin NON-HLOS.bin > modem.tar
tar -H ustar -c aboot.mbn sbl1.mbn sdi.mbn tz.mbn rpm.mbn > firmware.tar
md5sum -t my-file.tar >> my-file.tar
mv my-file.tar my-file.tar.md5
But Here you GO! For all who are UnAfraid!!
N910P-QC1-Firmware
N910P-QC1-Modem

Aloupha said:
I just re-flashed. Other than root, all the other issues are gone.
Click to expand...
Click to collapse
For anyone reading this,
I just verified results, Yes we must not flash rom and rom control at same time. Or no status bar.
Flash Rom, reboot, setup. Then flash Rom control.
All good! Reboot will take a bit, dalvik gets cleared.

aaron74 said:
Warning!! I am not Responsible for Brick!!!!
This is the first time I made a firmware and modem package!! Maybe someone can verify my commands below, before trying to Flash!!
Without going in detail, Heres my commands, If anyone wants to verify anything wrong!!
tar -H ustar -c modem.bin NON-HLOS.bin > modem.tar
tar -H ustar -c aboot.mbn sbl1.mbn sdi.mbn tz.mbn rpm.mbn > firmware.tar
md5sum -t my-file.tar >> my-file.tar
mv my-file.tar my-file.tar.md5
But Here you GO! For all who are UnAfraid!!
N910P-QC1-Firmware
N910P-QC1-Modem
Click to expand...
Click to collapse
Which download is bootloader?

reekotubbs said:
Which download is bootloader?
Click to expand...
Click to collapse
Firmware=bootloader.
Sent from my SM-N920P using Tapatalk

What about the root issue, did you get to the bottom of it?

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

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

Can I dirty flash this with LineageOS15?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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