System: Android 2.3.3 (Gingerbread) - Discontinued May 2, 2014
About:
This is a fork of the DSC ROM, which is based on the Olleh KT 407 ROM. Its genesis came about as a result of a request by lordofazeroth (here) asking to delete all unnecessary apps from /system/app in the next release. My answer was matter of fact: to do it himself rather than asking _n0p_ to do it. This was because I had already created a private version of DSC for my needs and felt that if people really wanted apps out they should take them out themselves.
However, thinking back on it, lordofazeroth's request wasn't wholly out of line. While getting rid of some apps, e.g. HTML Viewer, made no sense, one thing that did make sense was removing the Google apps from /system/app. This was in keeping with Google's direction regarding the apps. Starting around the time Gingerbread was released, Google began to remove most of the Google apps from new versions of Android and making them available for download via the Play Store. Looking in an ICS Google apps package for AOSP ROMs, the only Google apps remaining in the package that could also be downloaded from the Play Store are Google Talk (now known as Hangouts) Google Search, and Voice Search. I fully expect that future Google Apps packages for AOSP ROMs would only contain the Play Store, Google Services Framework, the minor apps that aren't on the Play Store (Google Gallery, News & Weather), and support files.
While getting rid of the apps from /system/app made sense, a lot of people still associate a complete Android experience with having the apps and didn't want to lose them. Fortunately, the DSC ROM has a solution in the form of a firstboot.zip whose contents are extracted and installed while the system boots the first time. It was a simple matter to move the Google apps currently in /system/app to the firstboot.zip and have them installed when the ROM is installed. This makes the end user expecting the Google apps preinstalled happy because the apps are present. And if an end user doesn't wish a particular app to be installed, e.g. Maps, they can completely uninstall it and not be left with the original version in the ROM.
So, based on this idea, I put together my own version of the DSC ROM with this shift in design and am releasing it to the public. Since the ROM is essentially DSC with a few minor changes, it should function as well as DSC does. It's hoped that if _n0p_ releases a new version of DSC that this design change can be folded back into DSC.
Differences between DSC and the Traveller DSC fork:
DSC 2.3's updates are included in the ROM, thus no need to apply patches after installing the ROM.
The DSC 2.3 kernel was replaced with the swap-enabled version of the same kernel (as of version 2.3.4).
SuperSU replaces SimpleSU. SimpleSU's binary isn't recognized as valid by certain apps, e.g. Busybox Free.
The Traveller ICS Theme and the Stargate boot animation are now the default. wway's Gingertrue theme and Ace32's boot animation are available as a flashable theme zip.
Zeam has been replaced with HoloLauncher.
The CM7 File Manager app has been added to /system/app.
Gmail, Hangouts, Maps, Quick Search, Voice Search, and YouTube are all in dsc_firstboot.zip instead of being embedded in the /system directory.
All Google apps, including the Play Store, were updated to their latest available versions.
Google Play Services and Google Street View are new to the ROM. If after uninstalling Google Play Services the app reappears in your app drawer, then Google has pushed the app back to the device. Please do not complain on the forums about this, as it is expected behavior and not a fault of the ROM or device.
Antutu CPU Master Free, WiFi Reassociate, Superdim, System Panel, and ClockSync were all removed from the ROM. In using DSC I have never encountered a problem that required any of these apps, and I replaced Antutu with the XDA version of SetCPU. All should be available through the Play Store if desired or needed, except for the XDA version of SetCPU.
Ghost Commander was removed because the CM7 File Manager app was included in /system/app. Ghost Commander should still be available through the Play Store.
The Streak FM Radio app was replaced by the March 11th version of Spirit FM Free. The limitations of the Streak FM Radio app are well known (no volume control). The Spirit FM Free app is apparently limited to either Blended Audio or Mono sound - it's not clear which - but at least the volume can be controlled. The March 11th version of Spirit FM Free is also the last version that supports the Dell Streak.
ZRAM Status was added to monitor ZRAM usage in the ROM (as of version 2.3.5).
Bugs:
Google Maps may cause excessive battery drain. Freeze Maps or uninstall it if this issue is encountered.
Arabic and Hebrew text in Aroma may appear backwards due to lack of right to left support.
Touchscreen support in Aroma is erratic. Scrolling using the touchscreen does not function, and it may require a few taps to get selections to properly register. As an alternative, the volume controls and the camera button can be used to navigate and select items. This is likely a hardware issue and not fixable in Aroma.
Tips:
Disable notifications in SuperSU for a clean look and to speed up the boot process.
SuperSU will receive updates from the Play Store. To save storage space convert the update to a system app.
Undervolting the CPU using the DSC CPU Voltage Configuration app is highly recommended to maximize battery life.
HoloLauncher has the ability to hide apps in the app drawer. If you know you're never going to use a particular system app, e.g. the email client, hide it instead of deleting it from the ROM.
Customize dsc_firstboot.zip to meet your needs. For example, if you use Google Earth, rename the APK file to com.google.earth.apk and add it to dsc_firstboot.zip.
Google Car Home was left in /system/app because if uninstalled it cannot be downloaded from the Play Store.
The original release of the Hangouts 2.0 app (from Android 4.4) had a bug which allowed it to work on Gingerbread. If wishing to use Hangouts in place of the stock Messaging app, set the app to not be automatically updated in the Play Store or you will lose SMS capability when the app updates.
Changelog:
2.4.6:
UPDATE: Hunderteins has released another SSL Ciphers update, this time around to boost speed and security of HTTPS connections by implementing new encryption and authentication algorithms.
UPDATED APPS: Google Play Services, Hangouts and YouTube.
Older Revisions:
2.4.5:
UPDATE: OpenSSL firmware updated to fix the Heartbleed bug.
UPDATED APPS: Google Play, Google Play Services, Hangouts, Maps, SuperSU, and YouTube.
2.4.4
UPDATE: HoloLauncher updated to 2.11. Now has a color theming option similar to what is available in KitKat.
BUG FIX: Hebrew language in Aroma now displays.
BUG FIX: Grammar fixes for some screen text in Aroma.
Because 2.4.4 is being released so soon after 2.4.3, I'm leaving 2.4.3's updates visible as well as providing a patch for current users to install rather than downloading the entire ROM and installing it again.
2.4.4 Update.zip - 819.16 KB
2.4.3
NEW: PDroid for Arabic users now available.
UPDATES: SuperSU, Flash Player, YouTube, Hangouts, Google Play Services, and AFWall+. The release of Flash Player included here is the final release from Adobe. There will be no further bug fixes or updates.
UPDATE: Aroma Installer updated to 2.70RC2. This update restores touch support to the installer, which was missing in 2.51 as well as allowing the user to quit the installer at any point prior to installing Traveller DSC or its features.
BUG FIX: Fixed the issue with Arabic support not properly installing. For Arabic support to work the base ROM (and any added features) must be installed prior to installing Arabic support. This means you will have to run Aroma twice to enable Arabic support. The first time will be to install the ROM. After installing the ROM and letting everything in dsc_firstboot.zip install, reboot into the recovery and run Aroma the second time. Select the Arabic menu choice and install those options on top of Traveller DSC.
After selecting Arabic in the Language & Keyboard options in Settings, the very first time the power button is used to shut down the Streak the device will hot reboot and attempt to cycle through the boot animation. It will fail and then hot reboot a second time. This second time the device should boot to the launcher.
2.4.2
UPDATE: Play Store updated to 4.5.10.
UPDATE: Clock font changed to the version used in Android 4.4, resolving an issue with a portion of the clock being cut off when the pattern lock is used.
UPDATE: Common fonts used in both Android 2.3.3 and 4.4 were updated to the Android 4.4 versions.
2.4.1
BUG FIX: Replaced the tabbed browser with the original stock browser to resolve a force close issue with Voice Search. Clearly the tabbed browser wasn't quite ready for prime time.
2.4.0
NEW: Installation is done via the Aroma Installer. There is no touch support for the Streak, so the volume controls and the power button must be used to navigate. As a result of this change, all the various modifications available have been rolled into the zip file, meaning there will be no separate downloads needed for this version of Traveller DSC. The increase in size of the zip file also means that MediaFire cannot be used. Dev-Host will be used instead.
NEW: A new version of the zRAM app was compiled from its sources, with a black background and with memory readouts expressed in MB rather than bytes. It is now also a system app.
NEW: The stock browser is now a version of Lightning Browser compiled from source, with a custom dark theme to fit the rest of the ROM.
UPDATED APPS: AFWall+, Google Play Services, HoloLauncher, SuperSU, and YouTube.
UPDATE: Roboto Condensed is now the default font, for that Android 4.4 look.
UPDATE: Arabic patch users can now fully benefit from the SSL Cipher improvements due to a fix in framework.jar.
BUG FIX: In QuickPanel, the Auto-brightness indicator can now be clearly distinguished from the maximum brightness indicator.
BUG FIX: The "System Updates" option in Settings > About phone now links to this thread instead of the DSC thread.
BUG FIX: The "Build Version" option finally had a version bump, to 2.4.
NOTE: Gingertrue users will not have the new browser installed. While the browser is available for download here, it may not install. Gingertrue users wishing to use the tabbed browser will need to convert it to a system app using an app like Apps2ROM. The other option would be to install a copy of Lightning Browser.
NOTE: The browser may force close after exiting. The cause is unknown at this time, but may also affect Lightning Browser, since the former was compiled from the source of the latter.
2.3.10
SuperSU reverted to 1.65. See explanation here.
Fixed bugs caused by developer error when adding ciphers patch.
Default wallpaper was changed.
Changelog for versions prior to 2.3.10 was removed.
Links:
Flashing Instructions
407 ROM [Dev-Host Links Removed]
Mega
ROM Download
DSC "Flash Me Before Installing" Pack
How to add your files to the Traveller DSC ROM
While the Traveller DSC ROM does change several things in the system, notably replacing SimpleSU and Zeam with SuperSU and HoloLauncher, its biggest "selling point" if you will is the ability to customize the app package that is installed with the base ROM. The DSC ROM includes a zip file located in /system/etc named "dsc_firstboot.zip". After DSC is installed and the system rebooted, during the Google account setup and for a short period of time afterwards a script is run that installs all the apps found in dsc_firstboot.zip.
The base DSC ROM included in its dsc_firstboot.zip the following apps: Adobe Flash, AnTuTu CPU Master Free, WiFi Reassociate, DSP Manager, Ghost Commander, Maps, YouTube, Droidwall, Dell Swype, DSC Wallpapers, Superdim, SystemPanel, ClockSync, and Streak FM Radio. Many of the Google apps remained in the ROM. For Traveller DSC, as already mentioned in the first post in the thread, all the Google apps except for the Play Store and Car Home were pulled from the ROM and stored instead in dsc_firstboot.zip. This is because all of these apps had new versions in the Play Store and thus there seemed to be no reason to keep old versions in /system/app. At the same time I changed up the apps package.
Traveller DSC includes in dsc_firstboot.zip the following apps: Adobe Flash, DSP Manager, Maps, GMail, Google Play Services, Quick Search, Street View, Voice Search, YouTube, Droidwall, Spirit FM Free, Dell Swype, zRAM Status, and DSC Wallpapers.
Traveller DSC encourages customization. I want you to make this ROM your own. If you want to delete the Google apps, go ahead. If you want to do what I did and add Google Music, you can do that too. This brief tutorial explains how. But keep in mind the following: dsc_firstboot.zip cannot be larger than the remaining space in the /system partition. If the file is too large the Streak may freeze at the Dell logo or end up in a boot loop. If this happens, remove apps until the file is smaller than the remaining space in the /system partition, then install the ROM again.
Tools required - PC: WinZip, WinRAR (preferred) or 7-Zip. Do not use the built-in Windows zip utility as it corrupts the zip file.
Tools Required - Streak: An app backup utility such as App Backup & Restore.
Optional - PC users with Chrome: APK Downloader extension.
Extract dsc_firstboot.zip from the Traveller DSC ROM.
On the Streak back up the installed app you want to add using an app backup utility. Ideally, when backing up the app you do not want its user-friendly name, but the name Android associates with the app, e.g. com.google.android.gm.apk instead of GMail.apk. There is a means to get the Android name of the app, using the Play Store on the PC.
Connect the Streak to the PC and download the backed-up app to a directory of your choosing.
Rename the app if necessary. See below.
Open up dsc_firstboot.zip with WinZip, WinRAR, or 7-Zip. Simply drag and drop the new app into the dsc_firstboot.zip window. The file will be compressed and added to the rest.
To add the new dsc_firstboot.zip to the ROM, open up the ROM's zip file, navigate to /system/etc, then simply drag and drop the new zip file into the directory. The ROM's zip file will update itself, overwriting the old zip file with the new one.
Copy the new ROM file to the Streak and install the ROM.
If the app on the Streak carries a friendly name, open up a browser window on the PC and head to the Play Store. Search for the app in the Play Store and look at the URL. The Android name of the app is found within the URL. For example, if wanting to embed Kongregate Arcade into dsc_firstboot.zip you would find it in the Play Store. The URL would be play.google.com/store/apps/details?id=com.kongregate.android.kongarcade. The Android name is found after /details?id= in the URL, thus the Android name for Kongregate Arcade would be com.kongregate.android.kongarcade. Rename the apk file from Kongregate Archade.apk to com.kongregate.android.kongarcade.apk and then follow steps 5-7 above.
If using Chrome, use the APK Downloader extension and download a copy of the app directly from the Play Store to eliminate the need to use a backed-up version of the app on the Streak. Google recently changed things and now all files downloaded from the Play Store using APK Downloader have a filename consisting of a random number, so it's necessary to give the downloaded file the correct name. When the Windows prompt appears asking for a location to save the file in, rename the downloaded file to the name referenced in the URL, e.g. com.kongregate.android.kongarcade.apk. From there, follow steps 1, 5, 6, and 7.
NOTE: This tutorial may be revised from time to time in order to clarify details or simply to make things easier to understand.
hello, thanks for the rom. i came from cm7 based rom. if i want to try this rom, can i just flash the zip just like usually ? I read instruction link, confused about flash_me, just seems lots of step to flash a DSC rom. My baseband already 406.
Thanks.
Sent from my Dell Streak 5
Powered by INDOSAT
The provided baseband files improve the voice quality but are not essential to getting the ROM to work. As this is merely a tweaked version of DSC I put out as a proof of concept, everything you know about DSC still applies.
I'm not sure what's the difference between the pdroid version and basic.....I don't know which one to try
Sent from my Dell Streak using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1357056
PDroid is a privacy add-on.
Had a data wipe after I did a reboot. Unfortunate as it seemed nice as a "update" for DSC 2.3.
Explain please? I've never had a data loss issue in the entire time I've been running this ROM (several months before I released it).
Strephon Alkhalikoi said:
Explain please? I've never had a data loss issue in the entire time I've been running this ROM (several months before I released it).
Click to expand...
Click to collapse
Don't take it as a slight on your ROM, personally I think it's more of an issue with my device. I did fresh install over DSC 2.3 after that I had a data wipe after a random restart. With this ROM I'd rebooted after I changed default orientation to portrait in DSC config resulting in complete wiping, i.e. upon restart I was welcomed with the Welcome to Dell Streak touch here to continue screen.
I wasn't taking your comments in a negative fashion. Sorry if I gave that impression.
I don't change the default orientation so I've not noticed that. One thing I did notice is that ever since I changed the baseband in my Streak to 366 WiFi has never failed to initialize after waking up the Streak. The "beta" versions of this ROM I ran using the 406 baseband and often had to engage and disengage airplane mode to wake up the WiFi. It still doesn't stop me from having an occasional spontaneous reboot, but it's an improvement. So, I recommend using the 366 baseband, which can be installed using the DSC "Flash Me Before Installing" pack.
Thanks for sharing... I am downloading the files and will read thru all the instruction before proceeding...
I have place back the picture to show the problem.
For some reason XDA is adding <br /> to the end of the links here, which is why people were getting the request for a decryption key. I've edited my post to fix the links.
ROM updated to correct the chef's not realizing that the version of Spirit FM he added did not support the Streak any longer.
Currently testing one of _n0p_'s older versions of the kernel to see if replacing the kernel fixes the spontaneous reboot issues I and a couple other people have been getting at random times. If this does fix things, I'll provide an updated ROM. If anyone wants to try this out, you can download the u28 (DSC 2.0 release) boot.img from _n0p_'s DSC thread here.
Some updated information available here.
Any update on your test results @strephon
Sent from my Dell Streak using Tapatalk 2
ammujee said:
Any update on your test results?
Click to expand...
Click to collapse
Check the DSC thread. I reported my results there.
Just for anyone waiting for an update.. @Strephon Alkhalikoi has updated an 'all in one' fixed version 2.3.3 in the OP.
Thanks. :highfive:
I'm having problems downloading from the MEGA links on the first page... does anyone have any mirrors set up?
I had no trouble. Possibly an Internet issue?
OK, I successfully grabbed the rom and the "Gingertrue Theme and Phoenix Boot Animation"
...however when attempting to install the theme zip I got a failure. (Status 6)
Related
Special thanks to the creator of the item inexus from which inspired me to give a graphic touch to the rom.
This rom (not a mod) has been developed entirely from the source of Google and very little of Cyanogen framework.
Thanks to Cyanogen and all his staff for the contributions received.
Is installed from the recovery, as always, do not worry if it takes a while to leave the first splash is entirely normal and configuration files running on first boot.
I strongly recommend formatting SDCARD total with three partitions, SDCARD 7.4 GB / EXT3 512MB / LinuxSwap 64MB, you can do from the recovery, but remember to keep you before your pictures and music. This is because directories are created in the sdcard called Android which are recorded in the data I have found to negatively affect the rom. PROVEN!,
This is only necessary in case you want to have Apps2sd or Linux Swap, if not going to do any of those things is not necessary to format the Sdcard with three partitions.
WARNING!
Only if you come from different roms (Donut, Eclair, Froyo) is necessary to WIPE, when coding in Gingerbread from this rom will not need to wipe again to install later roms.
This rom installs itself alone, that is completely reconfigures.
Before installing the rom Wipe recommend because it has many changes. When installed and out of recovery by restarting leave untouched while the LED flashes. At this point I recommend you salteis the account settings to skip giving google and once in the launcher and set podreis rom to your liking. This is because otherwise the phone will Autoconnect the market and begin to automatically download all the applications you had installed and it saturates the terminal because it does hit, besides putting the background image that you had prior to the rom and then you ask me that as it is possible that if I install the rom to wipe the bottom appears to me that I had before. In this way you will do a clean install. Then you enter the market and instalais a free application to refresh anyone that you have installed in the terminal.
Very attentive to you to do restorations of any kind against the rom or program that you can have problems. (I mean backups, including their own SupSetup least in the section on applications), special attention to restore configuration data of any kind. Under the best not to doubt.
SupSetup new V16 in all roms, not serve any previous SupSetup for this rom
The new integrated SupSetup activation brings on-demand applications in the applications section extras, you can enable applications that interest you as the Roma comes in "Lite" (without extra applications installed) so that everyone can choose the best configuration.
It is important before you set up Google account to be activated from applications before SupSetup so that when you connect to the servers to configure your Google account, they enter the downloads section.
After entering the market and to display applications install any application downloads for cool downloads.
Apps2sd
Apps2sd is to pass the phone applications both current and future to the ext3 partition, it is imperative not to activate any way to move application to the sd or change from internal to external location application. Simply activate it from the SupSetup without touching any configuration in the Spare Parts or applications from the rom settings.
Apps2sd not activate without at least once you have restarted
General
- Rom in "LITE"
- New graphical look different from SuperGinger's
- All you had the SuperGinger but since source of non-Cyano Google
Added
- Wake & Unlock
- Always visible Bluetooth Settings (tolemaC)
- Hide clock
- Percentage of battery
- It's part of Cyanogen CyanogenModsettings
- Etc ...
A rom much lighter than any other that you were able to prove, you could say that is the Nexus CSDI One (this rom Magic gave a lot to talk), completely stable and trouble-free calls or anything known, at least tests we are doing we have not yet found any fault.
Applications
- You can install more from the extra applications SupSetup
- Google Apps
- Flash Player 10.1
Download:
http://cdn.movilzona.es/repos/superatmel/ROMS/SuperAosp/[email protected]
Changelog:
SuperAosp 2.8.4
- unwonked End calls wonk
- Kernel with HAVS
- incognito mode in browser
- User agent in browser
- Fix wifi suspend
- more stable more battery life
- Very fast
- Recomended Adw Launcher EX in mode new vertical for drawer
SuperAosp 2.6
- New intent for fix black calls & sound
- Add ADWLauncher
- New kernel HAVS
SuperAosp 2.2
- Upgrade to version 2.3.3
- Fixed black calls (supposedly) I have no problems with AMOLED
Captures
Reservated
Looks good. Will be sure to give it a go now. If you want i could also make a video of the rom in action? here is the post. http://forum.xda-developers.com/showthread.php?t=966530 If you want me to i will make a video and put it up for you.
wow thanks been waiting for this.
This looks great! Can't wait to try it on my gf's N1
You are like a Dev God. Thanks.
hey guys here's a preview of this rom http://www.youtube.com/watch?v=RK_lmre2eh0
Stuart.upton666 said:
hey guys here's a preview of this rom http://www.youtube.com/watch?v=RK_lmre2eh0
Click to expand...
Click to collapse
Thanks for the video
I have been running super-ginger and it is an fantastic rom overall. I can't wait to try this new one. Hopefully, the dev will have a 2.3.3 ver once it is out in the wild. Awesome job.
What happened to theme Chooser? WILL It work with this rom?
Sent from my Nexus One using XDA App
robotnoize said:
What happened to theme Chooser? WILL It work with this rom?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Do you mean the theme chooser that's been added specifically to CM and not part of AOSP?
Oops In the version he made before this 2.6.8 he had it so I figured he would keep it. Never mind
Sent from my Nexus One using XDA App
I seem to be having issues with the A2SD. Apps such as Angry Birds won't install, and also, sometimes after rebooting, none of my apps are there.
Anybody else?
Any idea about battery life? Can i flash Wildmonk or IR kernel along with this rom?
chrisvuong said:
Any idea about battery life? Can i flash Wildmonk or IR kernel along with this rom?
Click to expand...
Click to collapse
Im pretty sure you can but it will probably not function the same since super customized the kernel for his rom
N1
is this a spanish rom? any english version? at least on that capture picture its spanish.
dnsmo said:
is this a spanish rom? any english version? at least on that capture picture its spanish.
Click to expand...
Click to collapse
It has option for English, only some supsetup is in Spanish
N1
djmasque said:
I seem to be having issues with the A2SD. Apps such as Angry Birds won't install, and also, sometimes after rebooting, none of my apps are there.
Anybody else?
Click to expand...
Click to collapse
What is problem with Apps2sd?
Installed this rom and have been using it for about an hour an I'm loving it so far! Excellent job. Seems I have found a new daily rom
Sent from my Nexus One using XDA App
superatmel said:
What is problem with Apps2sd?
Click to expand...
Click to collapse
Some apps won't install- Angry Birds, Aldiko eBook Reader. Then sometimes after a reboot, there are no apps installed at all, until I reboot again
I am looking for Google Apps for Froyo 2.2 (WildPuzzel ROM) for wildfire. can anyone send me link to download please
Thanks,
AQ
why do'n't you use a Market or google search?
eversyt said:
why do'n't you use a Market or google search?
Click to expand...
Click to collapse
I Did, currently google apps flash-able package is available for CM7 ROMs but cant find for froyo.
And another point is, i corrupted my market app.. cant download any app now
I think Google talk is also not available in the android market.
why i posted:
ROM developers may have it that's why i posted maybe someone can provide one.
otherwise i will extract apk from ROM and try to create update zip. might be useful for others too
GApps packages are only for CM Rom's (And AOSP ones), since, those ROMs by themselves do not have any Google copyrighted stuff.
Sense based ROMs do not need GApps packages because most of them include it by default. Or, even if they do not include the apps package, they include atleast the Market app,
Seeing that, as you have put, your best bet would be to extract the APK and create the Update Zip yourself.
Looks like there is more than corrupt application in my case. I have created and flashed update even individually installed apks and services over existing ROM but getting FC on launching the application. Setup Wizard doesn't seems to work anymore and getting FC in loops.
Some unknown system components or services also seems to be affected. I think I would need to go back and restore nandroid or reflash the ROM
time to flash a New ROM for primary use. and keeping nandroid backups for test purpose. as a Primary ROM I will prefer CM 7.0.3, Wildpuzzel freezes sometimes during a call. i have used cm7 before but for test purpose. So i till go for CM7 and look for solution to connect ad-hoc wifi
why not just reflash your rom and make a backup of any data you want before hand
This is my first attempt of creating any Android Rom myself, so don't expect too much.
Changes to the original OTA update which was the base for all:
Removed Superuser in favour for a fully integrated SuperSU by Chainfire.
Changed some root related settings in the kernel to allow a full root instead of factory default.
Keyboard bug fixed for all included keyboards and added a definition for those cheap wireless keyboards with touchpad you often get with the box.
This means pressing ENTER or OK really does just that instead of only producing unwanted characters.
Several versions for download (once I managed to test and upload all), all include a power menu for Kodi to shut down the box without the need for the IR remote.
General instructions:
Download the RAR archive of your choice and unpack the contents to a micro SD formatted in FAT32.
Insert SD into box and press the little button inside the AV port while you power the box up.
Once the logo appears release the button.
TWRP recovery will start and you should do a full backup of your box first!
I do recommend a full wipe after the backup to avoid conflicts after the firmware installation.
Install the ZIP and reboot once done.
Take your time as the initial boot will take quite some time, especially for the versions with more added programs.
Just the recovery image - for those who need it.
X96 stripped down...
In this version I removed all content from the OTA update that might be considered to be a concern in legal terms.
So no Kodi addons, no streaming apps, just a naked system with the standard Google apps and a modified Kodi.
The crappy file browser was replaced by the FX filebrowser.
For those with the need for more than the Media Box Launcher I added the ADW Launcher as well as the XMBC Launcher to have Kodi as the homescreen.
After the boot is finnished I strongly recommend to update the SuperSU binary.
I left this part manual as a confirmation that the first boot and setup really completed.
Only then can SuperSU update the binary in normal mode with success.
After that reboot to clear the memory and all leftovers.
Once you are done with all modifications and app installations you might need do a full backup trough TWRP again to safe you the time if something goes wrong.
Download RAR
After a lot of swearing, flashing, more swearing and flashing I finally managed to create a fully unbranded system that can be installed through TWRP.
If you still know how the original X96 looks with the original firmware you will be surprised
What has changed from the branded firmware:
Bootlogo original S905X.
Google bootanimation - that was the hardest part, allowing for a custom animation...
Media Box Launcher unbranded and with unbranded theme.
Unbranded Kodi completely removed so the rom will comply with all piracy laws and restrictions - more in the added apps section.
OTA updater removed.
All programs from the branded version removed, so no social media, Chrome, Netflix and so on.
Apart from the naked system with Google apps I included:
AdAway
ADW Launcher
XMBC Laucher for Kodi
File browser replaced by FX filemanager
Power Menu added - still requires to root the box! More under added apps.
Added apps and modifications:
Kodi was removed, but the install script for the addon packs is still valid.
The script no longer refers to the system folder but to /sdcard/apps
This means if you decide to install Kodi you can place the tar.gz archive for the addons in the apps folder of the internal SD.
Kodi itself is not included.
The additional apps I thought to be of use will be in the apps folder of the internal SD.
In FX file explorer it is called "Main Storage".
Here you will find:
Chrome
Facebook
Film On (from the branded firmware)
Lucky Patcher
Mobdro (from the branded firmware)
Netflix (from the branded firmware)
Showbox (from the branded firmware)
Skype
SuperSU by Chainfire
Twitter
VLC for Android
Three different Youtube apps to choose from, including a TV version.
How to install SuperSU:
All modifications to the boot image, scripts, libraries and so on are done and included.
This means the system is rooted except for the actual Superuser app.
Install from the apps folder and let the binary update, once done reboot and enjoy.
Ads...
Not all ads in programs or while surfing can be disabled by AdBlock.
For example everything coming from "trusted sources" like Google will still be allowed.
This is the only reason I included Lucky Patcher as it can be of use for some apps to enjoy without ads.
Install and use at your own risk!
Installation of the ROM:
As before wipe all through TWRP then install the ZIP file from extracted RAR archive - so unpack the RAR first to your SD card.
Installation through TWRP does take a few minutes due to the hash verification.
Since all included apps are integrated into the system the first boot is a bit faster compared to the above ROM.
And the additional apps land on the internal SD for everyone to choose or delete if not wanted.
Please allow about 5 minutes after after the launcher selection appeared before you actually start using the apps - some things are still installing in the background!
Once you finnished the network and personal setup of accounts and such bott into TWRP and make a full backup in case you need it.
A factory reset will set you back to the point of the installation of the rom - so no SuperSU and the added apps folder might be gone too.
Known bugs:
Just noticed the WiFi is not available at first activation.
As the chipset is identified during activation you might have to select the network twice until you see WiFi available.
Watch the boot on Youtube
Download from Filefactory
Beta2 with shutdown using F12 on the Wifi Keyboard and some other fixes. - This is just with the most basic apps.
I finally found a neat way to use the WiFi remote to shut down the box the same way the power button on the IR does.
Just press F12 and you will be asked if you want to power down
Will upload the Beta2 with this fix soon.
What's left to do?
Well, now that there is an unbranded and working S905x system out there it means someone could use it to make a ROM that works on all S905X systems out there...
Just needs including WiFi and where existant BT drivers, libraries and calls....
And of course a recovery capable of working on all boxes but that should not be too hard actually
Update: 12/05/2017:
Beta 3 and a Fully Naked Rom is available now.
The Fully Naked Rom has the FX File Explorer and SuperSU included, apart from that it is a naked Android without any Google apps left - great if you want to play around with different GAPPS packages.
The Beta 3 has some minor fixes and most apps moved into the system area instead of the user space.
If you need more apps or launchers then please check the Playstore.
Both have a system partition inflated to 1536mb, which is the same size as the factory OTA update.
On the Fully Naked Rom you can only install apps through the filemanager as no store of any kind is included.
Update 17/07/2017:
A new firmware was released and finally we have a navbar and notification shade "out of the box".
Other changes include the launcher and Kodi, now you find KD Launcher and KD Player...
The OTA can be found here, just unpack to the SD and use as usual, either with the supplied original recovery or your favourite TWRP.
Only downside is we have a locked bootanimation again
A cleaned rom with the usual fixes for keyboard and root can be found here as my Beta 4.
All removed and some additional apps can be found in this archive, just unpack to your SD and install with FX.
Those with just 1GB system memory or wanting to customise all themself can try the Beta 5, which is made small enough to fit on 1GB systems.
Use the above archive to add the programs you need.
Libreelec for SD or USB install.
Unpack the archive to your PC and use Rufus to get the tar.gz image to your SD/USB stick - all existing data will be wiped.
Copy the dtb.img to the SD, overwriting the existing file.
Plug in the box and boot using a toothpick.
Once Libreelec is set up it will work with the SD/USB inserted without you boot the normal Android from the internal memory.
Videoboot
With this version you can use a MP4 video file instead of a bootanimation.
Works with sound of course and should support every MP4 video the normal video player can play.
For your own video simply replace the bootvideo.mp4 in the systems media folder.
Update 04/06/2017: Finally with Open GAPPS!
The X96 showed some real resistance to overcome the chinese limitations and to allow a working installation of updated Google Apps.
As I already spent a lot of days trying to get it to work I only focussed on Open GAPPS but no manual install or the XIAOMI Gapps installer.
With the troubles in the beginning I created a way of installing it all that worked with no errors for me - I suggest to follow it before you try other ways.
This Beta is right now considered to be in an experimental stage until users provided enough feedback to confirm it indeed works fine.
All is based on a naked and slightly modified Beta 5.
The system itself is pretty much naked except for the usual fixes, everything that could make troubles was removed, this includes:
Camera, video and music, wallpapers and so on - install what you want and need through the playstore once all is working.
Main reason for this was to avoid problems with the GAPPS package and to allow the use on 1GB systems as well.
How to install:
Unpack the RAR archive to your favourite SD card or USB stick.
Plug into the box and start with a toothpick - TWRP will show up.
Go to Wipe, Advanced Wipe and wipe Dalvik/Art cache, Data, Internal Storage and Cache.
Go back and install the X96-no-gapps archive and add the opend gapps archive into the line.
Upgrading the neural network takes a few minutes, once the AI is fully operational the GAPPS package will install.
Simply ignore the fact that some of the listed apps will not be available, like Faceunlock - this is due to the removed camera and other things but also because of our harware platform.
After that reboot.
If all goes well and the intial boot goes well you can simply follow the on screen instructions from the wizard.
In case after 10 minutes the Google animation is still going you have to try again but with a different approach (50/50 chance for the first to work).
Start over with a another wipe as above, then install only the X96-no-gapps firmware.
Reboot and do your usual setup of network and screen settings - don't start any apps or mess with SuperSu yet!
Once all is good reboot into the TWRP recovery and install the Open GAPPS package.
Reboot.
Now all should go according to plan.
Troubleshooting and additional infos:
If neither the first nor the second way of installing works for I suspect that your previous ROM was not based on mine or the OTA firmware.
In this case try one of my other beta firmwares if the included firmware itself already failed to boot.
The initial connection to Google can take 4-5 minutes instead of the advertised 2 minutes, so please allow 5 minutes before you panic.
The additional Google apps are not available at this stage and the loading will stay on the screen until you click next - simply add whatever Google app you need from the playstore.
This included Google Music and Google Play TV.
Again: no additional apps of any kind are included, I suggest to use VLC for audio and video or simply whatever you prefer.
Oh, before you ask: Navbar and notification shade are active and working.
Allow some time and check the notification shade for the updates once the system is running, I did not include all updated versions at this stage.
Download the new Beta 6 - Open Gapps version.
Update 15/11/2017:
They finally released another update, got available two days ago but file date is a bit older.
You can check on the Baidu servers yourself if you like Baidu X96 Downloads
Password there is: hp7u
Download as a RAR from Filefactory.
Once I find some time I will check if and what fixes are needed that I can do.
My new x96 arrived yesterday also I found this thread and instructables yesterday. I'm really glad that you take care of this little machine.:good:
Sent from my I9195I using XDA Labs
Guess I was just in the same boat as everyone else with these noname things.
Figured almost everything out I need, ecxept how to change the bootloader/kernel to allow for a custom bootanimation.
Main thing though was to have a working recovery to avoid weird UBS cables and manual flashing.
I wish I was 2 weeks further so I could test your build but I have to look through these things atm. Its interesting that the youtube tv app hasn't changed for a while.
Too many boxes available but I do think x96 is a solid little machine.
There's also opportunity to work with libreelec.
On my s4mini I have a dolby atmos app running modded by ahrion here on xda. Maybe it would be interesting.,wheather it runs on our little devices or not.
I am working on a fully unbranded firmware for the X96 atm.
The problem of converting USB burn images into flashable ZIP was one problem to get the "unbranded" original firmware to at least install another.
They really don't like you messing with their toys in china LOL
If I can't solve the bootanimation problem I will at least upload the otherwise unbranded version with a choice of launchers and updated apps.
Chinese toys. LOL.
Who has made the custom rom from February 16th. Rar @entertainmentbox?
No clue as I did not do it and did not check either.
But the fully unbranded firmware is on the way to upload
Finally custom bootanimations are possible
The pictures I've seen on instructables are awesome. Nice launcher.
Hope you're having fun tuning these Chinese toys.
Sent from my I9195I using XDA Labs
Congrats to your unbranded system. Hope there will be soon more users for testing and enjoying your work
Fixed the shutdown through WiFi remote problem
Is it possible to have look like the normal android tablet/phone?
Hey Downunder35m http://www.tvboxforum.com/archive/index.php?thread-671.html
Just curious is the remote working? I btw changed the keyboard layout so the annoying enter key is fix as well as added the F1 = Power function
Nevermind I fixed my issues with the remote too. Now it is 100% working.
Wasn't aware that the keyboard needs fixing as it works fine here, including powering down the box
I didn't upgrade to the Beta2
Hello!
I have the X96 box mentioned here. Exactly this 2GB model: https://www.aliexpress.com/item/Hot...32779857015.html?spm=2114.13010608.0.0.dF9x4G
The problem is... No matter what i do, i get the error 7 in TWRP. I tried beta1 and beta2, but same error.
I have tried retrying, rebooting, but no effect.
Any suggestions?
What i did was;
-backup files (to internal memory)
-wipe all (byebye backup )
-try to install image from sd-card or usb-stick (both fat32)
-installed TWRP recovery (which caused SD card not to be recognized anymore)
The recovery is specifically for the X96, I had no time to make a generic recovery for all S905X boxes, but seems it should be the next step here.
The error 7 through TWRP is caused by two things (at least during all my tests):
a) The system is totally wiped and the updater script is unable to find the correct hardware info as the build.prop is no longer present.
For this problem and during my tests it just works if you flash again without a wipe.
So right after the error 7 go back and install the firmware again without any reboot or anything else and it should flash successfully.
b) Your system uses different space allocations for the boot, bootloader and recovery partitions.
For this problem the only real cure is to first use the OTA installer for the genuine firmware to get the system working again.
Then only wipe Dalvik, cache and data - the system partition will be overwritten once the update starts but then the installer can find the build prop and if compatible will continue.
If you have a download for the original firmware I will try to incule your system stuff into the next recovery I make.
Otherwise you can always try the hard way if the system is currently toast anyway:
Open the updater script in the META-INFO folder (down in the last subdirectory) and remove the device check for the X96.
That would be the first two lines of the script- everything before th OTA check.
Downside of this approach is that your entire system will be replaced by mine and if your hardware is differernt or the partition sizes won't match then it still won't boot.
Let me know how you go and I will see that by tomorrow evening I have a universal TWRP for all S905X ready.
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.
This is derived from the latest N910F UK BTU stock Marshmallow v6.0.1 firmware.
Some info:
PDA/AP (ROM firmware) version: N910FXXU1DRI2
CSC code: N910FBTU1DRJ1 (BTU)
Modem/CP/baseband version: N910FXXS1DQA1
There is no multi-CSC support, it is too much work to add. If you need a different CSC besides BTU, then you should consider @_alexndr's DevBase, @Andycar's ROM, etc. They are based on older firmware, but should work fine. Having this ROM's BTU CSC may mean that carrier-specific features like VOLTE/wifi calling/etc may or may not work. I think the BTU CSC should work fine for most.
Why am I doing this? Well, for one, noone has posted (to my knowledge) a deodexed version of this firmware. And 2nd, as a baseline modding resource for other users, I only ask that I'm given credit for providing the files.
Old zips:
I've taken the N910FXXU1DRI2 stock firmware from SamMobile, deodexed it with SuperR's Kitchen, and created a TWRP-flashable firmware/ROM zip. It is only deodexed, no other changes have been made, nothing has been removed. All stock bloat/Knox is present. It isnt rooted, but you may root it with Magisk/SuperSU/Phh's Superuser. The kernel is pure stock, but you may flash a custom kernel afterwards if you wish. This ROM should pass SafetyNet even without Magisk/SuperSU, as long as you dont flash something like Xposed. Private Mode will not work with this zip out of the box, you will need to flash the modded Private Mode zip to get it to work. You should only use this zip if you just want a deodexed ROM with no additional changes. Flash from TWRP. This zip only includes the stock boot.img and a deodexed system.img.
There is now a 2nd version of this, it is based on the original N910FDeodex.zip, but converted from raw img format to set_metadata format. This version will only flash the used portion of the system partition into /system, resulting in less write hits. If you want a deodexed only version of this ROM with no further changes, then use the set_metadata version. These 2 zips are otherwise identical.
https://androidfilehost.com/?fid=8889791610682928982
https://androidfilehost.com/?fid=8889791610682917301
New revised zip (deodexed, debloated, Knox removed, GApps removed, some minor changes):
This is almost the same as the above zip. Everyone should use this new zip, unless they only want a zip that is deodexed only with no further changes. Private Mode will work out of the box. You will also be able to pass SafetyNet with or without Magisk/SuperSU.
https://androidfilehost.com/?fid=8889791610682924674
See the following post for what's removed:
https://forum.xda-developers.com/showpost.php?p=83379549&postcount=38
And this one too. It includes an optional debloat script that removes even more:
https://forum.xda-developers.com/showpost.php?p=83385447&postcount=44
Link to script:
https://androidfilehost.com/?fid=8889791610682925297
Install order for revised zip:
1. Wipe system/data/cache and flash ROM zip
2. Flash my revised debloat script if you want it
3. Flash latest OpenGApps ARM 6.0 nano zip (dont use anything higher, system apps like Messages/Tags/dialer will be removed if you do!)
4. Flash Google Contacts Sync Adapter zip from Extras section (to avoid "Android is optimizing" on every boot)
5. Check /system/app/WebViewGoogle, /system/priv-app/GooglePackageInstaller, and /system/priv-app/Tags, make sure they're not deleted. If they are, flash the appropriate zips from Extras section
6. Flash any other extras you want
7. Flash custom kernel (optional)
8. Flash root (optional)
9. Reboot into ROM
For MicroG users:
1. Wipe partitions, flash ROM zip.
2. Flash my revised debloat script if you want it.
3. Flash MicroG installer zip. Signature spoofing patch is already built into ROM.
4. Flash play store, backup transport, calendar sync adapter, Google dialer, maps/media effects/widevine libraries, deodexed google contacts sync adapter, google keyboard and swype libraries. These are optional.
5.Flash any other extras you want
6. Flash custom kernel (optional)
7. Flash root (optional)
8. Reboot into ROM
Note: In my tests, ROM didnt pass SafetyNet with MicroG installed. but it did pass when I flashed OpenGApps. This means the fail is due to something in MicroG. Ask in the MicroG XDA thread for help.
Another note: I only used the official APKs from MicroG website, permissions XML file from MicroG Installer Revived, and Play Store APK from APKMirror. You can update MicroG if/when they release new APKs.
Make sure to follow these steps in the order I've listed them!
You only need to use my stock boot image and kernel library modules zip if:
1. Before you flash a custom kernel
2. Before flashing root (skip my zip if you are already using custom kernel)
You can also get rid of a custom kernel/root by flashing this zip. But it is advised that you use Magisk uninstaller zip first. Or to delete SuperSU, you can use the unSU zip by @osm0sis. Then flash my zip.
If you get an error in TWRP when flashing either of these zips, this probably means your MicroSD card is using the GPT partition table, instead of MBR. My advice is to use SD Card Formatter tool to format your SD, then copy the ROM zip onto it and try to flash the zip again. If this doesnt work, post the exact error here.
If you used the "nand erase all" option in Odin, it is advised to format data/cache in TWRP *BEFORE* flashing the ROM zip. Look at the Mount button in TWRP and see if they are checked. If they are, then all is good. If not, use the wipe/format data functions until they are checked. I advise using nand erase all because it cleans data/cache of incompatible data. Especially recommended if you are coming from different firmware/custom ROM.
Please only do clean flashes! Dirty flashes not supported! Do not report bugs if you have dirty flashed! Do not report bugs if you are using other mods like Xposed (or root), etc! Clean flash with no changes, then post here if the bug is still present.
Additional firmware-related files:
My N910FXXU1DRI2 mini firmware package. This includes all files from the stock firmware package with the exception of the boot, system, and cache partitions. This is intended to be flashed before flashing my ROM zip. Boot/system arent needed because they are included in the ROM zip. Cache also isnt needed because its' contents (the UK BTU CSC code) is already processed into the system.img. This package also includes the latest official TWRP recovery, instead of the stock recovery. I would advise that you flash this file before flashing the ROM zip, but it may only be necessary if the ROM fails to boot (which means your installed firmware is an incorrect/incompatible version).
https://androidfilehost.com/?fid=8889791610682917321
You need Odin (version 3.12.7 recommended), Samsung USB drivers, and a Windows PC. In Odin, select the "nand erase all" and select the tar file in the AP slot. Also uncheck the autoreboot box. Leave everything else as-is. Once it is flashed, wait a minute or 2 before unplugging phone from PC.
Once you've done this, pull battery from phone, put it back in, then use VolUp+Home+Power to boot into TWRP. From there you can flash the ROM zip.
Pure stock firmware N910FXXU1DRI2. This is identical to what you would get from SamMobile, I have not modded the firmware in any way. I have only recompressed the tar file so that the total overall download size is smaller. Unpack the 7z file with 7-Zip/WinRAR/some other software, then flash the tar file from Odin. Flashing instructions are the same as above. You only need this if you want a truly clean start with nothing whatsoever changed. This file can be used alone without the others, or it can be flashed before the stock ROM zip. This file does not include TWRP. If you intend on flashing the stock ROM zip, I would suggest using my mini firmware package instead.
Note: I've deleted this file, you can find it in my N910FXXU1DRI2 mega firmware collection thread.
N910FXXU1DRI2 pit file. This file is to be flashed with Odin, if you need to repartition the device. Only use it with a full, official firmware package, like the one from above. I extracted it from my device with TWRP, it is not changed in any way. Most people generally wont need this. Only use this on an N910F, it may brick other devices!!! You've been warned!
https://androidfilehost.com/?fid=8889791610682917326
Link to extra files folder:
https://androidfilehost.com/?w=files&flid=316633
You can use these files to restore removed functionality if you need it. Most of these should be flashed from TWRP. More info below:
1. AccuWeather: Restores AccuWeather widget
2. Android default hosts file: Restores the stock hosts file
3. ANT system apps: Restores ANT apps. These are mainly fitness-related
4. Autorotation library: Flash this if your autorotate isnt working
5. Car Mode/Car Mode Remote: Restores Car Mode
6. Chrome customizations: Restores a system app which sets defaults for Chrome. Generally unneeded
7. DiagMonAgent: Related to Knox, it likes to phone home
8. Dropbox stub: Restores Dropbox stub for SCloud in Settings
9. Easy mode contacts widget: self-explanatory
10. Google FaceDetect library: Part of GApps. Restores FaceDetect library. Google cancelled support for this due to security reasons. You probably dont need it
11. Google Package Installer: Needed by Android! Flash this if OpenGApps zip removes /system/priv-app/GooglePackageInstaller
12. Google WebView: Needed by Android! Flash this if OpenGApps zip removes /system/app/WebViewGoogle
13. Help widget: Restores help/manual widget
14. MicroG installer: This will install GmsCore, GsfProxy, DroidGuard, and a permissions XML file. OpenGApps users dont need this
15. Stock firmware media files: Placed in internal storage by stock recovery. probably not needed. Extract zip and copy to /sdcard/ or /storage/emulated/0
16. Official play store: Installs PS for MicroG users. OpenGApps users dont need this
17. Original Private Mode APK: Restores original Private Mode APK. PM will not work if you flash this. probably not needed
18. Patched Private Mode APK: Installs patched Private Mode APK. PM should work fine now
19. S-Voice: Restores Samsung S-Voice app (who uses this crap?)
20. Collection of updated apps from the Note 4. Extract zip and install the APKs you want.
21. Samsung Apps widget: widget for Galaxy Apps store
22. Samsung Email/Exchange: Restores Samsung email/Exchange apps
23. Samsung_Galaxy_Store_-_Samsung_Cloud_-_Samsung_Account: Restores system apps for Samsung Account, Samsung Cloud, and Galaxy Apps store
24. Samsung game optimizer: restores game optimizer
25. Samsung Gear/Watch: Restores Gear/Watch system apps
26. Samsung Health Service: Restores Health Service, which SHealth depends on
27. Samsung internet browser: Restores stock browser
28. Samsung Kies: Restores Kies stub, which is needed for interfacing with the Kies PC software
29. Samsung QuickConnect/SFinder: restores files needed to make these work. They will also reappear in the pulldown statusbar again
30. Scrapbook: restores Scrapbook app
31. SmartManager v3: restores Smart Manager
32. Stock task manager and widget: restores task manager and Active Applications widget
33. Stock boot image and kernel library modules: restores stock boot.img and the kernel library modules it depends on.
34. Calculator: restores stock calculator
35. Stock clock apps: restores all stock clock apps
36. Stock fonts: restore stock fonts system apps
37. Stock music: restores Samsung Music app
38. stock_others.xml: This is is default others.xml with no added icons in the statusbar quick pulldown menu. Rename to others.xml (all lowercase), copy file to /system/csc/, set permissions to 0644. It is preferred that you do this from TWRP. root file manager will work too, but the owner and UID values must be 0 (root). You must factory reset before the icons will go back to default settings
39. SPlanner Calendar app and widget: Restores stock calendar and widget
40. Stock Tags (NFC) system app: Flash this if the OpenGApps zip removes /system/priv-app/Tags
41. Voice recorder: Restores stock voice recorder app
42. Stock wallpapers: Restores NoiseField and PhaseBeam wallpapers
43. System daydreams apps: Restores stock daydreams apps
44. Tap and pay widget: restores widget that lets you choose payment method
45. Google backup transport: needed by MicroG users, if they want contacts/calendar sync to work. OpenGApps users dont need this
46. Google calendar sync adapter: For MicroG users. Must also flash Google Backup Transport zip. OpenGApps users dont need this
47. Google Dialer: Installs GDialer and other files it needs to work. This is for MicroG users. OpenGApps users can just install GDialer from Play Store instead
48. Google Maps/media effects/widevine libraries: For MicroG users. Some apps wont work without these. OpenGApps users dont need this.
49. Original deodexed Google Contacts Sync Adapter: For MicroG users and OpenGApps users. MicroG users must also flash Google Backup Transport zip. This APK prevents the "Android is optimizing" message on every boot.
50. Google keyboard and Swype libraries: For MicroG users. Installs GBoard, and Swype libraries that other keyboards can use. OpenGApps users dont need this, they can just install GBoard from Play Store.
51. RBoard Theme Manager: This is an app that lets you install optional themes for Gboard. Gboard has a few default themes you can pick, this app lets you install dozens more. Along with sound effects. This app needs root. You dont need to install the RBoard magisk module separately
52. Patched build.prop for RBoard Themes Manager: This zip includes an edited build.prop so that RBoard can work. And empty /system/etc/gboard_theme folder. Rboard installs themes into this folder. Flash this before installing RBoard APK
Other mods I've done:
1. Remove Smart Manager v3. Now you will see "Power Saving" instead of "Battery" in settings
2. Adblocking hosts file integrated
3. Modded Private Mode APK by @TEKHD (now it turns on). However, PM may still break with certain custom kernels, or if you install other mods/changes I havent mentioned
4. Added 27 toggles in the statusbar (pull down to see them). Restore my default others.xml if you dont want them
5. Changed ro.securestorage.support from true to false in build.prop. Apparently Private Mode and SHealth work better when this value is false
Other notes:
Custom kernels: I would recommend FlashPoint kernel, v3 or v4 is fine. I dont recommend Ram Kernel. It is stable, but it has a bug where mobile data will stop working after awhile. It just cuts out, only a reboot will fix it...really annoying. This especially tends to happen when doing big downloads. Other kernels may work too, but i havent tried them. if you install a custom kernel, i'm not responsible if things break, like Private Mode/SafetyNet!
SafetyNet: My revised ROM zip will pass SafetyNet without root. This means you can use Pokemon Go, Netflix, banking apps, etc. There are SN checker apps out there, install one and run the test, should pass. It should also pass even with Magisk installed (it does for me). I didnt test with SuperSU, but if you install it in systemless mode, it might pass SN...no gaurantees. However, if you install Xposed, SN will definitely break. Other mods may or may not break it. I'm not responsible!
2 new additions (modded FlashPoint kernels):
With @kevintm78's permission, I am posting modded zips of FlashPoint v3.1 and FlashPoint v4 beta. They are based on the following zips:
https://androidfilehost.com/?fid=745849072291697438
https://androidfilehost.com/?fid=890129502657582253
See the FlashPoint XDA thread for details on these kernels.
I did this for the following reasons:
1. The original zips have init.d related scripts in the boot.img that remount system partition to read/write on every boot. This is fine...but it prevents most Magisk modules from working (they cant bind mount into the system partition because of the remount).
The original zips also appear to flash BusyBox into the system partition. In addition to this, there is init.d stuff in the boot images. These 2 things can potentially cause SafetyNet to fail.
I have made the following changes:
1. Removed BusyBox installer zips (install it manually if needed, or use Magisk's systemless BusyBox module)
2. Removed Magisk installer zips (because they are very old)
3. Removed init.d functionality from the boot images (this involved deleting 2 scripts, and deleting a line from init.rc)
4. Removed some unnecessary ui_print and set_progress lines from the updater-script files
If you need init.d support in the kernel, then use @osm0sis's Kernel init.d Support Injector zip
http://forum.xda-developers.com/attachment.php?attachmentid=3761907&d=1464187934
Flashing order:
1. Flash either of my custom Flashpoint zips
2. Flash Kernel init.d Support Injector zip
3. Flash root
You can also use Magisk for script execution support on boot instead. SuperSU also has su.d scripts support which works like init.d. I still prefer init.d in the kernel (I'm old school), but others may not.
Kernel Adiutor app is the recommended way of configuring these kernels. Both of the modded zips have the extended battery patches built in, so if you have an extended battery (like me), then the kernels will support it fully. If you just have a stock battery, no worries. i've tried both batteries with these kernels, found no difference in battery life or % displaying correctly.
I cant gaurantee that SafetyNet will pass with my modded zips, I had Xposed installed when I tested them. But i think it should. If you're using Magisk on top of these modded kernels, try turning on Magisk Hide, then run a SN test.
Besides the changes I've listed, nothing else is changed, everything should work pretty much the same as the original FP zips. Report kernel issues in the FP XDA thread if you run into problems, but mention that you're using my zips.
At @kevintm78's request, here are links to the source code for these kernels:
https://github.com/kevintm78/Flashpoint-F_3
https://github.com/kevintm78/Flashpoint-v4
Awesome work!!! @AnonVendetta Nice to see development for the Note 4 in 2020. Much appreciated and I thank you.
this is really great news!
thanks a lot for your efforts, I do love my N4, it can't be simply replaced because of removable battery and s-pen...
I would like to make shure not to run into trouble and kindly ask for a short confirmation if I understand all the info in your first post correctly:
my phone info current status:
android 5.1.1 - N910FXXS1COK1 - TWRP 3.4 - rooted
my target is a rooted Android 6 stock ROM
action:
1. I directly flash your deodexed TWRP-flashable ROM with TWRP.
2. I check if the phone boots correctly.
The result is: I now have a unrooted StockFW still with my TWRP in place.
2. I flash Stock N910FXXU1DRI2 boot.img with Odin in order to be able to successfully flash Magisk via TWRP. (isn't it possible to flash the boot.img also with TWRP?)
3. I now flash latest Magisk.
thanks and best wishes,
Su
@suse_: it's been a long time since I ran KitKat/Lollipop on the Note 4. For your situation, I believe the following steps will work. Since you are coming from much older firmware, flashing the ROM zip alone will almost certainly not boot, because of your older bootloader:
1. Flash my mini firmware package. This will upgrade the bootloader, modem, etc to what is compatible with the ROM. My mini firmware will overwrite your TWRP with latest TWRP, no need to flash TWRP separately.
2. Flash my ROM zip from TWRP. Be sure to wipe data/cache. While it boots, wait up to 20 mins. Because the ROM is deodexed, the 1st boot will take much longer. This is the nature of deodexed ROMs. If it hasnt booted in 20 mins, or bootloops/autoreboots...
Then you should try flashing the full, official firmware package in Odin. You can flash my ROM zip after this, but you dont need to, however you will end up with an odexed ROM if you dont.
Odin will not directly flash boot.img files, but TWRP can. No need to flash this separately unless you havent yet installed root/custom kernel but plan to.
thanks a lot @AnonVendetta for your helpful reply, will try my luck tomorrow and report back:good:
best
Su
I may later release a lightly debloated and deodexed version later. And, if anyone wants it, a debloated odexed version as well. But for right now, my laptop is out of commission, so no more work can be done for about a month. There really isnt much to do anyway, besides change the system image storage format to one that is compressed. As it is, it is just a byte for byte identical copy of the deodexed system partition, no compression applied.
n910f samsung note4
yep cant replace due spen ir removable battery superb fone and very nice size
Ive loaded sooooo many custom roms, but cant find one where everything works and is fast, camera bluetooth etc, presntly on acip
if anyone knows a custom rom where everything works on sm910f appreciate a link.
Its a fone not a toy! I need it to work with the bluetooth in the car or i get fied, I need the camera to come on immediately and not freeze of i lose the pic, I need it to start reasonably quickly and not freeze!!!!!!!!
Thankyou for this marshmallow 6 rom, may I confirm
load zip file to sd card fat32 flash with twrp
end up with stock android6 still with twrp in case a good custom rom comes out.
Advantage of custom roms... note 4 commands similar to a modern fone, i forget stuff like swype up for appstore/left button app store or was it right etc runs apps like bose which no longer run on android6 possibility of volte for poor signal in home
Actually there are a couple of better features in android 6 not carried over, swype down once and see text as well as pic for data wifi etc on shade, and big bright typefaces......
gwm121 said:
yep cant replace due spen ir removable battery superb fone and very nice size
Ive loaded sooooo many custom roms, but cant find one where everything works and is fast, camera bluetooth etc, presntly on acip
if anyone knows a custom rom where everything works on sm910f appreciate a link.
Its a fone not a toy! I need it to work with the bluetooth in the car or i get fied, I need the camera to come on immediately and not freeze of i lose the pic, I need it to start reasonably quickly and not freeze!!!!!!!!
Thankyou for this marshmallow 6 rom, may I confirm
load zip file to sd card fat32 flash with twrp
end up with stock android6 still with twrp in case a good custom rom comes out.
Advantage of custom roms... note 4 commands similar to a modern fone, i forget stuff like swype up for appstore/left button app store or was it right etc runs apps like bose which no longer run on android6 possibility of volte for poor signal in home
Actually there are a couple of better features in android 6 not carried over, swype down once and see text as well as pic for data wifi etc on shade, and big bright typefaces......
Click to expand...
Click to collapse
The GRX TouchWiz Home mod V8 runs excellent with stock roms.
@gwm121: This isnt technically a custom ROM, it's just a deodexed stock ROM. As noted above, nothing has been removed, so everything should work, in terms of functionality it is identical to the odexed stock ROM. What mods you decide to install (root, Xposed, busybox, viper, custom kernel, etc), is up to you, this is just a baseline.
Yes, just flash the zip from TWRP. If it doesnt boot, then read my posts above, you will find the answer.
hi @AnonVendetta, I followed your recommendations and successfully updated my phone, looking foreward now to check battery drain over night...
unfortunately I could not (yet) install xposed, my first attempt ended in a not starting device and I had to restore backup, need to further investigate what to do.
anyway thanks a lot once more for all your efforts!
best
Su
@suse_: The battery life on this should be pretty much the same as the stock odexed ROM. I have ran many odexed/deodexed ROMs over the years, and never noticed any significant difference between them.
If you want Xposed, this is the right version to use:
https://androidfilehost.com/?fid=529152257862685344
Do not use @rovo89's regular Xposed for Marshmallow, it will bootloop/hang on Samsung stock ROMs.
You also need the Xposed Installer app by dvdandroid.
This is what I'm running now, no issues. The deodexed ROM I've provided does *NOT* have Xposed installed.
Here is a safe debloat script. It doesnt remove that much, and everything it deletes can be installed from Play Store/Galaxy Apps if you want them back. The only apps I've added are the ones that I feel are 100% safe to delete and wont affect system stability. Maybe will add more in the future as I test.
EDIT: DEBLOAT SCRIPT REMOVED
AnonVendetta said:
@suse_: The battery life on this should be pretty much the same as the stock odexed ROM. I have ran many odexed/deodexed ROMs over the years, and never noticed any significant difference between them.
If you want Xposed, this is the right version to use:
https://androidfilehost.com/?fid=529152257862685344
Do not use @rovo89's regular Xposed for Marshmallow, it will bootloop/hang on Samsung stock ROMs.
You also need the Xposed Installer app by dvdandroid.
This is what I'm running now, no issues. The deodexed ROM I've provided does *NOT* have Xposed installed.
Click to expand...
Click to collapse
running fine now, thanks a lot!
AnonVendetta said:
Here is a safe debloat script. It doesnt remove that much, and everything it deletes can be installed from Play Store/Galaxy Apps if you want them back. The only apps I've added are the ones that I feel are 100% safe to delete and wont affect system stability. Maybe will add more in the future as I test.
Click to expand...
Click to collapse
stupid question: how to apply this? I installed it via TWRP, it did nothing, I searched appdrawer without success... is it for the commandline?
thanks
@suse_: Yes, it's a script. I forgot to mention that it needs to be flashed from TWRP. I kind of just assumed that people would know how to use it.
Can i use this on but exynos
@Tx Panda: No, you definitely shouldn't flash this on Exynos N910C. Different model/CPU chipset = not compatible. You will at the very least not be able to boot the ROM, and your device may softbrick until you repair flash with Odin.
I borrowed a friend's old desktop, monitor, and keyboard for a few weeks, while my laptop is away for repairs. It's not nearly as powerful as what I have, but it enables me to do work that can only be done on a PC.
Last night I tried to convert the raw system.img to a compressed Brotli format, but the zip didn't flash. So tonight I'm going to try to convert it to compressed ext4. If it works, I'll upload it. I may debloat it as well, along with a list of what is removed.
I really don't see a point in releasing a debloated odexed ROM, since a debloated and deodexed zip accomplishes pretty much the same thing, and is much easier and less aggravating to mod system files. I actually do prefer odexed ROMS, because they seem to run slightly faster overall than deodexed. But the speed difference is minimal, and if you have a good device like the Note 4, the differences are negligable.
A few other things I'd like to note:
1. Do not use Titanium Backup to debloat. It has a tendency to delete a bit more than necessary. I have seen users complain in the past about auto-rotate not working after using TiBu. This is because it deletes, in addition to the APK, odex files as well, as well as library files (name's ending in *.so, you can find them in /system/lib/ and /system/vendor/lib/). Sometimes these library files are used by other Android processes. Use TiBu as a reference to find the location of an app that you want gone, then delete it manually with a root file manager or TWRP. This leaves library files intact. TiBu is great, I use it for backup/restore, but never for debloating.
2. If you want to confirm that the bootloader, ROM version, CSC version, and baseband/CP/modem version are the same as the values I posted, you can use the free version of Phone Info by vndnguyen (search Play Store). However, these values may not match if you didn't at least flash my mini firmware package or the full official package before the deodexed zip. This way you will know your firmware is up to date. And if you switch to a different ROM, then you probably don't need to update it. As an alternative to stock, I find Resurrection Remix Nougat to be very fast and stable. If you wanted to run this or one of the new custom ROMS, you could just flash my mini firmware, then skip this deodexed ROM.
So, I'm currently building a new ROM zip. It is deodexed, same as original zip, but also debloated/de-knoxed. I removed a fair bit more than what my safe debloat script zip deletes. Nothing has been added. This leaves the system partition with about 38% free space (2.2GB used). I've tried to limit the removals to what I feel won't affect system usability/stability. So, here's what's removed:
/system/app/Books (Google Books)
/system/app/Chrome
/system/app/Drive (Google Drive)
/system/app/Dropbox_zero (Dropbox app)
/system/app/Flipboard (news app)
/system/app/FlipboardBriefing (news app)
/system/app/Gmail2
/system/app/Hangouts
/system/app/Maps (Google Maps)
/system/app/Photos (Google Photos)
/system/app/Music2 (Google Play Music)
/system/app/Newsstand (Google Play Newsstand)
/system/app/PlayGames (Google Play Games)
/system/app/PlusOne (Google+)
task manager and associated widget (who uses a task manager these days?)
/system/app/Videos (Google Play Movies/TV)
/system/app/YouTube
lots of apps related to facebook/instagram/whatsapp/evernote
Samsung print service plugin
PEN.UP
Peel Smart Remote (constantly bombards the **** out of your phone with ads like every minute, and when you unlock screen, it had to ****ing go...never seen a more annoying app)
S Note
Galaxy Apps widget (Galaxy apps store not removed, only its' useless widget)
stock email/exhange app (there are way better email apps out there)
Hancom office
stock calculator
S Health (left S Health service intact, you can reinstall S Health if you want, it will work)
stock voice recorder (way better stuff out there)
bubbles/phase beam stock wallpapers
knox:
/system/app/BBCAgent
/system/app/Knox
/system/app/MDMApp
/system/app/RCPComponents
/system/app/SamsungDLPService
/system/app/SecurityLogAgent
/system/app/SecurityProviderSEC
/system/app/SysScope
/system/app/UniversalMDMClient
/system/container
/system/etc/secure_storage/com.sec.knox
/system/preloadedmdm
/system/priv-app/KLMSAgent
/system/priv-app/SPDClient
Knox has got to be the most annoying POS security system Samsung has ever made, it likes to block root stuff. I've always just ripped it out by the balls, never had a loss in functionality because of this.
Most of what i've removed can be reinstalled from Play Store/Galaxy Apps, except Knox. The rest is generally useless junk that I feel most people won't miss. The whole point is to decrease the installed footprint of the system partition, while saving battery/CPU/RAM.
I'll spend the rest of tomorrow testing, then upload. This will very likely be the last released zip, I don't intend on turning this into a full-on custom ROM. In fact, I mainly created this topic to help out @prkfsz with a deodexed ROM that he could easily install MicroG onto. So far he hasn't reported whether it works. But then I realized I'd be doing the community a small service, so I created this topic. With that said, I'm not inclined to do much more free work, I'm a very busy guy most of the time. But I'll still stick around to answer questions.
@AnonVendetta - thank you for all the work. Sorry for not answering before, as i said, i was away and just recently got back. Will not have time to try your ROM untill next week.
I did manage to deodex stock ROM before with that APKtool you suggested, and it was a breeze with your instructions. Even here your instructions are very clear. You should be writing manuals..
Glad to see that there still is an interest for this great device. Personally i am going to run it as long as it works. And then i have a backup or five..
Am gratefull also for this ROM you are working on. That is almost exactly what i was looking for to begin with. I just sortof don't really get why you would remove S Note from the stock rom - that is basically one of the greatest advantages of this phone. I know there are other writing apps out there, i guess Squid is ok but in my opinion no apps come close to original SNote.
Looking forward to trying out your creations!
@prkfsz: I removed S Note and PEN.UP because I very rarely use the pen. Both of these are installable from Play Store/Galaxy Apps, so you're not really losing them. I have always considered them to be bloat. Another reason is that the versions Samsung includes in the ROM are old and not up to date.
You could have deodexed the entire ROM with APKTool, but it would have taken forever compared to the Kitchen. On my powerhouse PC, deodexing takes about 15 mins.