Develop Bugs

[Q] Unroot EVO and still keep a custom rom?

Is this possible? I know most unroot the phone to take it in for service/exchange etc but my situation is different. I have to use Good for Enterprise to access my company's email and as you may know, Good does not allow rooted phones. So, I have no choice but to unroot my Evo.
The image that is used in unrooting is a stock ROM. What I want to do is setup my phone - the way I want it with Mikfroyo - with all the tweaks etc and then "just do the unrooting part". If that makes any sense - I don't need any superuser permissions etc.
Long story short - can a phone be unrooted with a custom ROM instead of a stock ROM?

im pretty sure this is impossible dude, sorry, just leave it all rooted, whats the problem

I know you can't unroot and keep a custom ROM but I wonder if there is a way to hide the fact that you're rooted from the app. What kind of message pops up when you install it?
Sent from my PC36100 using XDA App

It just says that Good cannot run on a rooted phone and just locks the app - I have to call IT to get an unlock code using the device ID that is displayed in Good's pop-up message.

It has to be checking for something specific and I bet there is a way to fudge it but unfortunately that's outside my realm of understanding. I would ask one of the devs here about it.

What permissions does the App request when you install? It could just check for SuperUser

SSjon said:
What permissions does the App request when you install? If could just check for SuperUser
Click to expand...
Click to collapse
I which case you could either delete superuser or use it to block the app... perhaps?

I am sure its more complicated than that - if they are touting themselves as a replacement for blackberry security for iPhones and Android - I seriously doubt a simple fudging of the superuser permissions will deceive it. Also, I'd like to comply with my company's requirements for using an Android phone so I don't get into trouble.
So from what I understand - you cannot have a custom ROM on an unrooted phone. Thanks so much guys - I'll just have to learn to live with the bloated stockware and manual restores arghh......

It's not possible.... to unroot, you'd have to RUU, which returns the phone back to stock. And then, you'd have no way of flashing a custom rom unless you rooted again

ok this is one thing that I am starting to not understand here...
so many people when they answer - say "yes" it can be done or "no" it can not be done...
...ummm where is the why? It would be very informative to know such things or if someone has even tried said thing before.
like why can't you just run a ROM or other flash file from renaming the file and letting the stock loader do the flashing? ......answer: because the stock loader does a file signature check - see? that makes sense and answers the why. it also helps users to retain the information as well as understand it.
I would love to know why the OP can't just run the unrevoked s-on tool from here http://unrevoked.com/rootwiki/doku.php/public/forever#custom_splash (in the FAQ section) without removing his custom ROM and just make sure he doesn't use any apps that need the su access. sounds like it should work? has someone done this and found that it does not work? flashing back to s-on should just prevent flashing to any other ROM's I would think from everything I have read in this forum.
or once s-on is back does it also check the current ROM on the phone and would cause some issues? would be great information to know. because if the security only checks file signatures of flies to be flashed and not the current ROM it seems like the OP could do what he is wanting to.
well, just thought I would ask to see if I could gain some more understanding as to the mechanics of everything

It would be good to know if this works with Good for Enterprise. I am stuck on an SGS 2.1 with Telstra and want a non stock ROM but really need to use Good.

ushkand said:
Is this possible? I know most unroot the phone to take it in for service/exchange etc but my situation is different. I have to use Good for Enterprise to access my company's email and as you may know, Good does not allow rooted phones. So, I have no choice but to unroot my Evo.
Click to expand...
Click to collapse
I did not know that, and that SUCKS. My company's piloting Good now, and I was really looking forward to it. This just infuriates me. Mobile device makers are getting away with things that desktop/laptop makers never dreamed of trying. We shouldn't even NEED to "root" a phone. Imagine if you needed to hack your Windows machine in order to get the admin password and be able to install whatever you want. Now yes, I get that companies often do add those restrictions on their devices, and that they need to protect their data. Allowing access to company data on a personal device might make it a little more of a gray area, but it still blows. Good should be able to develop a system that can be secure, even if you have root access.
Here's a thread I just found. It sounds like you can just delete su and the superuser.apk. I think you can keep the custom rom, but you probably wouldn't be able to run anything that needs root, like Wireless Tether, Titanium Backup, or whatever. But you could probably have a flashable zip to re-add them when you need them. Or maybe one of the temp root methods would work. But it makes me furious that this is needed.
http://androidforums.com/droid-x-all-things-root/207397-good-enterprise.html

bkrodgers said:
I did not know that, and that SUCKS. My company's piloting Good now, and I was really looking forward to it. This just infuriates me. Mobile device makers are getting away with things that desktop/laptop makers never dreamed of trying. We shouldn't even NEED to "root" a phone. Imagine if you needed to hack your Windows machine in order to get the admin password and be able to install whatever you want. Now yes, I get that companies often do add those restrictions on their devices, and that they need to protect their data. Allowing access to company data on a personal device might make it a little more of a gray area, but it still blows. Good should be able to develop a system that can be secure, even if you have root access.
Here's a thread I just found. It sounds like you can just delete su and the superuser.apk. I think you can keep the custom rom, but you probably wouldn't be able to run anything that needs root, like Wireless Tether, Titanium Backup, or whatever. But you could probably have a flashable zip to re-add them when you need them. Or maybe one of the temp root methods would work. But it makes me furious that this is needed.
http://androidforums.com/droid-x-all-things-root/207397-good-enterprise.html
Click to expand...
Click to collapse
My thoughts exactly

Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.

ushkand said:
Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.
Click to expand...
Click to collapse
Thanks for the information. What is the ROM that you are using?

bkrodgers said:
Or maybe one of the temp root methods would work.
Click to expand...
Click to collapse
are there still temp root methods that work on the EVO?

I am using Mikfroyo 4.5.

Just came across this thread and was seeing if your GFE was still working? I have a DX and put a custom ROM and could not get it to work. I'm waiting for my new PIN and have removed SU to see if it works.

ushkand said:
Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.
Click to expand...
Click to collapse
I rooted my HTC Salsa to install apps2sd which is great, but what commands do i have to run and where to be able to rename su.apk ?
Thanks,
Mike

Good for Enterprise - root user

I recently started working for a company that uses good for enterprise for their email. I know how it works but my question is this.
Can't I delete su and busy box to remove root. Then whenever i need root I can just go to recovery and install a .Zip package that adds the two files back.
Does anyone know if this would be possible?
P.s. what gets me is that pirates remove security protection from payed apps all the time, but a work around for this does not exist.
Thanks
Sent from my PC36100 using XDA App

You could nandroid your current setup then flash the unrooted OTA - leave s-off. You'll have to reflash recovery and nandroid the unrooted rom. Then you can restore your backup if you need root.
Or you can unroot and go to the 3.70 OTA (the last FroYo release) and use z4root for temp root. There isn't a temp root for the GB update, so do not unroot and accept the OTA unless you want to wait for a root exploit which could take weeks.
I don't know why you need to be unrooted for email. Depending on why, what you're asking may be possible. But do understand that modifying a rom is a lot more involved than modifying an app.
(from... Evo/MIUI/Tapatalk)

You could also try to badger your IT department to remove the restriction. It's configurable, and not something inherent in Good. My company doesn't have it enabled, for example, and I can run Good rooted.
Doubtful you'll succeed, but it can't really hurt to try, right?

Actually I'm in the IT department and only one person holds the keys, the answer was a no.. =(
But I do know GFE only checks for busybody and su. I was hoping I could delete the two files then just create a patch that could be deployed in recovery to add these m files back as needed.
But before I go flashing has anyone tried this?
Sent from my PC36100 using XDA App

I haven't tried it since I don't need to. But back before they'd rolled Good out for us (but after I heard it was coming), I read that the administrators have the option of locking root users out. I didn't know if they were going to do it or not, so I was thinking along the exact lines you were. Luckily it turned out to be unneeded for me, but it should work. As long as you're S-OFF, there shouldn't be any real risk in trying it.

Ill prob. Try it today. I have a transformer rooted as well. So we will see.
Sent from my PC36100 using XDA App

darkansi said:
Actually I'm in the IT department and only one person holds the keys, the answer was a no.. =(
But I do know GFE only checks for busybody and su. I was hoping I could delete the two files then just create a patch that could be deployed in recovery to add these m files back as needed.
But before I go flashing has anyone tried this?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes i do it all the time but I dont flash them, I remove them then add them in again. Be sure you turn persistent mode off, then quit the app.

I used my transformer as a guinea pig and it worked. But what I did was delete su, busybox and superuser.apk.
Then whenever I needed root I would flash my rom back without wiping.
I want to make a .zip file with only those 3 files in it. So the flash time and footprint is small. Any suggestions on reading material.
@ matt1313
how do you add them back, through recovery or within the OS. (if through the os how do you r/w access.
Thanks again.

darkansi said:
I used my transformer as a guinea pig and it worked. But what I did was delete su, busybox and superuser.apk.
Then whenever I needed root I would flash my rom back without wiping.
I want to make a .zip file with only those 3 files in it. So the flash time and footprint is small. Any suggestions on reading material.
@ matt1313
how do you add them back, through recovery or within the OS. (if through the os how do you r/w access.
Thanks again.
Click to expand...
Click to collapse
At the time of post I was using leaked GB and Gingerbreak, I would just use Gingerbreak to get root again when I needed it.
Now after the new update on Good to 1.73 I get ROOT detected when I have no Root. So now we need to see what they are detecting.
It would be nice if someone could decompile the app and change the ROOT detection method.

Root for AT&T N920A.

I know this is not the right place to ask. I need to know. Do we have developers working on root for this model?
Sent from my SAMSUNG-SM-N920A using Tapatalk

Yes and No...still having booloader issues!
And yes wrong place...this post belongs in Q&A!

We need firmware release so we can restore after. Tell then no one really wants to try because just messing with options in recovery disables the phone.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=N920

Will firmware release happen for our model?
Sent from my SAMSUNG-SM-N920A using Tapatalk

amwbt said:
Will firmware release happen for our model?
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
AT&T has to because it's open source. They however can keep it for like 6 months to a year or something. With the cracks down on root AT&T and Verizon it might be a long wait with the locked bootloader saidly and we need a custom kernel to get root and we can't flash kernels with locked bootloader. Just watch the website I linked and when we get our firmware then we can possibly expect root and someone to try and unlock the bootloader. I'm not sure if there is a "anti root" in the AT&T phone because I'm not going to lose my phone. I already had to return for warranty due to defective screen and spen. Look at how long it takes the new iPhone software to get jailbroken.

TechNyne66 said:
AT&T has to because it's open source. They however can keep it for like 6 months to a year or something. With the cracks down on root AT&T and Verizon it might be a long wait with the locked bootloader saidly and we need a custom kernel to get root and we can't flash kernels with locked bootloader. Just watch the website I linked and when we get our firmware then we can possibly expect root and someone to try and unlock the bootloader. I'm not sure if there is a "anti root" in the AT&T phone because I'm not going to lose my phone. I already had to return for warranty due to defective screen and spen. Look at how long it takes the new iPhone software to get jailbroken.
Click to expand...
Click to collapse
Needing a custom kernel for root is actually a false statement. A custom kernel is not needed to get root for this device. The AT&T S6 for example got root without the bootloader being unlocked or a custom kernel.
Which leads me to the bootloader being unlocked. There is probably a 100% chance that we don't get an unlocked bootloader for this device. It's extremely difficult and there hasn't been an AT&T device in a very long time that has had it unlocked.
And since we would need that for a custom kernel and aosp roms, those things will probably never happen unfortunately.
The very best we can hope for is root and a recovery like FlashFire like the S6 got. And even then we would be limited to only Touchwiz roms.

We will more then likely need custom kernel with permissive set. AT&T and Verizon are saying there's anti root and that would be in the kernel and would need to be killed. If we do obtain root with stock kernel the phone is said to not boot.
http://www.idigitaltimes.com/samsun...d-features-att-and-verizon-models-wont-468357

It is one of those things where they're will be zero development until some Uber-geek cracks the bootloader issue. Then there will be 20 devices or more that will be released from developer quarantine...
Sent from my SAMSUNG-SM-N920A using Tapatalk

AOSP will never happen without unlocked bootloader.
I do have hope for a root such as Ping Pong. Honestly, with how clean these phones ship nowadays, all I want root for is to replace emojis with iOS style throughout the system so I can grasp more context from my text messages lol. Also, LCD Density change would be nice too.

Is there anybody working on root for this phone?
Sent from my SAMSUNG-SM-N920A

Have no need for root either except for xposed. Only want root for like 4 xposed modules.. Otherwise this device is nearly perfect

I need to change muy dpis
Enviado desde mi GT-N7100 usando Tapatalk 2

Planning on getting this phone today..
I have rooted and installed ROMs on almost every phone I have owned and really hope that eventually a safe way of rooting is obtained.

jellybear456 said:
a safe way of rooting
Click to expand...
Click to collapse
heh. I know what you mean, but I'm grumpy this morning so I'm going to pick this apart anyway.
If root is found on a boot loader locked device, it's usually via an exploit... Basically, most rooting mechanisms are similar to computer viruses. Sure, most of them are controlled viruses, but they exploit and expose security holes that something malicious could use just as easily. Instead of copying a "su" binary, that same exploit could install something that uploads your private data somewhere, or monitors the android keypad entry when you type credit card numbers, etc.
Don't get me wrong... I don't think that most of the root exploits here on XDA are doing that... but any time you use one, you should seriously consider that it might be. It would only take a single mishap to completely destroy your life outside of XDA.
To that end, you should REALLY pay attention to the entire filesystem both before and after an exploit is applied. See what files, if any, are modified and/or added. If an exploit adds a "su" binary (which most of them do), try to replace that "su" binary with one from a trusted source BEFORE you put personal data on your phone. Never "root" a device that has any data on it.
Remember that no matter what precautions you might be taking, a rooted device has a lower level of security than one that isn't. Not only have you added a "simple" root mechanism, but you likely had to defeat the security mechanisms that are part of the security enhanced linux kernel. (There are exceptions to this, of course, but I've never seen the exceptions here on XDA or any other sites that aren't focused on security.)
If this message made you a bit more paranoid, that's a good thing. You should be paranoid about it. I'm not saying not to do it, and I'm certainly not saying that XDA is overflowing with malicious code...

garyd9 said:
heh. I know what you mean, but I'm grumpy this morning so I'm going to pick this apart anyway.
If root is found on a boot loader locked device, it's usually via an exploit... Basically, most rooting mechanisms are similar to computer viruses. Sure, most of them are controlled viruses, but they exploit and expose security holes that something malicious could use just as easily. Instead of copying a "su" binary, that same exploit could install something that uploads your private data somewhere, or monitors the android keypad entry when you type credit card numbers, etc.
Don't get me wrong... I don't think that most of the root exploits here on XDA are doing that... but any time you use one, you should seriously consider that it might be. It would only take a single mishap to completely destroy your life outside of XDA.
To that end, you should REALLY pay attention to the entire filesystem both before and after an exploit is applied. See what files, if any, are modified and/or added. If an exploit adds a "su" binary (which most of them do), try to replace that "su" binary with one from a trusted source BEFORE you put personal data on your phone. Never "root" a device that has any data on it.
Remember that no matter what precautions you might be taking, a rooted device has a lower level of security than one that isn't. Not only have you added a "simple" root mechanism, but you likely had to defeat the security mechanisms that are part of the security enhanced linux kernel. (There are exceptions to this, of course, but I've never seen the exceptions here on XDA or any other sites that aren't focused on security.)
If this message made you a bit more paranoid, that's a good thing. You should be paranoid about it. I'm not saying not to do it, and I'm certainly not saying that XDA is overflowing with malicious code...
Click to expand...
Click to collapse
Yes, I do realize that rooting a device often does take advantage of any security holes found, and I also realize that there is no, in the literal sense, "safe" way to root a phone considering it is exploiting security flaws. Personally, I have never had such an issue of having something malicious on my phone after rooting(at least not to my knowledge)
By "safe" I meant a way to root without having the phone locked down and unable to boot. I am not worried about AOSP ROMs as I am completely content with using an AOSP themed launcher. But I would love to be able to uninstall bloat, ad block, greenify/amplify etc.
But I do appreciate your input on the subject as I have never put much thought into the security of the phone before and after root, or replacing the su binary with one from a trusted source or checking if it is from a trusted source.
It is also great to see someone else on the forums from Pittsburgh:highfive:

I have n920a. Please share the path to rooting this phone.

Cuando se podra rootear el dispositivo Samsung Galaxy Note 5 N920A?

Possible way to root?
I don't know if this would work. But what about flashing one of those new root.tar eng kernal then manually pushing the survey binary and super apk into phone then reflash stock kernal. I'm just intermediate at all this stuff. So idk if it would work or if this is stupid.

vahalaru said:
I don't know if this would work. But what about flashing one of those new root.tar eng kernal then manually pushing the survey binary and super apk into phone then reflash stock kernal. I'm just intermediate at all this stuff. So idk if it would work or if this is stupid.
Click to expand...
Click to collapse
It's possible, after flashing the eng-boot do this:
adb shell mount -o rw,remount /system
Then manually push SuperSU to system, or install King/Kingo Root
Just be careful this is still a tethered root.

I have posted a teathered root process that Michael31 found from the AT&T s6 section. It works and you can get reboots with hoot booting. The locked bootloader causing issues with the kernel needed add commands on hard boot to change to permissive mode. Few of us have tried to fix this issue and haven't found anyway yet.

Question about a semi-custom stockish ROM/Cerberus? Developers?

My OnePlus 3 was lost/(more likely stolen) a few days back. It wasn't insured so I have accepted the fact that I probably won't get it back. I was then researching things that I could have done to prevent it from happening, and came across an app called Cerberus.
Cerberus seems to be a really cool app because you can do stuff like activate data via SMS, so if the thief disables it you can re-enable it. I know that they could also take out the SIM or clean flash a ROM, and then you're basically screwed unless there is somehow a Wi-Fi connection. If you integrate it as a system/app, it should survive a factory reset. And AFAIK, if the SIM is still in it it automatically connects to data on reboot so should be able to get info from cerberus' servers.
Is it possible to get a ROM zip, put the .apk to system/app, add cerberus_conf.xml from system/etc and put it into the stock ROM zip so it will always survive factory data reset.
By getting the .apk from their website and the cerberus_conf.xml from a temporary TWRP recovery or rooting temporarily just to make sure it is there and/or to gain access to it.
Then when that is done, re-zip the rom, relock bootloader, clean flash the ROM via adb sideload. <--- Is this part possible???
Because it is based on stock rom, would this work on a locked bootloader without root?
(I still want to use Android Pay)
I understand due to the nature of the cerberus_conf.xml file it will only work for personal use but is it theoretically possible?
Also, I haven't fully used Cerberus yet but it sounds like it could be worth it/ a lifesaver (metaphorically).

Basically the question I am asking is whether or not you can make small modifications to the system/app folder and still rezip and install successfully without having to unlock bootloader?

AlvieOP said:
Basically the question I am asking is whether or not you can make small modifications to the system/app folder and still rezip and install successfully without having to unlock bootloader?
Click to expand...
Click to collapse
I don’t really think so because If u lock bootloader on anything modified then either locking will fail or either brick ur device
Edit: after thinking a bit it may be possible but to know that it works you or someone else has to do it and report.
I once met a guy here who locked his bootloader on modified rom and his device got bricked but in case of semi stockish rom it may be possible
Any furthur insight will be helpful from the community

Dupleshwar said:
I don’t really think so because If u lock bootloader on anything modified then either locking will fail or either brick ur device
Edit: after thinking a bit it may be possible but to know that it works you or someone else has to do it and report.
I once met a guy here who locked his bootloader on modified rom and his device got bricked but in case of semi stockish rom it may be possible
Any furthur insight will be helpful from the community
Click to expand...
Click to collapse
Yeah I know that a custom ROM will brick it, but what if it is just one extra file in system?
Does anyone else know?

Google bought pixel, anyway to activate hotspot on vzw?

See title, any ROMs bypass subscription check? Or any way to by editing build.props to allow this with just root?

Hmm, mine just works. I'm unrooted. Maybe i oughtta check my bill and make sure Verizon isn't charging me, but they never have in the past.

Mind me asking, are you on a plan that allows tethering? I'm still on the original unlimited plan.

net.tethering.noprovisioning=true
Add that to the build.prop and save it. Should work.

coolhandz said:
net.tethering.noprovisioning=true
Add that to the build.prop and save it. Should work.
Click to expand...
Click to collapse
Phone arrives on the 5th, so ill report back (hopefully) with a success story. You've inspired two more questions, Does it matter where in the build prop i add that (certain line, or already existing; just changing false to true) and since I'll need root to edit that file, is there any difference (easier) rooting on 7.1.x vs 8.0.0?
Have had a few phones where the root method was patched by an OTA update.
Edit:in hindsight seems to be a stupid question. Rather, would systemless root or (system?) root be a better option? Whether su or magisk performs better?

I may be misinformed but..... Supposedly, if not bootloader unlocked, inserting Vz sim relocks bootloader. Again, I not sure if that is fact or fiction but just in case....
Before inserting Verizon sim card be sure to complete the process for unlocking phone thru settings and oem unlock thru platform tools so you are bootloader unlocked before inserting sim. Might also be smart to root and update phone to latest factory image before inserting sim, then set up phone.
Also before you mess with build.prop file be sure to save a copy renamed build.prop.bak as a backup. Once you do that, added lines to build.prop are normally placed at end.

AlPoo said:
Phone arrives on the 5th, so ill report back (hopefully) with a success story. You've inspired two more questions, Does it matter where in the build prop i add that (certain line, or already existing; just changing false to true) and since I'll need root to edit that file, is there any difference (easier) rooting on 7.1.x vs 8.0.0?
Have had a few phones where the root method was patched by an OTA update.
Edit:in hindsight seems to be a stupid question. Rather, would systemless root or (system?) root be a better option? Whether su or magisk performs better?
Click to expand...
Click to collapse
I actually thought rooting on 8.0 was a bit easier. I prefer to use SuperSU because it is what I'm used to and i felt Magisk was just picking up and had a few bugs still. Might try Magisk later.
Anyway, you just add that line to the build.prop. i put it at the very end, but it doesn't matter.

Born<ICs said:
I may be misinformed but..... Supposedly, if not bootloader unlocked, inserting Vz sim relocks bootloader. Again, I not sure if that is fact or fiction but just in case....
Before inserting Verizon sim card be sure to complete the process for unlocking phone thru settings and oem unlock thru platform tools so you are bootloader unlocked before inserting sim. Might also be smart to root and update phone to latest factory image before inserting sim, then set up phone.
Also before you mess with build.prop file be sure to save a copy renamed build.prop.bak as a backup. Once you do that, added lines to build.prop are normally placed at end.
Click to expand...
Click to collapse
I wasn't willing to find out if you were right, finally finished, without inserting sim. I'll be moving my device over 100% tomorrow, hope the sim doesnt have a fight with my system now. Ha!
coolhandz said:
I actually thought rooting on 8.0 was a bit easier. I prefer to use SuperSU because it is what I'm used to and i felt Magisk was just picking up and had a few bugs still. Might try Magisk later.
Anyway, you just add that line to the build.prop. i put it at the very end, but it doesn't matter.
Click to expand...
Click to collapse
phew finally got everything flashed! You're right, pretty darn easy on 8.0.0. One of the guides included an installation of twrp while the other did not. I tried installing twrp 3.1.1 after using the boot img, but the zip was "corrupt", tried 2 more fresh downloads with the same issue(yes, prompted for pin). Declined having twrp install itself at the end of the recovery script. Would have continued to try, but decided against fruitlessly flashing a recovery on the off chance i botched the system.
After su flashed, it failed to mount /system. But, everything loaded fine.
Currently downloading a file explorer (es file is my usual, unless there's an xda favorite im unaware of) and will get right on that build.prop edit. Hopefully if we get 8.1, it'll be a similarly easy task.
Anyway, i know the proper route would have been to post my questions in the matching threads without creating a new one. So I'd like to personally thank everyone who came and took the time to help me out.

Just so you know. There isn't a working TWRP zip yet for 8.0 (at least that i am aware of). So you would have to use the .img each time.