Database Develop

How to dualboot KitKat and Android 5.0 Lollipop on Nexus 5

This is a guide of how to dualboot KitKat and Android Lollipop on a Nexus 5. This will allow you to test out Lollipop while keeping a stable ROM to run as a daily driver. I am running CM11, but you can do this with any KitKat ROM, even stock.​
REQUIREMENTS
Nexus 5
Root
Unlocked bootloader
MultiROM
A brain
At least 1 GB of free space (I recommend 4 GB though)
1. Setting up.
I'm assuming you are already rooted if you are planning on doing this. If not, follow this guide to root and unlock the bootloader. http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-cf-auto-root-t2507211
1. After verifying you have root on your phone, download MultiROM Manager off Google Play: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=en
2. Install and open MultiROM Manager and install MultiROM, Recovery and the patched kernel.
Here is what the following is...
MultiROM: This boots before the system and gives you the option of what system you want to boot. When you select the system, it then hands it off to boot. This will not overwrite your current ROM, but make a backup to be safe
Recovery: This is a custom TWRP recovery with options to install a secondary system
Kernel: This will patch your kernel with kexec-hardboot patch which is requires to dualboot in general.
2. Installing Android Lollipop
1. After you install and verify that MultiROM is installed on your phone, download the Android 5.0 flashable zip from the downloads section at the bottom
2. Reboot into the recovery and go to Advanced> MultiROM> Add ROM
3. When you get there, set ROM type to Android and select "Dont share" for kernel sharing and then press next
4. select ZIP file and install "N5_L_PREV_LPX13D.zip" you downloaded earlier and flash it.
If you wish to not root L, you can go ahead and reboot your phone into Lollipop (The first boot will take several minutes). If you do want to root, go on to the next step. Your primary ROM won't be touched as your primary ROM and its root status won't be affected when using MultiROM.
3. Rooting Android Lollipop (optional)
Rooting is completely optional and is not required for it to run. You need to install root if you do plan on using root apps or busybox on Android 5.0.
As of the LPX13D build, there have been changes made in the bootloader that will prevent SuperSU or root from working. If you want to root on the LPX13D build, you will need to flash this bootloader: http://www.reddit.com/r/Nexus5/comments/2jkx7a/
1. Download the SuperSU zip in the downloads section and save it to your phone.
2. Boot into recovery and go to Advanced> MultiROM> List ROMs and select the L ROM you installed earlier (unless you renamed the zip file or the system name, it should show"N5_L_PREV_LPX13D")
3. Select flash zip and flash the SuperSU zip you downloaded.
4. Reboot and you should now be rooted.
Updating Android Lollipop
As of right now, there are issues if you try to do a dirty flash from DP1 to DP2 (These are issues with Android L and not MultiROM). These issues include home button not working, quick settings pulldown not working, no lockscreen when there is one and data issues (at least with Sprint). If you are coming from LPV79 and updating to LPV81C or LPX13D, it is recommended to do a clean install to avoid these issues. If you are doing a fresh install, you don't have to worry about this issue
Android Lollipop Bugs
These are issues with Android Lollipop and not MultiROM
-The issues stated above when certain things don't work after a dirty flash
-During the inatial setup, the phone may freeze and require reboot when trying to connect to wifi (seems like a new bug with LPV81C). The phone will say Connecting and show a white box before it freezes
-Some apps will crash or be buggy (this is to be expected though with the transition to ART)
-More bug reports can be found [Here]
-A list of apps that have issues with working with Android L can be found [Here]
Downloads
Android Lollipop flashable zip: http://forum.xda-developers.com/showpost.php?p=56112246&postcount=5498
L Root: http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
Thanks
Chainfire for CF Autoroot and SuperSU
Tasssadar for MultiROM to make this dualboot possible
davy917 for posting a solution for people having internal storage issues with L
For more information and general use of how MultiROM works, go to its main thread [here]
Also if you do have the issue where your internal storage doesn't mount, follow this solution found [here]

Thanks! First time trying multiROM & working great

In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?

davy917 said:
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
Click to expand...
Click to collapse
Strange. I didn't have that problem but I will look in to it. I recommend going to advanced> MultiROM> list ROMs and perform a wipe of the cache and dalvik of your L system. I was able to download without problems and the internal storage worked fine. Also, how much space was there on your phone before doing this
Sent from my Nexus 5 using Tapatalk

I can't boot to L. Says I need a kexec-hardboot enabled kernel.
Sent from my Nexus 5

Elisha said:
I can't boot to L. Says I need a kexec-hardboot enabled kernel.
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, you need a kernel that has that patch included to be able to use MultiROM. There are a few of them if you look around.
---------- Post added at 01:53 AM ---------- Previous post was at 01:53 AM ----------
davy917 said:
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
Click to expand...
Click to collapse
L does sdcard differently

ThatGuy94 said:
Strange. I didn't have that problem but I will look in to it. I recommend going to advanced> MultiROM> list ROMs and perform a wipe of the cache and dalvik of your L system. I was able to download without problems and the internal storage worked fine. Also, how much space was there on your phone before doing this
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Lethargy said:
L does sdcard differently
Click to expand...
Click to collapse
Do you know how I can access the files in my sdcard?

davy917 said:
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Do you know how I can access the files in my sdcard?
Click to expand...
Click to collapse
You'll have /system/sdcard/0/ and /system/sdcard/

davy917 said:
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Do you know how I can access the files in my sdcard?
Click to expand...
Click to collapse
Just wondering, what is your baseband version. I'm just thinking if it may be a firmware issue for some reason. Also try ES File Explorer to see if your files show up in it because my files in sdcard appeared with it
Sent from my Nexus 5 using Tapatalk

Lethargy said:
You'll have /system/sdcard/0/ and /system/sdcard/
Click to expand...
Click to collapse
I don't see such directories.. No sdcard folder in system
---------- Post added at 01:50 PM ---------- Previous post was at 01:49 PM ----------
ThatGuy94 said:
Just wondering, what is your baseband version. I'm just thinking if it may be a firmware issue for some reason. Also try ES File Explorer to see if your files show up in it because my files in sdcard appeared with it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am using ES Explorer but no luck
My baseband is M8974A-2.0.50.1.13
When I tried to take a screen shot, I got an error saying cannot save screenshot, storage may be in use. Any idea what the deal is?

davy917 said:
I don't see such directories.. No sdcard folder in system
Click to expand...
Click to collapse
In KitKat, try to find /mnt/shell/emulated/0 or /sdcard in L
Sent from my Nexus 5 using Tapatalk

I can find both, but in L the folders in /sdcard are all empty

davy917 said:
I can find both, but in L the folders in /sdcard are all empty
Click to expand...
Click to collapse
Are they empty if you try to open them in KitKat? Also it looks like your baseband is out of date. I have the baseband M8974A-2.0.50.1.16. I recommend updating your baseband to see if it fixes it. Also what is your primary ROM
Sent from my Nexus 5 using Tapatalk

ThatGuy94 said:
Are they empty if you try to open them in KitKat? Also it looks like your baseband is out of date. I have the baseband M8974A-2.0.50.1.16. I recommend updating your baseband to see if it fixes it. Also what is your primary ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's not empty when I open in KK.. I'm running SlimKat
I'll try updating my baseband and see if it helps. Thanks for all the suggestions!

davy917 said:
It's not empty when I open in KK.. I'm running SlimKat
I'll try updating my baseband and see if it helps. Thanks for all the suggestions!
Click to expand...
Click to collapse
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk

ThatGuy94 said:
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah I think I'll just try starting over.. Nothing seems to work. I basically don't have any access to storage when on Android L as my secondary. I can't even take photos lol it takes a pic and can't save anywhere

davy917 said:
Yeah I think I'll just try starting over.. Nothing seems to work. I basically don't have any access to storage when on Android L as my secondary. I can't even take photos lol it takes a pic and can't save anywhere
Click to expand...
Click to collapse
There have read people in the Android L thread that have had this same issue. That's why I always thought dual booting with Android L wasn't a good idea.

Got some help from the multirom thread.. Followed the below and it worked fine. Had to reinstall Android L afterwards tho.
1. Install terminal from play store in Android L ROM.
2. In terminal: "su" *enter*
3. In terminal: "restorecon -FR /data/media/0" *enter*
4. Wait.*
5. Reboot.
*If it doesn't boot anymore, delete Android L as ROM, and flash it again trough multirom.

ThatGuy94 said:
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Slimkat is AOSP/stock kernels.... Not CM11/caf. ?

KJ said:
Slimkat is AOSP/stock kernels.... Not CM11/caf. ?
Click to expand...
Click to collapse
Thanks for the correction. I don't use slimkat so I thought it was using the cm11 kernel.
Sent from my Nexus 5 using Tapatalk

[ROM] SPH-L720 OK3 Stock Deodexed

This is my first ROM for public use.
I used SuperR kitchen to deodexed and deknoxed.
* USB DEBUGGING Enabled by default.
* R/W fixed in permission for ExtSdCard
That's it no other tweaks...
Thanks to
@SuperR. for his kitchen-here
@bilgerryan for keeping the S4 alive!
To install the ROM
1. copy the zip to the extSdCard
2. TWRP recovery
3. Go into recovery mode.
4. Wipe Dalvik, Cache, system, data.
5. Perform factory reset before installing zip
6. Install zip.
7. Reboot.
This has been tested on SPH-L720
If you download press the thanks button.
DOWNLOAD ROM-here
OK3 Kernel Download -here
OK3 Modem Download (Flash with Odin)-here
[MOD] Hotspot Mod (My first Mod)
1. Make a nandroid backup!!!
2. Flash zip in recovery
3. Wipe cache and dalvik cache
7. Reboot
Hotspot-Mod Download-here
[MOD] Recent Apps Mod
This will add a recent apps shortcut to the pulldown statusbar.
1. Make a nandroid backup!!!
2. Flash zip in recovery
3. Wipe cache and dalvik cache
7. Reboot
Recent Apps Mod Download-here
More mod and links -here

About device screenshots

OK3 kernel Download updated.
Has Anyone flashed this Rom? Is everything fine?
My first rom just curious.

Did they touch the modem in the OK3 update or is it the same as OH1/OD2?

nismotigerwvu said:
Did they touch the modem in the OK3 update or is it the same as OH1/OD2?
Click to expand...
Click to collapse
I'm not sure. I Odin the OK3 Stock tar. So I'm really not positive but I think they did.
EDIT. Yes they did.

nismotigerwvu said:
Did they touch the modem in the OK3 update or is it the same as OH1/OD2?
Click to expand...
Click to collapse
It's really impossible for us to know as Samsung does not release any information on the modem.

OK3 Modem tar download added to OP in case someone needs it

My first Mod Hotspot-Mod Download link updated in OP. Please give feedback as I am still learning.. lol

I Gave It a Go...
I tried installing it this evening. Loaded just fine. But, I couldn't get the WIFI to turn on. But, I attempted to load all three of your modules at the same time: ROM, Kernel & Hot-Spot Mod. Some other stuff (kids!) came up, so I had to restore from my Nandroid Backup and move on. If I get some time tomorrow, I'll try them one at a time (in order) and let you know how that goes. Thanks for doing this.

dsjxxxxx said:
I tried installing it this evening. Loaded just fine. But, I couldn't get the WIFI to turn on. But, I attempted to load all three of your modules at the same time: ROM, Kernel & Hot-Spot Mod. Some other stuff (kids!) came up, so I had to restore from my Nandroid Backup and move on. If I get some time tomorrow, I'll try them one at a time (in order) and let you know how that goes. Thanks for doing this.
Click to expand...
Click to collapse
Try flashing modem with odin.
Sent from my SPH-L720 using Tapatalk

[MOD] Recent Apps Mod
[MOD] Recent Apps Mod
This will add a recent apps shortcut to the pulldown statusbar.
1. Make a nandroid backup!!!
2. Flash zip in recovery
3. Wipe cache and dalvik cache
7. Reboot
Download
https://www.androidfilehost.com/?fid=24391638059058192

Downloaded modem zip and it's labeled as an md5 but it's 60mb is this just a typo?

knoc said:
Downloaded modem zip and it's labeled as an md5 but it's 60mb is this just a typo?
Click to expand...
Click to collapse
Its not a zip file. Modem must be flashed with odin.

When I load.it through mobile Odin it uses modem 1 and modem2 slot..I'm on cm13 oh1 I can just flash through mobile Odin can't I?

knoc said:
When I load.it through mobile Odin it uses modem 1 and modem2 slot..I'm on cm13 oh1 I can just flash through mobile Odin can't I?
Click to expand...
Click to collapse
No, Mobile Odin hasn't worked since Jelly Bean.

It Works! It Works With Xposed!
Yes. I needed the modem. Everything works great - including Xposed. Thanks!!!
For those who need it, I provide a summary of the steps I took that resulted in success.
Base OK3 Install
1) Installed the OK3 ROM (SPH-L720_OK3_Stock_Deodexed.zip) using TWRP, following the 7 steps listed in katodragon's original post (including reboot).
- The phone took ~15 minutes on the Samsung splash screen (black background with pseudo fireworks coming out of the logo) to set up. Patience is required.
- No wifi. The ROM could not turn on the radio. The slider would hang halfway to on. If I backed out and went back to the setting, it was clearly "off."​
2) Installed the OK3 Kernel (SPH-L720_Stock-Deodexed-kernel.zip) using TWRP.
- I did perform another factory reset with TWRP just before installing the zip using TWRP, then rebooted. I did not wipe the system partition, though.
- Still no wifi. Same deal.
- I'm not sure if the kernel is necessary. But, everything is working well for me WITH the kernel. Enough said.​
3) Installed the OK3 Modem (OK3_Modem.tar.md5) using ODIN.
- Followed the usual process: phone in download mode, selected "AP" in ODIN, et cetera.
- Success! Everything - including wifi - has worked well since.
- Performed a NANDROID Backup using TWRP at this point, but I have not had to restore from it.​Xposed Install
1) Side-loaded "Xposed Installer" (XposedInstaller_3.0_alpha4.apk).
- Just for chuckles, I tried to fire it up. In failing, the app asked if the Xposed Framework was install (it wasn't).​
2) Installed "Xposed Framework" (xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC.zip) using TWRP.
- This time, I did not clear anything before installing the zip (because it isn't a ROM).
- My first attempt failed, but I received a clear report (in bold red letters) that I needed to use the "ConcurrentGC" version of the framework. The successful file is referenced above.
- Rebooted.
- Success! I have installed several (~12) Xposed Modules since. Mostly side-loaded, but a few from the Play Store. Zero issues.​
Xposed Notes
- Resources I Found Helpful
a) Announcement w/ Directions (rovo89): http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
b) HighonAndroid (Max Lee): http://highonandroid.com/android-ap...ed-installer-on-android-lollipop-5-05-15-1-1/
c) Xposed Module Repository: http://repo.xposed.info/module-overview
d) Wanam's Xposed Module Repository: http://repo.xposed.info/users/wanam
This is where I scored "Wanam Xposed for Android 5.x.x."​
- Xposed Installer (rovo89): http://forum.xda-developers.com/showthread.php?t=3034811
- Xposed Framework (arter97): http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
Thank You to KATODRAGON
Again, thanks to katodragon for the deodexed ROM for the SPH-L720! It's been about five months since I upgraded to Lollipop. And, that means five months without Xposed. Thanks to him, I'm back to where I want to be.
---------- Post added at 09:25 PM ---------- Previous post was at 09:22 PM ----------
katodragon said:
Its not a zip file. Modem must be flashed with odin.
Click to expand...
Click to collapse
I successfully installed the OK3 Modem file as-is (including the MD5 extension) using ODIN v3.10.6 (Windows 10 Pro desktop PC).

^^^ Great Post ^^^ Glad it working for you! Which exposed modules are u using?
Sent from my SPH-L720 using Tapatalk

katodragon said:
^^^ Great Post ^^^ Glad it working for you! Which exposed modules are u using?
Click to expand...
Click to collapse
Current Modules (all working - no issues):
3C Toolbox Pro v1.6.9
AdBlocker v1.4
Fix Lollipop Memory Leak v1.2
Greenify v2.7.1 (highly recommend this app)
Magnet Sensor Control v1.1
No Lock Home v2.0.1
Play Store Link in App Info v1.0
SwiftKey Goodness on More Fields v1.0
Wanam Xposed for 5.X.X v1.3.0 (highly recommend this app)
Waze Audio Interceptor v1.0 (not tested yet)
WiFi Filter v1.0.1
XInstaller v5.0 (not all functions work - but not causing any problems either)
Xposed Torch v2.1.1​
I also have Secure Settings v1.3.6, but it is not detecting the presence of Xposed. So, I can't used the one Xposed function in the app. It's not a function that I'm looking to use, so I decided not to mess around with it. But, I'm guessing that the problem MIGHT be fixable by CAREFULLY uninstalling the app, then reinstalling it. My hypothesis is that the problem stems from Secure Settings being installed before Xposed. Something that I left out of my last post is that I restored (Titanium Backup) all of my apps and data after completing the OK3 install but before I attempted to install Xposed.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
katodragon said:
[MOD] Recent Apps Mod
This will add a recent apps shortcut to the pulldown statusbar.
1. Make a nandroid backup!!!
2. Flash zip in recovery
3. Wipe cache and dalvik cache
7. Reboot
Download
https://www.androidfilehost.com/?fid=24391638059057708
Click to expand...
Click to collapse
I was going to give this mod a try. When I clicked the download link, I got a message saying that the file has been deleted.
FYI. I decided not to try out the Hotspot Mod because I use Ting (a less-expensive way to use the Sprint network) as my carrier. Ting lets me use the native hotspot capability for no extra charge.

Sorry. Try the link in the first post. I forgot to update that one.

dsjxxxxx said:
Current Modules (all working - no issues):
3C Toolbox Pro v1.6.9
AdBlocker v1.4
Fix Lollipop Memory Leak v1.2
Greenify v2.7.1 (highly recommend this app)
Magnet Sensor Control v1.1
No Lock Home v2.0.1
Play Store Link in App Info v1.0
SwiftKey Goodness on More Fields v1.0
Wanam Xposed for 5.X.X v1.3.0 (highly recommend this app)
Waze Audio Interceptor v1.0 (not tested yet)
WiFi Filter v1.0.1
XInstaller v5.0 (not all functions work - but not causing any problems either)
Xposed Torch v2.1.1​
I also have Secure Settings v1.3.6, but it is not detecting the presence of Xposed. So, I can't used the one Xposed function in the app. It's not a function that I'm looking to use, so I decided not to mess around with it. But, I'm guessing that the problem MIGHT be fixable by CAREFULLY uninstalling the app, then reinstalling it. My hypothesis is that the problem stems from Secure Settings being installed before Xposed. Something that I left out of my last post is that I restored (Titanium Backup) all of my apps and data after completing the OK3 install but before I attempted to install Xposed.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I was going to give this mod a try. When I clicked the download link, I got a message saying that the file has been deleted.
FYI. I decided not to try out the Hotspot Mod because I use Ting (a less-expensive way to use the Sprint network) as my carrier. Ting lets me use the native hotspot capability for no extra charge.
Click to expand...
Click to collapse
Here are my Xposed Modules
--APM+ (I like that you can use the screen record function)
--Downloads2SD
--Fix Lollipop Memory Leak (not sure if I still need this with OK3)
--Greenify with donation features
--Wanam Xposed
--YouTube AdAway

SuperSU system install.

Hey guys, quick question. I saw that there was a specific command to type to make newer SuperSU install in system mode, how and where do you actually type this command? I think someone said you type that command in TWRP, but I need details, never used a command in TWRP before. Thanks guys! Much appreciated!
Also, I hope I posted this in the right place, wasn't sure if I should have posted this in the Nexus 6 forum because it's what I'm working with, or in SuperSU because it's kind of a general question. Thanks again!

Have a look at this - http://forum.xda-developers.com/showpost.php?p=66321818&postcount=5659
BUT...
If you've never done it before, you're asking for trouble. There are others in the thread reporting that after playing with this their device didn't boot. It hardly seems worth the aggravation, does it...?

If you want system root just install SuperSu 2.65 in recovery. It is the *stable* release, not beta or alpha and installs in system mode with no further modifications necessary.

http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
---------- Post added at 20:31 ---------- Previous post was at 20:29 ----------
Dopamin3 said:
If you want system root just install SuperSu 2.65 in recovery. It is the *stable* release, not beta or alpha and installs in system mode with no further modifications necessary.
Click to expand...
Click to collapse
AFAIK this is not completely correct. If you flash 2.65 it will check first if system root is possible. If not it will root systemless.

dahawthorne said:
Have a look at this - http://forum.xda-developers.com/showpost.php?p=66321818&postcount=5659
BUT...
If you've never done it before, you're asking for trouble. There are others in the thread reporting that after playing with this their device didn't boot. It hardly seems worth the aggravation, does it...?
Click to expand...
Click to collapse
Do you have to navigate to where your SuperSU zip is located?

Droidphilev said:
http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
---------- Post added at 20:31 ---------- Previous post was at 20:29 ----------
AFAIK this is not completely correct. If you flash 2.65 it will check first if system root is possible. If not it will root systemless.
Click to expand...
Click to collapse
I don't think so. It clearly says in the thread you linked "This is SuperSU that always installs in System-Mode." Literally the first sentence in that thread you linked to. From my understanding SuperSu 2.65 is system root stable and 2.68 is system root beta. Other versions may be systemless, but these are definitely not.
Further what would make it fail system root on the Nexus 6? A kernel I guess? Not sure on that.

@H4X0R46 "Do you have to navigate to where your SuperSU zip is located?"
Sorry, I have no idea, since I'm not brave enough to risk bricking my $700 phone. Chainfire's programming is of a standard that I trust to make the best choice for rooting my device, and he hasn't let me down yet.

dahawthorne said:
@H4X0R46 "Do you have to navigate to where your SuperSU zip is located?"
Sorry, I have no idea, since I'm not brave enough to risk bricking my $700 phone. Chainfire's programming is of a standard that I trust to make the best choice for rooting my device, and he hasn't let me down yet.
Click to expand...
Click to collapse
I'd imagine worst case scenario you would have to flash a stock image, but you make a good point! Regardless of the type of install, it has always worked! Thanks for the reply!
Sent from my Nexus 6 using Tapatalk

Dopamin3 said:
I don't think so. It clearly says in the thread you linked "This is SuperSU that always installs in System-Mode." Literally the first sentence in that thread you linked to. From my understanding SuperSu 2.65 is system root stable and 2.68 is system root beta. Other versions may be systemless, but these are definitely not.
Further what would make it fail system root on the Nexus 6? A kernel I guess? Not sure on that.
Click to expand...
Click to collapse
In your post you didn't mention that you were talking about the same thread as me that's why i answered. The official supersu 2.65 works as i wrote (systemless only when system root is not possible). Check Chainfire's changelog. The thread i have mentioned is unofficial and made by someone else. Last official version that has no systemless root is 2.52
EDIT: about your question how Supersu decides to use systemroot/systemless: this is what Chianfire writes about it:
"ZIP: 6.0+: Detect firmwares that can reload sepolicy from /data and use system-based root on these ("allow init kernel:security { load_policy }")"
and
"Notes on 2.64+
There have been a lot of changes to the ZIP installer. Hopefully they won't break a lot of installs. If 2.64 works well, it is likely to be promoted to the "main beta" in place of 2.52, and the How-To SU document will be updated with the relevant information.
A major change in setup is that the ZIP installer will try to detect 6.0 firmwares that can be rooted without doing a systemless install. In other words, a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu"). This may catch (a) firmwares that allow sepolicy reloading from /data but have a locked bootloader and (b) custom firmwares setup to handle this. Regarding the latter, while it is not as clean as systemless, those running custom firmwares are more likely to want to modify /system anyway, it is less likely to mess with updates to those firmwares, and it prevents the necessity of reflashing the ZIP after each kernel switch. Of course, the kernel's SELinux policies must support this!"

Can't Login To Snapchat After Rooted

So, I rooted my Zenfone 2 with LineageOs Android 7.1. I could login to Snapchat, it was all cool even though my phone got slower. Then I installed a 3rd party Snapchat app, ''Casper.io'' and logged in to that with my Snapchat ID and password which got me logged out on the official Snapchat app. I uninstalled the 3rd party app, did whatever Snapchat told me to, I reinstalled the official app too. I couldn't login, it's failed. Then I tried to login to my account in a different device. It was successfull. And I don't know what to do now. Read some posts about Xposed Framework etc. There's no Xposed Framework for Android 7. Anybody can help please? It'll be much appreciated.
Thank you.

You need to temporarily disable root to log in to Snapchat. Once you're logged in you're OK.

Same !! did u resolve the issue?

Remove root, clear data on SC, login to SC and verify, re-root phone, create backup of SC so you can restore the logged in version in the future.

Use titanium backup to backup once ur into snapchat and u can restore the backup without logging in, even if you dont pass the safety net.

Snapchat has implemented SafetyNet to its app, which need a special root to access Snapchat, so to access Snapchat:
**WARNING** Your warranty is now void when rooting your phone/tablet! Backup your everything using TWRP cause I am not responsible for anything wrong happens to your device!
* Download your device stock/custom boot.img (kernel) without SuperSU mod and download UnSU.zip from the amazing @osm0sis
* Flash UnSu.zip and Flash stock boot.img in TWRP
* Flash Magisk
* Uninstall Xposed Temporary and Login to Snapchat and install Xposed again OR use Root Switch APK from amazing Corner23 to turn off Xposed with a soft reboot and enable it again with another soft reboot (You Shouldn't use Systemless Xposed, you should use the official one from amazing @rovo89 or the custom one for samsung devices from the amazing @wanam) [Note for Geeks: Wanam Custom Xposed can work on all devices whether Odexed or DeOdexed while Rovo's Official Xposed can work only on AOSP DeOdexed ROMs.]
* To know if you can login to Snapchat, download any SafetyNet Checker from Play Store and you should pass SafetyNet if everything was done correctly else you might have some residual files that detect that you used root before so you might need to start from beginning with stock ROM.
Hope it helps!

Method A
1. Unroot
2. Reinstall Snapchat
3. Login
Method B
1. Grab another rooted device
2. Install Titanium Backup on said device
3. Install Snapchat and login, on said device
4. Use either a MicroSD card or upload a zip file of your 'TitaniumBackup' folder
5. Put folder in root of internal SD card on rooted device
6. Restore backup
7. Launch and enjoy
I actually keep a copy of that zip file both on my computer and my Dropbox. Useful for any future phone and/or tablet!

LexignisOfficial said:
Method A
1. Unroot
2. Reinstall Snapchat
3. Login
Method B
1. Grab another rooted device
2. Install Titanium Backup on said device
3. Install Snapchat and login, on said device
4. Use either a MicroSD card or upload a zip file of your 'TitaniumBackup' folder
5. Put folder in root of internal SD card on rooted device
6. Restore backup
7. Launch and enjoy
I actually keep a copy of that zip file both on my computer and my Dropbox. Useful for any future phone and/or tablet!
Click to expand...
Click to collapse
Amazing!!!!!!!!!!!!!!! life saver, thank you!

Use Magisk root and enable Magisk hide to Snapchat, it should work, works for my sister on here Galaxy S5 (klte)
If coming from SuperSU you'll have to fully unroot before installing MagiskSU

LukeyWolf said:
Use Magisk root and enable Magisk hide to Snapchat, it should work, works for my sister on here Galaxy S5 (klte)
If coming from SuperSU you'll have to fully unroot before installing MagiskSU
Click to expand...
Click to collapse
This is more-or-less time sensitive, Magisk always has to stay updated to bypass Safetynet checks, and Safetynet has to update to bypass Magisk, my method is a lot more usable, and with the Uninstall feature from both Magisk, and with the Uninstall zip for your respected xposed variation, this method should always work, at least until they can start sensing more things like history, and file differences in the system between OTAs.
---------- Post added at 02:01 AM ---------- Previous post was at 02:00 AM ----------
rulezzy said:
Amazing!!!!!!!!!!!!!!! life saver, thank you!
Click to expand...
Click to collapse
Glad to see I could help, I like offering straightforward instructions because I always look for 'em, have fun with your rooted device!

I wasn't able to log in after uninstalling root and several times uninstalling Snapchat and phone restarts. Help

Aemyiam said:
Same !! did u resolve the issue?
Click to expand...
Click to collapse
Login with no root no xposed and make a backup of data with titanium backup
Now you can restore the data and login (with the backup) on all rooted device you want :good:

z300muser said:
Login with no root no xposed and make a backup of data with titanium backup
Now you can restore the data and login (with the backup) on all rooted device you want :good:
Click to expand...
Click to collapse
Titanium backup cannot run on a device without root access.

flamery said:
Titanium backup cannot run on a device without root access.
Click to expand...
Click to collapse
Humm of course ??
Login with no root no xposed than you're logged in snapchat root and make a backup with titanium backup with the save you can login multiple device with root and xposed ?

nothing works anymore for me
it looks like root switch is not doing its job anymore
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
nothing works anymore for me
it looks like root switch is not doing its job anymore

gsm0607455890 said:
nothing works anymore for me
it looks like root switch is not doing its job anymore
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
nothing works anymore for me
it looks like root switch is not doing its job anymore
Click to expand...
Click to collapse
Read solutions in this thread. So many ways to fix it

No one works for me. Otherwise I would not have posted. It worked before yesterday now it does not work anymore with any options

Hi all, none of this is needed. I found it really easy on my Galaxy S4 running the latest Lineage ROM. This looks like a lot of steps, but they're all very simple. and minimal risk.
1. Delete Snapchat.
2. By all means make a full backup just in case.
3. Disable root access in Developer options.
4. Boot to Recovery & wipe Cache & Dalvik cache, but NOT data or system (I use TWRP)
5. Re-flash the current or latest version of your ROM
6. Re-boot - everything will still be there just as it was before.
7. Install Snapchat and log in - you should now have no problem.
7. Restore Root access (if you need it)
Done.

Mavidica said:
Hi all, none of this is needed. I found it really easy on my Galaxy S4 running the latest Lineage ROM. This looks like a lot of steps, but they're all very simple. and minimal risk.
1. Delete Snapchat.
2. By all means make a full backup just in case.
3. Disable root access in Developer options.
4. Boot to Recovery & wipe Cache & Dalvik cache, but NOT data or system (I use TWRP)
5. Re-flash the current or latest version of your ROM
6. Re-boot - everything will still be there just as it was before.
7. Install Snapchat and log in - you should now have no problem.
7. Restore Root access (if you need it)
Done.
Click to expand...
Click to collapse
Instead of dirty flashing your rom, you can just uninstall root or Xposed, login, and reroot/install Xposed. What you're doing takes up far more time.

Actually, you can't do either of those things on a Galaxy S4 running the latest Lineage ROM (or at least I can't). I found this simple, without needing to be a serious android geek, and it worked straight up

So I have a few questions

some information: I have a rooted with magisk moto g(6). if you need more information, just ask.
question 1: probably the most important one, my USB debugging keeps turning off. after a reboot, it was on before I rebooted but now it's off. I want to know how to fix this and what in the world is making this happen.
question 2: my sim card isn't being detected, I don't know id this is related to my IMEI number being unknown which leads to my next question...
question 3: why is my IMEI number unknown? this one is self-explanatory and I don't know how to explain it more
Question 4: final question, can I update. I am running android 9 with security patch January 1, 2019.
this is my first post here and I hope I didn't make any errors. if you have an answer for any of these questions, please share your knowledge.
I have fixed questions 2 and 3 by reflashing stock images a few times
I also believe that fixed question 1 so now I just really need to know how to update

I have the same problem that USB debugging is switching off after a reboot. I'm on stock, rooted with magisk. Do really fix that problem for your device?
You can update to the latest security patch. There are no issues but a little bug related to Magisk. The latest v20.3 causes a bootloop when it's being installed on a clean and fresh stock rom. The solution is flashing v19.3, boot your device and update it through the Magisk Manager to v20.3.
Don't ask me why but it works.

WoKoschekk said:
I have the same problem that USB debugging is switching off after a reboot. I'm on stock, rooted with magisk. Do really fix that problem for your device?
You can update to the latest security patch. There are no issues but a little bug related to Magisk. The latest v20.3 causes a bootloop when it's being installed on a clean and fresh stock rom. The solution is flashing v19.3, boot your device and update it through the Magisk Manager to v20.3.
Don't ask me why but it works.
Click to expand...
Click to collapse
O that sounds like it would work, I used to flash 16 something because I didn't know 19.3 worked, definitely gonna make a few backups too

16??

WoKoschekk said:
16??
Click to expand...
Click to collapse
Yes I saw it in a guide once. Why can TWRP sometimes not see my internal storage, it says there is 0 bytes there. Also if my backup is in internal storage, does that mess anything up?
O and when I try to update, it loads into TWRP recovery. Help.

I think the best way is to give you a complete guide...
But this only works for PPSS29.55-37-7-2.
If your current FW is PPSS29.118-15-11-2 this method ends up in a bootloop!! Then follow this thread, please.
Find below two download links. One of them is the fstab.zip which contains the patched fstab.qcom file. Unzip it and put the file somewhere accessible for you while following this guide.
BACKUP YOUR DATA IF POSSIBLE!
I AM NOT RESPONSIBLE FOR ANY DAMAGES ON YOUR DEVICE!
1.) Flash the latest firmware based on your software channel from here
2.) Let the phone boot to "Hello Moto" just to be sure everything is fine.
3.) Reboot to bootloder and flash the latest TWRP via fastboot.
4.) Boot directly into recovery by choosing it in the bootloader's menu.
5.) The first boot takes a few seconds and then TWRP requests a password to decrypt /data => press "cancel"
6.) Format /data (do not wipe) to remove encryption. After that format /data a second time and reboot into recovery.
7.) Format /data again.
8.) Now mount /vendor, open the file explorer and go to "/vendor/etc" and erase the file "fstab.qcom". Copy the patched file in this directory. This will disable forceencryption on your device. The trick is to replace the word "forceencryption" by "encryptable" in line 9.
9.) Open the terminal and type these commands:
Code:
cd vendor/etc
chmod 644 fstab.qcom
touch -r gps.conf fstab.qcom
With the last command (it's optional) you restore the original timestamp of the file by copying it from another. I use gps.conf because it's pretty short and fast to type.
Check the commands with
Code:
ls -l fstab.qcom
The output should look like this:
Code:
-rw-r--r-- 1 root root 1680 2009-01-01 07:00 fstab.qcom
It's very important to have the right permissions -rw-r--r-- root root
10.) Almost done... Flash Magisk v19.3 and not the latest v20.3 or you will get a bootloop.
I don't know why it bootloops... But AFAIK the only difference between those versions are the signing keys that are used to sign the boot.img after patching it with Magisk.
While installing Magisk the .zip disables dm-verity so you don't need an additional tool for that.
11.) If you like you can delete some system apps or what ever you want.
12.) It's done! Reboot to system and enjoy your rooted and unencrypted Moto g6 with disabled dm-verity!!
Don't panic if your device reboots one time after a few seconds. That's normal.

I wish I knew about the fstab file, I assume it removes the need to do the formatting but I already set up everything after I figured the update thing out. Would it be worth it to try and do the fastab?
Also why does it say I can turn OEM unlocking on again in my developer settings? I find that weird. And why when I boot up do I get a screen like this
YOUR DEVICE HAS BEEN UNLOCKED AND CANT BE TRUSTED
(My code here)
Contact something
ID:
YOUR PHONE WILL BOOT IN 5 SECONDS
I would think that my code would be where it says ID. Also it's as accurate as I can make it but in reality the code is overlapping the contact stuff. Just wondering if this is normal or if it's a sign that my phone's gonna explode or something. And are there any custom ROMs I should look into?

What exactly is the problem??
---------- Post added at 07:18 AM ---------- Previous post was at 07:08 AM ----------
To solve all the issues with your device you should flash a clean stock rom to get things into shape. There're several things messed up on your phone I think. A clean installation is the basic for all.

Bulbasaur Army said:
Would it be worth it to try and do the fastab?
Click to expand...
Click to collapse
Encrypted = you have to format /data every time before you are going to use TWRP
Decrypted = TWRP works perfect
Bulbasaur Army said:
Also why does it say I can turn OEM unlocking on again
Click to expand...
Click to collapse
Magisk enables the verity_state which leads to those options.
Bulbasaur Army said:
YOUR DEVICE HAS BEEN UNLOCKED AND CANT BE TRUSTED
(My code here)
Contact something
ID:
YOUR PHONE WILL BOOT IN 5 SECONDS
Click to expand...
Click to collapse
really?
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
What about learning some basics before modifying your device?? I don't get in a car, sit down behind the wheel without even knowing how to drive.
I gave you a very detailed instruction about how to root your device. You will finally manage to get root or not.

I see, I already had my phone rooted but I didn't see the guide for fastab so I was wondering if I should apply it, I will attempt to do so later today. Thank you for all the help you have given.
PS: what does the "---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------" is it part of XDA?