Develop Bugs

[Q] Device saying it is rooted but cannot flash ROM's

I rooted my AT&T Samsung Galaxy S3 & when I go to recovery mode to try to install a ROM from SD there is no option to do so on the external or internal yet my phone says it is rooted.
I have rooted & installed custom ROM's on other android phones with no issues but this phone seems to not be as easy to root and install a custom rom :/
anybody ever heard of this ?

did you flash a custom recovery such as CWM or TWRP?

Galaxayy said:
I rooted my AT&T Samsung Galaxy S3 & when I go to recovery mode to try to install a ROM from SD there is no option to do so on the external or internal yet my phone says it is rooted.
I have rooted & installed custom ROM's on other android phones with no issues but this phone seems to not be as easy to root and install a custom rom :/
anybody ever heard of this ?
Click to expand...
Click to collapse
If in recovery you see a big green android you are in stock recovery. Won't be able to do much there
Check out xBeerdroidx guide
There is a section on installing recoveries and flashing roms. http://forum.xda-developers.com/showthread.php?t=2179330
Sent from my SGH-I747 using xda app-developers app

I flashed CWM
it is in CWM recovery mode so thats another reason why I am so confused

Try twrp. Just dl goo manager, it will install it for you.

I will try it, I really want a custom ROM, I loved them on my other device. I don't get why it seems so much more difficult on the S3

Galaxayy said:
I flashed CWM
it is in CWM recovery mode so thats another reason why I am so confused
Click to expand...
Click to collapse
what did you use to flash cwm? if it was a successful and correct flash, then there should be no issue.
Galaxayy said:
I will try it, I really want a custom ROM, I loved them on my other device. I don't get why it seems so much more difficult on the S3
Click to expand...
Click to collapse
its not difficult at all. i'm not bashing you, per se, just letting you know that if you have done what a million other S3 users have then it should be working just fine.

xBeerdroiDx said:
what did you use to flash cwm? if it was a successful and correct flash, then there should be no issue.
its not difficult at all. i'm not bashing you, per se, just letting you know that if you have done what a million other S3 users have then it should be working just fine.
Click to expand...
Click to collapse
I used CF auto root which means it should of done it correctly Super SU is on my phone and it says its rooted so I don't know what else , but if I did anything wrong I would be shocked I'm not a Noob at rooting and all that.

Galaxayy said:
I used CF auto root which means it should of done it correctly Super SU is on my phone and it says its rooted so I don't know what else , but if I did anything wrong I would be shocked I'm not a Noob at rooting and all that.
Click to expand...
Click to collapse
i didnt ask how you rooted. i believe you when you say you are. i asked how you flashed cwm. if all you have done is root, then you need to install a custom recovery to begin flashing ROMs.

xBeerdroiDx said:
i didnt ask how you rooted. i believe you when you say you are. i asked how you flashed cwm. if all you have done is root, then you need to install a custom recovery to begin flashing ROMs.
Click to expand...
Click to collapse
PHP:
cwm automatically was installed with cf root . so I didn't have the option to flash another.

Galaxayy said:
PHP:
cwm automatically was installed with cf root . so I didn't have the option to flash another.
Click to expand...
Click to collapse
then i would install custom recovery via either goo manager (for twrp) or rom manager (for cwm). what version of cwm does your recvoery say at the top of the screen? .
---------- Post added at 03:43 PM ---------- Previous post was at 03:27 PM ----------
Galaxayy said:
PHP:
cwm automatically was installed with cf root . so I didn't have the option to flash another.
Click to expand...
Click to collapse
you need to go back and look over the OP of the root method you used. no custom recovery is installed. it specifically states that. please read again: http://forum.xda-developers.com/showthread.php?t=1963790

xBeerdroiDx said:
then i would install custom recovery via either goo manager (for twrp) or rom manager (for cwm). what version of cwm does your recvoery say at the top of the screen? .
---------- Post added at 03:43 PM ---------- Previous post was at 03:27 PM ----------
you need to go back and look over the OP of the root method you used. no custom recovery is installed. it specifically states that. please read again: http://forum.xda-developers.com/showthread.php?t=1963790
Click to expand...
Click to collapse
I unrooted & re rooted & then I tried what mrhaley30705 said & it worked & I am flashing the ROM I want now. Thank you everyone

Galaxayy said:
I unrooted & re rooted & then I tried what mrhaley30705 said & it worked & I am flashing the ROM I want now. Thank you everyone
Click to expand...
Click to collapse
on a side note these is no easier phone to root and install rom's on than the SGS3

Can't load custom Recovery

Hi, I have the optimus g pro E980 and im having the following problem:
So i have a dillema with my custom recovery. I am trying to flash Beanstalk, but i had a problem with installing cwm. Rom manager's cwm an twrp wont work, it just has the android with his chest open and a red "!" triangle on him. goo manager's open recovery script says there is no recoveries found. I tried freeGee but the app wont load properly to use it. I have downloaded the madmack's updated TWRP and the modem to go with it but Idk how to install the zip on it without the custom recovery.
My root is successful as I followed the guide for the chinese root program since I had the 4.1.2 version of android. Sorry I sound nubbish, im just having trouble doing this since the rom manager failed me

jakobeisawesome said:
Hi, I have the optimus g pro E980 and im having the following problem:
So i have a dillema with my custom recovery. I am trying to flash Beanstalk, but i had a problem with installing cwm. Rom manager's cwm an twrp wont work, it just has the android with his chest open and a red "!" triangle on him. goo manager's open recovery script says there is no recoveries found. I tried freeGee but the app wont load properly to use it. I have downloaded the madmack's updated TWRP and the modem to go with it but Idk how to install the zip on it without the custom recovery.
My root is successful as I followed the guide for the chinese root program since I had the 4.1.2 version of android. Sorry I sound nubbish, im just having trouble doing this since the rom manager failed me
Click to expand...
Click to collapse
sounds like a root issue to me. freegee shdould load without issues.

luisoman2000 said:
sounds like a root issue to me. freegee shdould load without issues.
Click to expand...
Click to collapse
Idk what to do, Ive tried restoring to stock 3 times, I did a ton on troubleshooting with someone on these forums...it's not bootlooped but yet i cant ever get the recovery to work :/

jakobeisawesome said:
Idk what to do, Ive tried restoring to stock 3 times, I did a ton on troubleshooting with someone on these forums...it's not bootlooped but yet i cant ever get the recovery to work :/
Click to expand...
Click to collapse
you could try another method to root instead. the install freegee and cwm/twrp.

luisoman2000 said:
you could try another method to root instead. the install freegee and cwm/twrp.
Click to expand...
Click to collapse
Sadly I added cwm before I installed Freegee, and now freegee gives me tons of errors and freeze to where I cant use it

jakobeisawesome said:
Sadly I added cwm before I installed Freegee, and now freegee gives me tons of errors and freeze to where I cant use it
Click to expand...
Click to collapse
How did you return to stock, via KDZ? if so you are unrooted and have to root again. Installing freegee without root will give errors.
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
http://forum.xda-developers.com/showthread.php?t=2362657&postcount=1
try this root method, it worked for me.

luisoman2000 said:
How did you return to stock, via KDZ? if so you are unrooted and have to root again. Installing freegee without root will give errors.
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
http://forum.xda-developers.com/showthread.php?t=2362657&postcount=1
try this root method, it worked for me.
Click to expand...
Click to collapse
No I re root everytime. this is what I used to flash the stock. http://forum.xda-developers.com/showthread.php?t=2302660&highlight=recovery
Do you think the stock recovery mode doesnt flash back with this method? Even with I try to flash Twrp loki it still says i'm under my stock recovery on the flashify app.

luisoman2000 said:
How did you return to stock, via KDZ? if so you are unrooted and have to root again. Installing freegee without root will give errors.
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
http://forum.xda-developers.com/showthread.php?t=2362657&postcount=1
try this root method, it worked for me.
Click to expand...
Click to collapse
Also I did a boot with KDZ and now everytime I boot it puts my phone into "All auto test - FTM mode" and I cant exit out of it

Freegee has su permissions? On mine, su denied it after I allowed it. And this made it act abnormal when trying to open it.
Sent from my LG-E980 using XDA Premium 4 mobile app

Yup, freegee needs su permissions, that is why it sounds like a bad root to me
Sent from my LG-E980 using Tapatalk

I don't think ftm mode can be entered into with cwm present. I tried just now, with twrp, and could not enter into ftm.
Have you looked into using flashtools to flash stock image files? I don't know the ins and outs of that specific to this device, just an idea.
Sent from my LG-E980 using XDA Premium 4 mobile app

The only way to install a custom recovery on the e980 is by installing FreeGee, our boot loader is locked and the only way to bypass that is by installing FreeGee after you are rooted. You need to return back to stock using LG flashtools and start over again, once you are done with the restore, then you root and finally FreeGee, and you should be able to flash anything you like.
Hope it helps.
Erik

ricco333 said:
The only way to install a custom recovery on the e980 is by installing FreeGee, our boot loader is locked and the only way to bypass that is by installing FreeGee after you are rooted. You need to return back to stock using LG flashtools and start over again, once you are done with the restore, then you root and finally FreeGee, and you should be able to flash anything you like.
Hope it helps.
Erik
Click to expand...
Click to collapse
It worked after I did exactly this! I have a question, what does everyone normally set their core limits with the trickster mod? I read someone on the forum sets theirs on 810MHz min and 1350MHz max. I feel right now as though my idle battery is good but my active usage could be better. I'm on the beanstalk rom if it helps

Systemless Root: SuperSU v2.64... No (custom) Kernel needed

**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.

Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.

balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.

balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
Fixed!

koop1955 said:
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
Click to expand...
Click to collapse
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).

JoeFCaputo113 said:
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
Click to expand...
Click to collapse
I wasn't sure if CM13 is already working on International phones.
I only know what I read....
From Chainfire's post:
Rooting procedure:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload latest...
Joe, be careful if you try this. Looks like you need to Odin back to stock.

Does this still void knox?

1619415 said:
Does this still void knox?
Click to expand...
Click to collapse
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.

koop1955 said:
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
Click to expand...
Click to collapse
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox

1619415 said:
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
Click to expand...
Click to collapse
Well Merry Christmas!

JoeFCaputo113 said:
Well Merry Christmas!
Click to expand...
Click to collapse
You to
---------- Post added at 01:52 PM ---------- Previous post was at 01:01 PM ----------
Has anyone tried rooting with this method and trying samsumg pay?

Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.

todivefor said:
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
Click to expand...
Click to collapse
Try Number 15

1619415 said:
Try Number 15
Click to expand...
Click to collapse
Thanks. Been there done that.
Sent from my SM-T710 using Tapatalk

For those asking about whether this root method trips knox or not. Yes this will trip knox. Anytime you use odin to flash non official Samsung firmware/software then it forever trips knox. Therefore flashing any custom recovery will absolutely trip knox... forever.
Samsung and Android pay apps will not work on rooted devices. Period. The pay apps are intended for official factory software for obvious reasons. Security is the main focus with these types of apps that deal with your personal banking/credit card information. Hence a rooted device is not considered "secure".

using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.

yaibakt said:
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
Click to expand...
Click to collapse
Try installing/updating busybox and try removing titanium backups root access them regrant it

JoeFCaputo113 said:
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Click to expand...
Click to collapse
Nice work will give this a go soon.

1619415 said:
Try installing/updating busybox and try removing titanium backups root access them regrant it
Click to expand...
Click to collapse
thank you. ill give it a try. :good:

This may be a weird question, but we don't have a stock kernel to flash. Would there be a way to make a zip of a stock kernel and then use this to get root? I'd like to have a custom ROM but with the stability of a stock Kernel. This is the first phone I can think of that I've owned that didn't have a stock kernel with root.

Verizon Note 4 on 6.0.1 Help Rooting

Hey so i have done my job and spent the past week figuring out how to do this. Unfortunately i am on 6.0.1 and every time i flash TWRP 2.8.7.0 VSW with odin my phone blocks it and says SECURE CHECK FAIL (RECOVERY). yes my reactivation lock is off and nothing is encoded. as of right now my phone is working but i would really like to get it rooted soon and any help is appreciated.

joe1996 said:
Hey so i have done my job and spent the past week figuring out how to do this. Unfortunately i am on 6.0.1 and every time i flash TWRP 2.8.7.0 VSW with odin my phone blocks it and says SECURE CHECK FAIL (RECOVERY). yes my reactivation lock is off and nothing is encoded. as of right now my phone is working but i would really like to get it rooted soon and any help is appreciated.
Click to expand...
Click to collapse
You need to be rooted before you flash TWRP. Have you already gone through the steps to root your phone?

quinciebee said:
You need to be rooted before you flash TWRP. Have you already gone through the steps to root your phone?
Click to expand...
Click to collapse
No I am not rooted every guide I find says you need to flash a custom recovery then install the root from that recovery?

Hi i have Samsung note 4(SM-N910F). When i check root status with( phono info apk) it says root existence (/system/xbin/su) and check with Root checker apk it shows congratulations you are rooted. but super su apk not working after download this apk when i update binary it takes too long time and some times mobile restart itself. Total problem is super su apk not working Now what should i do? Please help me

joe1996 said:
No I am not rooted every guide I find says you need to flash a custom recovery then install the root from that recovery?
Click to expand...
Click to collapse
You may be confusing flashing supersu in a custom recovery, with rooting your phone. There are a number of steps you have to go through before you can gain root on the Verizon Note 4. Flashing a custom recovery will not root your phone. You have to first follow the steps here, before you can flash a custom recovery, then flash supersu, in order to gain access to your root.
---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------
Banty448 said:
Hi i have Samsung note 4(SM-N910F). When i check root status with( phono info apk) it says root existence (/system/xbin/su) and check with Root checker apk it shows congratulations you are rooted. but super su apk not working after download this apk when i update binary it takes too long time and some times mobile restart itself. Total problem is super su apk not working Now what should i do? Please help me
Click to expand...
Click to collapse
Try flashing the supersu zip in your custom recovery, instead of installing it through the app store. You also have an N910F, this thread is for N910V. You'd probably get a more accurate response if you posted to the N910F thread.

quinciebee said:
You may be confusing flashing supersu in a custom recovery, with rooting your phone. There are a number of steps you have to go through before you can gain root on the Verizon Note 4. Flashing a custom recovery will not root your phone. You have to first follow the steps here, before you can flash a custom recovery, then flash supersu, in order to gain access to your root.
So I have successfully restored my note 4 to 5.1.1 not im going for root and a custom rom. ill keep you updated.:good:
Click to expand...
Click to collapse

Banty448 said:
Hi i have Samsung note 4(SM-N910F). When i check root status with( phono info apk) it says root existence (/system/xbin/su) and check with Root checker apk it shows congratulations you are rooted. but super su apk not working after download this apk when i update binary it takes too long time and some times mobile restart itself. Total problem is super su apk not working Now what should i do? Please help me
Click to expand...
Click to collapse
Manually flash SuperSU 2.79 (or later) if you are prior to 7.0.1 at this point systemless root becomes necessary .....and I don't know man . I have it working on 7.1.1 but it came loaded I didn't have to install ....hmmmm I'd start at chain fires web site see what he says . ignore anything involving cfauto root unless u achieved root by this means in which case u r in the wrong forum
---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------
joe1996 said:
quinciebee said:
You may be confusing flashing supersu in a custom recovery, with rooting your phone. There are a number of steps you have to go through before you can gain root on the Verizon Note 4. Flashing a custom recovery will not root your phone. You have to first follow the steps here, before you can flash a custom recovery, then flash supersu, in order to gain access to your root.
So I have successfully restored my note 4 to 5.1.1 not im going for root and a custom rom. ill keep you updated.:good:
Click to expand...
Click to collapse
When you flash supersu it does install app and binary :laugh: see if u got to the point u could flash from twrp it would signify you are on unlocked boot loader. Without unlocking root will only persist til reboot then process would need to be repeated. The only way to fix this is to be able to mod the boot IMG which requires developer mode to be enabled . this is notable by the presence of an unlocked lock on the first splash screen (secondary program loader splash)
Click to expand...
Click to collapse

Root and update OTA?

Hello ,
I will have a ONE PLUS 5T.
I would like to root this one to have adblocker...
First question : How could root this?
Second question: If my phone is rooted, is it possible to have update OTA (or like samsung, impossible after)?
Thank you;

If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.

jim262 said:
If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.
Click to expand...
Click to collapse
it's chinese for me your answer... is there a tutorial for that?

ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
Guide: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
You can't use OTAs after you root. You'll need to download the full update every time one is released and flash it in TWRP.

ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.

jim262 said:
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.
Click to expand...
Click to collapse
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?

santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.

shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
If we root our device.can we install ota manually via twrp ??
If yes, then how??

Amanpreetsingh said:
If we root our device.can we install ota manually via twrp ??
If yes, then how??
Click to expand...
Click to collapse
Let me clarify: OTA stands for Over-The-Air and implies that you're going to download the partial update from OnePlus and install it in stock recovery. Do NOT do this.
OnePlus usually publishes full zips of their updates when the OTA is released. Currently a mirror for them exists in the guides section. You can flash those (>1 GB) safely in TWRP to update OOS.

santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
What's the difference? You still need to reroot.

jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
I apologize if I'm out of the loop. When I first read about OTAs with root I was on a Samsung device and everyone said that it would either brick the phone or upgrade the OS with no way to re-root the device. Looking through your answer it's obvious that that fear probably only applies to Samsung devices. Thanks for correcting me on this.

jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
Thanks Jim , I can confirm this works without problems on op5t. I had TWRP flashed and rooted with xposed installed.
I clean flashed the 4.7.1 stock ROM and got stock recovery and fresh os.
Just booted to TWRP using fastboot boot and rooted / installed xposed.
I got OTA updated to 4.7.2 and rerooted using fastboot boot TWRP and now rooted with xposed on stock ROM and stock recovery. ?

I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?

ilan78 said:
I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?
Click to expand...
Click to collapse
Exactly like I said. Rooting, by itself, does not wipe your storage. The only time your storage is wiped is when you unlock your (bootloader) phone, when you manually choose to wipe storage in TWRP or when you do a factory reset. If you do not have an unlocked bootlader, you must make a backup of your files first, as once you unlock it does a factory reset. You can then run TWRP and restore your files. You are now rooted with your files and ability to take OTAs. There are plenty of tutorials here on XDA describing the process step by step. May I suggest you do a search first. You are very likely to get all the answers to these questions as they have been asked many, many times.

Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Look through the Magisk forum. They have a method of rooting that doesn't require a custom recovery.
I use helium backup for my non-root app backup needs. Settings are trickier and I typically do them over every time. Super backup & restore is good for call logs, texts, and contacts.

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Did you read my post? The answers are all there. SEARCH! This question has been asked several times a day. You need to back up your data to another site, such as cloud, other device or PC. Then unlock bootloader, run TWRP and root file, then restore data. Tutorials are online. Now SEARCH!

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Man seriously! You got your answers and still you keep asking. Makes me wonder if you are just trolling

Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?

Tefzors said:
Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?
Click to expand...
Click to collapse
Yes, as far as I know, if on stock OOS, you download the full zip (over 1GB in size), flash that in TWRP, and then flash root solution right after (before leaving TWRP) to prevent it being overwritten by the stock recovery.
I don't think dirty flashing has any downsides, but if you do end up running into issues, a clean flash usually solves them