Related
I'm running stock EE4 but I'm getting ready to root and install one of the debloated ROMs. Currently I have a lot of apps, home screens and ADW Launcher set to my satisfaction and settings tweaked how I like them.
What are "best practices" for pre-rooting backup so all of these are retrievable? I've used Titanium Pro on my tablet so I'm conversant with that process but don't I have to be rooted first? Should I root the phone, install TP, back-up and THEN flash the ROM? Are there alternatives?
Thanks, I await advice.
adw settings you can backup by going to adw settings and doing a backup. Not sure if there is an unrooted version of titanium. Bad part is. You cannot just root if you are EE4 already. 1click and Gingerbreak do not work on EE4. You have to Odin flash a rooted rom. Sorry. Know thats not what you wanted to hear.
dragonstalker said:
adw settings you can backup by going to adw settings and doing a backup. Not sure if there is an unrooted version of titanium. Bad part is. You cannot just root if you are EE4 already. 1click and Gingerbreak do not work on EE4. You have to Odin flash a rooted rom. Sorry. Know thats not what you wanted to hear.
Click to expand...
Click to collapse
Not true. You simply need to use Odin to flash a new kernel which is rooted (pbj by immuts for example). Once you've done this you'll also get CWM. You need to find an Odin package that only contains the kernel.
Once you've done that, with root you can use TiBackup like you've done before and then flash your ROM.
Thanks, fellas. If you're monitoring this thread, would you mind having a look over here?
keithce said:
Not true. You simply need to use Odin to flash a new kernel which is rooted (pbj by immuts for example). Once you've done this you'll also get CWM. You need to find an Odin package that only contains the kernel.
Once you've done that, with root you can use TiBackup like you've done before and then flash your ROM.
Click to expand...
Click to collapse
OK SO, ROOTED means that the ROM has SU capability which is given to it by superuser app. Which allows you to have admin capabilities to change permissions to your filesystem.
The kernel allows you to overclock and undervolt your system while giving access to other HARDWARE specific functions.
Now please explain to me how a KERNEL can give you SuperUser permission to the filesystem if the KERNEL is a bridge between the Hardware and Software. Not saying your wrong, I just don't see how a Kernel can give you root access.
dragonstalker said:
OK SO, ROOTED means that the ROM has SU capability which is given to it by superuser app. Which allows you to have admin capabilities to change permissions to your filesystem.
The kernel allows you to overclock and undervolt your system while giving access to other HARDWARE specific functions.
Now please explain to me how a KERNEL can give you SuperUser permission to the filesystem if the KERNEL is a bridge between the Hardware and Software. Not saying your wrong, I just don't see how a Kernel can give you root access.
Click to expand...
Click to collapse
Indeed, strictly technically speaking you are correct. However after the radio on the charge got updated to EE4 the usual 'back doors' or exploits to get root no longer worked.
Therefore the developers of the kernels for the charge built in the capability to auto root when it boots and hands off the hardware to the software.
If you read the posts for the kernels (e.g. http://forum.xda-developers.com/showthread.php?t=1104634) you would see that.
Cheers!
I stand corrected. It's right there in black and white. Auto-Root on Boot.
We learn something new everyday. Thanks for getting me brought up to speed.
keithce said:
Not true. You simply need to use Odin to flash a new kernel which is rooted (pbj by immuts for example). Once you've done this you'll also get CWM. You need to find an Odin package that only contains the kernel.
Once you've done that, with root you can use TiBackup like you've done before and then flash your ROM.
Click to expand...
Click to collapse
Is flashing a custom kernel, like PBJ, easily done using Odin? Do I use the same procedure when flashing CWM?
The latest version of CWM is not working--the button mapping is all screwed up. So I can't install any .zip files from my SD card -- I just keep seeing this f***ing blue banana.
So do I already need to have CWM installed to install a custom kernel? I'm waiting for someone to post CWM 4.0.0.8 until danalo is able to fix the faulty CWM currently linked for downloading
---Thank you for any help you may provide---
MrMakeIt said:
Is flashing a custom kernel, like PBJ, easily done using Odin? Do I use the same procedure when flashing CWM?
The latest version of CWM is not working--the button mapping is all screwed up. So I can't install any .zip files from my SD card -- I just keep seeing this f***ing blue banana.
So do I already need to have CWM installed to install a custom kernel? I'm waiting for someone to post CWM 4.0.0.8 until danalo is able to fix the faulty CWM currently linked for downloading
---Thank you for any help you may provide---
Click to expand...
Click to collapse
Flashing anything in Odin uses an almost identical procedure unless you're trying to also upgrade the baseband/radio/modem.
Yes, you can flash a kernel using Odin. You just have to make sure that you download the right file to be flashed because it must be in specific format (*.md5).
Here is a link to jt's kernel from this post. Its a root kernel with CWM and also includes the lagfix (reformat to EXT4) that you should be able to flash using Odin.
That should give you a working (although limited functionality) version of CWM so that you can then install everything else and upgrade when a newer working version of CWM comes out.
Basically you just need to get CWM on there once as a starting point and then you can upgrade, update, and do whatever you want from there.
A while back, I always rooted and unrooted my Nexus S with no problems at all. Now whenever I try to root it, it just goes wrong. I've tried TWRP & CWM, CWM used to always work but now it just messes up. Both TWRP and CWM both give me an error that say Installation Aborted when I try to install a custom rom. I've redownloaded the rom from different browsers and even different PCs but nothing working, still that same error. Does anyone have a guide that is 100% to work without any errors during the process?
What guide are you using?
paul96 said:
What guide are you using?
Click to expand...
Click to collapse
I used this one: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
albundy2010 said:
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
Click to expand...
Click to collapse
Alright, thanks Do you recommend that I root my Nexus S or should I wait for the Jelly Bean update? I've rooted before and I enjoyed it but now I don't see that many reasons to root, do you have any good reasons?
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
albundy2010 said:
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
Click to expand...
Click to collapse
What are your reasons for root? Please share?
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
albundy2010 said:
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
Click to expand...
Click to collapse
Oh cool. There is this project that some members from XDA are working on called Sense4All and they are porting Sense to many devices. Im probably going to wait until a fully functionable release is available for the Nexus S. I do like AOKP a lot, so that might be a reason for why I'll root.
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
albundy2010 said:
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
Click to expand...
Click to collapse
Oh, I never knew that, haha. Is it possible to flash a custom kernel with an unlocked bootloader or does that require root access?
m1l4droid said:
No you just need a custom recovery. But using that kernel's mods, like BLN, OC, UV, touchwake, etc, requires apps that need root, like NSTools, SetCPU, etc.
Click to expand...
Click to collapse
Oh alright. Now I really wanna root + install a custom rom. Do any of you have a full 100% fully working guide for rooting Nexus S and which rom should I flash first? I already know what kernel I want.
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
leap_ahead said:
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
Click to expand...
Click to collapse
Thank you so much! I rooted my phone with CWM recovery installed and Paranoid Android + gapps installed
Hello guys,
I'm still relatively new to rooting stuff on the Nexus 5 (and 7). Running a rooted stock android 4.4.4. with Franco kernal, but with Lollipop now available.. Of course I want to upgrade. I am looking for a stock android 5 rom with prepoot. Is there a prerooted rom available? And do I have to flash stock kernal first before flashing the rom?
Thanks in advance!
Justin
IVS IVRIS said:
Hello guys,
I'm still relatively new to rooting stuff on the Nexus 5 (and 7). Running a rooted stock android 4.4.4. with Franco kernal, but with Lollipop now available.. Of course I want to upgrade. I am looking for a stock android 5 rom with prepoot. Is there a prerooted rom available? And do I have to flash stock kernal first before flashing the rom?
Thanks in advance!
Justin
Click to expand...
Click to collapse
Not exactly no. L root is different from KitKat. You have to flash a permissive boot.img (kernel) before flashing SuperSU in recovery.
There are flashable zips. There is one linked in the "guides and info" link in my signatrue (see section 6)... But you still need to flash the chainfire or @sykopompos Permissive boot.img
rootSU said:
Not exactly no. L root is different from KitKat. You have to flash a permissive boot.img (kernel) before flashing SuperSU in recovery.
There are flashable zips. There is one linked in the "guides and info" link in my signatrue (see section 6)... But you still need to flash the chainfire or @sykopompos Permissive boot.img
Click to expand...
Click to collapse
Thank you for the quick reply. The rom over here: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 may suit my needs indeed. Although he's saying "-Don't install SuperSU (won't work, must use CF-Auto-Root)"
So, in my situation.. what I should do would be:
Factory reset
Flash rom with TWRP (my recovery)
Flash radio
Use the latest CF-Auto Root (for Lollipop)
Do I keep my Franco kernal?
IVS IVRIS said:
Thank you for the quick reply. The rom over here: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 may suit my needs indeed. Although he's saying "-Don't install SuperSU (won't work, must use CF-Auto-Root)"
So, in my situation.. what I should do would be:
Factory reset
Flash rom with TWRP (my recovery)
Flash radio
Use the latest CF-Auto Root (for Lollipop)
Do I keep my Franco kernal?
Click to expand...
Click to collapse
I wouldn't use CF autoroot myself. Its similar to a toolkit which we don't recommend.
All you do is flash ROM.zip
Flash Permissive boot.img (kernel)
Flash SuperSU (It will work in this case)
I'll see if I can find a link to @sykopompos boot image
No, I don't believe franco will work. I would recommend trying ElementalX though. You flash it after the permissive boot.img. You jeep the permnissive stuff as ElementalX doesn't replace RAMdisk (just modifies it) so you get best of both worlds.
Plus ElementalX is a great kernel. You'll also be running teh same setup as me then
rootSU said:
I wouldn't use CF autoroot myself. Its similar to a toolkit which we don't recommend.
All you do is flash ROM.zip
Flash Permissive boot.img (kernel)
Flash Elemental X kernal
Flash SuperSU (It will work in this case)
I'll see if I can find a link to @sykopompos boot image
No, I don't believe franco will work. I would recommend trying ElementalX though. You flash it after the permissive boot.img. You jeep the permnissive stuff as ElementalX doesn't replace RAMdisk (just modifies it) so you get best of both worlds.
Plus ElementalX is a great kernel. You'll also be running teh same setup as me then
Click to expand...
Click to collapse
Thanks allot for the explanation! Alright, to do:
Put rom on internal memory
Boot into TWRP recovery
Whipe everything, cache, system etc.
Flash the rom
Flash the radio
Flash permissive boot.img
Flash Elemental X kernal
Flash SuperSU
Then reboot
Is that the correct way?
IVS IVRIS said:
Thanks allot for the explanation! Alright, to do:
Put rom on internal memory
Boot into TWRP recovery
Whipe everything, cache, system etc.
Flash the rom
Flash the radio
Flash permissive boot.img
Flash SuperSU
Then reboot
Is that the correct way?
Click to expand...
Click to collapse
Yep, hold on on that, let me source the link.
---------- Post added at 04:33 PM ---------- Previous post was at 04:23 PM ----------
Search the OP of this thread for "modified kernel"
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003
Sorry for bothering.. I think I've got everything setup up.
I've downloaded the files:
bigxie_hammerhead_LRX21O-signed.zip (rom)
LGD820_LRX21O_RADIO.zip (radio)
N5_+LPX13D_ModifiedKernel (modified kernal)
UPDATE-SuperSU-v2.01 (SuperSU)
ElementalX-N5-2.03 (ElementalX)
Is it correct to flash it in this order? Did I get all the steps? The files I have downloaded are partially for L developer (such as SuperSU) preview.. does that matter? I also see reports of sd card not showing up.. any problems ahead?
rootSU said:
Yep, hold on on that, let me source the link.
---------- Post added at 04:33 PM ---------- Previous post was at 04:23 PM ----------
Search the OP of this thread for "modified kernel"
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003
Click to expand...
Click to collapse
Sorry for bothering.. I think I've got everything setup up.
I've downloaded the files:
bigxie_hammerhead_LRX21O-signed.zip (rom)
LGD820_LRX21O_RADIO.zip (radio)
N5_+LPX13D_ModifiedKernel (modified kernal)
ElementalX-N5-2.03 (ElementalX)
UPDATE-SuperSU-v2.01 (SuperSU)
Is it correct to flash it in this order? Did I get all the steps? The files I have downloaded are partially for L developer (such as SuperSU) preview.. does that matter? I also see reports of sd card not showing up.. any problems ahead?
Guys, I got myself in some real trouble I think.
First of all:
I came from 4.4.4. stock rooted with Franco kernal
I did make a backup in TWRP, files are on my pc.
Process:
First of all, I did a factory reset in TWRP
I flashed the rom, radio, kernal for root and supersu.
First boot went fine, although WiFi couldn't be found.
I decided to boot into recovery again to wipe my SD Card
Upon rebooting, phone is looking all black without a real 'launcher', sd card not found etc.
Than:
I managed to push rom, radio, kernal and supersu to /sdcard by adb in rocovery mode
I reflashed all of these, but the same problems occur
What should I do now? I'm ****ting my pants..
IVS IVRIS said:
Guys, I got myself in some real trouble I think.
First of all:
I came from 4.4.4. stock rooted with Franco kernal
I did make a backup in TWRP, files are on my pc.
Process:
First of all, I did a factory reset in TWRP
I flashed the rom, radio, kernal for root and supersu.
First boot went fine, although WiFi couldn't be found.
I decided to boot into recovery again to wipe my SD Card
Upon rebooting, phone is looking all black without a real 'launcher', sd card not found etc.
Than:
I managed to push rom, radio, kernal and supersu to /sdcard by adb in rocovery mode
I reflashed all of these, but the same problems occur
What should I do now? I'm ****ting my pants..
Click to expand...
Click to collapse
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Try updating TWRP to 2.8.1.0. Wipe system/data/cache/dalvik under advanced and then flash the ROM.
Sorry, only way I know how to flash a recovery is with fastboot, no zips...
Or fastboot flash the factory image but do each img separately as I hear there are still issues using the flash.all script when it comes to the system image.
jeky82 said:
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Click to expand...
Click to collapse
Sounds exactly like me indeed. Anyone knows the steps to help us?
galakanokis said:
Try updating TWRP to 2.8.1.0. Wipe system/data/cache/dalvik under advanced and then flash the ROM.
Sorry, only way I know how to flash a recovery is with fastboot, no zips...
Or fastboot flash the factory image but do each img separately as I hear there are still issues using the flash.all script when it comes to the system image.
Click to expand...
Click to collapse
Will this fix the sd card as well?
Are people having the same problem with clockworks recovery mod?
jeky82 said:
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Click to expand...
Click to collapse
I fixed it! Please check this post: http://forum.xda-developers.com/showpost.php?p=56743199&postcount=10 and follow the instructions.. you may have to flash the seperate .img files though, like I had to.
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Preston2291 said:
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Click to expand...
Click to collapse
Most kernels r flashed in recovery.
Tigerstown said:
Most kernels r flashed in recovery.
Click to expand...
Click to collapse
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Preston2291 said:
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Click to expand...
Click to collapse
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Tigerstown said:
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Click to expand...
Click to collapse
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick because I can't write to the system with a new rom
Preston2291 said:
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick
Click to expand...
Click to collapse
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Tigerstown said:
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Click to expand...
Click to collapse
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Preston2291 said:
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Click to expand...
Click to collapse
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Tigerstown said:
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Click to expand...
Click to collapse
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Preston2291 said:
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Click to expand...
Click to collapse
You should be able to just flash pretty much any sense based rom and have what you want. Write protection is removed in all of them, or, at least in all the ones I've tried.
That said, if you've already flashed a kernel that has write protection removed, you should be able to check it by just copying any file to the system folder. A text file, picture, anything. Then reboot the phone and check to see if the file you copied to the system folder is still there. If so, you're good to go. If not, write protection is still being enforced.
Can we install ROM and Kernels change settings then uninstall Magisk/root/TWRP and still keep those features?
Will they stay except for the features which will still constantly need to access some type of root?
Is this ROM or Kernel dependent or do we need to keep Magisk/root for it to work?
I am just wondering because I came from an HTC10 using LeeDroids ROMs and there I was able to set all my settings then uninstall Magisk/root and the features stayed. I wonder if this was only because of his custom ROM or can I generalize this to work most ROMs or Kernels?
Thanks.
magistrateee said:
Can we install ROM and Kernels change settings then uninstall Magisk/root/TWRP and still keep those features?
Will they stay except for the features which will still constantly need to access some type of root?
Is this ROM or Kernel dependent or do we need to keep Magisk/root for it to work?
I am just wondering because I came from an HTC10 using LeeDroids ROMs and there I was able to set all my settings then uninstall Magisk/root and the features stayed. I wonder if this was only because of his custom ROM or can I generalize this to work most ROMs or Kernels?
Click to expand...
Click to collapse
The answer is trickier on this phone. Not due to the custom ROM/custom kernel, but due to the device's A/B partition scheme. On this scheme, both TWRP and Magisk are dependent on patching the boot.img partition, which also contains the kernel. There is no discrete recovery partition. So in order to unroot and uninstall TWRP, you will need to flash a new boot.img and therefore replace the kernel. In your case, I believe you can just flash your custom kernel again. This would remove both root and TWRP, but keep the ROM, and "keep" the kernel (in fact, flashing the kernel you already have, but a version that is not rooted or have TWRP injected). User data and settings will remain (as flashing boot.img does not touch data partition). Although I'm not a custom kernel user, so I don't know where kernel settings are stored. But you should be able to keep the ROM/kernel and use all function which don't require root. Magisk Manager app will remain, since it resides on the data partition. But doesn't serve any purpose if unrooted, so go ahead and delete the app. Also keep in mind that deleting Magisk Manager doesn't in itself remove root.
Take it all with a grain of salt. Before messing with it, back any personal data you want to keep, and know how to reflash your ROM or return to stock if things go south.
magistrateee said:
Can we install ROM and Kernels change settings then uninstall Magisk/root/TWRP and still keep those features?
Will they stay except for the features which will still constantly need to access some type of root?
Is this ROM or Kernel dependent or do we need to keep Magisk/root for it to work?
I am just wondering because I came from an HTC10 using LeeDroids ROMs and there I was able to set all my settings then uninstall Magisk/root and the features stayed. I wonder if this was only because of his custom ROM or can I generalize this to work most ROMs or Kernels?
Thanks.
Click to expand...
Click to collapse
Most changes are systemless, so that won't work on this device.
Also kernel changes/tweaks are not necessarily compatible across kernels.
But also, if the goal is to go back to stock: this won't work anyway.
Going back to stock and locking the bootloader, requires wiping the device.
redpoint73 said:
The answer is trickier on this phone. Not due to the custom ROM/custom kernel, but due to the device's A/B partition scheme. On this scheme, both TWRP and Magisk are dependent on patching the boot.img partition, which also contains the kernel. There is no discrete recovery partition. So in order to unroot and uninstall TWRP, you will need to flash a new boot.img and therefore replace the kernel. In your case, I believe you can just flash your custom kernel again. This would remove both root and TWRP, but keep the ROM, and "keep" the kernel (in fact, flashing the kernel you already have, but a version that is not rooted or have TWRP injected). User data and settings will remain (as flashing boot.img does not touch data partition). Although I'm not a custom kernel user, so I don't know where kernel settings are stored. But you should be able to keep the ROM/kernel and use all function which don't require root. Magisk Manager app will remain, since it resides on the data partition. But doesn't serve any purpose if unrooted, so go ahead and delete the app. Also keep in mind that deleting Magisk Manager doesn't in itself remove root.
Take it all with a grain of salt. Before messing with it, back any personal data you want to keep, and know how to reflash your ROM or return to stock if things go south.
Click to expand...
Click to collapse
So you are saying everything is dependent on the boot.img? So say I install and fiddle around with a ROM and flash a different boot.img then everything I did with the ROM such as themes, additive features, schedulers, etc. is overwritten with the new boot.img?
There is no way to have a custom ROM around without having TWRP and root?
tech_head said:
Most changes are systemless, so that won't work on this device.
Also kernel changes/tweaks are not necessarily compatible across kernels.
But also, if the goal is to go back to stock: this won't work anyway.
Going back to stock and locking the bootloader, requires wiping the device.
Click to expand...
Click to collapse
I don't want to go back full stock just system wide. Essentially I want to keep features from the ROM such themes, schedulers, pull-down, status bar, etc. without any trace of tampering such as TWRP/Magisk/root.
magistrateee said:
So you are saying everything is dependent on the boot.img? So say I install and fiddle around with a ROM and flash a different boot.img then everything I did with the ROM such as themes, additive features, schedulers, etc. is overwritten with the new boot.img?
There is no way to have a custom ROM around without having TWRP and root?
Click to expand...
Click to collapse
No, you are misunderstanding. That is about the opposite of what I was trying to tell you. TWRP are Magisk root are dependent on boot.img. Flashing a boot.img (compatible with your custom ROM) will keep the custom ROM, but uninstall TWRP and unroot (which it sounds like you are trying to do). I'm thinking it should keep the features/settings you mentioned. But not sure on every one of those features, how the info is stored, etc.. If they are only dependent of system and user data partitions, they should remain, I would think. Although this is all a bit theoretical, as I haven't tried it myself.
---------- Post added at 09:22 AM ---------- Previous post was at 09:18 AM ----------
magistrateee said:
There is no way to have a custom ROM around without having TWRP and root?
Click to expand...
Click to collapse
Still a little confused about what you are trying to do exactly. I interpreted it as what it says in the quote directly above: keep custom ROM/kernel, remove TWRP/root, but keep the ROM features.
The thread title implies differently, that you want to uninstall the ROM/kernel (which is the situation the other user is responding to, Post #3 above).
redpoint73 said:
No, you are misunderstanding. That is about the opposite of what I was trying to tell you. TWRP are Magisk root are dependent on boot.img. Flashing a boot.img (compatible with your custom ROM) will keep the custom ROM, but uninstall TWRP and unroot (which it sounds like you are trying to do). I'm thinking it should keep the features/settings you mentioned. But not sure on every one of those features, how the info is stored, etc.. If they are only dependent of system and user data partitions, they should remain, I would think. Although this is all a bit theoretical, as I haven't tried it myself.
---------- Post added at 09:22 AM ---------- Previous post was at 09:18 AM ----------
Still a little confused about what you are trying to do exactly. I interpreted it as what it says in the quote directly above: keep custom ROM/kernel, remove TWRP/root, but keep the ROM features.
The thread title implies differently, that you want to uninstall the ROM/kernel (which is the situation the other user is responding to, Post #3 above).
Click to expand...
Click to collapse
Thanks for the response. I apologize for the misunderstanding. I guess in POST 3 it was interpreted that I want to go fully stock like a brand new phone but that was not my intention. Your response is what I am looking for:
"keep custom ROM/kernel, remove TWRP/root, but keep the rom features"
magistrateee said:
Your response is what I am looking for:
"keep custom ROM/kernel, remove TWRP/root, but keep the rom features"
Click to expand...
Click to collapse
Ok, cool. So most (if not all) of what I posted should apply. I can't guarantee that the features will remain, as I haven't personally tried this. But I have a felling that many of them will.
magistrateee said:
Thanks for the response. I apologize for the misunderstanding. I guess in POST 3 it was interpreted that I want to go fully stock like a brand new phone but that was not my intention. Your response is what I am looking for:
"keep custom ROM/kernel, remove TWRP/root, but keep the rom features"
Click to expand...
Click to collapse
I guess, the question is why?
If you are running a custom ROM, why remove TWRP and root?
You can't lock the bootloader with a custom ROM installed.
That means widevine L1 isn't available.
Pay and other applications that see bootloader status as unlocked won't work.
Keeping Magisk installed solves the second issue but only locking the BL will solve widevine.