Related
I have a Note 2 (obviously), and I have rooted my phone the first day I got it and have never updated the phone since I purchased it. So, I am still on 4.1.2. My phone has been super laggy and I want to take the oppurtunity the when I reset my phone that I can take advatages of the new features that mobile phones have by upgrading all the way to 5.1.x.
So, I downloaded CM 12.1 by wilson3q with 5.1 system. I first tried the 5.0 version since the 5.1 looked too new, and did not have time to deal with the bugs. When I flashed the 5.0 version, I got errors of not being able to flash gapps for 5.0 and that I lost my root. I tried downloading the new TWRP to see if I can get a newer version that would work better, but no luck. I got an error saying that I lost my root privileges and did I want TWRP to fix it. I slid yes to fix, but no luck.
The same problem occurred when I tried with 5.1.
So, I ended up restoring my nandroid backup and I am back on 4.1.2 again with root working again.
I am thinking that I am probably supposed to 'step up' the updates, but not sure. Does anyone have a solution or a link to the solution that they can help with?
PS: I did not like the camera that came with the new mod. I do like the stock one. Are there flashes of cameras that I can use as well when I do end up upgrading?
Thank you in advance!!!
geske001 said:
I have a Note 2 (obviously), and I have rooted my phone the first day I got it and have never updated the phone since I purchased it. So, I am still on 4.1.2. My phone has been super laggy and I want to take the oppurtunity the when I reset my phone that I can take advatages of the new features that mobile phones have by upgrading all the way to 5.1.x.
So, I downloaded CM 12.1 by wilson3q with 5.1 system. I first tried the 5.0 version since the 5.1 looked too new, and did not have time to deal with the bugs. When I flashed the 5.0 version, I got errors of not being able to flash gapps for 5.0 and that I lost my root. I tried downloading the new TWRP to see if I can get a newer version that would work better, but no luck. I got an error saying that I lost my root privileges and did I want TWRP to fix it. I slid yes to fix, but no luck.
The same problem occurred when I tried with 5.1.
So, I ended up restoring my nandroid backup and I am back on 4.1.2 again with root working again.
I am thinking that I am probably supposed to 'step up' the updates, but not sure. Does anyone have a solution or a link to the solution that they can help with?
PS: I did not like the camera that came with the new mod. I do like the stock one. Are there flashes of cameras that I can use as well when I do end up upgrading?
Thank you in advance!!!
Click to expand...
Click to collapse
Try Phiz recovery, I've never had trouble with "[I605][CWM Advanced Edition] PhilZ Touch". If I recall we had to start using that one when kit-kat was released (i reserve the right to recall poorly)
I have a link to download mirror here:
http://forum.xda-developers.com/showpost.php?p=60899023&postcount=146
from your new recovery, you should be able to install CM12.1 and 5.1 gaaps recommended in the Wilson3Q i605 thread. from here:
http://forum.xda-developers.com/note-2-verizon/development/rom-unofficial-build-i605-t3069506
FWIW, I am on the 20150803 build and still using the GApps Minimal Edition 2015-04-04 for Android 5.1 (91 MB) from here:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
with no issues to report.
You may also need to track down updated radios (to flash from CWM). I think you can find a link to the updated ND7 Modem/Baseband here:
http://forum.xda-developers.com/showthread.php?t=2765021
somewhere in middle of first post
Good Luck!
PS you may want to flash superSU from recovery... get the zip from chainfire's xda thread here:
http://forum.xda-developers.com/showthread.php?t=1538053
(I've been dirty flashing for so long I dont' remember if the rom came with SuperSU or superuser... as such I can't recall if I had to flash this zip or not, but I probably did if I had issues with root)
Note you may also need to enable root from the settings menu after enabling developer mode.
there should be a "root access" option (or somehting like that there)
PPS are you also remembering to wipe data & clear cache/dalvik?
I have found zoot's mega wipe useful...
http://forum.xda-developers.com/showthread.php?t=1983489
it is for the N7100/N7105, butI have used it on the i605 quite a bit. Initial test result reported here:
http://forum.xda-developers.com/showpost.php?p=44093932&postcount=117
that said zoot's script is probably overkill
jheide44 said:
Try Phiz recovery, I've never had trouble with "[I605][CWM Advanced Edition] PhilZ Touch". If I recall we had to start using that one when kit-kat was released (i reserve the right to recall poorly)
I have a link to download mirror here:
http://forum.xda-developers.com/showpost.php?p=60899023&postcount=146
from your new recovery, you should be able to install CM12.1 and 5.1 gaaps recommended in the Wilson3Q i605 thread. from here:
http://forum.xda-developers.com/note-2-verizon/development/rom-unofficial-build-i605-t3069506
FWIW, I am on the 20150803 build and still using the GApps Minimal Edition 2015-04-04 for Android 5.1 (91 MB) from here:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
with no issues to report.
You may also need to track down updated radios (to flash from CWM). I think you can find a link to the updated ND7 Modem/Baseband here:
http://forum.xda-developers.com/showthread.php?t=2765021
somewhere in middle of first post
Click to expand...
Click to collapse
I assume that you are giving steps in order, BUT I feel that I should flash the radio to 4.4.2 first, in which the link was broken. I have spent a couple hours trying to find another link, but I am afraid that I may be using an incorrect one. Do you have a good link for that, please?
Also, I have ready the newest Samsung 3.10 Odin downloaded and installed, as well as the USB driver installed and downloaded the ADB fastboot. If I remember correctly, I am supposed to move this onto C: and run it to access the device (Note 2). It has been since Android first came out since I have used the ADB though. So, I apologize for the ignorance. So, do I just make sure the adb is in the same directory and run Odin or did I not need ADB and just run Odin?
I also assume that I run the Philz touch after I have gotten to 4.4.2 rooted first. Am I correct by assuming that?
jheide44 said:
Good Luck!
PS you may want to flash superSU from recovery... get the zip from chainfire's xda thread here:
http://forum.xda-developers.com/showthread.php?t=1538053
(I've been dirty flashing for so long I dont' remember if the rom came with SuperSU or superuser... as such I can't recall if I had to flash this zip or not, but I probably did if I had issues with root)
Note you may also need to enable root from the settings menu after enabling developer mode.
there should be a "root access" option (or somehting like that there)
PPS are you also remembering to wipe data & clear cache/dalvik?
I have found zoot's mega wipe useful...
http://forum.xda-developers.com/showthread.php?t=1983489
it is for the N7100/N7105, butI have used it on the i605 quite a bit. Initial test result reported here:
http://forum.xda-developers.com/showpost.php?p=44093932&postcount=117
that said zoot's script is probably overkill
Click to expand...
Click to collapse
Yes, I have done a cache/dalvik wipe a few times (because I have tried reflashing to get it to work with no luck).
I have downloaded the .zip version of superSU as well, and gapps minimal 5.1 with wilson3q's 5.1 ROM. So, I am almost ready to go with the exception of the correct radio upgrade file.
Thank you so much for your help!!! Much appreciated!
PS Will my old WifiTether apk files still work with 5.1 or do I need to get a new one?
Thanks Again!
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
jheide44 said:
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
Click to expand...
Click to collapse
I will try this later. Thank YOU! I have to take kids to practice now.
jheide44 said:
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
Click to expand...
Click to collapse
Sorry to bother you, but I still am getting errors with Failed root access for Titanium Backup Pro. I also cannot find Developer Options in the settings menu.
I have tried flashing the radio before and after wiping and installing the ROM then gapps then superSU. I get into superSU and it asks me for root access and I grant it, but Titanium Backup Pro still says that it has no root access.
Any ideas? Thank YOU!!
geske001 said:
Sorry to bother you, but I still am getting errors with Failed root access for Titanium Backup Pro. I also cannot find Developer Options in the settings menu.
I have tried flashing the radio before and after wiping and installing the ROM then gapps then superSU. I get into superSU and it asks me for root access and I grant it, but Titanium Backup Pro still says that it has no root access.
Any ideas? Thank YOU!!
Click to expand...
Click to collapse
with SuperSU installed, you may need to just need to update binaries. open SuperSU and it should prompt you if necessary. the "normal" option should work (no need to flash from recovery)
for TiBu...
--within SuperSU settings you may need to disable (uncheck) "mount name separation".
--You may also have to enable unknown sources (under settings, security).
-- there might be something to enable for USB debugging as well (TIBU should prompt for it)
FWIW, you can restore user apps/data... but I would not attempt to restore any system data. Personally, I have found it best to get to know a fresh ROM for a while before trying to restore crap from an older ROM . there might be value in re-configuring apps manually and/or restoring them one at a time (after making sure the ROM is working properly) i.e. you won't need any of those aforementioned WiFi tether apps since it is built into the ROM now.
Instructions on enabling developer options in CM ROM, from here: http://wiki.cyanogenmod.org/w/Doc:_developer_options
1- In the Settings app, select About Phone (or About Tablet).
2- Scroll down, and tap the Build number entry seven times. On the seventh tap, you will be notified that "You are now a developer."
3- Return back to the main Settings menu. Developer options and Performance entries should now be visible.
Click to expand...
Click to collapse
(that is likely how to enable superuser that is "baked" into the rom, given you already installed SuperSU it may only complicate matters)
You may be rooted and just having TiBu issues. If all else fails you can check with an app. A long time ago, I've used "Simple Root Checker" by SimoneDev to check root/busybox. It is still in the play store.
Good Luck!
jheide44 said:
with SuperSU installed, you may need to just need to update binaries. open SuperSU and it should prompt you if necessary. the "normal" option should work (no need to flash from recovery)
for TiBu...
--within SuperSU settings you may need to disable (uncheck) "mount name separation".
--You may also have to enable unknown sources (under settings, security).
-- there might be something to enable for USB debugging as well (TIBU should prompt for it)
FWIW, you can restore user apps/data... but I would not attempt to restore any system data. Personally, I have found it best to get to know a fresh ROM for a while before trying to restore crap from an older ROM . there might be value in re-configuring apps manually and/or restoring them one at a time (after making sure the ROM is working properly) i.e. you won't need any of those aforementioned WiFi tether apps since it is built into the ROM now.
Instructions on enabling developer options in CM ROM, from here: http://wiki.cyanogenmod.org/w/Doc:_developer_options
(that is likely how to enable superuser that is "baked" into the rom, given you already installed SuperSU it may only complicate matters)
You may be rooted and just having TiBu issues. If all else fails you can check with an app. A long time ago, I've used "Simple Root Checker" by SimoneDev to check root/busybox. It is still in the play store.
Good Luck!
Click to expand...
Click to collapse
Thank you! It ended up being my version of Titanium Backup. I downloaded a new version and it is good. As far as restoring is concerned, I do not even want the apps themselves restored from there, because there may be a new version and would like a fresh install of those apps. I just want my data restored. For example, I have a surveillance software that I would just like to restore the entries (IP's usernames and passwords). I would like my email settings to be there, so that I do not have to re setup my 7 email addresses. My Text/SMS messages and my alarms. So, I am not trying to do a full restore.
On another note, I am trying to get my calendars back into my phone with no luck. I cannot install google calendar and get my google calendars to populate into my task widget, and the ROM is not letting me set up my POP email addresses. Also, I see no ringtones, so I have no ringers to ring my phone nor tones for my alarm clock. I flashed gapps for 5.1 and I see nothing extra from the ROM. I thought gapps was google apps. Am I trying to do stuff differently than you? There seems to be a few problems in that manner that I am trying to work with.
I am thinking of downgrading to 5.0. Maybe the 5.1 is too new?
Again, THANK YOU for your help!
geske001 said:
Thank you! It ended up being my version of Titanium Backup. I downloaded a new version and it is good. As far as restoring is concerned, I do not even want the apps themselves restored from there, because there may be a new version and would like a fresh install of those apps. I just want my data restored. For example, I have a surveillance software that I would just like to restore the entries (IP's usernames and passwords). I would like my email settings to be there, so that I do not have to re setup my 7 email addresses. My Text/SMS messages and my alarms. So, I am not trying to do a full restore.
On another note, I am trying to get my calendars back into my phone with no luck. I cannot install google calendar and get my google calendars to populate into my task widget, and the ROM is not letting me set up my POP email addresses. Also, I see no ringtones, so I have no ringers to ring my phone nor tones for my alarm clock. I flashed gapps for 5.1 and I see nothing extra from the ROM. I thought gapps was google apps. Am I trying to do stuff differently than you? There seems to be a few problems in that manner that I am trying to work with.
I am thinking of downgrading to 5.0. Maybe the 5.1 is too new?
Again, THANK YOU for your help!
Click to expand...
Click to collapse
I wouldn't downgrade, nobody is actively working on 5.0.2 anymore.... that thread is basically dead. Also, it is likely less "stable"/mature than what you have installed now (that is currently being maintained). i.e. you have the ROM that I would stick with.
like I said I wouldn't restore any thing into system (apps or data)... you can do whatever you please. (but it could be causing you more issues than just biting the bullet & configuring manually) i.e. restoring accounts might result in unanticipated issues, you came from a much older version of android.
all I had to do was install google calendar from play store and then the CM12 calendar stuff all worked (I might have had to restart and/or install the google calendar prior to setting up primary gmail). you might need to remove all your accounts and load them again (a factory reset might be faster though.)
also you might have to update google services and the play store before certain things "play nice".
I know you don't want to hear this but...
from here on out i'll likely point to all your issues being based on restoring system data. (based on my limited knowledge and personal experience). FWIW, I'd try to reconfigure/setup everything manually and you will likely have much better results.
jheide44 said:
I wouldn't downgrade, nobody is actively working on 5.0.2 anymore.... that thread is basically dead. Also, it is likely less "stable"/mature than what you have installed now (that is currently being maintained). i.e. you have the ROM that I would stick with.
like I said I wouldn't restore any thing into system (apps or data)... you can do whatever you please. (but it could be causing you more issues than just biting the bullet & configuring manually) i.e. restoring accounts might result in unanticipated issues, you came from a much older version of android.
all I had to do was install google calendar from play store and then the CM12 calendar stuff all worked (I might have had to restart and/or install the google calendar prior to setting up primary gmail). you might need to remove all your accounts and load them again (a factory reset might be faster though.)
also you might have to update google services and the play store before certain things "play nice".
I know you don't want to hear this but...
from here on out i'll likely point to all your issues being based on restoring system data. (based on my limited knowledge and personal experience). FWIW, I'd try to reconfigure/setup everything manually and you will likely have much better results.
Click to expand...
Click to collapse
I figured that, and feared that and the same time. So, what am I flashing onto the phone with gapps then? Also, one of the reasons I was wanting to go back was because there are a few apps that are not 'compatible' with this system. Meanwhile, I am going to wipe and reset again, and do what you suggested and just reconfigure.
Thanks again!
geske001 said:
I figured that, and feared that and the same time. So, what am I flashing onto the phone with gapps then? Also, one of the reasons I was wanting to go back was because there are a few apps that are not 'compatible' with this system. Meanwhile, I am going to wipe and reset again, and do what you suggested and just reconfigure.
Thanks again!
Click to expand...
Click to collapse
GAaps are the google apps... good read:
http://wiki.rootzwiki.com/Google_Apps
(hopefully I am not out of line for posting a link to that wiki)
many ROMS like CM don't' include gaaps due to licencing/legal issues. which is why the AOSP roms devs often have you flash the GAAPS package separately (also you can pick your package for your fact pattern... full gaaps/minimal gaaps/etc.).
Also the gaaps zip files you flash from recovery install the files into system. a lot of folks like the minimal editions of GAaps because it doesn't force all the apps into system. instead it just gets you up and running with the play store and a few essentials... that lets the user install all the other google apps as user apps, from the play store.
basically taking the "debloat" mentality as far as you can... keep stuff out of system and let the user decide what to install.
Want to update to CM13? Read this first!
Welcome to my upgrade guide that will allow users to painlessly upgrade from an earlier version of android to CM13.
Background info:
Our Cyanogenmod maintainer, Lysergic Acid, started bring alpha builds of Cyanogenmod 13 since October of last year. Now, we have official nightlies on our device which just proves how strong of a device we have and how strong we are as a community on XDA. With all of the exciting new features Marshmallow brings to the table, people have been flashing CM13 without reading any precautions or information about the possible consequences of not doing a particular step or procedure. With this guide, you will learn how to successfully flash CM13 on a device, everytime!
This guide will assume you are on a rooted custom ROM with a working custom recovery. It will not guide users how to update from stock ROM to CM13. If you haven't rooted your phone yet or are on stock ROM, use a different guide to install a rooted custom ROM (KK or LP preferred) then follow this guide.
Another important tip is to read the issues post before flashing the latest build of CM13. There could be issues that you could encounter so make sure to read before flashing!
How to install:
CM13 is available to install for CM12.1 users via the OTA updater. However, updating to CM13 via OTA updater is buggy and will remove gapps and Isorec Recovery. If you receive notifications about the CM13 update, don't use the OTA updater! Use this guide below instead.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the upgrade process or you don't like CM13 in general. If you are using Cyanogen recovery from CM12.1, you should flash a isorec recovery from this thread. TWRP or CWM are both fine. Note: If you are using a build earlier than 20160119 nightly or not using one of Lanchon's isorec kernels, you will not be able to use a isorec recovery. This will not apply to people on older versions of android (for older versions of android, KK compatible recovery or higher is all you need).
If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section. It is required for users to re-partition their system partition to 1GB to prevent issues when flashing gapps. Please also note that when upgrading from an older ROM, you must flash a newer Gapps to keep Gapps on your phone.
Download CM13 from the official cyanogenmod downloads page onto your phone. Update: The Cyanogenmod downloads page is gone, instead download from here.
If you are in CWM, while on the main menu, choose factory reset. Then go into mounts and storage and select format system. If you are in TWRP, go into the wipe menu, select advanced wipe, check wipe system, data and cache, then swipe the bar to wipe.
Flash the CM13 zip.
(Optional)Install Gapps (if you've re-partitioned already, if you didn't, you will get errors!).
(Highly recommended)If you don't have isorec recovery already installed, you should flash an isorec recovery here: Thread link
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken.
I will repeat what I said earlier but with more explanation. Why don't I have a guide on how to update to CM13 via OTA? OTA update from CM12.1 to CM13 is broken! You will lose gapps and it will cause a lot of problems to user. Just follow the above guide to flash update manually and no issues will be encountered.
Gapps on Android Marshmallow:
Recommended Gapps: OpenGapps Pico
What to select on OpenGapps page: ARM>6.0>Pico
While flashing Gapps is an optional step during the upgrade process, many people require the Google Play store to install all of their apps. It is required for people who want to flash gapps to increase their system partition to 1GB (or more). Stock partition sizes have a system partition size of about 500MB which is not enough to hold even the smallest gapps packages available!
Re-partition guides
You can re-partition your device by following my guide (Requires PC): http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162 or Lanchon's guide (Doesn't require PC): http://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
If you have working recovery, use Lanchon's guide (second link). Otherwise, my guide (first link) will work for everyone else.
Please note that re-partitioning your device via ODIN (first link) will delete all of your data, including your internal storage which contains all of your personal files. You must backup all of your files to an external sd card or PC if you want to keep them! However Lanchon's guide (second link) keeps all of your personal data but requires a working custom recovery!
Please also note about the naming of the zip/pit files!
If you get error 70 while flashing Gapps, make sure you are using the re-partition guides properly, you may have missed a step or forgot to do something. If you didn't bother reading all of the information I've given and decide to post about your error, you will be told to read the information properly and nothing else. All help was given already If you get some other error, read the OpenGapps FAQ.
Stock Cyanogen Recovery:
CM13 Stock Cyanogen Recovery is a basic recovery that allows you to flash zips from your internal and external sd storages. It provides wipe options and ADB flashing support, but was only designed to provide the basic tools for flashing. Although it works fine in recent builds of CM13, it is highly recommended that you use an Isorec Recovery like TWRP.
Update: Cyanogen recovery has fixed mounting support for internal and external sd as of the 5th of October nightlies. The steps below now only apply to people who want to use older CM13 builds.
If you have build 20161005 or later, you can now easily switch to an Isorec recovery simply by flashing it via Cyanogen recovery. You can not do this in older builds!
Isorec install on builds older than 20161005
1. ADB Sideload Method (requires PC)
This is the easiest and quickest method to restore Isorec Recovery on your device. However it will require ADB/Fastboot tools to be installed on your computer. You also need to enable ADB debugging and enable root access for ADB in the development settings to use this method. If you don't have ADB/Fastboot tools installed, download it from this thread
Download recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip onto your PC
If you haven't enabled ADB debugging and root for ADB, do this now in the development settings menu
Reboot your phone into Cyanogen recovery
Select apply update from ADB sideload
In the ADB/Fastboot folder containing ADB.exe, hold shift + right click the window to open up the folder menu.
Select open command line menu here
Type or copy and paste this command: adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
Cyanogen recovery should begin flashing TWRP recovery
Once completed, reboot your device
2. ODIN method (requires PC)
This method requires ODIN to be installed on your computer. You will be connecting your phone to the computer which may or may not be a problem for some users.
Put your phone into download mode (Power key, home button, Volume Down button)
Connect your phone to your PC
Open ODIN. Make sure that it detects your device. If it doesn't, check if you have the right drivers installed and if the usb cable/port is damaged
Download ODIN-flashable CM12.1 kernel here: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4 Don't worry if it isn't CM13 kernel, you will have to reflash CM13 anyway! If you don't know which one to choose, the TWRP CM12.1 kernel is fine.
Select the CM12.1 kernel as PDA (or AP)
Make sure you untick auto-reboot
Start the flash.
Once flash is successful, disconnect your phone from your PC. Remove your phone battery, then reinsert it.
Get into recovery mode (Volume Up, Power Key, Home button)
Repeat CM13 flashing guide above without any backup.
If you have linux, use JOdin instead of ODIN.
3. Terminal method (Doesn't require PC)
This method requires a terminal emulator. Either download one from the google play store or enable the in-built terminal emulator in development settings. Follow the guide carefully. You can use this method if your USB port is broken.
See Lanchon's post: http://forum.xda-developers.com/showpost.php?p=65164875&postcount=1002
As mentioned in Lanchon's post, IF YOU MAKE A MISTAKE IN ONE SINGLE CHARACTER YOU TYPE IN THE TERMINAL, YOU COULD BRICK YOUR PHONE FOREVER!!!
Root on Android Marshmallow
CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for ADB too because this can help you recover from some problems that may occur in the future.
You may be familiar with the root tool, SuperSU, and it may have been installed in CM12.1 or earlier versions of android. Android Marshmallow has a different way of rooting the device. It is not compatible with older versions of root.
Currently, SuperSU doesn't work on CM13. Do not attempt to install it with system method and don't try to install it with systemless method.
How to update to a newer build of CM13
1. OTA Updater method
This method of updating Cyanogenmod is usually preferred by many users because it is ready-to-use and is quite simple to do.
Go into settings>about phone>system updates
If there is a new build available, press the download button. The OTA updater will now download the update to your phone
Once it finishes downloading, it will prompt you if you want to install the update. Confirm that you want to update and your phone should restart
Your phone will reboot into recovery mode. The update process is automated. Once the progress bar is full, your phone should reboot again.
If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
2. CyanDelta Update method (Popular method)
This method of updating Cyanogenmod is most beneficial to people who want to save bandwidth and/or want to download the update via their mobile data. This method typically saves around 200MB of data which makes it a quick way of updating, without sacrificing stability.
Download Cyandelta from the google play store
Download from CyanogenMod website the .zip file of the ROM you are using. Please note that if you haven't saved a copy of your current build onto your phone, the Cyanogenmod Downloads server usually deletes old nightlies. Update: The Cyanogenmod downloads page is gone, instead download from here.
Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
If you are stuck using the CyanDelta update method, check out their FAQ on their website.
3. Manual method (Recommended)
If you have issues using the other methods to update CM13, you can also install the update manually via recovery. This method usually has the greatest success rate.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the update process. If you don't have Isorec TWRP or CWM, use the guide above to reinstall CM13 with a working recovery!
Download newer CM13 build from the official cyanogenmod downloads page onto your phone. Note: Old cyanogenmod nightlies are usually deleted from the Cyanogenmod server if you haven't downloaded your current build onto your phone yet. Update: The Cyanogenmod downloads page is gone, instead download from here.
Flash the CM13 zip
Wipe cache
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken. If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
New users are encouraged to post questions about CM13 here and not in the CM13 Development thread, this will leave everyone happy and everyone gets what they want
Thanks to Lysergic_Acid for CM13, Cyanogenmod team, CyanDelta team, arnab for his TWRP isorec recovery, Lanchon for his Isorec kernels, repartition script, Isorec recovery and guides.
Updated on 02/02/17
Since the wiki for our device hasn't been updated yet, here are a list of some issues on CM13:
Issues marked with red are recent issues you will experience in any current build of CM13.
Ongoing issues:
MX Player can not use HW+ decoder. Instead, use HW or SW decoder. The developer of MX player is working on a fix.
Cyanogenmod OTA Updater sometimes can be buggy. MD5 errors, download errors, installation errors. Although it is working fine for most people, I still recommend just to flash manually via recovery!!!
Internal storage and external storage is not labelled correctly and has a random name. This is not a bug but a feature of one of the mounting ways of MM.
Screenrecorder works for some users, however it seems that you can not playback them on your phone. Workaround: Play the videos using your PC.
Some apps may have trouble detecting internal/external storage.
Some bluetooth devices may not behave properly or connect
Multiple issues with F2FS. Please note that this FS is still relatively new for our device so bugs are likely to be experience. Stay on ext4 for best stability!
Some people have reported that they have lost connection to their mobile network. This usually can be fixed by resetting APNs. If this doesn't help, you may need to downgrade back to stock 4.1.2 ROM.
MMS video file (.3pg format) will not play on the default video player. Workaround: Play the video through MX Player on SW renderer.
Hardware button is always on until screen is switched off. Workaround: After installing the BLN MOD and synapse, you can control the timeout values.
You may experience reboots when you receive phone calls
More to be added later
Fixed issues:
(from latest issue solved to earliest)
Cyanogen Recovery can not mount internal and external storage. You can not flash zips via internal or external storage. ADB sideload or other methods of flashing can be used instead. Fixed in nightly 20161005
Battery Percentage Incorrect and Causing Constant Low Battery Warnings. Fixed in nightly 20160818
As of the 20160722 nightly, decryption of /data partition is broken. Keyboard can't be switched to enter digits. Fixed in nightly 20160724
As of the 20160722 nightly, setup wizard is broken. When you press next, the notification bar drops down instead of the next screen showing. Fixed in nightly 20160724
Some people have reported that the youtube app (play store version) displays green lines during playback.
Front camera errors in recent builds
Phone dialer is currently broken Workaround: Use google dialer from Google Play Store
Live lockscreen has multiple issues being experienced in recent builds.
Nightly 20160326 is experiencing Google Play Launcher FCs. Please stay on a earlier build until this is fixed. Fixed in nightly 20160329
People who are using a non-english language may experience Clock app FCs. This problem is under investigation. Update: Fixed in nightly 20160325
Doze feature can not optimize any apps. This is not a bug, doze is disabled on our device! Please ignore this menu! Update: Fixed in nightly 20160325. Note: This is the app standby feature that is now working and not motion sensor doze!
Nightly 20160323 is experiencing CM file manager FCs Fixed in nightly 20160325
Nightly build 20160216 is currently affected by the no signal bug and dialer issues. Update: Calling issues have been fixed in nightly builds 20160218 or newer. If you are on build 20160216, you should update immediately to fix this issue.
FAQ
Q: What is cyanogenmod?
A: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device. CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Q: What version of android is CM13 based on?
A: Android Marshmallow 6.0.1
Q: What is Gapps?
A: Google Apps (Gapps) is an app package containing the Google Framework which is required for most apps from Google to function. This will include the Google Play Store and other Google apps and services depending on what setup you select (it varies on what Gapps package you select, I recommend OpenGapps).
Q: Is this ROM pre-rooted?
A: CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for adb too because this can help you recover from some problems that may occur in the future.
Q: I get error 70 when flashing gapps. What can I do to solve it?
A: Error 70 means that you have insufficient space available in the system partition. Your device does not have sufficient space available in the system partition to install the Open GApps package. As I have said in my guide, you will need to repartition your system partition using one of the links in the gapps installation section of my guide. Then only you will be able to install gapps on your phone.
Q: Help me! My phone says that sdcard0 is corrupted! What can I do to solve it?
A: If you've re-partitioned your device recently using the ODIN method, it is highly likely that you forgot to format your internal sd card. You can do this in the recovery by selecting sdcard0 or internal sd, format as vfat (fat) or default (CWM). Alternatively, you can use your computer to format it manually by mounting your phone's storage via recovery then using a formatting utility such as the built-in windows formatting tool.
Q: Does xyz app work with CM13?
A: I don't know. Check the app's website, check the google play store, check other users comments. Google is your best friend. If not, try it out for yourself! Some apps require selinux to be set to permissive, you can do this in apps like SELinuxModeChanger.
Q: Does SuperSU work on CM13?
A: While there are ways to get SuperSU working, this guide is only here to provide basic procedures. I do not recommend new users to install SuperSU on any Android 6.0 ROM.
Q: My apps that require root say that I need busybox to use the app. What should I do?
A: You do what it tells you to do. Download busybox installer from the app store, install busybox and your app will hopefully work as it should.
Q: What happened to busybox? It was available on older android versions but why do I have to install it myself on CM13?
A: Busybox was replaced with toybox in CM13. As a result, you can not run apps that require busybox so you need to install a busybox installer from the google play store.
Q: Does GPS work well on CM13?
A: Reports have shown that GPS is still not reliable like in CM12.1.
Q: Does CM13 have Isorec Recovery Support?
A: Yes, it does. However CM13 comes with CM recovery as the default recovery.
Q: Does xposed work on CM13?
A: Yes it does. Use the latest installer (xposed-v80-sdk23-arm or newer) and make sure selinux is set to permissive.
Q: Which is better, CM13 or CM12.1?
A: CM13 is still new for our device. Naturally, there will be bugs experienced by users. Over time, the ROM will mature and it will become stable for everyone to use. Try it out for yourself and see which one is best for you
Q: Can I install CM13 on {different S2 model}?
A: If it is just a carrier/region variant of the international s2 i9100, it should work without problems. If it is different physically (hardware), then it will not work!
Q: Battery life sucks on CM13! What happened to doze mode?
A: Our device lacks the (low power) sensors that take advantage of this feature, therefore making it useless so it was disabled. Don't forget our device (s2) is quite old now, it shouldn't be a surprise that we can't take advantage of new features like this.
Q: Battery life sucks on CM13! (General)
A: Download and install betterbatterystats onto your device. Check what app is the culprit to your poor battery life. If there are no apps that are behaving strangely, try reflashing your current ROM and making sure to factory reset and format system partition. A lot of battery problems are created by the user, maybe brightness is set too high, change the screen timeout delay, etc.
Q: Can I update to CM13 without a computer?
A: Yes you can. I have included guides/steps that are not computer dependent if you haven't noticed already. If you have a broken USB port, you need to get it fixed ASAP because if anything happens during the flashing process, your phone is useless!
Q: My device runs slow on CM13. Can I do anything to make it go faster?
A: Make sure to close all apps that are not needed. Change swappiness to a lower value or 0. Change CPU governor parameters: Up threshold, sampling rate. Make these values smaller to give more performance. Remove apps that may be hogging up your CPU/RAM. Reboot, it helps
Q: What does android security patch level mean?
A: Google regularly updates their newer android versions with security fixes. Cyanogenmod will apply those fixes to their ROM so you will stay protected as well.
Q: Why is xyz feature not available in CM13 when it was available in CM12.1?
A: It is a good possibility that Cyanogenmod are not ready to add the feature yet. It could still need more internal testing or other more important features have to be added first for adding it to the ROM.
Q: Why can't I install gapps?
A: Now before you post this, have you read the post given by the users on the CM13 thread? I have said in my guide that in order to flash gapps, you will need a larger system partition. Please re-read the guide and make sure to read carefully before posting questions.
Q: What is BLN?
A: BLN (Backlight Notification) is a feature which uses your phone's hardware button lights to notify you whenever you receive a notification such as SMS, email, etc.
Q: How do I use BLN?
A: BLN is disabled by default. You need to use Synapse to configure it. See this thread
Q: How do I change the behavior of BLN?
A: See this thread
Q: Will BLN drain my battery?
A: BLN (not BLN without wakelock) prevents your CPU from going to deep sleep mode (low power CPU mode to save battery) which will drain your battery quicker versus having it disabled. Lighting up your hardware buttons will also use a little more power, so please take these factors into account before posting about poor battery life.
Q: Why is my button backlight always on?
A: See this thread
Tuning guide
For performance
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Change CPU governor to PegasusQ
Change swappiness to 20
Change I/O scheduler from CFQ to Deadline
Decrease CPU governor sampling rate to 40000
Decrease CPU governor up threshold to 60
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Change entropy read threshold to 512 and write threshold to 256
Disable entropy for internal and external sd
Disable iostats for internal and external sd
For battery life
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Kernel Adiutor
Change CPU governor to PegasusQ
Change swappiness to 40
Change I/O scheduler from CFQ to SIO
Increase CPU governor up threshold to 90
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Decrease vfs cache pressure to 60
Change entropy read threshold to 512 and write threshold to 256.
Disable entropy for internal and external sd
Disable iostats for internal and external sd
Greenify
Enable aggressive doze (beware, you may lose notifications!)
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
rolves1899 said:
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
Click to expand...
Click to collapse
Repartition is highly recommended, otherwise you will have a hard time finding a gapps package that will work. Use lanchon's guide linked in the OP now that you have a working recovery.
gsstudios
Got it. I'll try as soon as possible . Phone looks smooth atm. thx to u
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Draky50110 said:
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Click to expand...
Click to collapse
You have good luck then However, it still needs to be worked on.
Although it is not required to reflash isorec, I include it anyway in the steps to prevent issues that may occur anyway. That way, users are 100% sure that they don't end up with cyanogen recovery.
gsstudios
stylemessiah said:
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Click to expand...
Click to collapse
Thanks, will add this to the guide soon.
gsstudios
Thanks for your work and this nice guide.
In this guide in the repartition part where is instructed
to flash kernel with ODIN, i would instruct to set the option
for AUTOMATIC RESET after flash to OFF, and pull battery after flash.
Because the flash happens so quickly and its a little difficult to
do the 3-finger boot then.
Best regards.
Thanks for this thread, I wanted to ask questions on the other thread but think the devs are getting overwhelmed by basic questions so this thread is perfect.
I wanted to ask what exact steps I need to take as I am on cm12 with cyan recovery and it's been years since I flashed this phone so I don't want to brick it. I am on the original 512mb system partition.
I have Ubuntu not windows and struggling to get jodin loading and heimdall worries me a bit so I am going to borrow a windows machine later but before I do I want to make sure I have the steps right.
So I figure I need to install Odin, then use this to flash a twrp kernel first to get my recovery is that right? And at the same time I need to repit so I can do both things at once, then reboot my phone into twrp have I got that bit right?
Next I need to format the partitions, then reboot again into twrp? At the next reboot I then can flash cm13 from an external zip file, isorec and gapps all at once, then reboot again and the handset should come up?
I hope I don't upset anyone asking all this and I really appreciate help, for the past 2 weeks I have been googling and reading the other thread to make sure I have understood it right but bit put off from asking questions that might upset others.
OP updated with recommendations from other users. Thanks for the suggestions!
Remember that new users are encouraged to post in this thread as it was specifically created to help new users install/update CM13.
gsstudios
System partition looks risky to me. Is there any other way to flash gapps ? I can format internal memory if it helps. Im using phone to connect internet. If there is something wrong with partition i cannot solve it ..
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
fireburner-de said:
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
Click to expand...
Click to collapse
Already in the OP. It is the second link for the repartition section
gsstudios
AT LAST ! Now they will not spam the official thread of cm 13!
gsstudios said:
Already in the OP. It is the second link for the repartition section
gsstudios
Click to expand...
Click to collapse
Well I know, that the link is there. Just 2 lines after the links you write in red that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
UsualSuspectReaL said:
AT LAST ! Now they will not spam the official thread of cm 13!
Click to expand...
Click to collapse
I fear, they still will
fireburner-de said:
Well I know, that the link is there. Just 2 lines after the links you write in read that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
I fear, they still will
Click to expand...
Click to collapse
Yes, I forgot to change that. Updating now... I read your post wrong
gsstudios
Edit: Done. Thanks!
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.
Disclaimer: I am not responsible for anything bad that may occur with your device, but I will take all the credit you can give me if it works for you!
Finally, I would like to present first custom ROM for our device (Teclast T8)! It was ported by me from ASUS ZenPad 3S 10 Z500M and this firmware has lots of great features! It was tested for about a month before release, because I didn't want to share beta ROM with a lot of bugs/issues.
This version is only for flashing via TWRP! (it can be found here https://forum.xda-developers.com/android/help/twrp-root-custom-recovery-teclast-t8-t3892647)
Version Information
Status: stable (suits for everyday usage)
Created: 08.01.2019
Updated: 25.06.2020
Android version: kernel 3.18.35, android 7.0 Nougat
What's done/features
Added ROOT (Magisk)
No bugs with battery statistics (like it was on stock ROM)
Unique ASUS design and customization (icons, themes, etc)
New useful functions (split screen, quick launch apps on lockscreen, etc)
Advanced power/battery control tools
04.03.2020 - fixed issues with sound
25.06.2020 - fixed offline charge
Bugs
Double tap to awake function
Gestures on lockscreen
All other functions work great! (fingerprint, camera, etc)
Installation
Download firmware to internal storage
Reboot into TWRP
Do this wipes in Wipe section: system, cache, dalvik,data
Reboot recovery: go to reboot section -> choose Reboot recovery
Go to install section and choose .zip package
After installation completed just reboot device and enjoy
If you face error "failed to mount system" or something like this after installation completed - don't mind it and reboot
Screenshots
P.S After device is booted you can choose any language on system setup. I used MIUI icon pack here.
Download
The link is here - https://mega.nz/file/WxYTDSiI#tFXlrqjv3z9qgXI1aZoUM8NdTP99PvKI5eXJSmIeLEQ
If you would like to support further development - https://www.paypal.me/teclastT8development
Brilliant! Thank you Sword900 - GREAT JOB!
Thanks to the developer for this ROM and TWRP. It's a good device let down by lack of software support and removes all the Chinese native apps which I could not remove even with Titanium backup.
I was running TOS 2.0.1 but with a magisk patched boot image which I flashed a long time ago. This makes it simpler.
There are some issues with the TWRP but atleast I can update Magisk without having to patch the boot image and flash it every time.
The zip file in OP, the folder names have a comma after the number as pointed out earlier. Remove that before attempting any operations or you will face weird and wonderful behaviour.
Works like a charm !
I have problem with the sound. When i turn on the volume and play ssomething, i will hear annoying sound (ezzzzzz,,*%$)
zenacute said:
I have problem with the sound. When i turn on the volume and play ssomething, i will hear annoying sound (ezzzzzz,,*%$)
Click to expand...
Click to collapse
I too... any solutions?
zenacute said:
I have problem with the sound. When i turn on the volume and play ssomething, i will hear annoying sound (ezzzzzz,,*%$)
Click to expand...
Click to collapse
saddys said:
I too... any solutions?
Click to expand...
Click to collapse
Seems like I finally fixed it. You should install new version with all wipes listed, download link was updated. Let me know if you find any other issues.
How did you make this?
I'm trying to do the same with other Teclast tablets.(With P80X)
I would appreciate it if you could tell me.
(I used Google Translate)
few__ said:
How did you make this?
I'm trying to do the same with other Teclast tablets.(With P80X)
I would appreciate it if you could tell me.
(I used Google Translate)
Click to expand...
Click to collapse
I've just ported this ROM from another device with alike parameters (chipset, android os version, etc). There are lots of guides on the net which will help u. Another way is to find or make it manually kernel-source for your device, so u could compile firmwares on your own. But it requires appropriative knowledges in android development. Also u may take a closer look at GSI project as if your stock firmware is based on android 9.0.
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.