Galaxy Note4

[MrJavi]

Hey one more question before I do all this reading..whle I was doing some flashing..the phone was saying "systemless found"..how can this be possible if I have super su..not systemless..it didn't make sense to me..but I do remember that much..it was a couple of days ago

Its either Magisk root incorporated in the rom itself of systemless SuperSu (Android 6 will generally have systemless root).

 

[Xavier Black]

Hey Javi, what's a "dirty flash"?

 

[Xavier Black]

That may be how that rom is or maybe that sinior member dosent know what the freak their taking about . All I know is mines deodextef and debloated and I haven't got any rotational issies at all. In all my 7 years modifying I have never ever, ever, ever, ever, had rotational issues whatsoever. LOL

Brother, I did have rotation issues when installed the deodex..then I came across this post back then..so that kind of explained the rotation issue I was having..that's how I ended up with odex..now all the memories are coming back to me, baby..lol..men it's been like eight months!!!.

Maybe you since you deblowed the room and apps with the method of changing the permits rather than deleting everything..that might be the reason your way did work..

So I'm thinking since your way came through..and I already have all my room and apps to your way(as we speaking now)..and I already did a back up to this odex with all settings and permissions adjusted accordingly to your advices..

So what I can do is go ahead and flash that deodex you are referring to..then restore this very back up of this odex on top of the deodex I'm about to flash..

Will my phone still be working as a deodex rom??..this is ultimately my question, brother..

 

[MrJavi]

Brother, I did have rotation issues when installed the deodex..then I came across this post back then..so that kind of explained the rotation issue I was having..that's how I ended up with odex..now all the memories are coming back to me, baby..lol..men it's been like eight months!!!.

Maybe you since you deblowed the room and apps with the method of changing the permits rather than deleting everything..that might be the reason your way did work..

So I'm thinking since your way came through..and I already have all my room and apps to your way(as we speaking now)..and I already did a back up to this odex with all settings and permissions adjusted accordingly to your advices..

So what I can do is go ahead and flash that deodex you are referring to..then restore this very back up of this odex on top of the deodex I'm about to flash.

Will my phone still be working as a deodex rom??..this is ultimately my question, brother..

Maybe its a thing with the n910t's. I haven't read any posts of that nation on the XDA n910p threads. I posted 3 deodexted roms maybe its just specific to one of those and not to all.

 

[MrJavi]

Hey Javi, what's a "dirty flash"?

Dirty flashing is flashing a .zip over your pre-existing roms (may or may not include debloater .zips).


https://amp.reddit.com/r/Android/comments/sthr8/dirty_flashing_what_it_is_and_is_not_lets_set_the/

 

[Xavier Black]

Dirty flashing is flashing a .zip over your pre-existing roms (may or may not include debloater .zips).


https://amp.reddit.com/r/Android/comments/sthr8/dirty_flashing_what_it_is_and_is_not_lets_set_the/

Very good article!, great explanation!

 

[MrJavi]

Very good article!, great explanation!

Just bear in mind that is an 8yr old post. Personally, I prefer using TWRP advanced wipe function. For one, its a good idea to wipe catche and Dalvik/catche after system modifications. In the link they recommend doing this before dirty flashing. Im accustomed to doing this after dirty flashing. Its a good idea to do this when porting system apps with a root file manager as well (twrp, advanced wipe, Dalvik/catche and catche).
When installing a clean flash, I preform and standard wipe (factory reset) three times. I then go to the advanced wipe and format data and type yes (this will erase all internsl data).


As you know, restoring a twrp backup will not included all user data. Tipatch aatches TWRP to allow full data backups, including internal storage. As you may know, TWRP already backs up the data partition without /data/media, so with Tipatch you’ll now be able to make a truly full backup.

https://www.google.com/amp/s/www.xda-developers.com/tipatch-patches-twrp-full-data-backups/amp/

 

[Xavier Black]

Hey Javi speaking of which..I always do the cleansed up before any thing..

But I stopped doing the clear data because once I did the cache/dalvik/data at the same time..the phone didn't want to boot not even in recovery..I had too flash with Odin the original firmware(good thing I keep it in a thumb drive)..every since that I don't mess with the data..but for some reason I feel the phone isn't as clean as I would preferred to with out the data partition cleared..

What you think?

 

[MrJavi]

I usually wipe system/dalvik/catche and catche then reflash a backup system partition, depending on the circumstances. If I believe its a user app causing the issue, I boot into safe mode and xheck things out.

 

[MrJavi]

Brother, I did have rotation issues when installed the deodex..then I came across this post back then..so that kind of explained the rotation issue I was having..that's how I ended up with odex..now all the memories are coming back to me, baby..lol..men it's been like eight months!!!.

Maybe you since you deblowed the room and apps with the method of changing the permits rather than deleting everything..that might be the reason your way did work..

So I'm thinking since your way came through..and I already have all my room and apps to your way(as we speaking now)..and I already did a back up to this odex with all settings and permissions adjusted accordingly to your

So what I can do is go ahead and flash that deodex you are referring to..then restore this very back up of this odex on top of the deodex I'm about to flash..

Will my phone still be working as a deodex rom??..this is ultimately my question, brother..

Yes your phone will still be working with a deodexed rom. If that particular deodexed rom develops rotational issues when deleting system apps (an issue I've never come across when it comes to deodexed) Then choose another deodexed MM rom. It may be that the deodexed with the Magisk root method incorporated as part of the rom (su binaries) is has better network connectivity (wifi, Bluetooth, 4G LTE). That might be the case being that back then, Magisk was the new kid on the block. I wouldn't attribute a better data conection to Magisk but to the rom itself. This doesn't mean you can't replace Magisk with Chain Fires SuperSu. It only means you have to know how to go about it.
If my priorities were to run banking apps, Netflix, pokemon and had no intressed in Viper4Android, Double Atmos, Xposed firmware, full R/W access or a permissive overclocked custom kernel and needed to pass Safty Net checks with ease then Magisk would be my choice. Both methods have advantages over the other.
One rom I flash had Magisk in-corporated with the rom. I then flashed SuperSu .zip on top of Magisk. Well 2 separate su binary rcause issues galore, sometimes subtle and then begin to increase over time. My inital thought wete that flashing SuperSu would replace Magisk. It did not. I rember wanting that rom for some particular reason and so I used a root file manger to look threw the rom. I then removed the Magisk files,folders snd I think it came with busybox applets that also needed to be deleted. Its been a while, I think I might have examined a seprate Magisk.zip in order to determine what had to be deleted from the pre rooted magisk rom.

PS:

https://root-checker-pro-free.en.aptoide.com/app

Download the app above, Its the only one I know that shows the path and status. If it looks like mine its good. If it shower Multiple busy boxes installed correctly let me know.

Oh: I had to flip kill back botton setting back to on in an exposed module. I rebooted turned it off and rebooted and left side bar work again.

 

[MrJavi]

Thanks to you, my very good friend and brother @Xavier Black . I accomplished a long time goal long forgotten. It began when I turned of device administrators. I noticed after I rebooted the enable themselfs automatically. One thing I've always hated about Google is its deceptive practices. Add a toggle to turn off Google davice administrators and knowing 99.99999% of the people will havr no idea it enable after start up and even if you do whos going to go to settings evry reboot to turn it off. Its social psychology and they know it all to well. Heres what I mean.

Can you uncheck them, reboot and confirm if they re-enable themselves automatically?

There is no spp on my device called "Find my device" so that leaves out disabling and uninstalling. I hit pay dirt non the less

I did this woth Rom Toolbox pro Version 6.0.6.5 in "Auto Start Manager" (recievers).

To remove the "Find My Device" Administrator I disable it from Google Play Services in the midle of the screen shot below. "MdmDeviceAdministratorReciever"

 

[Xavier Black]

Thanks to you, my very good friend and brother @Xavier Black . I accomplished a long time goal long forgotten. It began when I turned of device administrators. I noticed after I rebooted the enable themselfs automatically. One thing I've always hated about Google is its deceptive practices. Add a toggle to turn off Google davice administrators and knowing 99.99999% of the people will havr no idea it enable after start up and even if you do whos going to go to settings evry reboot to turn it off. Its social psychology and they know it all to well. Heres what I mean.

View attachment 154497

Can you uncheck them, reboot and confirm if they re-enable themselves automatically?

There is no spp on my device called "Find my device" so that leaves out disabling and uninstalling. I hit pay dirt non the less

View attachment 154499

Yes I've unchecked it a million times..and look for it to delete its as..no where to be found..how do I delete it???

 

[Xavier Black]

Javi my system said magisk but the super su is surely running shit around here. How do I get to those magisk files to get rid of them?

 

[Xavier Black]

Yes your phone will still be working with a deodexed rom. If that particular deodexed rom develops rotational issues when deleting system apps (an issue I've never come across when it comes to deodexed) Then choose another deodexed MM rom. It may be that the deodexed with the Magisk root method incorporated as part of the rom (su binaries) is has better network connectivity (wifi, Bluetooth, 4G LTE). That might be the case being that back then, Magisk was the new kid on the block. I wouldn't attribute a better data conection to Magisk but to the rom itself. This doesn't mean you can't replace Magisk with Chain Fires SuperSu. It only means you have to know how to go about it.
If my priorities were to run banking apps, Netflix, pokemon and had no intressed in Viper4Android, Double Atmos, Xposed firmware, full R/W access or a permissive overclocked custom kernel and needed to pass Safty Net checks with ease then Magisk would be my choice. Both methods have advantages over the other.
One rom I flash had Magisk in-corporated with the rom. I then flashed SuperSu .zip on top of Magisk. Well 2 separate su binary rcause issues galore, sometimes subtle and then begin to increase over time. My inital thought wete that flashing SuperSu would replace Magisk. It did not. I rember wanting that rom for some particular reason and so I used a root file manger to look threw the rom. I then removed the Magisk files,folders snd I think it came with busybox applets that also needed to be deleted. Its been a while, I think I might have examined a seprate Magisk.zip in order to determine what had to be deleted from the pre rooted magisk rom.

PS:

https://root-checker-pro-free.en.aptoide.com/app

Download the app above, Its the only one I know that shows the path and status. If it looks like mine its good. If it shower Multiple busy boxes installed correctly let me know.

View attachment 154476


Oh: I had to flip kill back botton setting back to on in an exposed module. I rebooted turned it off and rebooted and left side bar work again.

View attachment 154475

Javi, no where says deodex..

 

[MrJavi]

Javi my system said magisk but the super su is surely running shit around here. How do I get to those magisk files to get rid of them?

Thats your biggest issue, I know it all to well. I've been there lol. Ill refresh my memory befor I resoond. Its been a while and I want to give you the best advice my friend.

 

[Xavier Black]

Javi!, I forgot to tell you I'm in Deodex now as we speak..last night I worked it out..it took me a few hours because I was trying to implement a tether hack to fix the hot spot but it boot looped every times(like three times)..supposedly that hack was for T-Mobile Note4 deodex stock..well go figure..didn't work

 

[Xavier Black]

Yes I've unchecked it a million times..and look for it to delete its as..no where to be found..how do I delete it???

How do I uninstall it?

 

[Xavier Black]

Its either Magisk root incorporated in the rom itself of systemless SuperSu (Android 6 will generally have systemless root).

I also fail to mention..have not rotation issues so far..I think because I applied all your security settings advices..you know folder, subfolders, apps and libs..

 

[Xavier Black]

Hey bro..seems to have super su and but

Yes your phone will still be working with a deodexed rom. If that particular deodexed rom develops rotational issues when deleting system apps (an issue I've never come across when it comes to deodexed) Then choose another deodexed MM rom. It may be that the deodexed with the Magisk root method incorporated as part of the rom (su binaries) is has better network connectivity (wifi, Bluetooth, 4G LTE). That might be the case being that back then, Magisk was the new kid on the block. I wouldn't attribute a better data conection to Magisk but to the rom itself. This doesn't mean you can't replace Magisk with Chain Fires SuperSu. It only means you have to know how to go about it.
If my priorities were to run banking apps, Netflix, pokemon and had no intressed in Viper4Android, Double Atmos, Xposed firmware, full R/W access or a permissive overclocked custom kernel and needed to pass Safty Net checks with ease then Magisk would be my choice. Both methods have advantages over the other.
One rom I flash had Magisk in-corporated with the rom. I then flashed SuperSu .zip on top of Magisk. Well 2 separate su binary rcause issues galore, sometimes subtle and then begin to increase over time. My inital thought wete that flashing SuperSu would replace Magisk. It did not. I rember wanting that rom for some particular reason and so I used a root file manger to look threw the rom. I then removed the Magisk files,folders snd I think it came with busybox applets that also needed to be deleted. Its been a while, I think I might have examined a seprate Magisk.zip in order to determine what had to be deleted from the pre rooted magisk rom.

PS:

https://root-checker-pro-free.en.aptoide.com/app

Download the app above, Its the only one I know that shows the path and status. If it looks like mine its good. If it shower Multiple busy boxes installed correctly let me know.

View attachment 154476


Oh: I had to flip kill back botton setting back to on in an exposed module. I rebooted turned it off and rebooted and left side bar work again.

View attachment 154475

Hey brother seems to have super su and not magisk systemless..also apparently also has busy box..didn't know.

 

[Xavier Black]

Yes your phone will still be working with a deodexed rom. If that particular deodexed rom develops rotational issues when deleting system apps (an issue I've never come across when it comes to deodexed) Then choose another deodexed MM rom. It may be that the deodexed with the Magisk root method incorporated as part of the rom (su binaries) is has better network connectivity (wifi, Bluetooth, 4G LTE). That might be the case being that back then, Magisk was the new kid on the block. I wouldn't attribute a better data conection to Magisk but to the rom itself. This doesn't mean you can't replace Magisk with Chain Fires SuperSu. It only means you have to know how to go about it.
If my priorities were to run banking apps, Netflix, pokemon and had no intressed in Viper4Android, Double Atmos, Xposed firmware, full R/W access or a permissive overclocked custom kernel and needed to pass Safty Net checks with ease then Magisk would be my choice. Both methods have advantages over the other.
One rom I flash had Magisk in-corporated with the rom. I then flashed SuperSu .zip on top of Magisk. Well 2 separate su binary rcause issues galore, sometimes subtle and then begin to increase over time. My inital thought wete that flashing SuperSu would replace Magisk. It did not. I rember wanting that rom for some particular reason and so I used a root file manger to look threw the rom. I then removed the Magisk files,folders snd I think it came with busybox applets that also needed to be deleted. Its been a while, I think I might have examined a seprate Magisk.zip in order to determine what had to be deleted from the pre rooted magisk rom.

PS:

https://root-checker-pro-free.en.aptoide.com/app

Download the app above, Its the only one I know that shows the path and status. If it looks like mine its good. If it shower Multiple busy boxes installed correctly let me know.

View attachment 154476


Oh: I had to flip kill back botton setting back to on in an exposed module. I rebooted turned it off and rebooted and left side bar work again.

View attachment 154475

Seems like there's two different locations for the busy box..

 

[MrJavi]

ill look at the rom you installed from XDA. I will use the build number to determine which one it is. Did you install root checker pro free? if so did it display busybox applets in two locations? If so will need to correct that as well.

 

[Xavier Black]

Thanks to you, my very good friend and brother @Xavier Black . I accomplished a long time goal long forgotten. It began when I turned of device administrators. I noticed after I rebooted the enable themselfs automatically. One thing I've always hated about Google is its deceptive practices. Add a toggle to turn off Google davice administrators and knowing 99.99999% of the people will havr no idea it enable after start up and even if you do whos going to go to settings evry reboot to turn it off. Its social psychology and they know it all to well. Heres what I mean.

View attachment 154497

Can you uncheck them, reboot and confirm if they re-enable themselves automatically?

There is no spp on my device called "Find my device" so that leaves out disabling and uninstalling. I hit pay dirt non the less

View attachment 154499

I did this woth Rom Toolbox pro Version 6.0.6.5 in "Auto Start Manager" (recievers).

View attachment 154500
To remove the "Find My Device" Administrator I disable it from Google Play Services in the midle of the screen shot below. "MdmDeviceAdministratorReciever"

View attachment 154501

Sorry I wasn't reading you well..so you did it with the Rom Toolbox?

 

[Xavier Black]

Thanks to you, my very good friend and brother @Xavier Black . I accomplished a long time goal long forgotten. It began when I turned of device administrators. I noticed after I rebooted the enable themselfs automatically. One thing I've always hated about Google is its deceptive practices. Add a toggle to turn off Google davice administrators and knowing 99.99999% of the people will havr no idea it enable after start up and even if you do whos going to go to settings evry reboot to turn it off. Its social psychology and they know it all to well. Heres what I mean.

View attachment 154497

Can you uncheck them, reboot and confirm if they re-enable themselves automatically?

There is no spp on my device called "Find my device" so that leaves out disabling and uninstalling. I hit pay dirt non the less

View attachment 154499

I did this woth Rom Toolbox pro Version 6.0.6.5 in "Auto Start Manager" (recievers).

View attachment 154500
To remove the "Find My Device" Administrator I disable it from Google Play Services in the midle of the screen shot below. "MdmDeviceAdministratorReciever"

View attachment 154501

Let me rechapter..where or what option inside the Rom Toolbox you go to to get that menu of the targeting app?

 

[Xavier Black]

ill look at the rom you installed from XDA. I will use the build number to determine which one it is. Did you install root checker pro free? if so did it display busybox applets in two locations? If so will need to correct that as well.

Yes bro, it did in two different locations..found one with my file manager..the other one couldn't find it

 

[MrJavi]

I use BusyBox Pro by Jrummy

Now look at Root checker pro free on mine notice the location su/zbin/busybox and at the top "busybox has been installed correctly"

Scroll down on yours and you'll see a second busybox location. Thats the one that needs to be deleted using BusyBox pro by Jrunmy.

Where it says su/xbin on the right hand side tap the little triangular icon

Now tap the second busybox location that you saw in Root Chwcker Pro.

At the bottom tap uninstall.