Related
Hi guys,
hope you might be able to help.
I was fiddling around trying to access my work emails from home yesterday and G mail asked me to install android device manager so that my work could control security protocols on my phone in case it was lost. It asked me to encrypt my device which i did and left it plugged in for a few hours while it did it's stuff. On reboot it loads into the usual registration stuff after installing a new ROM, but the keyboard is not usable it will only use speech recognition input and then the installer stops working.
All i really want is to get my photos off of my phone the rest is backed up to my g mail contacts list etc. can anyone help me out of this mess i made?
I will guess you have Archi 2.4. And about the photos, are they on the external SD crd or on the phone ? if they are on the SD card, then you can simply format everything and install another ROM (let's say archi 2.4.1 updated in the morning )
First I would try to download the Archi 2.4.1 to my SD card and flash it. (select in Aroma to update it, as you already have ArchiDroid installed). Flash it without wiping, first. It should install the element that are missing from the keyboard (I would reccomend to select in Aroma both keyboards. If one does not work, you have the other one).
If that does not work, flash the ROM again, now select that you don't have the ROM installed. And it will flash it entirely. Repeat the part with the keyboards.
Third solution would be to flash a stock ROM via Odin.
Come here and report on what you have done.
Hello I have made a very detailed video showing how to get Stock Samsung Lollipop (5.0.1) and CyanogenMod 12.1 (5.1.1) on the same phone [n910w8] dual booting.
THIS IS DONE AT YOUR OWN DESCRETION and I am not responsible if something goes wrong or you do something wrong. I have repeated the process at least 10 times to see how it works. Even did it on a Samsung Galaxy S4 with no issues.
This video is demonstrating the installation process for the Galaxy Note 4 n910w8 (Canadian snapdragon version used in video)
PLEASE TAKE YOUR TIME even watch the video a few times before you give it a try. In the end you can always flash stock Samsung Rom and do a factory reset.
I really enjoy using this feature and having the choice between two different roms on the same phone.
You can share apps from your stock Samsung Rom to your Cyanogenmod Rom without having to reinstall most of your apps. Saving lots of space.
I hope you enjoy.
Like.
Subscribe.
Click an add or two.
Thanks and a wonderful day.
Happy dual booting.
VIDEO LINK:
Samsung Galaxy Note 4 Dual Boot/multi Rom support:
https://youtu.be/CpegzNc4ZH0
Download Link Dual Boot Patcher:
https://snapshots.noobdev.io/
Download Link CM 12.1 (trltetmo) WORKING ON N910w8:
https://download.cyanogenmod.org/?device=trltetmo
Download Link Cyanogenmod Google Apps:
http://wiki.cyanogenmod.org/w/Google_Apps
Thanks:
chenxiaolong
Working on getting support brought to the Samsung Galaxy Tab S 8.4 also. Awaiting conformation, working with the developer. No garinties but fingers crossed that another top device gets dual boot compatibility.
Does anyone have a link to this build????
cm-12-20150413-NIGHTLY-trltetmo.zip
i keep trying on cyanogenmod website but the link is down.
If anyone could help it would be greatly appreciated.
It would really help with Google cardboar/vr testing. Native sbs is reported working on the rom I am looking for and it would be worth a try.
Nice mate
So by using FolderMount I am able to save so far 3gb of space on my data folder. I transfer app data to external SD card. Link the app data on external SD card with FolderMount which tricks the app into thinking it is installed on internal data.
Then I created a backup in FolderMount. Switch roms load FolderMount. Restore backup for FolderMount. Restore link app data locations because cm and touchwiz see external SD card different and FolderMount corrects this thankfully.
Click the green linking tab a few times and FolderMount will recognize the data.
As I said I have saved 3gb of room on my internal data having app data on external SD card.
If something like this was built into our dualboot patcher it would make things easier. Maybe if we spoke to the developer of FolderMount. If not using both FolderMount and Dual boot patcher I now have 3 roms on my Note 4 and almost 4gb free space on internal data between all 3 roms. Look at the pics of before in my previous comment and this one to see.
Just finding ways of maybe booting 4 roms on one phone.
Will report back.
Think I am on to something, let me know what you think. Give it a try possibly. I will be making a youtube video to help better demonstrate.
Before and after of data saved
My current Tri Boot state on my Note 4
Currently running Touchwiz stock lollipop 5.0.1 (primary partition), cm12.1(secondary partition) and cm12(data partition) all on the same phone.
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
samurai_vara said:
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
Click to expand...
Click to collapse
Try reinstalling cm12 and sharing again once you boot up.
Leonidas87 said:
Try reinstalling cm12 and sharing again once you boot up.
Click to expand...
Click to collapse
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
samurai_vara said:
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
Click to expand...
Click to collapse
Once you do those 3 steps all apps should share between both the primary and secondary Rom once you do a quick reboot after enabling the app sharing. Whenever you install a new app on one or the other Rom and then boot in to one of the roms you will usually see android upgrading or upgrading apps something like that during boot up. But yea you only need to enable app sharing in the second Rom not primary. Everything from the secondary Rom seems to share with the primary Rom. Overall it is a great system. Complicated in thought but it works. Once you get a feel for it you will be impressed.
Nice. I will try this when I get home. Been wanting to run CM but gear vr has me stuck on touch jizz. Will report how it works.
Sent from my SM-N910T using Tapatalk
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
chrisa887 said:
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
Click to expand...
Click to collapse
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Leonidas87 said:
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Click to expand...
Click to collapse
I see, I want the cm12 as my secondary rom so I patch it first then install it then I patch the gapps then install them then I can reboot to secondary rom and set everything up right?
Sent from my SM-N910T using Tapatalk
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Leonidas87 said:
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Click to expand...
Click to collapse
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Great job, thank you dev.
I have question about App Sharing. Should I install Gapps on both roms or only on Primary and share them?
chrisa887 said:
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yes patch then install. No need to reinstall Google apps all that will still be there.
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 a port of OMNIRom 6.0.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. OMNI is a minimalist ROM created by devs from the CM project.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
Though this is stable enough that I use it currently as my daily driver, make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on OMNIRom 6.0.1 MOB31K sources which is based on Marshmallow.
For more information on OMNIRom and its features see their site here.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Update Dec 8, 2016
===============
* Fixed sideloading apks from internal sd card
* Fixed selection of preferred network mode
* Enable soft navigation bar (googe now on tap should work with this)
* Adjust heap settings
Works:
- Wifi/LTE/SMS (Some users report data intermittently not connecting, though toggling airplane mode on/off can fix it)
- Audio
- Graphics with glitches (minor screen tearing, blank screen showing up on overlays)
- Camera (works if a third party camera app is used. Does not work on the stock camera app)
- Bluetooth
- GPS
- Wifi Hotspot
- Incoming/Outgoing Calls
- MTP
Does not work:
- Calls (Incoming)
-- MTP (Browse Only)
- probably more (need testers)
Bugs/Known Issues
* Bluetooth A2DP streaming issues when both bluetooth and Wifi is on and network traffic is occuring. There are reports that this also happens in order ROMs, not sure if stock also has this issue.
* Screen turns upside down for a brief moment when turning off the device.
* Unable to select preferred network mode e.g. LTE, 3G, 2G (fixed 12/08/2016)
* Error while entering USSD code in the dailer
* Unable to tap to install apks for sideloading (see workaround below)(fixed 12/08/2016)
* Problems recording video
Other Notes:
- selinux permissive
Most of the issues are fixable, I just need more time and encouragement
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty, Samsung representatives will probably not be able to help you as they are still stuck at 5.1.1 land as of now and have no idea how to handle a Sm-T285 that is running 6.0.1.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section for older releases. Or click below for the latest release:
Build Dec 9 2016
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
Workaround for apk install issue
=========================
Due to a possible bug with how sdcardfs is implemented in this device, apks downloaded externally and placed in external storage like Download show the apk is corrupt error when trying to install it.
however you can do a workaround by having root and doing the following:
1. Root your device (Download SuperSU and install via TWRP)
2. Download root file explorer
3. Using root file explorer move your apk to /data/local/tmp or create a folder under /data/local and move it there
4. Install the apk from that location and it should work.
Note that apps downloaded from the play store or install using "adb install" are not affected and works properly.
XDA:DevDB Information
OMNIROM 6.0 for the Galaxy Tab A 2016 7.0 LTE SM-T285, ROM for the Samsung Galaxy Tab A series
Contributors
jedld
Source Code: https://github.com/jedld/device_samsung_gtexslte
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: OMNIRom
Version Information
Status: Beta
Created 2016-10-28
Last Updated 2016-12-09
Thanks for releasing. Will definitely try it out if time permits.
I hope you will keep at this. This device needs marshmallow..
Great ROM! It is surprisingly usable, even at this stage of development, and feels far faster than stock. In addition to the bugs you mentioned, I also found out that apps will not install. Attempts at installation trigger a 'this package seems to be corrupt' error. Did anyone else encounter this problem?
acornkenya said:
Great ROM! It is surprisingly usable, even at this stage of development, and feels far faster than stock. In addition to the bugs you mentioned, I also found out that apps will not install. Attempts at installation trigger a 'this package seems to be corrupt' error. Did anyone else encounter this problem?
Click to expand...
Click to collapse
How are you installing it? via ADB?
jedld said:
How are you installing it? via ADB?
Click to expand...
Click to collapse
I've only tried using adb install and it seems to work fine.
jedld said:
How are you installing it? via ADB?
Click to expand...
Click to collapse
No, via Odin. I even thought I had made a mistake at some point during the installation process, so I repeated it twice, once with Gapps, and once without, but the problem persisted.
---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------
jedld said:
I've only tried using adb install and it seems to' work fine.
Click to expand...
Click to collapse
Hmmm...I'll try installing it via ADB, see if the problem will go away.
---------- Post added at 09:32 PM ---------- Previous post was at 09:31 PM ----------
And I can confirm MTP is indeed not working
---------- Post added at 09:40 PM ---------- Previous post was at 09:32 PM ----------
But for an initial release, this is surprisingly good.
jedld said:
This is a port of OMNI 6.0 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. OMNI is a minimalist ROM created by devs from the CM project.
5.1.1 is the best that you can get from samsung and it is not known if they plan to do any upgrades. This custom rom is probably the best you can get if you want an upgrade from Lollipop.
I don't recommend this for daily use as this ROM is to be used mainly for testing and contains a lot of bugs and features that don't work. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on OMNI 6.0 sources which is based on Marshmallow
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Works:
- Wifi/LTE/SMS
- Audio
- Graphics with glitches (minor screen tearing, blank screen showing up on overlays and app switching)
- Camera with issues (works if a third party camera app is used (OpenCamera). Does not work on the stock camera app and possibly some other apps)
Does not work:
- Calls
- Bluetooth
- GPS(?not too sure, need more testing)
- MTP
- probably more (need testers)
Other Notes:
- selinux permissive
Most of the issues are fixable, I just need more time and encouragement
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Download
========
Odin/Heimdall Flashable Zip: http://forum.xda-developers.com/devdb/project/dl/?id=21180
Installation Instructions:
If coming from stock, make sure you oem unlock first in developer settings. A full wipe is required so make sure you backup all your data.
Extract Zip and flash using ODIN or Heimdall. A TWRP recovery c/o @ashyx and repacked by me for the T285 is included in the package.
If you plan to install a GApps package it is recommended to do a full wipe so make sure you do that before you start using the device.
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
Special Thanks
===========
@ashyx - TWRP build
koquantam - work on the core33g provided an invaluable resource for porting the SM-T285 which is also a sc8830 device.
XDA:DevDB Information
OMNIROM 6.0 for the Galaxy Tab A 2016 7.0 LTE SM-T285, ROM for the Samsung Galaxy Tab A series
Contributors
jedld
Source Code: https://github.com/jedld/device_samsung_gtexslte
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: OMNIROM
Version Information
Status: Testing
Created 2016-10-28
Last Updated 2016-10-28
Click to expand...
Click to collapse
Many thanks for your hardwork jedld
build 20161104 is now available. GPS and bluetooth should now be fixed. Most of the hardware support for the SM-T285 seems to be working on a basic level, I am now attempting to use it as my daily driver.
Though bluetooth seems to work I haven't tested all possible bluetooth profiles yet, so keep your fingers crossed.
The remaining major issues are being unable to make/receive calls, Graphics overlay issues, being unable to play some video content in facebook (not sure if DRM related or Graphics related) and MTP.
There are also minor issues related to battery monitoring and screen flipping when going into low power mode.
I don't usually use this tablet to make/recieve calls so I am currently fixing graphics as a priority.
I use this tablet as a phone constantly so please get the calls working!! Great job so far!!!
jedld said:
build 20161104 is now available. GPS and bluetooth should now be fixed. Most of the hardware support for the SM-T285 seems to be working on a basic level, I am now attempting to use it as my daily driver.
Though bluetooth seems to work I haven't tested all possible bluetooth profiles yet, so keep your fingers crossed.
The remaining major issues are being unable to make/receive calls, Graphics overlay issues, being unable to play some video content in facebook (not sure if DRM related or Graphics related) and MTP.
There are also minor issues related to battery monitoring and screen flipping when going into low power mode.
I don't usually use this tablet to make/recieve calls so I am currently fixing graphics as a priority.
Click to expand...
Click to collapse
1. Great job! In the course of testing, I bumped into a very odd problem; apps from the Play Store install just fine, but the apks I have saved on both the internal memory and the memory card will not. Has anyone else encountered a similar problem? How do I solve it? Thanks in advance. I installed the ROM via Odin
2. The WiFi hotspot is not working
acornkenya said:
1. Great job! In the course of testing, I bumped into a very odd problem; apps from the Play Store install just fine, but the apks I have saved on both the internal memory and the memory card will not. Has anyone else encountered a similar problem? How do I solve it? Thanks in advance. I installed the ROM via Odin
2. The WiFi hotspot is not working
Click to expand...
Click to collapse
Nice catch on the wifi hotspot.
For the apk installation problem, yes I am able to replicate it, turns out to be some permissions I incorrectly set for the filesystem, will investigate. However note that using adb install works fine.
jedld said:
Nice catch on the wifi hotspot.
For the apk installation problem, yes I am able to replicate it, turns out to be some permissions I incorrectly set for the filesystem, will investigate. However note that using adb install works fine.
Click to expand...
Click to collapse
I tried installing both the previous and current releases using adb, but for some reason, that didn't work.
I suspect the problem is at my end, though. I'll use another computer, see if that will solve the problem.
Thanks for the prompt response, and for the work that you're doing.
New build released for 11132016, main fixes are wifi hotspot, outgoing calls and partial MTP fix (still broken though).
I use this phone for business..when you fix for incoming phone calls...I'm downloading!!! Thanks for your hard work
corzradio said:
I use this phone for business..when you fix for incoming phone calls...I'm downloading!!! Thanks for your hard work
Click to expand...
Click to collapse
Or tell people not to call you and you will call them. I just discovered a bug where it won't hang up though so they have to hang up first
jedld said:
New build released for 11132016, main fixes are wifi hotspot, outgoing calls and partial MTP fix (still broken though).
Click to expand...
Click to collapse
1. Compared with the previous build, scrolling feels faster
2. A personal favorite; it is possible to enable softkeys without triggering system UI errors
3. Just like in the previous build, apks stored on the internal memory or microSD will not install if the ROM is loaded via Odin. Apps from the Play Store install just fine, though, and the problem completely disappears when the ROM is installed via ADB
For the Nov 21 release, all major issues have been fixed except for MTP. Graphics issues have also been fixed, expect a major performance boost, No promises but the user experience should be superior to that of stock, and I haven't even compiled for a release build yet. This release should be good enough as a daily driver assuming its ok for you to have SeLinux in permissive mode.
what.....
jedld said:
For the Nov 21 release, all major issues have been fixed except for MTP. Graphics issues have also been fixed, expect a major performance boost, No promises but the user experience should be superior to that of stock, and I haven't even compiled for a release build yet. This release should be good enough as a daily driver assuming its ok for you to have SeLinux in permissive mode.
Click to expand...
Click to collapse
does that mean "SeLinux in permissive mode"?
corzradio said:
does that mean "SeLinux in permissive mode"?
Click to expand...
Click to collapse
It will be hard to go into details, but to make it simple it is less secure than a build with with selinux enabled. Since this is still a development build if security equivalent to stock is a concern of yours, I suggest waiting until I compile a proper release build.
how do i...
jedld said:
For the Nov 21 release, all major issues have been fixed except for MTP. Graphics issues have also been fixed, expect a major performance boost, No promises but the user experience should be superior to that of stock, and I haven't even compiled for a release build yet. This release should be good enough as a daily driver assuming its ok for you to have SeLinux in permissive mode.
Click to expand...
Click to collapse
get google play or google play services to load? every gapps i try it wont load. please help!
Hi All,
sharing the guide to install the multiple Rom's in our Axon 7 (as we don't have multi-boot in place).. as the development already kicked with Noughot.. and multiple roms are landing here...
this is for people who can't move out of Stock (due to Audio issues including me) and want to sneak peak the other LOS based roms.
Dual Boot Patcher is an app created by chenxiaolong for S4 initially and it broadly supports more than 150 devices now, whoever used in S4 would be familiar with it.. this app allows you to have multiple ROMs on a single device.
If you loved his work, go to his thread say Thank You
Axon 7 is official supported
I have tried with RR as Secondary and it's working.. so thought of sharing this.
For More details on this Dual Patcher official Thread:
https://forum.xda-developers.com/showthread.php?t=2447534
Working:
- patch ROM zip files
- patch GAPPS zip files
- patch SuperSu zip files
Instructions: More details
Keep the Stock Rom as always Primary.
Use the Data slot and create a name for the folder, as the System/Cache space will be small for LOS Rom
If you want to flash the LOS, RR roms remove the below script in the update-script (ROM\META-INF\com\google\android)
Code:
assert(getprop("ro.product.device") == "ailsa_ii" || getprop("ro.build.product") == "ailsa_ii" || getprop("ro.product.device") == "axon7" || getprop("ro.build.product") == "axon7" || abort("E3004: This package is for device: ailsa_ii,axon7; this device is " + getprop("ro.product.device") + "."););
assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");
ui_print("Target: ZTE/P996A01_N/ailsa_ii:7.0/NRD90M/20170128.052618:user/release-keys");
Issues:
- Encryption and Boot UI are not supported
- trustzone verification in the Update-script will fail while flashing the TWRP, remove the above code before flashing the zip file.
- Pins, patterns or passwords are wrong in one of the ROMs . Then simply delete the file /data/system/locksettings.db (your saved fingerprints won't be lost) with TWRP.
Warning: for me setting the PIN in one rom works, if i enabled PIN in 2 roms it's not working, everytime you have to delete the locksettings.db and boot into other rom. Fingerprint works in 2 ROMS
- if In-app flashing doesn't work, you have to use TWRP to flash the patched zip files (use the latest TWRP)
- If flashing of a patched zip fails for any reason, you have to choose another install location ("Partition Configuration" in the app) when patching the same zip file again!Note: If flashing fails, first look up the error at /sdcard/MultiBoot.log and google it before reporting it...
Download
Download Dual Boot Patcher APP
Download Dual Boot Utilities
Credits to:
@chenxiaolong - for the great app and supporting till date.
@jimbo77 - for making Dual boot Axon 7 official support
@Glove007 - for additional details on workaround for Op3 - applies to Axon7
XDA Community
if i missed any plz let me know.
i can't find anyother thread related to this Dual Patacher, if it's available please merge the thread.
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Nik2424 said:
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Click to expand...
Click to collapse
No you won't lose any data when you flash this.. (But take a backup for safety)
Plz follow this steps.
Install the Dual patcher app and set the current Rom as primary
Make sure you patch the second Rom and Gapps (Super SU optional) in the Dual Patcher App before flashing in TWRP (or it will overwrite the Primary ROM)
in the patched rom remove the TrusstZone entries as mentioned in OP
then flash it via TWRP.
the Rom will be added to your Data or Cache based on the selection you made while patching the Zip file in the Dual Patcher (Preferable is data slot, and rom will be saved in Data>multiboot).
once logged in the Second rom, use the patcher to set the Rom as secondary.
when you want to switch rom, select the rom in the Dual Patcher app and reboot. (the app will move the correct boot.img to partion and selected rom will boot. )
if you want to Wipe Primary Rom or Second/Third Rom use the Dual Boot Utilities in the TWRP, this will wipe only the specified rom and you Second/third Rom won't get deleted. (if you wipe data/cache using TWRP menu, it will wiped your Second/third roms)
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Nik2424 said:
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Click to expand...
Click to collapse
those are added in the Rom to validate you're flashing in the right firmware.. like Noughot roms shouldn't be flashed in MM firmware.
Nothing wrong here in removing in those lines during flashing as secondary Roms..
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
I edit the update-script and remove the quoted lines
I install the dual boot patcher app
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs.
I boot to both ROMS and select stock as primary and LineageOS as secondary
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
Does this seem about right?
Thanks.
So glad this got brought to our phone
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
you should patch with Dual Patcher APK... -- Dual Boot utilities will be flashed in TWRP to install/wipe/update Primary Roms without impact to other Roms.
I edit the update-script and remove the quoted lines - yes
I install the dual boot patcher app - in primary Rom, yes
Open the App, give Root permission - it will prompt you for making the kernel as Primary, set it now - this is required so that App can switch between multiple Roms
1. basically the App will copy the boot.img of primary into storage>multiboot>primary
2. when you install the secondary rom and boot it up, install the app set the rom as secondary.
3. it will copy the secondary rom boot.img in to the same folder
4. whenever you switch rom, the app will copy the switched roms's boot.img to the Boot partiion so that corresponding rom will start on reboot
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
In-app flashing is failing for me, use TWRP to flash it.
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs. - yes
I boot to both ROMS and select stock as primary and LineageOS as secondary
Set the Primary when you installed the App in primary Rom itself.
and set the secondary when installed the app in secondary rom
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
I doubt App sharing is working correctly, please try and let me know
hope this helps
Does this seem about right?
Thanks.
Worked!
Great, this workd for me thanks!
thank you so much for this post
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Sebastian Fox said:
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Click to expand...
Click to collapse
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
`SBR` said:
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
Click to expand...
Click to collapse
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
mvortex3710 said:
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
Click to expand...
Click to collapse
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
`SBR` said:
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
Click to expand...
Click to collapse
Thanks very much for your fast reply.
When I checked the main thread it seems like this problem may be caused by not flashing a patched kernel as well, so I will try that presently and report back!
Edit: The patched kernel I'm using (AX7Kernel) is returning the error: "unable to find boot block location!", I've tried googling it but haven't found anything. Would you happen to know what might be causing this? Flashing in TWRP seems to have fixed this. Attempting boot now.
Edit 2: Boot didn't succeed, I was faced with 5 vibration then a restart to TWRP, where I used the Dual Boot utilities to change back to my Primary (stock) boot.
I'm going to try the other way round, with RR as primary and Stock as (secondary) data boot.
`SBR` said:
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
Click to expand...
Click to collapse
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Sebastian Fox said:
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Click to expand...
Click to collapse
thats not possible...
`SBR` said:
thats not possible...
Click to expand...
Click to collapse
Oh then it seems we reached a blocked road, is there anyway to convert the stock to f2fs??? Partitioning data???
I will try partitioning if possible but it's useless if the dualboot app/utility doesn't support it.
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Nik2424 said:
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Click to expand...
Click to collapse
for me i'm able to ptach RR and it's working in data slot..
did you try to install anything after patched RR and patched Gapps?