SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
New!: Spacesung Oreo Debloat ScriptNotes:
1. Flash in recovery after the first boot.
2. Wipe dalvik cache ONLY! (Oreo cleans up data from removed apps automagically after rebooting.)
3. Profit!
*If you want to modify what's removed, simply open the updater-script with a text editor (preferably Notepad++) and add or remove the # sign. All apps in the stock Oreo system are listed in alphabetical order. This script should be safe to flash as is. Touchwiz, Theme store, Google play, and Samsung keyboard, are not removed by default. No files will be added to your OS either.
Ex.
delete_recursive("/system/app/AmazonMP3"); ← This would be deleted. #delete_recursive("/system/app/AmazonMP3"); ← This would be ignored.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
peter couniaz said:
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
Click to expand...
Click to collapse
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
J727P
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
Thank you for getting back to me an good luck with your build on a custom kernel for this phone we can really use one !! Thanks again !
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
Downloaded and installed nicely. Tried to switch superuser with magisk but no go, need stock boot image but all in all a good clean debloated Rom. You should include a keyboard though, your link did not work so I downloaded one on my PC and transferred to internal sd and installed. If you can get magisk instead of superuser, you will have a winner !
Sent from my SM-J727P using Tapatalk
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
You may want to try this Build I Built on TomeGJ7p's WIFI BUILD it's a good one I THINK YOU WILL LIKE IT !
https://mega.nz/#!aUlU3CiD!QERLRerFDA8497aKopbqZqZh-ZSTVfZ9GhfQQy2mBrs
PS if you like it you can use it to Build on you have mine an tomeGJ7p's Blessing !!
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
This ROM is totally debloated. I went back and tried it again, very smooth, very fast but Contacts would not sync so I could not call anyone. Google account would not sync so no play store apk update from old account.Samsung account missing so no way for me to bring certain apks and utilities from stock ROM. Bare-bones android op. But I will keep it on my sd card.
PS
I just remembered those system apks that are missing that I need, I could have installed thru Titanium Bkup! [emoji846]
Sent from my SM-J727P using Tapatalk
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
JeepinxJosh said:
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
Click to expand...
Click to collapse
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Spaceminer said:
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Click to expand...
Click to collapse
Thanks man
I used this rom as the base for my gaming phone and then stripped it down to only system framework apps. If the latter were removed it would crash the phone. Anything I removed to get to that point, had minimal impact on space (fifty or so megs) and bootup times compared to a fully loaded phone (5 seconds). Spaceminer did an excellent job on this.
Video here of bootup comparison between two Galaxy J7 Perx, one with the Spacesung rom:
https://www.youtube.com/watch?time_continue=2&v=z9bcqwLVIAA
Is the Oreo stock ROM a battery chugger?
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
ct760ster said:
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
Click to expand...
Click to collapse
Have you tried turning off all the scanning features? Also in the dev options, the switch that keeps mobile data always on, is enabled by default. It's normally off in Nougat. Turning that off should help tremendously.
That being said, I do think Oreo is a battery hog, and I don't think there's any performance gain over Nougat. My best benchmarks with this phone are running Nougat (ARG2), debloated. My battery gives me 51-52hrs on Nougat, with 17-18hrs of that being screen on time. I plan on running Oreo this week to get a good comparison between them.
Related
Welcome to slashadb!
Mandatory disclaimer that I take zero responsibility for your phone or the actions you partake in. This program is for personal use and does not come with any warranty, implied or otherwise.
I'm not a coder, or a dev. Let's get that out right now. But I wanted to make a tool that would allow me to "chain flash" my rom, gapps, kernel, etc... So, I made some batches. Batches turned into batches to control batches, to a simple GUI, then to this. After learning to code all this from scratch though, I may have to change that first statement!
This should be a simple to use tool, it works for everything I've been able to throw at it, and it was a ton of fun making it. This is NOT TO COMPETE with any other toolkit. This isn't meant to be "the best" or "better" than anything else. It was just my after work project, and it was a blast to learn about. I've been using this for all my flashing for a week without fail. I find it faster to open this and click Install TWRP, than it is for me to open terminal and fastboot it myself!
If you're bored, lazy, busy, or whatever, give this a try. If you find something broken, or have a suggestion of something to add, while trying to keep with the theme of "simple and easy to pick up and use" then drop a comment. I built an updater that checks on start, so any additions or modifications I make, you can get too. You can always decline to update as well and keep on using an old version.
I plan on continuing to work on this, because it's a fun hobby for now. Any future plans or known bugs I'll post in post #2.
-Make a nandroid in line with your flashing.
-Flash a rom, gapps, a custom kernel, and xposed, or any combination of them, all at once. You can just walk away and this will flash what you want, only what you want, and do all the necessary reboots and what have you by itself!
-Backup and Restore your user apps WITH appdata! (Note: some user apps don't allow app data backup. I haven't run into a single app that doesn't allow it, but be warned)
-Backup or Restore a Nandroid to / from your PC.
-Make a full SDCARD clone, and restore it for when you have to wipe userdata!
-Backup your camera pics, and your pictures folder right to your PC's Pictures folder, with just a click!
-Make a backup of all your SMS / MMS, and sent / recieved pics, and restore them after a flash. Restores pics IN MESSAGE too! (Tested only on stock MMS app)
New to the Nexus 6?
-Install ADB, Fastboot, and Drivers, with just a click.
-Unlock your bootloader, or re-lock it for warranty work
-One step install root and busybox
-Flash a full factory system image, it'll do all the needed wiping and flashing by itself
-Install custom bootloader, boot.img, root, recovery radio, etc.
-Install TWRP automatically.
-Change your DPI, fonts, bootanimation, take screenshots, record your screen!
-Disable forced encryption, and stop Google Play Store wakelocks / battery drain!
More to come!
Happy Flashing!
Download link:
https://dl.orangedox.com/xoio1ViSiG7SeYUfHX/setup.exe
Special Thanks:
ChainFire - for Root
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Stericson - for busybox
https://github.com/Stericson/busybox-free
Snoop05 - for 15 sec ADB
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Choristav - for his Google Services Tame script
http://forum.xda-developers.com/nexus-6/general/script-reduce-google-play-services-t3171224
Hlxanthus and dk_zero-cool - for Disable Forced Encryption
http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788
Thanks again to all the above devs for their work on their respective projects, in addition to being linked to here, all of their threads and recognition for what they made can be found in the help file for easy access / reading. If any of the above have any issue with me using their work, send me a PM or an email and I will remove it. Thank you.
XDA:DevDB Information
slashadb, Tool/Utility for the Nexus 6
Contributors
dinclala, Dinclala
Version Information
Status: Testing
Current Beta Version: 1.01
Beta Release Date: 2015-10-07
Created 2015-10-06
Last Updated 2015-10-06
Future Plans:
I want to add in a toggle to switch between Lollipop and Marshmallow support files. That'll happen.
I plan to add some more features, as well as clean the code up fix any bugs people may find.
I also forgot to make the gui able to adjust scale and re-size. So I don't know if it will fit in everyone's monitor for now.
Again, this is just something fun I made and felt like sharing with the community.
Added support for restoring a nandroid straight from your phone is in the works, as well as link to factory images. Also, I want to make all files able to be selected from your phone, so you don't have to download a rom (gapps, kernel, whatever) to your PC if you don't want to.
Known Bugs:
As much as I enjoy the Google Services scripts, they're probably gonna get removed from here. They flash great when I'm running PureNexus or Chroma, but on a factory image, even when using the terminal they seem to hang for no reason and with no apparent cause. I'll re-run, and it goes through fine. Weird.
Sweet!
Sent from my Nexus 6 using Tapatalk
The screenshots looks fantastic. I'll download and toy around with it.
Looked very nice. I can't wait to give it a try. Thank you for sharing.
"Chance Favors the Prepared"
Thanks for the kind words and checking out my first project. With marshmallow dropping, and after installing that and rooting, gaining R/W and all, I've found some pretty serious (to me at least) flaws in my first try. I'm going to write this from the ground up, with more than one core version in mind (LP & MM). Sorry for dropping this version so early, Hopefully, it'll be back soon, and actually work a bit smoother. Thanks again.
Neat project, gonna sub and see where it goes. Good luck!
Sent from my Nexus 6 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current Events
Dodo released! This means this ROM is now extinct. Sorry! If links below fail, try this one!
OTA is in Beta. Will be included in CM 13 release once both are stable. OTA will be available before full-sized versions due to the testing process (updates are tested first).
SnapChat will not work without some help. This is entirely SnapChat's fault for trying to control your device. Please read this thread before flashing and how you can make it work. Or just open Xposed installer, install Snapprefs and reboot.
Introduction
Welcome to the fastest and most stable ROM for your OnePlus. This thread is mainly a support thread for Jgcaap's awesome work, allowing him to spend more time working on "M" and less time answering questions. His latest builds will be tested by me, hand selected for stability, and the best of the crop will be repackaged, enhanced, and placed here. If you are new to this ROM, check the screen shots for benchmark results and battery life screenshots. Be amazed, then download the ROM and be even more amazed! Smooth as glass and flows like water! As one person has said, "Disgustingly Fast!"
Please read this entire post! Check back often for updates. Also, current jgcaap users will get additional information and tips that can be useful. Check out all the links! And if you want to try some Bacon wrapped Marshmallow, click the bent arrow in the Announcement's line.
Wildlife
Each ROM will be named by an animal, starting at A for Aardvark. A picture of the animal will be placed here so you can see at a glance which release is current. The original jgcaap ROMs often have multiple releases in a single day, and every country has a different date format, so the animal names will allow us to represent specific "official" releases with memorable names.
Release (CM 12.1 - jgcaap 11/30): (click image to update)
Downloads | Other Stuff | Links
Features & Changes
The ROM gets repackaged so that new users don't have to go about tracking down which files they need and which order to flash things. The firmware is included and everything is set and ready to go. For legal reasons, just add your own GApps and go. This ROM currently has the following feature's prepackaged and already included with the ROM ...
SuperSU (pre roooted)
Xposed (special jgcaap version)
Moab Ad Blocker
--- ZooKeeper can configure this!
ColorOS Camera
--- with manual focus option
Viper (Audio Eargasm)
Dolby ATMOS! (Dodo+)
Send Reduced (send small pics)
CatLog (for bug reports)
Show On Lockscreen (wallpaper)
OmniSwitcher (optional)
Init.d Support (Badger+)
Governor: blu-active (Badger+)
Low call volume fix
OTA Support (coming soon!)
Support, Questions, Feature Requests and Bugs
Please report all bugs for CM12.1/Lollipop based Jgcaap ROMs to this thread. Even if you didn't download one of the Wildlife pre-packaged ROM sets! Feel free to ask questions. This thread will have the same warm inviting atmosphere that jgcaap's development thread has always had. Newb-friendly and all are welcome!
Getting Started
There will be two ROM images available. The update packages will be designed with a smaller download size with only the files that have actually been changed. The installer will not remove things you have added nor re-install programs you have removed. If you are already using a WildLife ROM, use the Update packages to upgrade. This does not apply to full versions. The full versions should be clean flashed.
The next post will have Step-by-Step instructions telling you exactly what you need to do and how to go about flashing your phone or upgrading. The post after that will have all the tips and tricks for maximum tweaker power. Finally, we'll have instructions on how to rescue your phone when something goes wrong.
Sponsored by Eddon Systems
Additional Downloads at Eddon Systems Download Page
XDA:DevDB Information
Wildlife Android, ROM for the OnePlus One
Contributors
uudruid74, jgcaap, purerawenergy
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: INCLUDED
Source Code: Jgcaap's Github Repo
Based On: CyanogenMod 12.1
Version Information
Status: Stable
Current Stable Version: See Post
Stable Release Date: 2015-11-16
Created 2015-11-16
Last Updated 2015-12-11
Flashing WildLife
Flashing Instructions - Full ROM
Step 1 - Backup
If you don't have a backup program, you can grab a really fast and free one, Backup+. XDA Forum | My Mirror - Direct Download. Be sure you keep the APK on your Internal Storage so you can install it easily and restore the rest of your apps. Also, I strongly recommend you copy your internal storage (or at least the backup directory) onto a PC, a harddrive, a flash drive, or cloud storage such as Google Drive. Get it off your phone and make it safe.
Step 2 - Boot into Recovery
Even if your reboot menu doesn't have a Recovery option, you can always just hold down the Volume Down button when your phone boots and you're good. I recommend Philz Recovery from this XDA thread or you can download the exact ZIP I use.
Step 3 - Wipe Carefully
This step is what is known as a "clean flash". Do not perform this step if you are flashing an upgrade or addition. If this is the first time you've flashed this ROM, you want the full version and you want to do it cleanly. Failure to clean flash leads to odd problems. For example, Agent stopped reading my calendar, or my Camera plugins would start to disappear.
You do not want to do a Factory wipe or anything like that or you'll lose all your data. Do not format /data. Here's where it gets confusing. Many recovery systems treat /data and Internal Storage as if they were separate partitions, but they are not. Your internal storage is on the same partition as /data. If you are from Windows, image your /system is your C: drive, and /data (where your apps are at) and your internal storage are both on D:. Your recovery has a specific wipe designed to safely wipe /data without wiping out your internal storage by erase directories individually, yet automatically.
Philz makes this simple and direct. Select Wipe and Format Options, then select Clean to Install a New ROM. Confirm the wipe, and you are ready to go.
Step 4 - Flash the ZIP
This is pretty easy. Select the option to flash it, find it on your device, and away it goes. If you downloaded the file to your PC (or wiped your internal storage and now have no files on your phone), you can use the "sideload" option you see in the menu. Just plug in a USB cable and type: adb sideload Aardvark.zip This does require that you have adb drivers set up on your PC, but you needed that to unlock your bootloader, right? More tips like this in a later post!
Step 5 - Flash your Gapps
The most important part of Gapps is making sure its for Lollipop. The more up to date, the better. You should download the smallest GApps that fits your needs, just so you don't have to download so much. You can specifically control which Gapps are installed with a config file. Just drop the gapps-config.txt into the same directory as your gapps ZIP file. This file can even delete crufty Cyanogen apps that you don't need or want (you have better ones from Play store right?) and reduce bloat considerably.
About the Gapps Config | OpenGapps is the recommended Gapps package | Newer Sources for Gapps | My gapps-config.txt ... note: you might not want to use my config unless you want almost all your Cyanogen apps to go away. When the system comes up, you won't have a file manager to install Backup+. I install it with "adb install BackupPlus.apk" or if its on the phone, you can log in with adb shell and then install with pm install $PWD/BackupPlus.apk
TIP: If you have Chrome installed from Gapps, you can open it and type "file:///sdcard" in the URL window and then select your Backup+ or Titanium Backup APK to install it. Be sure you have "Install from unknown sources" turned on. Now you can restore your good File Manager (like FX File Manager mentioned in Post #5) from your Backup and don't need Cyanogen's!
NOTE: If you have trouble with OpenGapps, then you can try my stable mirror or SlimGapps (which is now recommended by jgcaap, but I've not tried it myself yet ... but expect it to be the new recommended after I run it through the paces).
Step 6 - Reboot your Phone
After flashing, the first time your phone comes up, its going to optimize itself and you should expect it to take awhile. Don't panic, and wait a few minutes. I refuse the CyanogenMod account (you already have a Google one, and Cyanogen doesn't offer anything extra and defintely do NOT send bug reports or analytics to Cyanogen!). I also go into Settings, About Phone, tap the Build Number like a mad monkey to turn on Developer options, and from there, I enable the Reboot Menu, Fast Boot, Cut the animations down to below 0.5, and turn on ADB since I'll be installing Backup+ over ADB.
Step 7 - Restore your Backup
Use your file manager (or ADB) to install your backup program and then restore the rest of the apps from your backup. I keep my Wifi off so that Google Play won't freak out and try upgrading stuff while its restoring. Do not use ROM Settings Backups to try to move settings from one ROM to another (thats what Update files are for). You can usually restore your Desktop with Backup+ by restoring the data for Trebuchet if you formerly used another Cyanogen release. The next reboot I go to Play Store and upgrade any apps that need it.
Step 8 - Final Config / Updates
I haven't found a perfect way to back up Trebuchet and my desktop ... but Backup+'s system backup tool (paid feature) can be used to restore the Trebuchet data, which gets everything but the widgets. If you use OmniSwitcher, just turn it on. If you use Xposed, it should already be working and active. If you don't use Xposed, jgcaap's version won't slow down your phone or cause glitches. However, if you really don't want it on your phone, you can flash this to deinstall it and can reinstall it without flashing the whole ROM by flashing this file.
MaxxAudio is gone ... use Viper. Set it to Super Audio Quality and reboot when it says to (Aardvark only, no reboot required for Badger and above). More about Viper here. I strongly recommend reading as there are a lot of optional add-ons (convolvers and such for emulating other tones and systems) but many of these will use significant battery power. I don't even use it for the built-in speaker. You can control it per output device, and have different profiles, such as if you have multiple pairs of headphones or different USB Audio devices.
Please Donate to the developers when you use an app. It is only through your support that you get to use high quality apps. This ROM has ads blocked, so developers of free apps will go poor and hungry since they won't be getting any revenue from your ad clicks!
Flashing Instructions - Updates
An update is a slimmed down version without any apps (unless they've been updated), no firmware, no media files, etc. And it avoids flashing over files you may have changed or deinstalled, like the hosts file or various bundled apps. It doesn't touch your settings, you don't need to wipe anything, and it just upgrades in-place. All you need to do is Steps 2 and 4 and 6!! Updates are clearly labelled. Never wipe your phone when installing an update! No OTA yet.
Tweaking
Tweaking, Trimming and Theming
Kernel
There is a UKM for jgcaap's kernel which is in the download area. You'll need Synapse from Play store to use it. I don't recommend tweaking the kernel, but if you want the option it is there. Just download the ZIP, flash it in recovery, and you can start tweaking some kernel parameters! Personally, I use 3C Android Tuner (see below) because it can tune more than just the kernel, but you might find something UKM does that 3C doesn't. As as Badger, you can use the init.d script option for restoring settings imposed by kernel tweakers.,
Governor
Your governor controlls when your CPU is at full blast, when it throttles down, and how quickly it changes and by how much. This will affect battery and performance (and "lag") considerably. As of Badger, the default CPU governor is "blu_active". You won't need to ever change to "Performance" mode to squeeze out more power, its runs even more fluid than before, and battery life is as good as ever. There are a couple ways to select the governor. The one I use is 3C (below). The only source of lag is memory. If you run out and Android has to swap stuff out, there will be a noticeable delay. If you rarely get lag, but get it rather severely, I bet its when you have 20 apps open and a million installed with their own background services and content providers! Suddenly the OOM (Out Of Memory) killer attacks and your phone stops for a second or two. I'm testing a possible solution, but everyone's phone is different.
CPU Temp
How hot does your CPU get? If you run Cardboard like me, you might be concerned. If you have to switch to an app to find out, then your CPU will have already cooled by the time you see the temp. This CPUTemp App displays an overlay anywhere you want that will show you your exact temperature. It can also save the data and give you in-depth graphs of CPU speed, load, and temperature. Alternately, you can just use this Xposed module to always show the CPU temperature in your status bar. (WARNING: I've not tested this Xposed module myself).
Xposed
Wildlife already has Xposed installed. If you have heard of requirements that your ROM must be deodexed or odex or and that you will have compatibility issues or slowdown, the current news is that the latest Xposed works on odexed ROMs and jgcaap has personally blessed some modifications to increase speed and compatibility with this ROM, and final result is packed into Wildlife. However, until you install some Xposed modules, it lies dormant. Fire up the Xposed Installer and you can start searching for tools to tweak how your phone looks, how it acts, how it sounds, and tweak some more battery life. Once you install a module, activate it, and then reboot.
Please be aware that not all Xposed modules are compatible with Lollipop and not all modules are created equal. I have heard mixed reports on GravityBox in particular. If for some reason your phone gets horribly confused and won't boot because of some Xposed module you have installed, or if you just hate the idea of having Xposed and want it gone. There is a solution! Flash this Xposed Uninstaller and if you flash this and want Xposed to come back, just Flash Jgcaap's modified v75 Xposed framework.
Ones I use are the 3C Toolbox helper, Clarity (makes your contacts in better definition), No Device Check (privacy), RootCloak (hides root), Smart Network (auto switches between 3G and LTE to conserve battery).
3C ToolBox
If you like tweaking, this toolbox has a little bit of everything. You can view logs, including last kernel boot log (the one that ran before you crashed), open a terminal, set a firewall, change CPU and GPU governors, disable services, remove programs from the start-up list, change network congestion control ... the list goes on and on!
Here is the XDA thread (with download links) for this tweaker's toolbox.
Battery Extensions
The first step to checking battery problems is Wakelock Detector and Better Battery Stats. These tools will tell you where your juice is going. If an app is holding a wakelock, ditch the app or alert the developer. Once you see what is chewing the most battery you can launch an assault on it with these tools:
Xposed Modules - Again, I'm going to defer to an expert source, @V7 's Extreme Battery Life Thread for all the goodies on PowerNap, Greenify, Amplify, and all the others that you've heard about.
Underclocking - I simply do NOT recommend this. Why? Well I checked Better Battery Stats! And my CPU had only been at full speed for 6% of the time. The next speed was under 2Ghz. So, is it worth slowing down your phone by 20% in order to achieve an overall savings of about 1.2% battery? The reason for this is that your system has what's called a governor that predicts how much CPU you need at any given moment and adjusts accordingly. This means you only use max CPU when you need it! If you underclock, then you are slowing down your phone when you need it most. You might even waste more battery because you'll be keeping your screen on longer waiting for your phone to finish!
Undervolting - I don't like this idea either. Basically, the voltage is how much strength it takes to open the transistor gates, like little doors. When your CPU gets busy, the voltage can fluctuate by small amounts, and if you undervolt your CPU, you can occasionally get a gate that doesn't open, and your get a CPU doing really crazy things and some app with crash or your whole system will crash. Generally, higher speeds require higher voltage to keep your CPU stable, and less voltage at lower speeds. Imagine trying to open and shut a door really fast ... you'll need more force than just shutting the door gently.
Can I get 9hrs SOT? - Sure! See the screen shot, but here's the secret. WASTE battery power! If you have a flip-case, remove it. Take your screen timer and set it REALLY high and don't turn off your screen. Let it BURN! This will ensure that your screen is on for a really long time. Cheating? Well, yes and no. The point is that someone who is chatting on their phone over Wifi and rarely touches it, but leave the screen on while doing so will get great SOT. The guy streaming Bluetooth audio all day long and has their phone tethered to use LTE internet with a low signal will waste tons of battery and may not have the screen on at all. The 9hr screen on time was done while doing all the above, plus some web browsing using ....
Ultimate Browser - This browser is said to use less battery than Chrome and others. You can check it out and see for yourself on The Ultimate Browser XDA thread.
Themes
Many people ask about the themes pictured in the screenshots. This is the Deep Darkness Overhauled Theme but with the thinner fonts from Cosmos CM12. Just select which parts of each theme you like before clicking the Update button.
I'm now using an Add-On package for this theme that gives icons that aren't so dark. It has a cool font, too, but I don't know if I like the Cosmos or Deep Darkness Add-On better. I'm also using a compromise between the 400 DPI (real) and 480 DPI (stock) of 440 DPI. This still gives me 5 icons wide on the home screens without throwing off apps that expect stock DPI (much).
Rescuing Your OnePlus From Disaster
Rescuing Your OnePlus From Disaster
I sure hope you never need any of this information! The following links are from Heisenberg's OnePlus One thread
Device Recovery/Unbrick Tools
[TOOL] One-Click Backup & Restore EFS on OnePlus One
[TOOL] OnePlusRecovery Tool | Restore Stock (CM11S) | Fix Bricks | ETC
[TOOL] OnePlus One Return To Stock - Automated!
[GUIDE] [UNBRICK] Unbrick Oneplus One
I originally intended to post a step-by-step, but instead I'll defer to existing/tested sources. Heisenberg's thread has tons of useful information and is well worth checking out.
More Info
Link Database
Someone has an awesome thread listing all the links you could ever ask for, so I'll defer to those that are already maintaining this. Here you are ...
http://forum.xda-developers.com/showthread.php?t=2843675
Recommended Apps
Please note that these are some of the best of the best, and most of them are not free!
Email - [email protected] Mail This is a fork of K-9, which is the Android Mutt (from Dr Who) .. mutt being a classic Unix mail program. I love Dr Who, but [email protected] was such a big improvement, I had to go with it. If you need full folder support, multiple accounts, and support for email cryptographic signing and encryption, multiple identities, and html editing of email and html signatures!
Music Player - PowerAmp - this is by the best music player I've used, bar none. If you don't want it messing with your custom lockscreen wallpaper, you can tell it not to, or add a whole second/custom lockscreen over the original. It has its own EQ, but I don't need it with Viper. To make PowerAmp compatible with Viper, simply turn off the direct volume control. You can use Xposed to add more volume steps if you like the extra control that PowerAmp's default has.
Video Player - VLC Video Lan Client Plays everything, does everything, streams videos, and has remote control apps to connect to other VLCs anywhere on your network.
QuickPic - QuickPic is a replacement for the stock Cyanogen Gallery. It works and acts much the same only its much much faster. Another good choice is Piktures, but new users may find it a bit more complicated, and it doesn't seem to be nearly as fast.
Agent - While much of what Agent does can be duplicated with other tools, the ease of use and flexibility of this tool can't be beat. It monitors your calendar for meetings and silences your phone, knows when you are driving and responds to your texts (and/or reads them to you), detects when your sleeping and makes your phone quiet (even if you sleep at different times). Has a battery saver mode, and can even remember where you parked. The Meeting agent works best if your calendar supports the "Busy" flag, which Google removed about a year ago, so ...
Today Calendar - The Today Calendar is just a really beautiful app and has some nice widgets (although I just use cLock from Cyanogen to show my calendar and make appointments via Voice commands, so I don't see Today much, I still bought it). It has the Busy flag and all sorts of features. If you want one a little less flashy (and free), try Boxer Calendar.
File Manager - The FX File Manager is by far the greatest file manager. It has everything built in, including SMB to network with Windows and SFTP to network with any machines running SSH. App Management, Media Refresh, and nice clean material design! Bloat free!
FXR Wifi Repair - Get this app and install it NOW! You will thank me the day you end up needing it!
Project Toolbar
For those on Tapatalk that don't get the toolbar, here it is ...
Downloads
ScreenShots
Reviews
Feature Requests
Bug Reports
.
I'm running 12.1-20151030 deodexed version. Could you provide me links to proper Xposed installer? Or is it ok to flash that one package with all that installed?
Sent from my A0001 using XDA Free mobile app
Tyga187 said:
I'm running 12.1-20151030 deodexed version. Could you provide me links to proper Xposed installer and Viper? Or is it ok to flash that one package with all that installed?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Don't know if 10/30 needs deodex or not but if its before jgcaaps hacks you'll need the older Xposed. I have it and Ill upload it for you to my site (Eddon Systems Download Page ... link in first post). Viper is already there (look for LolliViper).
If you don't mind taking the time to do a clean flash, Aardvark is based on the 11/08 build with the Apple code. All works out of the box Dirty flash possible, but can lead to weird problems.
I'll upload Xposed v75 right now
More about me at https://eddon.systems
Ok so it is possible to run odexed version and have Xposed working? I've heard that I need deodexed version for exposed that's why I'm on 20151030.
Thanks a lot for fast response!
Sent from my A0001 using XDA Free mobile app
Deodex and Xposed
The newer builds are made in such a way that you can use them with Odex builds without problems. We even have a special "Hacked" version of Xposed that prevents the possible slowdown issues and bypassing jgcaap's ART improvements.
So yes, use Odex and new builds and preferably the "Hacked ZIP" for the framework, although normal v75 still works. Or flash Aardvark. I've got maybe a dozen Xposed modules active.
The reason you don't see newer Deodex is because they aren't needed anymore
uudruid74 said:
The newer builds are made in such a way that you can use them with Odex builds without problems. We even have a special "Hacked" version of Xposed that prevents the possible slowdown issues and bypassing jgcaap's ART improvements.
So yes, use Odex and new builds and preferably the "Hacked ZIP" for the framework, although normal v75 still works. Or flash Aardvark. I've got maybe a dozen Xposed modules active.
The reason you don't see newer Deodex is because they aren't needed anymore
Click to expand...
Click to collapse
Which build has Apple code ? Normal odexed build , deodexed or bionic build ?
lokesh.3440 said:
Which build has Apple code ? Normal odexed build , deodexed or bionic build ?
Click to expand...
Click to collapse
It varies based on date and jgcaap's whim. The 11/08 builds do. I don't think any deodex builds do because he stopped making those before the Apple assembler code experiments.
Since 11/08 has it, Aardvark has it.
Bionic isn't a ROM build, its the Android low level C library to which the Apple code is being added.
More about me at https://eddon.systems
uudruid74 said:
It varies based on date and jgcaap's whim. The 11/08 builds do. I don't think any deodex builds do because he stopped making those before the Apple assembler code experiments.
Since 11/08 has it, Aardvark has it.
Bionic isn't a ROM build, its the Android low level C library to which the Apple code is being added.
More about me at https://eddon.systems
Click to expand...
Click to collapse
I m downloading latest build now.
Good job Evan. This will definitely help Jorge and the Marshmallow project. Thanks in advance brother.. See you on the testing ground.
Tom 2.0
Purerawenergy said:
Good job Evan. This will definitely help Jorge and the Marshmallow project. Thanks in advance brother.. See you on the testing ground.
Tom 2.0
Click to expand...
Click to collapse
I'm going to be stealing your post you made in the other thread about battery tweaks ... Greenify, Amplify, PowerNap and all that. It will go in the tweaks post. Let me know if that info is changed and if you can remember the date or post number for when I go digging.
More about me at https://eddon.systems
uudruid74 said:
I'm going to be stealing your post you made in the other thread about battery tweaks ... Greenify, Amplify, PowerNap and all that. It will go in the tweaks post. Let me know if that info is changed and if you can remember the date or post number for when I go digging.
More about me at https://eddon.systems
Click to expand...
Click to collapse
You may want to link my buddy @v7 in there somewhere if you want. He's the wake lock master Bro. And his helpfulness is awe inspiring.
Tom 2.0
---------- Post added at 03:36 PM ---------- Previous post was at 02:50 PM ----------
Oh and it's not stealing if you ask someone. Haha
Tom 2.0
Purerawenergy said:
You may want to link my buddy @v7 in there somewhere if you want. He's the wake lock master Bro. And his helpfulness is awe inspiring.
Tom 2.0
---------- Post added at 03:36 PM ---------- Previous post was at 02:50 PM ----------
Oh and it's not stealing if you ask someone. Haha
Tom 2.0
Click to expand...
Click to collapse
Actually, I put your name in as a contributor (and obviously @jgcaap) which gives you a lot more access. That way, if I'm hit by a bus tomorrow, other people can step in (its the admin in me). You might be able to edit the project page and initial reserved posts yourself.
My routed here is getting old so I'm doing a reflash and adding a captive portal to disconnect people when there isn't a human body using it. I need to cut down on everyone's bandwidth usage. So ... gonna be a busy night.
More about me at https://eddon.systems
uudruid74 said:
Flashing Instructions - Full ROM
If you don't have a backup program, you can grab a really fast and free one, Backup+. XDA Forum | My Mirror - Direct Download.
Click to expand...
Click to collapse
Hi,thanks for this thread. I've downloaded aardvark but for the backup+ download from : https://eddon.systems/Download/Backup+_Beta_1_R2.apk I get a 403 forbidden.
Verstuurd vanaf mijn A0001 met Tapatalk
I am going to download your rom and test it in a couple of days
Wysłane z mojego A0001 przy użyciu Tapatalka
Well this came around at a perfect time! I haven't been actively flashing my phone much this year and my current ROM is from July 5th lol. So I'm not really new, but could use something pre made like this. Reading, backing up, and downloading this afternoon, then flash later tonight. Thanks for putting this up.
Is the rom ok to flash on system/data/cache on f2fs ?
Hi there. I'm really confused about how to proceed and would appreciate some help.
I have a Kindle Fire HDX 7 (3rd Gen) on which I would like to wipe the Fire OS, and replace it with a working, functional Android ROM. I have some basic competence with installing software, flashing phones, etc., but am by no means an expert. I have both Windows & Linux PCs with which to connect.
A year or so ago I tried to get the tablet working with Google Apps, etc.. I can't remember precisiely what I did (!), but I think I used TWRP, I rolled back the operating system to 4.5.2, turned off the updates, and installed a Google Apps piece of software. The tablet then worked reasonably well, but not great. By that I mean I could web browse, and download and use some apps from the Play Store, but lots of stuff didn't work preoperly. At some time since then, the tablet decided it no longer wanted to install/update from the Play Store, and more of the apps have stopped working. I can still web browse.
TBH, I've got to the point where if I can't completely replace the OS then I think I'm just going to stop using it.
What steps should I take to get a 'proper' ROM working on the tablet?
Thanks very much in advance for any help,
Aaron
alhroot said:
Hi there. I'm really confused about how to proceed and would appreciate some help.
I have a Kindle Fire HDX 7 (3rd Gen) on which I would like to wipe the Fire OS, and replace it with a working, functional Android ROM. I have some basic competence with installing software, flashing phones, etc., but am by no means an expert. I have both Windows & Linux PCs with which to connect.
A year or so ago I tried to get the tablet working with Google Apps, etc.. I can't remember precisiely what I did (!), but I think I used TWRP, I rolled back the operating system to 4.5.2, turned off the updates, and installed a Google Apps piece of software. The tablet then worked reasonably well, but not great. By that I mean I could web browse, and download and use some apps from the Play Store, but lots of stuff didn't work preoperly. At some time since then, the tablet decided it no longer wanted to install/update from the Play Store, and more of the apps have stopped working. I can still web browse.
TBH, I've got to the point where if I can't completely replace the OS then I think I'm just going to stop using it.
What steps should I take to get a 'proper' ROM working on the tablet?
Thanks very much in advance for any help,
Aaron
Click to expand...
Click to collapse
There's a good chance you can replace FireOS with CM11 or Nexus, two popular ROMs that are well suited to this device. First order of business is to assess the current status of your device. What version of FireOS is currently installed? It it reasonably stable? Many times laying Google components over FireOS creates other issues that can interfere with components needed to support an alternative rom.
Davey126 said:
There's a good chance you can replace FireOS with CM11 or Nexus, two popular ROMs that are well suited to this device. First order of business is to assess the current status of your device. What version of FireOS is currently installed? It it reasonably stable? Many times laying Google components over FireOS creates other issues that can interfere with components needed to support an alternative rom.
Click to expand...
Click to collapse
Davey, thanks for the reply.
I've just checked, and the Fire OS version running on the tablet is 4.5.2.
The device is stable.
alhroot said:
Davey, thanks for the reply.
I've just checked, and the Fire OS version running on the tablet is 4.5.2.
The device is stable.
Click to expand...
Click to collapse
Next step is to allow the device to update to FireOS 4.5.5.1. While you could get by with 4.5.2 the newest rom builds require low level (kernel) components that get installed with 4.5.5.1. Replacing FireOS is the only way to get these pups on an HDX; there is no way to install them separately.
To obtain 4.5.5.1 you need to unblock OTA updates which typically involves renaming a file back to its original ID using a tool such as ES File Explorer. Search for a file starting with 'DeviceSoftwareOTA' which is typically located in /system/priv-app/. It will probably be called 'DeviceSoftwareOTA.bak' or something similar. Rename that to 'DeviceSoftwareOTA.apk', reboot and check for updates. You will loose root if 4.5.5.1 is successfully found/installed but you can get it back fairly easily.
FWiW - There are other methods of blocking OTA updates such as renaming the otacerts.zip file. That approach is less common on this device.
Davey126 said:
Next step is to allow the device to update to FireOS 4.5.5.1. While you could get by with 4.5.2 the newest rom builds require low level (kernel) components that get installed with 4.5.5.1. Replacing FireOS is the only way to get these pups on an HDX; there is no way to install them separately.
To obtain 4.5.5.1 you need to unblock OTA updates which typically involves renaming a file back to its original ID using a tool such as ES File Explorer. Search for a file starting with 'DeviceSoftwareOTA' which is typically located in /system/priv-app/. It will probably be called 'DeviceSoftwareOTA.bak' or something similar. Rename that to 'DeviceSoftwareOTA.apk', reboot and check for updates. You will loose root if 4.5.5.1 is successfully found/installed but you can get it back fairly easily.
FWiW - There are other methods of blocking OTA updates such as renaming the otacerts.zip file. That approach is less common on this device.
Click to expand...
Click to collapse
Bang on.
I renamed the file from '.bak' to '.apk', rebooted, and did a couple of updates cycles.
I'm now on FireOS 4.5.5.1 ...
alhroot said:
Bang on.
I renamed the file from '.bak' to '.apk', rebooted, and did a couple of updates cycles.
I'm now on FireOS 4.5.5.1 ...
Click to expand...
Click to collapse
Fantastic! Next step is to root with KingRoot (apk or tethered version). After that the good stuff starts happening. Sorry for piecemealing out details; I find it works better in the absence of an A to Z guide.
Be out-of-pocket for a few hours; will look for your response later.
Davey126 said:
Fantastic! Next step is to root with KingRoot (apk or tethered version). After that the good stuff starts happening. Sorry for piecemealing out details; I find it works better in the absence of an A to Z guide.
Be out-of-pocket for a few hours; will look for your response later.
Click to expand...
Click to collapse
Okay, I think that's all good ... Kingroot apk downloaded & installed, device rooted, turned on root explorer in ES File Explorer as a test: prompted for permission.
Davey, thanks again for your help.
So now for the good stuff ... ??? :good:
alhroot said:
Okay, I think that's all good ... Kingroot apk downloaded & installed, device rooted, turned on root explorer in ES File Explorer as a test: prompted for permission.
Davey, thanks again for your help.
So now for the good stuff ... ??? :good:
Click to expand...
Click to collapse
Excellent. Next step is to install Safestrap 4.0.1 which provides a pseudo recovery environment that supports the installation of custom roms. It looks a lot like TWRP (but isn't). You can snag the app from here; be sure to select the appropriate format. Once installed launch the app and install Safestrap recovery which is the component that does the heavy lifting.
Important: Once Safestrap recovery is installed never (never!) attempt a 'factory reset' - either from the stock recovery menu or from within FireOS. Doing so will brick the device with no possible recovery.
Now reboot. You'll notice a new screen that has a couple options at the bottom. Select the option that launches Safestrap recovery. Take a look around but don't change anything. When ready return to the home screen and then go into the backup section. Take a backup of your current FireOS installation (selection all partitions). You will want this should you every want to restore you device to it's current configuration. The resulting files will be quite large and should be copied to another device for safe keeping. Exit Safestrap and reboot into FireOS. Tether your device and copy the files to a suitable host. You seem to be familiar with ES File Explorer so should have no problem finding them. Should be in the TWRP directory located within sdcard (or just browse internal storage from the host machine).
Next step is to decide which rom to flash. Two are available/compatible with Safestrap 4.0.1: CM11 and Fire Nexus which are both KitKat based. Both are solid, feature complete and regularly updated with security patches. My daily driver on this device is Nexus as I prefer to build upon a pure Android foundation. That said, CM11 is a fine choice and my preferred rom on secondary devices as it contains a suite of nice UI enhancements minimizing post flash tweaks. FWIW - Lollipop+ roms are not an option as they require an unlocked bootloader which is not possible on your device.
Once you decide upon a rom I'll provide the final set of instructions (really best practices) for installing the rom and related components such as Google Play Services/Store. Feel free to read through the linked threads which contain numerous 'how-to' posts, especially the first couple posts in the rom threads. If all goes well you'll be running a custom rom by this time tomorrow.
Another step complete ...
I downloaded the Safestrap apk from the link contained in the thread, choosing THOR (HDX 7"), installed the app, then installed the recovery software. After a reboot I backed up, and then copied the resultant folder to a PC.
Question: The back up folder is really big (4GB) ... is it okay if I now delete the back up on the tablet? To do this, can I just delete with ESFE?
Duly noted about not doing a factory reset.
After having a read, I think I'm happy to go with the Nexus ROM - keeping things as clean as possible. It sounds like it's very solid with no real issues.
Davey, thanks once again for your precise and excellent help.
Cheers,
Aaron
alhroot said:
Another step complete ...
I downloaded the Safestrap apk from the link contained in the thread, choosing THOR (HDX 7"), installed the app, then installed the recovery software. After a reboot I backed up, and then copied the resultant folder to a PC.
Question: The back up folder is really big (4GB) ... is it okay if I now delete the back up on the tablet? To do this, can I just delete with ESFE?
Duly noted about not doing a factory reset.
After having a read, I think I'm happy to go with the Nexus ROM - keeping things as clean as possible. It sounds like it's very solid with no real issues.
Davey, thanks once again for your precise and excellent help.
Cheers,
Aaron
Click to expand...
Click to collapse
Super! Final step is to install Nexus. Grab the Thor (nickname for 3rd gen HDX 7) installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
Boot into Safestrap recovery. Use the File Manager (under advanced) to confirm the existence/location of the Nexus rom zip. Return to the home screen and then access the wipe menu. Use the slider at the bottom to perform a factory reset which wipes the data, cache and dalvik partitions. Note this is different that a stock 'factory reset' which was discussed in a previous post. Also note it is impossible to wipe the system partition in Safestrap v4 even if selected in the advanced section. I won't get into the reasons; just know it isn't necessary for the upcoming operation.
Return to the home screen and select install. Navigate to the folder containing the Nexus rom, select it and then and then swipe the slider at the bottom to install (flash) the zip which will overwrite FireOS. When complete (assuming no errors) reboot your tablet and select continue to fire up Nexus. First boot make take some time as caches are populated. However, anything over 5 min indicates a problem. Once Nexus starts I assume you know where to go from there. You can safely enable WiFi, register with Google and perform all other requested initialization steps.
A few final footnotes:
- Nexus is pretty bare bones; not even a browser in included in the base build. Head over to the Play Store to grab what you need
- While Google's stock launcher is nice I suggest replacing it with Nova which offers a superior AOSP experience along with robust customization
- Xposed Framework and associated modules offers some excellent additions to this rom if you wish to customize further (advanced topic)
- Once you are confident Nexus is stable you can delete the huge FireOS backup created in an earlier step. Either via ESFE or from Safestrap
You may be aware Safestrap supports multi-boot through the use of user created slots. Unfortunately, they do not work with this device and can lead to unrecoverable bricks. You'll see various cautions in the Safestrap, Nexus and CM threads. Short version: do not create or use secondary slots.
Aaron - Feel free to post any questions/concerns/comments. Someone from the HDX community will likely respond within 24-48 hours. On a personal note it's been awhile since I did a long hand 'step-by-step' which is a refreshing change of pace from the usual bullets. I appreciate your patience as I dusted off various cob webs and hope you make the most out of your newly liberated device.
Nice!
Nexus installed, and I'm using it right now ?
Absolutely superb help Davey. I was totally confused trying to work out how to go from where I was to where am now, and you've completely sorted me out. A massive thanks from me.
Everything seems to be working well (!) ... I'm going to test things out a bit more before deleting the FireOS back up folder. I think I messed around with the xposed framework before... I'll definitely take another look.
Seriously, thank you.
Cheers,
Aaron
alhroot said:
Nice!
Nexus installed, and I'm using it right now ?
Absolutely superb help Davey. I was totally confused trying to work out how to go from where I was to where am now, and you've completely sorted me out. A massive thanks from me.
Everything seems to be working well (!) ... I'm going to test things out a bit more before deleting the FireOS back up folder. I think I messed around with the xposed framework before... I'll definitely take another look.
Seriously, thank you.
Cheers,
Aaron
Click to expand...
Click to collapse
Great to hear! As an aside (not for me) don't forget to click the 'Thanks' button on XDA posts when appropriate, especially for newer members trying to build a reputation. Great working with you and gratified by the positive outcome.
Davey126 said:
Super! Final step is to install Nexus. Grab the Thor (nickname for 3rd gen HDX 7) installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
Boot into Safestrap recovery. Use the File Manager (under advanced) to confirm the existence/location of the Nexus rom zip. Return to the home screen and then access the wipe menu. Use the slider at the bottom to perform a factory reset which wipes the data, cache and dalvik partitions. Note this is different that a stock 'factory reset' which was discussed in a previous post. Also note it is impossible to wipe the system partition in Safestrap v4 even if selected in the advanced section. I won't get into the reasons; just know it isn't necessary for the upcoming operation.
Return to the home screen and select install. Navigate to the folder containing the Nexus rom, select it and then and then swipe the slider at the bottom to install (flash) the zip which will overwrite FireOS. When complete (assuming no errors) reboot your tablet and select continue to fire up Nexus. First boot make take some time as caches are populated. However, anything over 5 min indicates a problem. Once Nexus starts I assume you know where to go from there. You can safely enable WiFi, register with Google and perform all other requested initialization steps.
A few final footnotes:
- Nexus is pretty bare bones; not even a browser in included in the base build. Head over to the Play Store to grab what you need
- While Google's stock launcher is nice I suggest replacing it with Nova which offers a superior AOSP experience along with robust customization
- Xposed Framework and associated modules offers some excellent additions to this rom if you wish to customize further (advanced topic)
- Once you are confident Nexus is stable you can delete the huge FireOS backup created in an earlier step. Either via ESFE or from Safestrap
You may be aware Safestrap supports multi-boot through the use of user created slots. Unfortunately, they do not work with this device and can lead to unrecoverable bricks. You'll see various cautions in the Safestrap, Nexus and CM threads. Short version: do not create or use secondary slots.
Aaron - Feel free to post any questions/concerns/comments. Someone from the HDX community will likely respond within 24-48 hours. On a personal note it's been awhile since I did a long hand 'step-by-step' which is a refreshing change of pace from the usual bullets. I appreciate your patience as I dusted off various cob webs and hope you make the most out of your newly liberated device.
Click to expand...
Click to collapse
Hey Davey,
Thanks for reaching out to my thread and directing me to your conversation here. I followed all your steps and was able to successfully install the Nexus ROM and have everything running smoothly!!! Very happy! I had been hunting for a while to find a step by step instruction like yours!.
Thanks a lot!
P.S. Wasn't sure whether I should post this here or in my own thread but figured you were actively following this
One week on and I've been using my 'new' tablet quite a bit. It's been really solid with no crashes or problems whatsoever. Fantastic. I've now deleted the 4GB back up on the device, freeing up loads of space again.
I've had another good look at the Xposed framework, but frankly I'm so pleased to have the tablet running smoothly I think I'm just going to keep things nice and standard for now.
Davey, thanks (I found the button now!) again for sharing your knowledge, and giving your time and help. Very much appreciated.
Cheers,
Aaron
alhroot said:
One week on and I've been using my 'new' tablet quite a bit. It's been really solid with no crashes or problems whatsoever. Fantastic. I've now deleted the 4GB back up on the device, freeing up loads of space again.
I've had another good look at the Xposed framework, but frankly I'm so pleased to have the tablet running smoothly I think I'm just going to keep things nice and standard for now.
Davey, thanks (I found the button now!) again for sharing your knowledge, and giving your time and help. Very much appreciated.
Cheers,
Aaron
Click to expand...
Click to collapse
Hey Aaron, thanks for the follow-up. If you are happy with native rom/app capabilities there is no need to complicate matters. That said, if you every have a need for additional core functionality Fire Nexus, an AOSP clone, has proven to be an ideal platform for Xposed Framework and associated KitKat modules.
A tip of the hat to @ggow for his outstanding adaptation and ongoing support of this rom that is cornerstone of the post FireOS experience.
Enjoy your rejuvenated HDX!
Hi there. Thanks for this tutorial - I used it to install the Nexus ROM on my device. One weird thing; everything works, but I have NO sound? Any ideas why that might be?
skoop99 said:
Hi there. Thanks for this tutorial - I used it to install the Nexus ROM on my device. One weird thing; everything works, but I have NO sound? Any ideas why that might be?
Click to expand...
Click to collapse
Thoughts:
- a full power off/on (vs reboot) sometimes solves weird HW issues
- what version of FireOS was on the device prior to Nexus? 4.5.5.1 is recommended for the proper binaries
- might try a simple (dirty) reflash of Nexus in case something didn't 'take' on the first attempt (stranger things have happened)
Davey126 said:
Thoughts:
- a full power off/on (vs reboot) sometimes solves weird HW issues
- what version of FireOS was on the device prior to Nexus? 4.5.5.1 is recommended for the proper binaries
- might try a simple (dirty) reflash of Nexus in case something didn't 'take' on the first attempt (stranger things have happened)
Click to expand...
Click to collapse
Rebooted. I was on 4.5.5.1...
Will try a quick re-flash. ? Thanks!
Update, I have sound over headphones, but not over the speakers... :-S
skoop99 said:
Update, I have sound over headphones, but not over the speakers... :-S
Click to expand...
Click to collapse
Suggest you backup your current Nexus build from within Safestrap, then flash the Safestrap compatible version of cm11 to see if the problem persists. Yep, a bit of trial-and-error but not sure how else to diagnose. You could also try the Safestrap compatible build of FireOS (4.5.2; be sure it's the Safestrap build as a standard FireOs build will brick the device). Another option is to flash the Dolby enhancements which use a different suite of binaries. Post back if you need links to any of the above.
Hello!
Before proceeding. It is absolutely necessary for you to be on a stable TWRP build (currently, RC8, 3.0.2-0, and 3.0.2-1). Also, you must have already have had decrypted your ENTIRE phone. If your phone bootloops into TWRP, you probably didn't decrypt, and/or didn't flash no-verity properly, or it could also be that you are on an old TWRP build.
Here we have the base NRD90M ROM from LG.
I have added a few mods to it.
FEATURES
**Multi-user working!
**This ROM is deODEXd
**Has init.d support
**Modified build.prop for better performance and hardware utility
**Removed bloatware (including that HORRID Lookout)
**Force encrypt disabled
**New kernel built-in.
**Based off 3.18.31 from @jcadduono source (thanks so much)!
**Added in the blu_active governor and set as default (via post_boot)
**No-op scheduler is default, and recommended
**Updated build.prop for better Hotspot support.
**More build.prop tweaks
**init.d support baked into the kernel
**Battery life should be noticeably improved, with no loss of performance (maybe even a bit faster).
**No need to wipe anything. System and caches are automatically wiped.
**Updated to SuperSU 2.78 SR4
**Updated boot and shutdown animation to the Android 7 default (thanks @freeza )
**More bloat removed
** Now includes more performance tweaks.
**Full Busybox support included!
**Fixed updater-script and binary
**Removed Sony Bravia/Xperia Engine
**Zen_Decision HotPlug enabled by default. (This will improve battery life, especially when your screen is off)
**TCP Congestion controller set to Westwood+ (improved download speeds)
**KCAL Color Control! Plus the Color Control app! Thanks to @savoca for KCAL and the app! Thanks to @freeza for the updated KCAL.c source file
**IO Stats for scheduler turned off
**IO Read ahead set to 2048kb
**Added init.d scripts to optimize your phone, and keep it fast over time.
**VPN is fixed!
**Gallery locked files are fixed!
**Bluetooth and FM should be fixed!
**No hotspot or ADB debug issues!
**More things I can't remember.
Kernel built on the Linaro 6.1.1 x86_x64 toolchain
Latest: v5.1 combined with v5.5
v5.5 is intended only for people already on v5.1. It will not wipe anything, and your phone will not need to do its initial setup. 5.5 is an update only! You must first flash 5.1, then 5.5. You can tell TWRP to flash files in sequence, so it's no hassle. ZIP no longer checks your device, so be sure that you are flashing for the model the sticker on the phone says that it is.
Here are the changes for v5.5:
Removed boot state verification. This allows your device to pass CTS on SafetyNet. That means that you might be able to use a root hide program, or maybe full unroot within SuperSU, and perhaps apps like Android Pay and Pokemon GO will work. They will never work if root is detected, no matter what.
Used more independent defconfig lines, hopefully static will go away... I highly doubt it, might even cause a no-boot issue. If it does, just tell me and I'll fix it up.
The main changes here are even more battery saving
**some voltage control preparations (still not active)
**added a DNS resolver module to maybe help some people with hotspot.
**Bluetooth and FM should work even better than before (hopefully not worse lol)
** C-states are made aware in the kernel, so sleeping should be more effective, while waking up should be more snappy.
More things. Do it!
Here are the changes for v5:
**ViPER4Android is preinstalled
**Kernel updates to latest sources (no changes other than updates)
**Included Titanium Backup pre-installed. I highly recommend getting the license, this program rocks, and never has ads. With a license you can do batch functions, and theres more features.
**Included Kernel Adiutor to prepare future kernel updates (CPU/GPU under+over clocking later on). You can also use this to tweak I/O settings, governor, screen color). Everything should run pretty good as it is, but what I do, is set read_head in I/O to 2048, and disable I/O Stats. I also set it on boot. I do not recommend modifying any CPU or GPU frequencies since there are no changes in the kernel to allow for that.
**Updated to latest Super SU
If the ROM won't flash because it says you have the wrong device
This is likely due to the conversion thing you guys had to do to root. I don't have the AT&T device and I don't know about that conversion thing. To bypass it, open the ZIP, go into META-INF/com/google/android and delete only the file called updater-script. Replaced it with this one
No need to wipe anything. If you are on stock ROM, ODEXd or deODEXd, or any other NRD90M ROM, you don't need to wipe, the ZIP will take care of everything for you. /data will not be wiped, so all your old apps and settings will be there. Internal storage is of course untouched.
For anyone interested in my color options, they are:
My new settings are:
All 3 colors at 256
Saturation 68
Value 129
Contrast 127
Know that I love deep, rich, vibrant colors. Also, changing colors will not change effects on pictures taken! This is post-processing. Your phone's screen is what changes, not the files that you create.
Note: Adding saturation (vibrance) will always give some sort of color banding -especially since KCAL is post-processing. You can minimize color banding by ever-so-slightly reducing gamma (read as "Value" in the Color Control app), and by ever-so-slightly fine-tuning Contrast. The value changes would be minimal, and the color banding will only be reduced ever-so-slightly, but this is just how it is. Nonetheless, the device looks friggin amazing with the color options set.
Having issues? Read below.
I need you guys to hear me out on this...
I do not have this phone, I cannot do any sort of testing, nor do I keep up with your rooting method.
That said, I cannot fix things that were broken due to the bootloader (such as Static Boot), so if WiFi calling did not work for you after flashing the custom bootloader, please don't ask if it is fixed... I do not know how to fix it. When/if it is fixed, I will let you guys know that it is fixed and who to thank for said fix.
Additionally, I need you to tell me things that do not work. I might not be able to get to all messages, or questions, so if you see that I did not reply, ask again and again until I do... I will reply and answer (obviously don't spam). Be sure to quote me, mention me, or message me. I do not check-in with these threads, just the H918 thread. If you do not send me a notice, I will not know that my attention is needed.
What issues that are ROM-related, not user-related can you report? You will know it is user-related if you modified anything in the phone/ROM.
If you flashed a different kernel, I cannot help you; flash back to the NSS kernel, and re-test.
If you are unsure about an issue, do a clean flash (in TWRP: Wipe-->Advanced-->select Dalvik, System, Data, and Cache (DO NOT SELECT INTERNAL STORAGE OR SDCARD)-->Swipe to wipe-->Install ROM-->boot phone, do not change or install anything. Retry your issue, if it is fixed, great. If it persists, go into your SD Card, and Internal Storage, remove the folders called "Android" and ".android_secure", reboot and try again. Still doesn't work? Mention me and post it here.
Remember, you can backup your USER apps in Titanium Backup (do NOT backup system apps, or restore system apps/system data).
You can also backup your existing setup and apps in TWRP so you can flash back to your original setup. This is good if you did a clean flash, and your problem is still there, you can restore your backup and be like nothing was changed.
Thanks @zhuhang for V4A!
Major thanks to @Chainfire for creating SuperSU
Major thanks to @jcadduono for the root exploit, AND for the TWRP image(s), AND for inspiring me to learn to do it. Also, he supplied the stock System.img, boot.img, and sources for a custom kernel!/RealMVP
Viper4Android is included! To enable, run the app, and configure how you please!
More to come (as I learn to do it)
Please make any requests. If it is not too difficult, I will learn how to, and add it to the MODDED ROM!
Debloat list
Removed from /system/
system/app/CloudPrint*
system/app/Drive*
system/app/DriveActivator*
system/app/EditorsDocs*
system/app/Gmail2*
system/app/Hangouts*
system/app/Music2*
system/app/talkback*
system/app/Videos*
system/app/YouTube*
system/etc/recovery-resource.dat*
system/priv-app/LGEmail*
system/priv-app/LGTasksProvider*
system/recovery-from-boot.p*
system/app/AndroidPay*
system/priv-app/facebook-installer*
system/priv-app/GoogleFeedback*
system/app/LGAccount*
system/app/LGAirDrive*
system/priv-app/LGAirDriveSetting*
system/priv-app/LGBackup*
system/app/LGBackupLauncher*
system/priv-app/LGExchange*
system/app/LGFOTA*
system/app/LGMusicShare*
system/priv-app/LGPartnerBookmarksProvider*
system/app/LGSpringCleaning*
system/priv-app/Lookout*
system/priv-app/TMO_MyAccount*
system/priv-app/LGApplicationManager*
system/vendor/overlay/com.lge.friendsmanager*
system/vendor/app/facebook-appmanager*
system/priv-app/LGPCSuiteService*
system/priv-app/PromoHelper*
system/priv-app/LGQHelp*
system/priv-app/LGQHelpService*
system/priv-app/NameID*
system/priv-app/LGUpdateCenter*
system/vendor/overlay/com.lge.updatecenter*
system/vendor/overlay/com.android.providers.partnerbookmarks*
system/vendor/overlay/com.lge.appbox.client*
system/vendor/overlay/com.lge.exchange*
system/vendor/overlay/com.lge.updatecenter*
system/vendor/overlay/com.lge.bnr*
system/etc/amzn.mshop.properties
system/vendor/overlay/com.lge.lgworld*
system/vendor/overlay/com.lge.mlt*
system/vendor/overlay/com.lge.lifetracker*
system/priv-app/AdaptClient*
system/priv-app/ATT_ProtectPlus*
system/priv-app/ATT_DeviceHelp*
system/priv-app/ATT_Lookout*
system/priv-app/ATT_SmartLimits*
Source for kernel is at (need to update)https://github.com/jcadduono/android_kernel_lge_msm8996/tree/android-7.0-security
Thanks to @jcadduono for the amazing original source he made for us ( you can find it here : https://github.com/jcadduono/android_kernel_lge_msm8996/tree/android-7.0-security
Everything is still working great! Thanks again @Tilde88. Those color settings are awesome, too. Much better than stock!
Glad to see this! Trying now..
UPDATE: Runs pretty smooth. Thanks again!
Yeah it worked perfectly now after replacing the updater-script (correctly). Thanks for doing this! My only request is just on adding the advanced power menu options such as reboot to recovery/bootloader Other than that - its perfect.
Twisted
twistedvip said:
Yeah it worked perfectly now after replacing the updater-script (correctly). Thanks for doing this! My only request is just on adding the advanced power menu options such as reboot to recovery/bootloader Other than that - its perfect.
Twisted
Click to expand...
Click to collapse
I second this! Advanced power menu with recovery/bootloader reboot would be great. I use ROM Toolbox Pro to boot into recovery as it is now.
Also, would like to put GApps Pico with the ability to add any extra Google features as necessary. I pretty much just use the play store and some services. I like minimal Google services and apps on my phone. For example, I use Waze instead of Google Maps, and I use Gmail, but not the app. I use a different email app but I cannot delete Maps or Gmail since they are system apps, just disable them and their services. I don't use OK Google, Google Now, Hangouts, etc... There are a lot more examples like this.
nikktrikk said:
I second this! Advanced power menu with recovery/bootloader reboot would be great. I use ROM Toolbox Pro to boot into recovery as it is now.
Also, would like to put GApps Pico with the ability to add any extra Google features as necessary. I pretty much just use the play store and some services. I like minimal Google services and apps on my phone. For example, I use Waze instead of Google Maps, and I use Gmail, but not the app. I use a different email app but I cannot delete Maps or Gmail since they are system apps, just disable them and their services. I don't use OK Google, Google Now, Hangouts, etc... There are a lot more examples like this.
Click to expand...
Click to collapse
You can delete system apps by using a program such as Titanium Backup. You can also backup your apps, and restore them on other ROMs. Don't backup system apps, just user apps.
I recommend the Pro version of Titanium; I bought it years ago, and still use it today. One of, if not the actual best, backup/restore program.
With pro you can do batch files, instead of 1by1. Also good for games to save their current state.
Tilde88 said:
You can delete system apps by using a program such as Titanium Backup. You can also backup your apps, and restore them on other ROMs. Don't backup system apps, just user apps.
I recommend the Pro version of Titanium; I bought it years ago, and still use it today. One of, if not the actual best, backup/restore program.
With pro you can do batch files, instead of 1by1. Also good for games to save their current state.
Click to expand...
Click to collapse
Titanium Backup is great! I have the pro version as well and use it constantly. I guess I'm not really concerned with the apps taking up space, rather just starting with the bare minimum of necessary things and adding what is needed afterward. But I usually freeze the apps just to avoid any possible issues with deleting. Another app that is just as great is ROM Toolbox Pro. Their App Manager and Auto Start Manager have advanced freeze functions that show you every single activity, receiver, and service attached to each app and gives you full functionality over them.
@nikktrikk @twistedvip or anyone else that wants to test.
@me2151 has given me a new defconfig for the kernel which might fix the static boot thing. Can anyone try it out for me please? It can be found here. Let me know how it goes. Thanks.
Tilde88 said:
@nikktrikk @twistedvip or anyone else that wants to test.
@me2151 has given me a new defconfig for the kernel which might fix the static boot thing. Can anyone try it out for me please? It can be found here. Let me know how it goes. Thanks.
Click to expand...
Click to collapse
Just flashed on my H910. Unfortunately, it still gave me the static screen upon reboot.
EDIT: It also seems to have made the phone very laggy compared to your original custom ROM.
Twisted
:/
twistedvip said:
Just flashed on my H910. Unfortunately, it still gave me the static screen upon reboot.
EDIT: It also seems to have made the phone very laggy compared to your original custom ROM.
Twisted
Click to expand...
Click to collapse
You can flash the boot.img from the ROM you already have downloaded. Just extract it out of the .ZIP, go to twrp, and flash the image as Boot
Tilde88 said:
You can flash the boot.img from the ROM you already have downloaded. Just extract it out of the .ZIP, go to twrp, and flash the image as Boot
Click to expand...
Click to collapse
Thanks, I just flashed back to your original custom kernel. Let me know if there's anything else y'all might come up with and want me to test out. Always willing to help out.
Twisted
Tilde88 said:
You can flash the boot.img from the ROM you already have downloaded. Just extract it out of the .ZIP, go to twrp, and flash the image as Boot
Click to expand...
Click to collapse
Everything is still running great. Much better battery life than stock! Just wanted to let you know, the only thing I have found that is missing is the Screen Capture feature. On the stock AT&T ROM, it is included in the pull down menu from the top, but it is not here at all in the custom ROM. If you navigate to Settings>Display>Home touch buttons>Button combinations, you can actually see the capture icon used as an example in the help section in the bottom half of the screen showing how to rearrange the buttons. The center button shows the capture button icon, but that button is not an available button to choose from when actually rearranging the Home touch buttons.
nikktrikk said:
Everything is still running great. Much better battery life than stock! Just wanted to let you know, the only thing I have found that is missing is the Screen Capture feature. On the stock AT&T ROM, it is included in the pull down menu from the top, but it is not here at all in the custom ROM. If you navigate to Settings>Display>Home touch buttons>Button combinations, you can actually see the capture icon used as an example in the help section in the bottom half of the screen showing how to rearrange the buttons. The center button shows the capture button icon, but that button is not an available button to choose from when actually rearranging the Home touch buttons.
Click to expand...
Click to collapse
Screen capture can be done by pressing Vol Down and Power at the same time in any screen.
*click*
Tilde88 said:
Screen capture can be done by pressing Vol Down and Power at the same time in any screen.
*click*
Click to expand...
Click to collapse
I have no problem doing a screen capture, I just wanted to let you know for the sake of knowing that the capture button icon is not included. Just so you have a comprehensive list of features no matter how minor they might be
Tilde88 said:
Screen capture can be done by pressing Vol Down and Power at the same time in any screen.
*click*
Click to expand...
Click to collapse
Its also on the second screen and is very handy and much faster. I know for me my case is of some crap rubber amd hard to hit both at the same time
Got the error that I'm not a 910. Tried swapping the update script to bypass the check, but now get an error that the update binary is missing while trying to flash it. Went to check and it is still the in the zip however. Did I miss something obvious?
Sent from my Pixel using Tapatalk
streetpounder said:
Got the error that I'm not a 910. Tried swapping the update script to bypass the check, but now get an error that the update binary is missing while trying to flash it. Went to check and it is still the in the zip however. Did I miss something obvious?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Sounds like you broke the ZIP. Don't modify it on your phone. copy the ZIP to your PC (don't open it from internal storage). Well, since it's broken now, download it again. When it's done downloading, open the ZIP on your PC, remove only the updater-script file, and once you have only the update-binary, re-add the updater-script.
I made a copy before I modded it. I'll try your approach and give it another go. Thanks!
Sent from my Pixel using Tapatalk
Still getting bluetooth shutting off randomly.
I flashed this using no wipe, as in instructions...on Dirty Santa AT&T rooted phone. Bluetooth STILL is completely annoying and disconnects whenever it feels like it. Even Bluetooth Auto Connect and Bluetooth Keep Alive are of no use as fixes. Any ideas??? Should I wipe and just flash your rom to clear up any bugs??
[EDIT] I JUST WIPED AND FLASHED...WILL POST RESULTS!!!!!
Thanks for your awesome work and thank you for your time!!!!
Updated and revised, 11-29-20
In this post I am presenting a way to slightly extend the practical range of the 8 gb Nook Tablet by using microG for Google Services Framework spoofing rather than the resource-hogging GApps. Although I have tested these ROMs thoroughly on the BNTV250a, they would all likely run just fine with GApps on the 16 gb model (I currently run AOSP 7.0 with microG on my 16 gb tablet), while only CM 11 runs acceptably on the 8 gb model with GApps. Let's get that simple setup out of the way first.
I selected the unofficial CM 11 ROM with the final security patches by Chris Hoffmann [https://www.mediafire.com/?gq1y21uz11lr1c0]. It is serviceable for me. The main drawback is the old WebView (which cannot be updated) resulting in the inability of browsers to display many sites properly, including the current default skin for XDA. Despite this, I've come to feel that it's perhaps the best option, with or without GApps. Installing this ROM is easy. Flash with the recovery listed in post #2, reboot, then flash a pico GApps package from Open GApps. To run the ROM without GApps, read on.
I made a quick tour of CM 12.1, CM 13, AOSP 6.0 and AOSP 7.0, and Lineage 14.1. In the following post I'll lay out some pros, cons and hints based on my experiences. I flashed each ROM several times, trying different things, building the system from scratch each time rather than restoring apps from backup. That gave me a chance to work with each OS and see how it would perform not only during setup, but also during a shakedown/tweaking phase. What I can say about all of these ROMs is that GApps effectively kills each and every one on the BNTV250a.
Life without GApps
I, of course, tried side-loading apps without GApps. Easy, right? I thought so until I came to a few that whined about requiring Google Play Services to run. Even mundane things like the NPR News app, my local newspaper and MX Player are "GSF dependent" (Google Services Framework). Then I tried another app that would not install at all. Turns out it did a license verification check (it's free!) and saw no Google anything, so forget it. This was sort of news to me I suppose because even my lowly NST had GApps installed once upon a time, so I never encountered this issue before. You can hunt around for apps elsewhere but if you pick up an app that happens to be featured in the PlayStore, you may be out of luck no matter where you got it from. Or maybe not.
There is a project called microG by XDA member @MaR-V-iN. It consists of a lightweight set of apps (two at minimum, a third if you want location services) which provide the needed authentication to Google servers and/or inquisitive apps. There is a catch: the ROM must support "signature spoofing".
These ROMs do not have that option. You can Google "signature spoofing" to read the pros and cons. This is just information. Caveat emptor, etc. There is an Xposed module called FakeGapps which enables signature spoofing. I tried this on a few ROMs and found it worked fine. At the time I started this there was no official Xposed update for Android 7.0 and as that was one of my targets, I started looking for something else [note: Xposed has since been updated to include Android 7.0 and beyond]. That led me to Tingle by XDA member @ale5000. This is a Python/ADB based method of automatically patching framework.jar to enable signature spoofing. This seemed to me a more direct and elegant approach. Although I was intimidated by it at first, I eventually just dove in. The only thing I didn't already have was Python and that was easy enough to install. The process is basically automatic once it gets going. Unfortunately it does not work for ROMs that are odexed or deodexed. The AOSP 7.0 ROM turned out to fall in that category. Xposed must be used there.
OK, what can all this do for you? It can get you a spoof of Google Services Framework without GApps. Period. There are a few simple additions to allow for location services. It used to be that you could also enable Calendar and Contacts syncing. No more. As for PlayStore access, this is possible running microG with CM 11, but not beyond. It's just too resource intensive. For ROMs beyond CM 11 I found the Aurora Store (F-Droid) to work OK, although not always in the same way. On some ROMs you can use the anonymous Aurora Store login, on others you need to supply a Google account (email). Trial and error.
The General Process
If you have never "flashed" anything before that you can talk about at work, then you need some basic instructions for creating an SD card that will allow you to try out these procedures. The excellent instructions by @digixmax here will get you started with the SD card. You need to follow steps 1-2 to prepare the card, although the version of TWRP you use will depend on the ROM you want to try out (see second post for links). Also, the ROM itself will vary (see second post for links) and you will not want GApps (unless you are just installing CM 11 with GApps). The remainder of the steps (3-10, skipping 9) also describe the general process of flashing a ROM (or other "flashable" files like Xposed, etc.) using the SD card.
1. Flash the ROM using an appropriate recovery (I have listed the ones I used in the following post)
2. First boot, enable root, USB debugging and ADB
EITHER
3. Connect tablet to PC via USB and access via ADB ("adb devices"--some of these ROMs require that you approve PC access to the tablet via ADB, so check the tablet screen to approve that option if needed)
4. Open a command window on the PC and navigate to your Python installation directory. Because I was not sure what I was doing I just dumped the entire contents of Tingle into the Python directory. That simplified path issues for me. Type "python main.py" and select option 1. Wait for the "all done", hit CTRL-c and kill ADB server. Disconnect tablet from USB and reboot.
OR
3. Flash appropriate Xposed for the OS; reboot
4. Install Xposed installer app and FakeGApps.apk; use Xposed installer app to enable FakeGapps (signature spoofing); reboot
5. Install root file manager of choice if desired (the CM stock file managers are totally capable of the following operations if given root access; the stock file explorers of the AOSP and Lineage ROMs may allow the same, although I have had mixed results. You can always install a root file manager via ADB before continuing if all else fails) A copy of ES File Explorer is attached below.
for CM 11 without GApps but with the PlayStore:
6. Move Phonesky.apk--i.e. the PlayStore-- (old, lightweight version from a KitKat ROM: http://www.mediafire.com/file/1c2f0n3k3cwsln7/Phonesky.apk/file) into /system/priv-app; set apk file permissions to rwx-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given; set to enable Google device registration; add an account. This process can be slow. Be patient. If you end up at a black screen, reboot and try again or see if the account is already established.
10. Open the PlayStore. Do some searching. You want to give it time to auto-update (this process may be completely silent). Exit. Check Settings>Apps>Downloaded to see if PlayStore has shown up there. If it has, then it may be updated. You can check yourself to see if the version number is higher. If there is no update, access the PlayStore again and check again. Once you have an update, you're good to go.
OR, for ROMs beyond CM 11:
6. Use root file manager to create the folder "Phonesky" in /system/priv-app. Set folder permissions to rwx-rx-rx. Use root file manager to move "FakeStore" apk into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given.
It's a lot, but if I could do it many times over you could do it once
In the end you'll have a tablet spoofing Google Services Framework so most apps will run without whining, but without the crushing weight of the PlayStore or the full GApps.
Contacts and Location
Life without GApps doesn't mean you have to give up these services. Just keep in mind that running background services can compromise a system that is already on the edge.
I tested the instructions that follow on a BNTV250a, using the stock Contacts and Calendar apps.
1. Contacts
There are some places in "on-line land" that describe a method for enabling contacts sync. I have not found the various methods to work any longer. It is possible to sync Contacts using DavDroid. There is only one version that will run on CM 11 and the same app will run on the other ROMs as well (attached below). However, you are adding more overhead to a device that is already pushing the limits. In the end I opted to export my contacts in vcard format and read them in as a local file. The more socially active may find this unacceptable, but it works for me.
2. Location
To enable location you will need to install an app which coordinates WiFi triangulation (something usually handled by GApps). There are two possibilities. You can get a Unified NLP apk from the microG download page. After installing the app you can check your microG settings to see if everything is OK. Then you can check Settings>Location and set it up the way you want.
If you want to use Maps you will also need to flash a maps.zip file from microG. This contains a couple of library files for Maps. As far as the Maps app itself, I have never had good performance from any version of Google Maps on my devices--until now. That's because I went fishing for an older, less bloated version that would run on the BNTV250a. It works beautifully on all my devices from KitKat to Nougat and allows pre-cache of map areas which don't expire. I've attached a copy of the apk file below.
Email
The stock Email client works great (at least for GMail accounts) and looks a lot like GMail (no surprise there). If you have your heart set on GMail, version 4.5.2--from GApps for Jellybean--seems to run just fine with a footprint of about 11 MB. I've attached a copy below.
The ROMs
Updated and revised 2-5-23
Generally I disabled any stock stuff I could that I would not use. Anything past CM 11 has a maddening issue I call "peek-a-boo keyboard", most noticeable when using the browsers. The keyboard drops out while you are typing or simply refuses to open without a struggle. You can solve this problem in CM 12 and minimize it in CM 13 by installing Simple Keyboard.
CM 11 is beginning to show expired certificates and SSL issues. You can try replacing or adding new certificates, but it's not easy and you're left with warning artifacts in the status bar. Ditto with CM 12 and CM 13, but they are not nearly as bad--for now. The stock browsers, fortunately, allow you to "ignore" security warnings which makes browsing more pleasant. You may not feel that's a great idea, but the reality is that browsing is the Achilles Heel for all these ROMS, and it's worse the higher you go. The stock browsers may give the best overall performance, whatever their shortcomings.
Because of the SSL issues, I don't recommend CM 11 any longer unless you are not going to do much in the way of internet stuff.
Note: I have noticed that both my Nook Tablets (8 and 16 GB) run better if they've been on for a bit. If yours is cranky when it gets up in the morning, pouring coffee on it won't help, but a little siesta after boot may be just the thing
CM 11 (but with issues as described above)
https://www.mediafire.com/?gq1y21uz11lr1c0
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
This is arguably the best choice for the BNTV250a if you want something other than the stock B&N ROM. It runs smoothly enough that you could even keep the PlayStore app on it and it would still behave reasonably. It's even better without it. The only drawback with this ROM is that Android Webview cannot be updated. This means that some websites will not display properly or may simply crash, regardless of what browser you choose to use. I found the antique stock browser to be surprisingly good, but Via also works well. Also, the SSL is in need of updating, so you will run into issues with some websites and apps like OverDrive.
The lesson that this ROM taught me is that these tablets are for casual use. You can't just load them up with apps and expect them to run well. Think about what you really would like to use the tablet for. Consider older versions of apps that will probably still have more features than you will ever want but are less taxing to the system. You can see from the attached screenshot how I eventually pared my choices down. I should probably pare it down even more. Most of the apps are older versions and I've kept the total count low, certainly less than on my 16 GB tablet and other devices. You don't want to exceed about half of the internal storage capacity.
CM 12.1 (potential WiFi issue as described below)
http://www.mediafire.com/file/7zxc2e...K6-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Edit 9-30-22: I recently booted this up to find that it would no longer connect to my fairly new ATT router. Puzzled, I took the tablet to my local library and had no difficulty connecting there (open network, though). Next I started restoring backups of each of the other ROMs in this list and each one had no trouble with WiFi at home. I installed a fresh copy of the CM 12.1 ROM. It also refused to connect to the router. I scrounged around the web and found two more versions of CM 12.1. Neither would connect to my router. So...I'm not sure if there is some additional security ATT has built into their WPA2 authentication or what, but I mention this just to alert you that this might be a problem. I was even able to connect to a mobile hotspot generated by my Windows 10 machine (password needed). Why this new(?) problem for the 12.1 ROM only, I have no idea.
Before you start installing apps the behavior is sprightly, even on the BNTV250a. As the internal space decreases and RAM use increases, it becomes a little less so. Even so, when running well I think it comes close to CM 11 (with GApps), albeit with more lag.
The stock browser seems like the best bet (I tried many), though it can be slow.
For me this ROM has two major issues. When it is unhappy, it will simply shut down the tablet, literally turning it off. This used to sometimes happen when I ran it on my 16 GB model, so it's not the fault of the BNTV250a. The other issue is problems for apps writing to the external SD card. For a tablet with precious little internal space, you just don't want apps downloading into internal space or storing lots of data there. There is an edit to the file /system/etc/permissions/platform.xml which corrects this issue for some apps. Find the section of platform.xml below and add the last line:
Code:
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
This change enabled OverDrive and Kodi, for example, to download files to the external SD card. It might work for others.
Not as fluid as CM 11, but WebView issues are gone and you can access most up-to-date content (if slowly).
CM 13
https://archive.org/download/cmarchive_snapshots/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Never having tried this ROM on my 16 GB tablet, I was actually pleasantly surprised by its behavior on the BNTV250a. There's a funny WiFi thing where if you leave WiFi on when you shut down and then boot up again, it will not automatically connect (unless the lockscreen has come on, which is pretty fast after booting, so no biggie). Otherwise it's pretty much like CM 12 although maybe a little more stable--if you don't overdo it. The Sound Recorder app is somehow broken on the CM 13 ROM. If this is something you'd like, you can replace the broken version in /system/app/SoundRecorder with the one attached below. Make sure the permissions are rw-r-r and reboot.
Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I did this using the editor from the CM File Manager. There are probably easier ways. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
This change will be overwritten if the app updates, so you might want to keep that in mind.
This is the ROM I've settled on for my BNTV250a (screenshot of home screen below)
AOSP 6.01 "Marshmallow"
Box
notredame.app.box.com
(you want aosp_acclaim-ota-MOB30Z.160820.zip)
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is one of the ROMs built by @amaces. The AOSP builds are very lean compared to CM ROMs so I was hoping this might perform somewhat better than CM 13. But I don't think it does.
The first big hurdle is enabling root. My thanks to @digixmax for pointing out the right tool. After first boot (or maybe even before, but I did it after) you need to flash UPDATE-SuperSU-v2.46.zip. Works perfectly.
The stock launcher is, well, funky. I replaced it with Nova Launcher but after installing a few other apps it was clear the system was under great stress. Lots of black screens and crashes. Not a good option for the BNTV250a.
AOSP 7.0
https://www.mediafire.com/?5vcw8l603d3r5sc
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Xposed
This is another ROM by @amaces and what I run on my 16 GB tablet. On that device it is virtually flawless. I really wanted to say the same for the BNTV250a, but I can't.
Enabling root for the ROM is achieved with Magisk.
The ROM appears to be odexed to Tingle and so you must flash the correct Xposed (for 7.0 and Magisk) and install the installer app along with the FakeGapps app as described in the previous post.
The stock launcher is pitiful and you need to install a root file manager to get anything done. The system is laggy and video is not smooth. Not even a potential option for the BNTV250a.
Lineage 14.1
Box
notredame.app.box.com
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Edit 2-5-23: Well...no, it does not have the classic shut-down bug (tablet reboots right after it "shuts down"). Instead, it often shuts down just fine, but occasionally locks up during shut down and has to be forced off with the power button.
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is a third ROM built by @amaces (his most recent for the NT). I didn't have much hope for this because if 7.0 was an issue, I didn't expect 7.1 to perform well.
The only native root capability is for ADB. To enable full root, you need to flash addonsu-14.1-arm.zip (attached below). I did that after first boot but perhaps it can be done along with the ROM.
Not surprisingly the ROM has the feel of CM. There appears to be a file manager but it is only a partial reflection of the native file explorer and is useless for the manipulations that need to be done, so you need to adb install a root file manager as described in the previous post.
The stock browser is complete rubbish. It looks to be Gello(?) but it is the most infuriating collection of electrons I have ever encountered. There are no navigational buttons, no bookmark button--no buttons at all! I really tried. I used gestures (some rude), I tried magic words (many of which do not appear in children's books). Nada. When I finally managed to reach my test site it was like wading through, well, Jello! So....attached below is the nice lightweight stock browser from AOSP 7.0. Navigate to /system/app/Browser and there you will find Browser2.apk. Rename it to something else and copy in the Browser2.apk attached below, setting file permissions to rwx-r-r. Reboot. If you are successful, you can delete the old, useless browser apk. To enable bookmarks, navigate to /system/app/BookmarkProvider and inside you will find the apk file. Tap to install. I don't know why this needs to be done, but it does even on AOSP 7.0. Reboot and you've got a functioning browser (rife with "peek-a-boo keyboard")
The ROM hates Kodi, crashing constantly. Video from other apps is not smooth. Not a viable choice for the BNTV250a.
For a lark I tried it on the 16 GB model and it's actually not bad, but then I saw that embedded browser videos (like YouTube, for example) were funky colors, so... It may be that later versions corrected this, but those likely have the shut-down bug. In any event, a terrible choice for the 8 GB model.
Took a bit of trial and error to get the perfect version of playstore to not give an error, but I got it working. Thank you a lot for this write-up!
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
denmalley said:
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
Click to expand...
Click to collapse
While you're becoming familiar again with the procedures, give me a day or two to update the post. I recently redid my BNTV250a with CM 13 to try some things and then finally went back to CM 11 using the MicroG components rather than GApps. I'm really happy with it, but I have to say that the tablet (just like my BNTV250 with AOSP 7) behaves better if it's been on for awhile. It can be really cranky if you try to start using it right after boot.
So I'll update the post title to include CM 11 and add some details about CM 11 to the second post in a few days.
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
denmalley said:
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
Click to expand...
Click to collapse
I don't remember seeing the "adb" after "> 1", but I may just not remember. So, just in case and to be really clear (in case I wasn't before):
1. I assume you have adb working on your PC or you wouldn't have gotten to the Python step. Did you ever set the PATH for adb? I confess I never bothered until I tried this procedure. But you have to be able to access adb from the Python folder for this to work. If you're not sure, just cd to the Python folder and try starting adb. If it doesn't work then the PATH needs to be set. Here's a good description for Windows (scroll down to "Step 2"): https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. When I said I dumped the contents of Tingle into the Python folder, I meant that literally. There is no "Tingle" folder in my Python folder,but there are a bunch of extra files that are "Tingle". Just want to be sure.
Those are my only ideas at present. I hope one of them does the trick!
Ah yes path variable did the trick! On to the next steps, I'll keep you posted!
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
denmalley said:
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
Click to expand...
Click to collapse
Did you
1. Check microG settings to be sure everything is OK?
2. Sign in to your Google account from the microG settings (add account)?
3. Then try the PlayStore (check permissions on Phonesky folder and app)
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
denmalley said:
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
Click to expand...
Click to collapse
Yes, the PlayStore icon should appear--admittedly a very old and funky one with this old version.
The Playstore automatically updates. I wish it did not, but there is no way to stop it. But to have that happen you have to access the Playstore at least once, maybe even download an app, and leave wifi on awhile.
On my main microG settings screen I show Google device registration ON. On the self-check screen, everything is checked except the last box. I have the location stuff installed.
So if PlayStore is unchecked, something is not right. Perhaps the app got corrupted when I uploaded it. I am shut down right now but can reup tomorrow. Or you can just get another app from Apkpure or similar. I used to use something around 8.02 to get started.
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
denmalley said:
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
Click to expand...
Click to collapse
Phonesky=PlayStore, just renamed--microG expects to see Phonesky
Something is not right with the app. I have to run, but here is a link to v. 8.02 which I have used in the past:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-8-0-23-release/
Rename to Phonesky before using. It will be a little more cranky but it will work to get you going. I hope.
Edit: or, if you prefer, go to OpenGapps and download a KitKat pico GApps. Extract from that zip the Phonesky app and use it.
Edit, Edit: yeah, I tried reupping a copy of the Phonesky app but when I downloaded it the file size did not match. So I changed the first post and inserted a link to a copy on my mediafire account. That downloads with the right file size.
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
edit
The only other thing I haven't yet tried is redownloading everything and maybe even using a different PC. Ah heck who am I kidding, like I've got anything better to do. I'll keep cracking at it.
denmalley said:
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
Click to expand...
Click to collapse
I'm really baffled by this behavior. When you add a Google account via microG nothing changes on the microG settings page, but the account should show up in the CM11 settings under "accounts".
When you prepare the system for flashing, do you do an Advanced Wipe? I'm a little AR about this sort of thing, especially as my devices have been flashed with different OS's many times. I start with an Advanced Wipe, clearing out everything except, of course, the microSD card, and then I follow that by a regular wipe. Then I start flashing.
If you are still having trouble, let me know and I'll wipe my current system (I have a backup) and start again from scratch, downloading copies of the files I have posted to see if I can duplicate what is happening to you. Maybe Google has changed something in the time since I did my newest configuration and the microG folks have not caught up with it yet. This appears to be true for Contacts because I cannot get them to sync up or even see my Google contacts. This was not the case in the past. There is chatter about it on the microG site, but none of the "solutions" go anything beyond what I have already related and some of the conclusions are like "and it just started working..."
I did not do the advanced wipe, so let me try that. I'm also going to redownload everything and give it another go. No need to wipe your device just yet - you've already done WAY more than I expected to help! I will do this over the next few days and keep you posted.
Well I tried six different ways, full wipe, change the "group" set for the group permissions to "root" (it had been set to sdcard), redownloaded every last bit of software used in this process, used a different computer, etc etc etc. Nothing is working. Still no play store. Everything else seems to be fine except that.
So anyway, I finally just did a full wipe, flashed the CM11 unofficial that you provided in second post, and grabbed a kk gapps package and flashed that. Switched from trebuchet to nova and I've got a tablet I can live with! Working much better then the cm10 rom I had on there before (like swipe to unlock screen, wait 5 seconds....touch app drawer, wait 5-10 seconds....touch an app, wait 30 seconds....slooooooow).
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
denmalley said:
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
Click to expand...
Click to collapse
I'm glad you reached a point where you feel good about the outcome but sorry that you had to waste so much time.
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
nmyshkin said:
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
Click to expand...
Click to collapse
Well.....I'm not sure how the error crept in, but it looks like the creation of the Phonesky folder was the issue. This is needed for ROMs beyond CM11, but there are no folders in /system/app or /system/priv-app for CM11. Thus for CM11 only, the files like Phonesky.apk are simply dropped into /system/priv-app and the permissions set as described, Then everything works as it should.
I've corrected the instructions. My apologies.