I have a lot of doubts, I have a G960F/DS, RMM state is not prenormal anymore so I have the option to unlock OEM. I'll use stock ROM because I don't want to lose camera quality, so I need to figure how to install twrp, root and install xposed. I haven't even installed TWRP yet.
I see in some threads that after installing TWRP but before rooting I should install a kernel.
My phone basebands is BRF5 and compilation number is BRF8. Should I install kernel BRG5? The one in This thread, the stock one kernel. Also, should I install the TWRP flashable firmware updates to upgrade my bootloader and modem?
In which order should I do the things to have a magisk root and xposed working on my S9? I know there are some tutorial threads but I'm new to this, can't figure what things to do in which order. I have download all the things I need, odin, drivers, twrp tar file, magisk, etc.
Edit: Would it be better if I use ElementalX instead of that stock one, in terms of stability and performance? Do I still need to install the twrp flashable firmware updates?
You need to do alot more reading up and such on all the threads involved. That's the best way to fully understand all of your questions and find the answers confidently. Happy flashing
Related
Hi everyone,
I have some questions that will help me understand a lot more regarding rooting, unlocking, custom ROM's etc.
I have read a lot of things in the forums, but despite the trove of information, it's still not always easy to piece together what you need to know in order to understand or feel confident about the process. Sometimes I find answers, but they are a couple of years old and no indication they are still currently valid, etc.
- Is there any danger to sticking with the Stock Recovery as opposed to using ClockworkMod or TWRP if I am only going to be rooting, unlocking and using official Android OTA releases? If I remain with Stock Recovery, do I lose any rooting related features, or the ability to perform certain functions using NRT later?
- I want to confirm, if I keep the Stock Recovery and then I use NRT to root, unlock and flash an official stock Android release, should I then be able to get official OTA updates without having to wipe the device as I would with a Custom Recovery? I believe I would just need to unroot before the OTA, then reroot immediately after, correct?
I did read a thread that talked about how to restore stock recovery without losing data... but I'm using NRT and want to stick with that, which I don't think offers that option. I just want to keep it as simple as possible since I'm new to this. I'm afraid that if I mix methods, it will cause issues.
- If I decide to try an alternate ROM such as CyanogenMod, is that when using a Custom Recovery will become absolutely essential?
Under this scenario, would updates to CyanogenMod (or the other popular ROM's) require wiping the device data?
Thanks to anyone who can confirm if I'm understanding this all correctly.
dezzo77 said:
Hi everyone,
I have some questions that will help me understand a lot more regarding rooting, unlocking, custom ROM's etc.
I have read a lot of things in the forums, but despite the trove of information, it's still not always easy to piece together what you need to know in order to understand or feel confident about the process. Sometimes I find answers, but they are a couple of years old and no indication they are still currently valid, etc.
- Is there any danger to sticking with the Stock Recovery as opposed to using ClockworkMod or TWRP if I am only going to be rooting, unlocking and using official Android OTA releases? If I remain with Stock Recovery, do I lose any rooting related features, or the ability to perform certain functions using NRT later?
- I want to confirm, if I keep the Stock Recovery and then I use NRT to root, unlock and flash an official stock Android release, should I then be able to get official OTA updates without having to wipe the device as I would with a Custom Recovery? I believe I would just need to unroot before the OTA, then reroot immediately after, correct?
I did read a thread that talked about how to restore stock recovery without losing data... but I'm using NRT and want to stick with that, which I don't think offers that option. I just want to keep it as simple as possible since I'm new to this. I'm afraid that if I mix methods, it will cause issues.
- If I decide to try an alternate ROM such as CyanogenMod, is that when using a Custom Recovery will become absolutely essential?
Under this scenario, would updates to CyanogenMod (or the other popular ROM's) require wiping the device data?
Thanks to anyone who can confirm if I'm understanding this all correctly.
Click to expand...
Click to collapse
I'll try to answer as many of these as I can.
1. There is no danger in sticking with the stock recovery, but you do lose some features - most notably stuff like backup/restore, and a whole bunch of advanced features that are either not present in, or are hard to get to in the stock recovery. I'd suggest TWRP - works great with mine, even though I use CWM for all my other devices.
2. In theory yes, not sure about this though.
3. Just get TWRP makes life easier.
4. It's still not essential, but VERY useful unless you want to push every zip through ADB instead of just hitting the "install zip" button. As for the updates - if it shows up in the update section it won't wipe your data, if you have to flash through a recovery it MIGHT, but not 100% sure.
There you are - feel free to correct me on any of this
Sorry for asking this in others thread but I just want to know something..
I am currently on aicp which is 4.3.1..if I want to update to kitkat..what method can preserve the data on my sdcard?
Well, I did have TWRP installed, running stock 4.4 and rooted and unlocked... then the 4.4 build got a minor OTA update.. and guess what?
Can't install it without losing all my data, because TWRP is installed. At least, that's what I read.
So, I decided TWRP had to go.
I can't keep wiping the device every time I do an OTA, so that's really the main thing I want to avoid.
dezzo77 said:
Well, I did have TWRP installed, running stock 4.4 and rooted and unlocked... then the 4.4 build got a minor OTA update.. and guess what?
Can't install it without losing all my data, because TWRP is installed. At least, that's what I read.
So, I decided TWRP had to go.
I can't keep wiping the device every time I do an OTA, so that's really the main thing I want to avoid.
Click to expand...
Click to collapse
You can install the ota with twrp.
You can also replace twrp with stock recovery without wiping the device.
The only process that wipes the device is unlocking the bootloader,. If you leave it unlocked you can switch around as much as you like
I have the Galaxy S3 I747 rooted with CF auto-root (I used the instructions on the second post of this thread:http://forum.xda-developers.com/showthread.php?t=1963790) and the root went great. But now that it's rooted, I can't flash CWM ROM manager recovery because the KNOX security system won't let me. I can't install new ROMs and I keep getting a pop-up that says 'superSU has stopped working.'
Dose anyone know of a way to remove KNOX or of some other solution that will allow me to flash custom ROMs? I've skimmed a lot of the threads in the development forums and the general discussion forums but haven't found any sort of guide that I can understand (I'm a bit of a n00b when it comes to bootloaders and such).
Without Reason said:
I have the Galaxy S3 I747 rooted with CF auto-root (I used the instructions on the second post of this thread:http://forum.xda-developers.com/showthread.php?t=1963790) and the root went great. But now that it's rooted, I can't flash CWM ROM manager recovery because the KNOX security system won't let me. I can't install new ROMs and I keep getting a pop-up that says 'superSU has stopped working.'
Dose anyone know of a way to remove KNOX or of some other solution that will allow me to flash custom ROMs? I've skimmed a lot of the threads in the development forums and the general discussion forums but haven't found any sort of guide that I can understand (I'm a bit of a n00b when it comes to bootloaders and such).
Click to expand...
Click to collapse
You can de-knox in several ways - from the phone settings; by flashing a pre-rooted and de-knoxed ROM e.g. the modified (stock) MJ2 ROM. You can also flash the knox removal tool which you will find in the thread below which also shows another way to route other than CF-Auto Root.
http://forum.xda-developers.com/showthread.php?t=2538991
Strictly speaking, however, I would doubt Knox is the culprit here. Knox is a security tool designed primarily for enterprise settings and would not stop you from flashing a custom recovery like CWM. I would suggest you re-root via Method 2 in the above thread as CF-Auto Root doesn't always work with stock 4.3.
You can also try flashing other custom recoveries like Philz Touch (enhanced CWM) or TWRP to install custom ROMs.
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
itsfredo said:
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
Click to expand...
Click to collapse
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
The Sickness said:
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
Click to expand...
Click to collapse
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
I don't know if towelroot will root 4.2.2, but it doesn't install a recovery.
Rob
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
lordcheeto03 said:
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
This.
You really don't need CF Auto Root at all until all you want to do is root the stock rom.
If you want to install a customer rom, use Odin to install a custom recovery and flash whatever you want from there.
lordcheeto03 said:
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Use cf autoroot and flash clockworkmod through Odin. Download rommanager. Download a rom. Hit install rom from SD card. Pick your ROM from downloads.
itsfredo said:
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Click to expand...
Click to collapse
I understand your apprehension, i really do. What I've said to do has worked for me when i got the phone over a year ago, and has worked here recently when i did it again. I'm trying to tell you there is no need for an updated way of doing what you want. If you want root, use CFauto root. Like i said, that method was done specifically for MDB and MDL firmwares, there is no better choice. Newer yeah, but better? Not a chance. Your firmware is equally outdated and it's worked for millions of users without fail.
As far as a custom ROM goes, find one you want to use, put it on your SD card, pick a recovery (CWM, Philz, or TWRP), flash that in Odin, boot to recovery (power+volume up) , do a full wipe (system, data, and cache) select the ROM, and flash. No need to root at all if you want to go straight to a custom ROM.
EDIT: Obviously, you might want to perform a nandroid backup once you flash your recovery... but that's really optional as long as you have the stock Odin-flashable firmware. Totally up to you.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Hi everyone.
I searched a lot but I did not find any clear answer to my issue.
Pre-conditions - I have:
- the original stock rom kernel .108
- root permissions obtained via Easy Root Tool
- locked bootloader
- dual recovery
- xposed module
My simple questions are:
1 - To update to the latest firmware (.157) I can update via OTA or, as I have obtained root permissions, I need to do a manual flash?
In case I would like to update manually, is it sufficient to flash only the kernel? Or is it necessary to flash the complete .ftf?
2 - If I update to .157 via OTA, I will loose the root permissions and/or xposed module and/or dual recovery and/or I risk to soft-brick my phone and/or to cause any relevant problems?
Probably the questions seems very similar to many others already posted (and answered) but, to be honest, I never found this questions with the important pre-condition to come from the stock rom and from .108 kernel (almost the latest).
I read that after updating to .157, in case of root loss, you have to flash .108 kernel, root again and then flash .157 kernel.
So I have supposed that the issues that seem to come with the update could not apply in case of coming from the "almost latest kernel" (.108).
Besided, I supposed I could not face any issue in case I try to update via OTA, as I am using the stock rom (although it is rooted).
Thanks to everyone who would like to help me.
Gianluigi
Hello All,
I am currently looking at different ways to try and update my device to dojc or doj7. Right now it is on DOH6 and seems like I have a few random glitches with the way it works and crashes. I am rooted currently with engineering bootloader with a custom recovery. I am thinking of one of two paths and wondering what might be the better of the two options in your opinion.
First, create a firmware file to flash with Odin that does not have the bootload file in it and flash that. Then root the device again the same way I did with the DOH6 root method and engineering bootloader. Stay on that install from Samsung and just root it.
Second, install a custom rom with that new version as a base (I think I remember seeing some stock rooted roms). and then upgrade the modem only with odin. Not sure if there is anything else other that the modem that would need to be updated with Odin.
I am just not sure if that second option would work if the firmware is too different to work with it. Any opinions on which might be the better option? How have you been able to update to DOJ7 or DOJC and root without worrying about Knox? And input would be greatly appreciated.
Couldn't you just flash a custom Rom and flash the new modem with Odin?
Would that work okay guys? I think that should be fine and leave the bootloader on 5.0 engineering and it won't trip Knox.