Develop Bugs

SuperSU and Stock Recovery

is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..

You need a custom recovery (TWRP or CWM).

bkeaver said:
is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
Click to expand...
Click to collapse
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img

uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.

uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Thanks this worked :good:

so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls

bkeaver said:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
Click to expand...
Click to collapse
You have stock recovery.

BenPope said:
You have stock recovery.
Click to expand...
Click to collapse
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...

bkeaver said:
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
Click to expand...
Click to collapse
I think you have to hold volume up and hit power or something.

ok I am good.. thank you... I'm putting everything back to stock because someone bought my phone and I just want to make sure everything is correct on it now.. thanks!!

redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves

and btw thanks everyone for the help. I hit my thanks button but on my browser it it isn't showing it just to let you know....

bkeaver said:
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
Click to expand...
Click to collapse
Sounds like somebody that is a bit ill-informed. They want root, but they probably also want OTA (the 2 don't go together, IMO) and heard that you need stock recovery for OTA. I suppose they can change everything back that they modified with root, and unroot or hide root to install the OTA. But it just seems they are making life more complicated than it needs to be.
Also sounds like its a person that wants root, but not willing to do it themselves. But I suppose that's not really your problem!

Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified

Mr Hofs said:
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Click to expand...
Click to collapse
yeah this is what I did for them so who knows.. I've never tried it that way but i guess it would work like that

redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
Rooting doesn't affect ota's, at least not in my experience.

ashyx said:
Rooting doesn't affect ota's, at least not in my experience.
Click to expand...
Click to collapse
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.

redpoint73 said:
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
Click to expand...
Click to collapse
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.

ashyx said:
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
Click to expand...
Click to collapse
Because once you accept an OTA, you will be unrooted. You will have to root again, either by installing custom recovery (than back to stock recovery so you can OTA) or the trick of booting custom recovery via adb to flash SU (as described here). Its just a lot of jumping through hoops with little added value.
On the other hand, if you have custom recovery installed, you can flash any of the array of stock rooted or awesome custom ROMs posted here. This includes stock rooted ROMs taken from OTA updates from lots of versions (often posted within days of the OTA starting to roll out), not just your carrier, so you can possibly get an update much faster than waiting for the OTA to roll out from your carrier (although that depends on what carrier version you have). You also don't have to constantly be worried "well, if I change this I won't get OTAs". You can do whatever the heck you want, and isn't that really the whole point of root?
Its just my opinion. And a lot of this may stem from the fact that I'm on AT&T, who are not only agonizingly slow about rolling out OTAs (sometimes 3-4 months or even later than other carriers on my past HTC device) and have even went to the effort to close exploits and prevent unlocking of bootloaders when rolling out new OTAs (on the One X EVITA). In fact there was even a bug (I assume it was a bug - others may accuse that it was intentional) where installing the Jellybean OTA with SuperCID and S-on bricked the phone.
As I said, its just an opinion. But there are many others on XDA that will agree that OTAs have no place on rooted Android devices.
And to be fair, I did cover myself and stated "there is little point" instead of "there is no point"

advice please

was wondering can i just root my m8 without flashing recovery all i want is to install adaway to block ads thats if someone could please advise

Depending on what build you are on (newer ones can't go it), you may be able to fastboot boot recovery instead of flashing recovery. Once booted into recovery, you can flash SU or SuperSU.
You need to be bootloader unlocked either way. So I actually don't see a point in doing what you ask. Once you root, you can always install stock recovery again.

redpoint73 said:
Depending on what build you are on (newer ones can't go it), you may be able to fastboot boot recovery instead of flashing recovery. Once booted into recovery, you can flash SU or SuperSU.
You need to be bootloader unlocked either way. So I actually don't see a point in doing what you ask. Once you root, you can always install stock recovery again.
Click to expand...
Click to collapse
ok thanks i get phone tomorrow so will give it a go i used to have s5 which was easy to root this sounds complicated

pnr2020 said:
ok thanks i get phone tomorrow so will give it a go i used to have s5 which was easy to root this sounds complicated
Click to expand...
Click to collapse
Every device and manufacturer has its own subtle differences and learning curve. Its really not what hard, just read up and make sure you understand before messing around with it.

pnr2020 said:
was wondering can i just root my m8 without flashing recovery all i want is to install adaway to block ads thats if someone could please advise
Click to expand...
Click to collapse
Follow this guide for rooting.
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
but as redpoint73 said you have to unlock bootloader and install custom recovery.

Rantrave07 said:
but as redpoint73 said you have to unlock bootloader and install custom recovery.
Click to expand...
Click to collapse
That is not exactly what I said. If the phone is 4.4.3 or 4.4.2, OP should be able to fastboot boot recovery without flashing it. Then flash SU/SuperSU. I've seen others do it this way, although I personally don't see much point to it.
But yes, bootloader still needs to be unlocked.

redpoint73 said:
That is not exactly what I said. If the phone is 4.4.3 or 4.4.2, OP should be able to fastboot boot recovery without flashing it. Then flash SU/SuperSU. I've seen others do it this way, although I personally don't see much point to it.
But yes, bootloader still needs to be unlocked.
Click to expand...
Click to collapse
yeah one can always flash the stock recovery after rooting.

redpoint73 said:
That is not exactly what I said. If the phone is 4.4.3 or 4.4.2, OP should be able to fastboot boot recovery without flashing it. Then flash SU/SuperSU. I've seen others do it this way, although I personally don't see much point to it.
But yes, bootloader still needs to be unlocked.
Click to expand...
Click to collapse
Booting it instead of flashing it is better if you want to make a backup of stock recovery. Especially if it's Philz that you're booting since TWRP doesn't seem to make backups of the stock recovery anyways.
Using the dd command to make a "copy" of the recovery works if you're rooted and to be rooted you have to have custom recovery which doesn't help much since you lose stock recovery the moment you flash the custom one, but if you boot it and root then at least you can use the dd command if that is the way you want to make a "backup" of your stock recovery. Silly little circle to run around in

BerndM14 said:
Booting it instead of flashing it is better if you want to make a backup of stock recovery. Especially if it's Philz that you're booting since TWRP doesn't seem to make backups of the stock recovery anyways.
Click to expand...
Click to collapse
Yes, I was aware of that; although it didn't seem to be the OP's goal. But thanks for pointing it out for their benefit.

thanks everyone for advice im sure i will get it right just one more quick question can you still upgrade with OTA when rooted or is it like other phones where you can not

Rantrave07 said:
Follow this guide for rooting.
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
but as redpoint73 said you have to unlock bootloader and install custom recovery.
Click to expand...
Click to collapse
thank you for the guide that makes it sound straight forward

pnr2020 said:
thank you for the guide that makes it sound straight forward
Click to expand...
Click to collapse
:good: glad it helped

The m8 was a little complicated at first than my previous phone the nexus 5 but I figured out the m8 and I love it a lot more than my n5

spinninbsod said:
The m8 was a little complicated at first than my previous phone the nexus 5 but I figured out the m8 and I love it a lot more than my n5[/QUOE
At first i wasn't sure i liked it but im getting used to it. When lollypop comes out do i need to restore to stock or can i just OTA and root again
Click to expand...
Click to collapse

pnr2020 said:
spinninbsod said:
The m8 was a little complicated at first than my previous phone the nexus 5 but I figured out the m8 and I love it a lot more than my n5[/QUOE
At first i wasn't sure i liked it but im getting used to it. When lollypop comes out do i need to restore to stock or can i just OTA and root again
Click to expand...
Click to collapse
To get updates you need a stock ROM unmodified, it can be rooted just do not mess with build.prop or platform.xml. However, to be able to install updates you need a stock recovery.
Click to expand...
Click to collapse

XSL-FO said:
pnr2020 said:
To get updates you need a stock ROM unmodified, it can be rooted just do not mess with build.prop or platform.xml. However, to be able to install updates you need a stock recovery.
Click to expand...
Click to collapse
thank you for info so if i stay on stock rom rooted i will have no trouble installing lollypop when released
Click to expand...
Click to collapse

pnr2020 said:
XSL-FO said:
thank you for info so if i stay on stock rom rooted i will have no trouble installing lollypop when released
Click to expand...
Click to collapse
As long as you have a stock recovery it's all good. But even if you have a custom one, before doing the update install a custom recovery. Make the update, and after that if you want flash again a custom recovery.
Click to expand...
Click to collapse

[TWRP][v3.1.1][xt907][KKBL][EXPERIMENTAL]TWRP for xt907 KKBL EXPERIMENTAL build

TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?

DiamondJohn said:
Please let me know if it works for you?
Click to expand...
Click to collapse
No-one has tried it?

Works like a charm for me

Worked like a charm here.

Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"

Works great so far, just about to try a lineage rom.
DiamondJohn said:
TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?
Click to expand...
Click to collapse
Will keep you posted.

For anyone wanting to try this just a pointer. This isn't a TWRP flashable zip so you will need to use your computer to extract the IMG file and sideload using fastboot. Working great so far.

Does this require an unlocked bootloader? I am rooted.
---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------
DiamondJohn said:
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"
Click to expand...
Click to collapse
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.

DragonFire1024 said:
Does this require an unlocked bootloader? I am rooted.
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.
Click to expand...
Click to collapse
you MUST have an unblocked bootloader to flash a custom recovery. ie this.

DiamondJohn said:
you MUST have an unblocked bootloader to flash a custom recovery. ie this.
Click to expand...
Click to collapse
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh

Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.

It appears it was just me
I re-flashed my bootloader upgrade CAREFULLY via fastboot, and the error on wiping cache disappeared. however, I still haven't been able to flash a bootable KKBL ROM. It was suggest via PM that I also wipe my internal SDCard, which I have yet to try.
Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
mr3p said:
Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.
Click to expand...
Click to collapse
I see the posts saying it works, but has anyone actually successfully flashed and booted (ie past the bootanimation ) any ROM Zip file using this recovery?
Or performed a backup and restore?
I ask this as I finally got around to creating an upgrade (from JBBL to KKBL) for my phone (an xt905 not an xt907) and the two ROMs I tried both boot looped on the bootanimation. Also, I get errors when i try to wipe my cache.
Is it just me?
-----edit-----
I got a PM saying that someone has managed to flash an LP ROM for KKBL using this recovery. So obviously I need to go back to the drawing board on my upgrade to KKBL...

I am considering adding PDS (ie FSD) backup to my TWRP builds see https://forum.xda-developers.com/showpost.php?p=74136332&postcount=9 it also applies to KKBL.

DragonFire1024 said:
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh
Click to expand...
Click to collapse
The boot loader has to be unlocked because of the nature of the boot loader itself. I ain't no expert, but based on my understanding and what I personally know, here is what a boot loader does:
A boot loader checks the various images (recovery, boot, radio, etc.) and if any of these are incorrect/unsigned (like a custom recovery), your device won't boot. This makes sense, because most users aren't flashing their devices, so when an image is unsigned something is VERY WRONG. Unlocking a boot loader basically turns off the signature check that the boot loader does. If the boot loader isn't checking each image than it will boot up fine whether you have a custom recovery or not.

Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.

DragonFire1024 said:
Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.
Click to expand...
Click to collapse
Easy is a relative scale to the person asking the question. Read and answer it for yourself. TWRP builds are muuuuuch simpler than ROM builds.
The following two may mean you do not have to build. I have never used them, as I built mine from source.
https://forum.xda-developers.com/android/general/unofficial-twrps-devices-source-code-t3833338
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
https://forum.xda-developers.com/showthread.php?t=1943625
The question may also be better asked, after reading, in the thread above

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

SafetyNet FAILED after stock rom and relocked bootloader? (Cant use Google Pay)

I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?

ntelas said:
I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?
Click to expand...
Click to collapse
Just an idea, take a look at your build.prop and see if anything looks off. Maybe you need to format some partitions before flashing the stock zip?
Cheers!

Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?

ntelas said:
Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?
Click to expand...
Click to collapse
I think that certain partitions need to be formatted you might want to search about that. I think TWRP can access the build.prop but not sure. I suggested checking build.prop because it will show different models, builds and basically would be an easy way to see if you are truly back to stock.
Good luck!

Thanks! I would have to install TWRP again maybe ?

ntelas said:
Thanks! I would have to install TWRP again maybe
Click to expand...
Click to collapse
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.

uweork said:
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.
Click to expand...
Click to collapse
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive

ntelas said:
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive
Click to expand...
Click to collapse
Then You didn´t read Properly.
I didn´t mean Root itself more Remnant parts of Root, that cause ur Saftynet fail.
on Samsung S2 once i thought so too, but banking app said no no no...
Only an Option

a user from this forum said that you need to take the line "ro.build.firgenprint=..." of the any MM/LP build.prop and insert it into the N build.prop (including reboot btw) and try again if google pay works for you...
I don't know if it works, I don't tried it, but you say us.