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.
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
Dear all,
I've been reading on this forum for some time because I rooted an Ainol tablet an a Sony phone with help from here before. But now I am totally stuck with my newly acquired 2nd-hand HTC Sensation.
I successfully flashed the Revolution Rom HD 7.3 to the phone but even with OC Daemon (or any other CPU tweaker) I cannot go over 1188000 as the max value. No overclocking possible.
Phone specs:
* bootloader unlocked (this means 'rooted', right?)
* Hboot 1.27.0000 (Pyramid)
* Firmware 3.33.401.1 series.
* S-ON RL.
Further info is eMMC-boot, and it has fastboot on it.
Is it necessary to make the phone S-OFF in order to enjoy the overclocking benefits of the custom Rom?
If so, do I need to do a factory reset to stock ICS rom before I can do the S-OFF?
What is the best method for my specs to get to S-OFF?
I tried in various ways with the Revolution Rom on there, but I didn't manage to do it.
I saw this method ( http://forum.xda-developers.com/showthread.php?p=41244866 ) but I wonder if there isn't another way? I saw other methods for other Hboot numbers but not for Hboot 1.27 ... and if I do use this method, can I do it with the Revolution Rom installed?
I tried flashing various kernels not in the stock rom (some of which wouldn't flash and some of which caused the famous wi-fi error - luckily I did a Nandroid backup of my last known good configuration... had the wi-fi error twice already now). It seems also that i get some sort of 'image error' or something every time the phone goes into bootloader. I was unsure what to do with the radio file that came with the rom. I tried to flash that with CWM because I didn't know any other way, and maybe that was a mistake? I read that this may cause battery issues, and it does seem as if the battery drained fairly quickly especially while on 3g or WiFi despite black screen etc.
Please help.
PS I can provide screenshots if it helps.
Hi.
1. No, unlocked BL does not mean rooted, it's irrelative. But as you have a custom ROM installed after unlocking bootloader, you're rooted. Because custom ROMs are normally pre-rooted.
2. S-off is not required to have your CPU/GPU overclocked, but you have booted up your ROM, this means you have a flashed kernel. But I suspect something right now. Did you perform a full wipe (deleting all data on internal partitions, data, system, cache and boot)? I don't think you have done. Therefore, you might still have stock kernel, which is not overclockable. To flash a kernel without a computer, you must have gained s-off. Otherwise you may not flash any kernel flawlessly, unless you either get s-off or flash the boot.img of the kernel using fastboot commands (as you mentioned, I don't think you know it, do you?) Post a screenshot of your kernel info at about phone - software section.
SENT FROM WHATEVER IS NOT SOMETHING TO BE LOCKED AT, THE THING IS THAT IT IS SENT.
ashkan-khatar said:
To flash a kernel without a computer, you must have gained s-off. Otherwise you may not flash any kernel flawlessly, unless you either get s-off or flash the boot.img of the kernel using fastboot commands (as you mentioned, I don't think you know it, do you?) Post a screenshot of your kernel info at about phone - software section.
SENT FROM WHATEVER IS NOT SOMETHING TO BE LOCKED AT, THE THING IS THAT IT IS SENT.
Click to expand...
Click to collapse
he can flash kernel without pc(if it is as a flashable zip file)
with 4ext recovery and smartflash enabled
edit: OP you can't flash radio while on S-ON and that file can be flashed only from bootloader
you were thinking that you flashed it
and about battery in fresh install don't judge it so quickly
give it 4-5 circle charges until it settles down
then see how it bahaves
rzr86 said:
he can flash kernel without pc(if it is as a flashable zip file)
with 4ext recovery and smartflash enabled
Click to expand...
Click to collapse
Oops... I didn't remember that at all..
SENT FROM WHATEVER IS NOT SOMETHING TO BE LOCKED AT, THE THING IS THAT IT IS SENT.
Thank you to both posters so far.
I do not remember if I did a full wipe at the time.
I just remember it seemed to have fully installed...
Here is the kernel details:
3.0.16-g31a4fc7
[email protected]#1
SMP PREEMPT
This is displayed regardless of which kernel I flashed... even with faux, this is what it would show.
I thought that might be because all kernels mimic the stock kernel...
So can you confirm that this is the stock kernel?
If so, I will go ahead and wipe everything... and start from scratch.
BUT - if I do that and then restore my Nandroid backup - won't the stock kernel be back?
And can I then reflash with faux kernel or any other compatible kernel while keeping my OS configuration?
Extra info:
I have CWMrecovery on it and Fastboot.
The Revolution Rom contains 3 kernels to choose from.
Initially I probably chose stock, but then reflashed the whole thing, trying to change it to on of the other two available choices.
So if I did a complete wipe and factory reset, and then reflashed with one of the other two built-in kernels,
would it then be overclockable?
And what would happen if I then restored my Nandroid backup - would the kernel I chose with the new installation remain in place as the backup is merely the configuration?
bel1eve said:
Extra info:
I have CWMrecovery on it and Fastboot.
The Revolution Rom contains 3 kernels to choose from.
Initially I probably chose stock, but then reflashed the whole thing, trying to change it to on of the other two available choices.
So if I did a complete wipe and factory reset, and then reflashed with one of the other two built-in kernels,
would it then be overclockable?
And what would happen if I then restored my Nandroid backup - would the kernel I chose with the new installation remain in place as the backup is merely the configuration?
Click to expand...
Click to collapse
if you choose one of the other two kernels then you can overclock
when you are restoring a nandroid backup it restores everything(system,data,boot,cache etc)
so if did a nandroid with stock kernel then it will restore that kernel too
edit: i advise to use 4ext recovery for flashing roms and kernels since you are on S-ON
rzr86 said:
if you choose one of the other two kernels then you can overclock
when you are restoring a nandroid backup it restores everything(system,data,boot,cache etc)
so if did a nandroid with stock kernel then it will restore that kernel too
edit: i advise to use 4ext recovery for flashing roms and kernels since you are on S-ON
Click to expand...
Click to collapse
Ok, thank you very much for the insight. Yes, I believe the backup had stock kernel. Must have been...
3 more questions before I consider taking action:
1. How do I get 4ext on there now that I have CWM already?
2. Is there a way to backup my current setup and later restore it minus the kernel?
3. Since my phone runs real smooth as is right now and I don't play 3D games anyway - what noticeable benefits do I get from overclocking?
bel1eve said:
Ok, thank you very much for the insight. Yes, I believe the backup had stock kernel. Must have been...
3 more questions before I consider taking action:
1. How do I get 4ext on there now that I have CWM already?
2. Is there a way to backup my current setup and later restore it minus the kernel?
3. Since my phone runs real smooth as is right now and I don't play 3D games anyway - what noticeable benefits do I get from overclocking?
Click to expand...
Click to collapse
Disclaimer :I don't know much, everything I say could be wrong for all I know. But if It is I hope someone corrects me on it
1. http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
The file name for sensation should be PG58IMG.zip
2. Titanium backup
3. If you're getting the level of performance you already want, I don't think there will be any noticeable difference. Most roms come with cpu governor that will adjust the cpu speed depending on task, low cpu to intensive, overclocking increases the maximum allowed, some app will take advantage of this it will drain battery faster and since you don't require more juice why waste battery?
stillsober said:
Disclaimer :I don't know much, everything I say could be wrong for all I know. But if It is I hope someone corrects me on it
1. http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
The file name for sensation should be PG58IMG.zip
2. Titanium backup
3. If you're getting the level of performance you already want, I don't think there will be any noticeable difference. Most roms come with cpu governor that will adjust the cpu speed depending on task, low cpu to intensive, overclocking increases the maximum allowed, some app will take advantage of this it will drain battery faster and since you don't require more juice why waste battery?
Click to expand...
Click to collapse
or follow only step 2 from this thread
http://forum.xda-developers.com/showthread.php?t=1631861
for restore yes you can do also an advanced restore from 4ext recovery except titanium backup
just go to backup/restore->advanced restore and choose data
but don't restore system partition if you are coming from different rom or different base because you will have many fc's
Thank you to you both.
PG58IMG.zip - this file is 4ext? I do have this file and remember trying to install it via WMrecovery, but unsuccessful. How do I install it?
So if I understand this right, with Titanium Backup or via a 4ext advanced restore I can backup my whole configaration (installed apps, frozen apps, startup apps, accounts, screen config) for a given Rom? ANd then I can wipe everything and reflash the Rom with the desired kernel and then restore this backup and everything goes?
bel1eve said:
Thank you to you both.
PG58IMG.zip - this file is 4ext? I do have this file and remember trying to install it via WMrecovery, but unsuccessful. How do I install it?
So if I understand this right, with Titanium Backup or via a 4ext advanced restore I can backup my whole configaration (installed apps, frozen apps, startup apps, accounts, screen config) for a given Rom? ANd then I can wipe everything and reflash the Rom with the desired kernel and then restore this backup and everything goes?
Click to expand...
Click to collapse
since you are on S-ON forget any pg58img.zip file
in my previous post i gave you a link on how to install 4ext recovery
about restore absolutely yes but don't restore boot partition
note: another way to install 4ext is to install 4ext updater apk
open the apk
select the touch version if you want
it will download it and install it for you
done:good:
rzr86 said:
or follow only step 2 from this thread
http://forum.xda-developers.com/showthread.php?t=1631861
for restore yes you can do also an advanced restore from 4ext recovery except titanium backup
just go to backup/restore->advanced restore and choose data
but don't restore system partition if you are coming from different rom or different base because you will have many fc's
Click to expand...
Click to collapse
What exactly do you mean by "except Titanium Backup" ?
What are "fc's" ?
ANd what do you mean by "base" ? Kernel?
bel1eve said:
What exactly do you mean by "except Titanium Backup" ?
What are "fc's" ?
ANd what do you mean by "base" ? Kernel?
Click to expand...
Click to collapse
the ability for backup/restore exists in recovery not only in titanium backup app
that's what i mean by "except"
fc's->forceclose
it means when you are opening an app(especially a system app)it crashes immediately
by base i mean a different version of android of the same rom or a completely different rom
kernel is the brain between software and hardware
rzr86 said:
the ability for backup/restore exists in recovery not only in titanium backup app
that's what i mean by "except"
fc's->forceclose
it means when you are opening an app(especially a system app)it crashes immediately
by base i mean a different version of android of the same rom or a completely different rom
kernel is the brain between software and hardware
Click to expand...
Click to collapse
@rz86
Thanks for the steps and clarifications. Life got me away from the screen awhile but I've now successfully done what you recommended. Works a charm
I am about to flash my nexus 5 device.
I was wondering.. if i unlock the bootloader and install a custom recovery plus create a backup.. that means ill have basicly a backup on my phone of a factory ROM and kernel right ?
So If i play around with custom roms and Kernels does that mean if I want to go back to stock kernel or/and ROM I can just recover my backup files from ,for example, CWM ?
And also if anyone here knows... how big difference can a kernel for battery life extension make ?
Then..
If I want to flash both.. Custom ROM and Kernel.. Rom comes first ? And if after that .. lets say I have flashed Cyanogenmod , and I have decided to change ROMs , Do I have to flash factory ROM ? Or I can just factory reset and Flash ir over the Cyanogenmod ?
For example.. for elementalX kernel I read this line... "You should only flash ElementalX over the kernel that came with your ROM!!!" I assume that means I do flash the ROM first... and what if I want to change Kernels later on? I re-flash the factory kernel ? And how do I do that?
For now that would be it
Thanks
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
audit13 said:
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
Click to expand...
Click to collapse
Thanks!
What advantages does TWRP has over CWM ? And also does it recover other files as well or just the system ones ?
And I guess its safer to just extract the original ROMs kernel.. Just how do i do that ?
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help: https://www.youtube.com/watch?v=rLhprnOF6-U
audit13 said:
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help:
Click to expand...
Click to collapse
Thanks!
So.. If, lets say, I flash cyanogenmod. Then Flash custom kernel. In order to change other kernel which is also custom , I should first flash the factory ROM which will have kernel on it ? And then reflash the ROM and then flash the new kernel ?
Im sorry , I also read a lot about this and somewhere on the way got really confused , haha.
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
audit13 said:
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
Click to expand...
Click to collapse
Thank you. Made things much clearer. Dirty flash means just flashing over the existing custom ROM and Kernel right?
And also.. What about if i have CM and Kernel B ... But i want to go change to ParanoidAndroid and still keep the Kernel B? This ROM would remove the Kernel and I would have to re flash ir right?
And also if I am just switching around ROMs only.. I can just flash them one over another? Perhaps a factory reset is healthy in between though.
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
audit13 said:
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
Click to expand...
Click to collapse
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
rihz said:
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
Click to expand...
Click to collapse
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
wangdaning said:
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
Click to expand...
Click to collapse
Okay, thanks!
And Happy New year to you all!
So I see ALOT OF CONFUSION regarding Safestrap on the Verizon Galaxy S5, I think its about time to explain it to stop this nonsense
THIS IS MEANT FOR 11 eMMC Users, 15 eMMC Users should unlock their bootloader and use TWRP instead
What is safestrap?
Why thank-you for asking, Safestrap is essentially a second recovery written by member @Hashcode to be used for systems with locked bootloader. Safe strap IS NOT A REPLACEMENT FOR YOUR STOCK RECOVERY OR A CUSTOM RECOVERY. Safestrap on a locked bootloader cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels,(well it can but it is gonna brick) all this requires a custom bootloader, in which you could flash those things but at that point, you'd be better using SafeStrap, Flashfire or Odin to flash TWRP first.
So then what can safestrap do? Well safestrap is capable of flashing system partitions, data, cache and taking backups and even restoring them. It also has a built in file manager to give you access to system allowing the deleting, moving, and changing of files
You could run some stock based ROMs with this and in some cases pre-rooted ROMs. If you are on MM and running a pre-rooted rom, you must flash the stock kernel everytime you leave. YOU WILL NOT HAVE ROOT, but it will allow booting.
How do I access or use safestrap
Well I'll tell you this much, you DO NOT use your hard keys to do such. Don't try any button combos it just won't work. Safestrap doesn't exist on your recovery partition, but instead it exisst on the system partition, meaning you have to use the kernel to load safestrap, not hardware recovery.
On Lollipop its very simple, you need root first which can be obtained here http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 @jrkruse
In this thread it also includes instructions for installing safestrap
Once safestrap is installed, continue by opening lollipop safestrap and selecting reboot to recovery. To exit, you can simply reboot to system
Now the hardest part comes down to Marshmallow. @jrkruse has a thread here about it http://forum.xda-developers.com/ver...ow-to-flash-custom-6-0-1-roms-locked-t3393943
Unlike Lollipop you DO NOT HAVE ROOT. Sorry, just won't happen. But you can still flash some stuff. The worst part is "how do I get into safe strap?"
In the magical folder you downloaded and probably deleted when you rooted your galaxy S5, there was a Kernel file. NI2 or NK2. Either works, what you do is open up Odin on your PC and put your phone into download mode, when it boots into download mode, just flash it and it will reboot. When your phone starts up it will say "safe system not installed" or something. Press recovery. If you wait too long it'll freeze and need a battery pull. Now your in safe strap. to exit just reboot to system(possibly need to flash stock kernel via Odin for MM as safe strap flashes stock LP kernel. Again if you followed the directions in @jrkruse thread then it will manage to boot without any hassle
So why bother?
That! Is an excellent question.
For lollipop users you can flash prerooted stock based ROMs and such. You can use debloat scripts, Knox removal scripts, even modify system files and build.prop and boot and shutdown animations, change boot sounds, install xposed, use rooted apps, go crazy!!! And you can take system backups and restores. Its just awesome!
However, those on Marshmallow have a more sinister fate. Verizon doesn't like us so you CANNOT ROOT. Which means NO YOU CANNOT USE FLASHFIRE TO BOOT INTO SAFESTRAP, NOR SAESTRAP REBOOT OR SUCH. They all require root. So what can you do? Your in luck, you can flash debloat scripts to debloat some ROMs, Knox removal, take backups and do restores, you can still modify build.prop(I don't recommend it, take a backup), and even use Safestrap built-in file manager to edit the system partition, just remember, don't do anything without a backup. Also YES you can DOWNGRADE back to Lollipop if you read @jrkruse thread. You can flash custom ish stock based ROMs but you still CANNOT GET ROOT. DO NOT TRY TO FLASH A ROOTED ROM WITHOUT FLASHING A STOCK KERNEL BEFORE REBOOT.
Thanks to changes made by google you no longer can root MM+ without a custom kernel and you cannot get custom kernels without custom recovery which needs unlocked bootloaders. So sorry to those who want it but nothing we can do right now
So that's the majority of how to safestrap. Any comments or questions leave them below and I probably will answer them maybe kinda probably not.
GeTex said:
So that's the majority of how to safestrap.
Click to expand...
Click to collapse
How to safestrap? Do you even safestrap?
Nandr0idC0nsumer said:
How to safestrap? Do you even safestrap?
Click to expand...
Click to collapse
Instructions unclear, ended up with unlocked bootloader and TWRP
GeTex said:
Instructions unclear, ended up with unlocked bootloader and TWRP
Click to expand...
Click to collapse
Instructions unclear, ended up with my eMMC chip reaching terminal velocity on its ride to space
GeTex said:
So I see ALOT OF CONFUSION regarding Safestrap on the Verizon Galaxy S5, I think its about time to explain it to stop this nonsense
What is safestrap?
Why thankyou for asking, Safestrap is essentially a second recovery written by member @Hashcode to be used for systems with locked bootloader. Safe strap IS NOT A REPLACEMENT FOR YOUR STOCK RECOVERY OR A CUSTOM RECOVERY. Safestrap cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels, all this requires a custom bootloader.
So then what can safestrap do? Well safestrap is capable of flashing system partitions, data, cache and taking backups and even restoring them. It also has a built in file manager to give you access to system allowing the deleting, moving, and changing of files
You could run some stock based ROMs with this and in some cases pre-rooted ROMs. If you are on MM YOU CANNOT NOT USE SAFESTRAP WITH A PRE ROOTED ROM. YOU WILL BRICK!!!
How do I access or use safestrap
Well I'll tell you this much, you DO NOT use your hard keys to do such. Don't try any button combos it just won't work
On Lollipop its very simple, you need root first which can be obtained here http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 @jrkruse
In this thread it also includes instructions for installing safestrap
Once safestrap is installed, continue by opening lollipop safestrap and selecting reboot to recovery. To exit, you can simply reboot to system
Now the hardest part comes down to Marshmallow. @jrkruse has a thread here about it http://forum.xda-developers.com/ver...ow-to-flash-custom-6-0-1-roms-locked-t3393943
Unlike Lollipop you DO NOT HAVE ROOT. Sorry, just won't happen. But you can still flash some stuff. The worst part is "how do I get into safe strap?"
In the magical folder you downloaded and probably deleted when you rooted your galaxy S5, there was a Kernel file. NI2 or NK2. Either works, what you do is open up Odin on your PC and put your phone into download mode, when it boots into download mode, just flash it and it will reboot. When your phone starts up it will say "safe system not installed" or something. Press recovery. If you wait too long it'll freeze and need a battery pull. Now your in safe strap. Again if you followed the directions in @jrkruse thread then it will manage to boot without any hassle
So why bother?
That! Is an excellent question.
For lollipop users you can flash prerooted stock based ROMs and such. You can use debloat scripts, Knox removal scripts, even modify system files and build.prop and boot and shutdown animations, change boot sounds, install xposed, use rooted apps, go crazy!!! And you can take system backups and restores. Its just awesome!
However, those on Marshmallow have a more sinister fate. Verizon doesn't like us so you CANNOT ROOT. Which means NO YOU CANNOT USE FLASHFIRE TO BOOT INTO SAFESTRAP, NOR SAESTRAP REBOOT OR SUCH. They all require root. So what can you do? Your in luck, you can flash debloat scripts to debloat some ROMs, Knox removal, take backups and do restores, you can still modify build.prop(I don't recommend it, take a backup), and even use Safestrap built-in file manager to edit the system partition, just remember, don't do anything without a backup. Also YES you can DOWNGRADE back to Lollipop if you read @jrkruse thread. You can flash custom ish stock based ROMs but you still CANNOT GET ROOT. DO NOT TRY TO FLASH A ROOTED ROM UNLESS YOU WANT A BOOTLOOP.
Thanks to changes made by google you no longer can root MM+ without a custom kernel and you cannot get custom kernels without custom recovery which needs unlocked bootloaders. So sorry to those who want it but nothing we can do right now
So that's the majority of how to safestrap. Any comments or questions leave them ebloe and I probably will answer them maybe kinda probably not.
NOTE mods may move this thread as seen fit
NOTE2 anyone may correct, suggest content, or give me pointers, I wrote this while sick laying here in the doctors office
NOTE3 Notes will be deleted after a few days
Click to expand...
Click to collapse
Safestrap cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels, all this requires a custom bootloader. Safestrap can flash bootloader and custom kernels and TWRP This is why you should not try to do so it has safety feature built in where normal script will not flash them but it can be made to like I did with the Bootloader update and downgrade zips
DO NOT TRY TO FLASH A ROOTED ROM UNLESS YOU WANT A BOOTLOOP. As long as you flash the stock kernel back after you flash the rom systemless root will be broken and you will not bootloop. So you can flash MM roms that have systemless root just always make sure to flash stock kernel when finished if you dont you wont even have time to bootloop you will be taken to that unauthorize software is detected on your device screen
jrkruse said:
Safestrap cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels, all this requires a custom bootloader. Safestrap can flash bootloader and custom kernels and TWRP This is why you should not try to do so it has safety feature built in where normal script will not flash them but it can be made to like I did with the Bootloader update and downgrade zips
DO NOT TRY TO FLASH A ROOTED ROM UNLESS YOU WANT A BOOTLOOP. As long as you flash the stock kernel back after you flash the rom systemless root will be broken and you will not bootloop. So you can flash MM roms that have systemless root just always make sure to flash stock kernel when finished if you dont you wont even have time to bootloop you will be taken to that unauthorize software is detected on your device screen
Click to expand...
Click to collapse
I meant to say it cannot flash those on locked bootloaders
Can you reword what I should replace those with and I'll update the OP
Do you think this thread is even helpful?
GeTex said:
I meant to say it cannot flash those on locked bootloaders
Can you reword what I should replace those with and I'll update the OP
Do you think this thread is even helpful?
Click to expand...
Click to collapse
Well it can flash those on locked bootloaders but you wont like the outcome!
I need you to write my stuff your so much better at explaing stuff than me. I just had a rant on your bootloader unlock page. Nothing meant towards you!
Haha alright, just trying to not mess things up in translation, gonna attempt to reboot your root page now that MM is here and I think we can overhaul it completely, along with a few minor changes to the batch files to streamline everything. Your Rant is justified, I honestly wanted to myself but I've been holding back
My experience
Okay! I ABSOLUTELY had to add to this thread because it was so helpful and confusing at the same time. I wanted to put in some points that seriously helped me. It took me about 8.5 hours total to get this done and I think this can help save people a lot of time.
Phone, I bought an unlocked verizon samsung galaxy s5 off the web (used). 5.0 lollipop with OK base from what I could tell. I was a ten year iphone user so this was all new to me. But I've run a web company for years so I'm very familiar getting around networks and software.
The first recommendation I would have is to read, then re-read, then re-read, then re-read the initial instruction page. The original writer didn't make it Step 1, Step 2, but put multiple steps inside a sentence so you have to sometimes figure out what he's trying to say.
The first problem I ran into was flashing the NK kernel. This is confusing because the Samsung logo will freeze and no where did it say how long to wait, just be patient. This cost me HOURS. There are two things happening, the root.bat file is giving you information and then the phone is responding. I would get all the ##### notifications and then a cursor sitting at the bottom with no response. Samsung logo would freeze. To get it to work I had to install the Factory Tar BPB1 Full Restore Image.
G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip by unzipping and then using the Odin app to install. Once I did that the root.bat file would flash the kernel, I'd wait about 3-4 mins at the blinking cursor after the ### notices, then it said Root Installed and then I was off to the races. I would HIGHLY recommend doing this as from that point forward everything was soooo much smoother. I had about a dozen failures further down the process over about 4 hours because i never saw that Root Installed message at this stage. Once I did, everything was smooth.
I also did not opt out of buying Super Sume. I bought it and then removed kingroot with it and all the other steps were flawless.
For a new droid user one thing you may want to also need to know is that to move files over to the android download HandShaker, it's a much easier file transfer app to move those zip files in later stages over to the phone.
SO - If I am on Lollipop, I can load a custom ROM with Safestrap that is pre-rooted. Right? Would that allow me to load a ROM based on CM 14? What would or would not work. I have had a lot of prior experience with rooting and custom recovery, etc with my Razer M and an Xperia Play and the old LG Ally, but nothing with this S5 and no experience with Safestrap (that I can recall). Cut me a little slack - I'm 59 years old and a tech, but no experience with Samsung except ODIN a couple of times. Thanks.
netizenmt said:
SO - If I am on Lollipop, I can load a custom ROM with Safestrap that is pre-rooted. Right? Would that allow me to load a ROM based on CM 14? What would or would not work. I have had a lot of prior experience with rooting and custom recovery, etc with my Razer M and an Xperia Play and the old LG Ally, but nothing with this S5 and no experience with Safestrap (that I can recall). Cut me a little slack - I'm 59 years old and a tech, but no experience with Samsung except ODIN a couple of times. Thanks.
Click to expand...
Click to collapse
Only with an unlocked bootloader
Okay so I come from dos and Lynx area late 90s going to college and back then it was fun to sit down and code stuff and drink beer on the weekend can I just delete the hole OS out of my g900V cid 11 make my own somehow. It's been 23 yrs but sudo apt update still probably over rides a regular program saying no oh a and I barely got my first smartphone three or four months ago when I would consider smart I don't think the Samsung whatever it was was smart and just could text
averydiablo said:
Okay so I come from dos and Lynx area late 90s going to college and back then it was fun to sit down and code stuff and drink beer on the weekend can I just delete the hole OS out of my g900V cid 11 make my own somehow. It's been 23 yrs but sudo apt update still probably over rides a regular program saying no oh a and I barely got my first smartphone three or four months ago when I would consider smart I don't think the Samsung whatever it was was smart and just could text
Click to expand...
Click to collapse
No idea what you are trying to ask
CID 11 cannot run a custom OS.
Making your own OS is not anywhere near easy either
Inglis Second language is possible on rooted phone like LG spectrum 2 or g900v to get rid android just have kali or unbunt do you need bootloader unlock
averydiablo said:
Inglis Second language is possible on rooted phone like LG spectrum 2 or g900v to get rid android just have kali or unbunt do you need bootloader unlock
Click to expand...
Click to collapse
again, you cannot run anything but touchwiz based roms on a locked bootloader. you cannot use a custom kernel.
Thank you very much so now I went and traded for lg g2 and still have the vs93o old as dirt And the pixel 2 xl I don't want to mess with the other old ones I can root do they make os for lynux or Kali sorry I do understand I have hard time wording questions
GeTex said:
again, you cannot run anything but touchwiz based roms on a locked bootloader. you cannot use a custom kernel.
Click to expand...
Click to collapse
For now
ryanbg said:
For now
Click to expand...
Click to collapse
Indeed
Looking for a bit of help. I have a S5 with Emmc = 11. Know I cannot install TWRP. Have gone with all the steps from jrkruse here: http://https://forum.xda-developers.com/verizon-galaxy-s5/general/testers-required-easier-root-method-t3561529 I have no trouble getting into safestrap after rooting. The issue I have is once I flash a stock lollipop rom (either EMMC_11_PB1_LL_STOCK_SAFESTRAP_ONLY.zip or VZW_BPB1_ODEX_DEODEX_V9.zip), I can no longer access safestrap. I still have root (Super SU Pro) and busybox etc. However I can install, uninstall & re-install safestrap and when I click re-boot to recovery, it just reboots the system. I cannot figure out what the heck I am doing wrong. Is there a way to force a safestrap install that works? Or how am I destroying the SafeStrap that's part of the rom? Any suggestions would be greatly appreciated!
Thanks
John
Never mind. Installed LL_MM_SafeStrap.apk and that resolved the issue. Now have safestrap.
Thanks anyway!