Database Info

Rooted Nexus 5 out of box, recently updated 4.4.2 OTA and now root is gone

When I open up superSU, it says:
There is no SU binary installed, and super SU cannot install it.
If you just upgraded to android 4.3, you need to manually re-root.
If I turn the Nexus on in recovery mode, it still says it's unlocked.
So at this point, is there anything I can do to restore root status without factory resetting? I made a backup with titanium backup but it was a while ago so I would rather not use it if there is another way.
I've read somewhere that rooting it should mean OTA updates should no longer work but somehow, it still went through and I updated it without thinking too much.

Download the supersu zip file and flash it in recovery.
http://download.chainfire.eu/371/SuperSU/UPDATE-SuperSU-v1.85.zip

This will throw me back into rooted mode while keeping my phone as is?

BruceHsiang said:
This will throw me back into rooted mode while keeping my phone as is?
Click to expand...
Click to collapse
this will update the binaries and restore root. no data will be lost or formatted. simply flash the zip in twrp or cwm.

xBeerdroiDx said:
this will update the binaries and restore root. no data will be lost or formatted. simply flash the zip in twrp or cwm.
Click to expand...
Click to collapse
I don't have twrp or cwm installed yet. Which one is generally simpler/easier to install/use?

So I installed goomanager and tried to install twrp, but it all goes back to the same problem which was that I am now not in root mode anymore.
Also what do you mean by flashing the zip? Which options am I supposed to use?

BruceHsiang said:
I don't have twrp or cwm installed yet. Which one is generally simpler/easier to install/use?
Click to expand...
Click to collapse
I've been using TWRP with no problem and it's been awhile since I've used CWM. I've never used a toolkit or flashify but with adb it would probably take a couple minutes max to flash either one.
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
BruceHsiang said:
So I installed goomanager and tried to install twrp, but it all goes back to the same problem which was that I am now not in root mode anymore.
Also what do you mean by flashing the zip? Which options am I supposed to use?
Click to expand...
Click to collapse
Choose "Install" in recovery, with either TWRP or CWM is flashing the zip.

wantabe said:
I've been using TWRP with no problem and it's been awhile since I've used CWM. I've never used a toolkit or flashify but with adb it would probably take a couple minutes max to flash either one.
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
Choose "Install" in recovery, with either TWRP or CWM is flashing the zip.
Click to expand...
Click to collapse
Problem is, I didn't install twrp when I had root access before, and now when I try to use it, it says I need root to use it.
Can I flash the zip using adb in the fastboot recovery menu?
What should I do from here?

BruceHsiang said:
Problem is, I didn't install twrp when I had root access before, and now when I try to use it, it says I need root to use it.
Can I flash the zip using adb in the fastboot recovery menu?
What should I do from here?
Click to expand...
Click to collapse
Sorry I've never done that. I guess you could adb push superuser.apk to the system but you still need the binary wherever that goes. Honestly I would just flash TWRP using adb and use TWRP to flash the SuperSu zip.
---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
Do you have adb already working?

Not yet, I just saw it as an option while reading around.
How would I install twrp with that image file?
All tutorials I've found said I needed root to install it in the first place.

BruceHsiang said:
Not yet, I just saw it as an option while reading around.
How would I install twrp with that image file?
All tutorials I've found said I needed root to install it in the first place.
Click to expand...
Click to collapse
No.You do not need root to install a custom recovery. You need an unlocked bootloader. How did you get root in the first place? You must have used a toolkit of some kind? Use it again? I've only every used adb so I can't help with any toolkits but lots of people use them, I guess!

Download the latest TWRP or CWM recovery. Put it in the same folder as your adb and fastboot files. Open a command prompt and type adb reboot bootloader(you have to make sure developer settings are enabled and USB debugging is checked). Then flash recovery using fastboot by typing fastboot flash recovery name_of_file.img and then you can flash the supersu zip file.
Sent from my Nexus 5 using Tapatalk

Exactly! I'm thinking he doesn't have adb setup yet.
---------- Post added at 11:36 PM ---------- Previous post was at 11:28 PM ----------
This is a pretty decent video on how to setup adb, not the newest video out there probably but it should work!

I used chainfires autocf root file from here
http://forum.xda-developers.com/showthread.php?t=2507211
and followed a youtube tutorial.
When I try adb devices it shows my serial number followed by sideload.
I've tried sideloading both twrp and the superSU.zip, and they fail to verify and the installation aborts =\

[Q] 4.3 Update + TWRP

So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....

Carousser said:
So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....
Click to expand...
Click to collapse
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery

ThePagel said:
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery
Click to expand...
Click to collapse
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?

Carousser said:
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?
Click to expand...
Click to collapse
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might

ThePagel said:
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might
Click to expand...
Click to collapse
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root

Carousser said:
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root
Click to expand...
Click to collapse
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.

ThePagel said:
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.
Click to expand...
Click to collapse
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.

Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Carousser said:
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.
Click to expand...
Click to collapse
Oh your stuck on twrp can't boot up to usable state?

ThePagel said:
Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Oh your stuck on twrp can't boot up to usable state?
Click to expand...
Click to collapse
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it

Carousser said:
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it
Click to expand...
Click to collapse
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.

ThePagel said:
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.
Click to expand...
Click to collapse
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Edit-----
I found the zip file while browsing TWRP. Can I just install it?

Carousser said:
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Click to expand...
Click to collapse
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of the 3 options I gave you are your only options.

ThePagel said:
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of thoughs 3 options are your only options.
Click to expand...
Click to collapse
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible

Carousser said:
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible
Click to expand...
Click to collapse
Sure you can try tell me if it works

ThePagel said:
Sure you can try tell me if it works
Click to expand...
Click to collapse
Is there a chance of me bricking my phone?

Carousser said:
Is there a chance of me bricking my phone?
Click to expand...
Click to collapse
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.

ThePagel said:
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.
Click to expand...
Click to collapse
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?

Carousser said:
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?
Click to expand...
Click to collapse
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
If you have backups of stuff on your internal sd it would be much faster to just Odin to 4.3 right now.

ThePagel said:
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
Click to expand...
Click to collapse
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x

Carousser said:
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x
Click to expand...
Click to collapse
Factory reset deals with the rom. So no it will stay twrp.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
Using Odin is a lot like SBF'ing on the droid x (that was my last phone also). So if you can remember installing cyanogen mod 6 or 7 you probably always did a factory reset before first boot. Custom recovery stays intact the only way to get rid of it was to flash stock recovery with terminal emulator or sbf back to pure stock. Luckily Odin let's us flash the recover by its self so we have more options with Samsung.

[Q] OTA version XNPH38R Incremental does not install

I'm prompted to install the XNPH38R Incremental with the message "System update is ready"
I tap on Install update, the phone then does it's thing, reboots and shows the splash screen logo a few seconds, then the recovery comes up and the text scrolls at lightning speed (a second or so) then the phone powers up in full and is ready for use.
When I go to my homescreen the prompt is there again for me to upgrade with the "System update is ready" message.
As such the update doesn't apply successfully. No error messages at all.
Phone is stock ROM (version 11.0-XNPH33R), only thing I did extra was to unlock the bootloader using OnePlus One Toolbox v2 (64 GB). This was done in order for me to root it. Oh, I also installed PhilZ Recovery using this same toolbox.
Any ideas why this happens?
...or suggestions as to how I can do the update?
PS, I saw that there's another tread (http://forum.xda-developers.com/oneplus-one/help/apply-ota-stock-root-franco-23r-twrp-t2900311) with a OTA update failure but that one is different as there's errors involved so I felt that the suggestions were not applicable in my case.

try manually going thru the recovery and run update file from /cache directory. and see what errors is trowing
look for cm-bacon-3628510d76-to-ac1ccf7921-signed.zip

NiTRoN69 said:
try manually going thru the recovery and run update file from /cache directory. and see what errors is trowing
look for cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
Click to expand...
Click to collapse
I found the update file and tried to install in manually. The attached image shows the error message which has no meaning to me. I then cleared the cache and also the dalvik cache, booted up, checked for update, downloaded the update and install.
Same problem happened so back to square one

JJD809 said:
I found the update file and tried to install in manually. The attached image shows the error message which has no meaning to me. I then cleared the cache and also the dalvik cache, booted up, checked for update, downloaded the update and install.
Same problem happened so back to square one
Click to expand...
Click to collapse
That error message is saying that you have a modified lockscreen.
Transmitted via Bacon

timmaaa said:
That error message is saying that you have a modified lockscreen.
Transmitted via Bacon
Click to expand...
Click to collapse
Ah! that makes sense. I got the lockscreen after reading an article about it on the XDA news pages (http://www.xda-developers.com/android/dynamic-oneplus-one-lock-screen/) which took me to this thread http://forum.xda-developers.com/oneplus-one/development/dynamic-oneplus-one-lockscreen-t2890808
From here forward, how do you suggest I proceed. Is there a way to "uninstall" this lock screen or is it a matter of me doing a factory reset and starting afresh?

Unless there's a return to stock zip in the thread where you got your modified lockscreen, you'll need to start fresh.
Transmitted via Bacon

Trying to apply on a stock Oneplus One, just with root and TWRP.
Code:
asset failed: apply_patch_check("/system/app/Music2.apk","....","....")
E: Error executing updated binary in zip '/cache/cm-bacon...signed.zip
Any ideas?

timmaaa said:
Unless there's a return to stock zip in the thread where you got your modified lockscreen, you'll need to start fresh.
Transmitted via Bacon
Click to expand...
Click to collapse
hi, I have the almost the same problem, I did a factory reset but it gives me error again, what should I do

fackamato said:
Trying to apply on a stock Oneplus One, just with root and TWRP.
Code:
asset failed: apply_patch_check("/system/app/Music2.apk","....","....")
E: Error executing updated binary in zip '/cache/cm-bacon...signed.zip
Any ideas?
Click to expand...
Click to collapse
System modification on Music2.apk. Read the above advice by timmaaa.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
shcxatter2 said:
hi, I have the almost the same problem, I did a factory reset but it gives me error again, what should I do
Click to expand...
Click to collapse
Boot on TWRP recovery and flash XNPH38R OTA zip. See here: 4. Latest OTA incremental update zip

Primokorn said:
System modification on Music2.apk. Read the above advice by timmaaa.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
Boot on TWRP recovery and flash XNPH38R OTA zip. See here: 4. Latest OTA incremental update zip
Click to expand...
Click to collapse
that's exactly what my problem is I cannot install the update , twrp just gives me error

Use the modified XNPH38R update. You can find it in the xnph38r thread in general.
You did system modifications. By using the modified script, it won't check for those files.
This is why I say when you want to do system changes, just use a custom ROM because OTAs are going to be a headache for you if u dont intend on using what the OTA provided to you.

zephiK said:
Use the modified XNPH38R update. You can find it in the xnph38r thread in general.
You did system modifications. By using the modified script, it won't check for those files.
This is why I say when you want to do system changes, just use a custom ROM because OTAs are going to be a headache for you if u dont intend on using what the OTA provided to you.
Click to expand...
Click to collapse
I'm trying to figure out what "system modifications" I've done. It's probably freezing apps in titanium backup, as google's music always FC's on all devices, so had to be ignored.

fackamato said:
I'm trying to figure out what "system modifications" I've done. It's probably freezing apps in titanium backup, as google's music always FC's on all devices, so had to be ignored.
Click to expand...
Click to collapse
Freezing apps in TB does nothing for those system modifications. Just flash the modified script XNPH38R update and you'll be able to update. I've said this 2 times now.

zephiK said:
Freezing apps in TB does nothing for those system modifications. Just flash the modified script XNPH38R update and you'll be able to update. I've said this 2 times now.
Click to expand...
Click to collapse
Thanks. I think it only has the full one not the incremental one?

[ROM] SU4TL-44 100% Stock

SU4TL-44 Stock Image for XT1254: https://mega.nz/#!v4QWiITb!_0jWWzE4KWCEgT__C36rYe0vaTzGKcEFsZm0vvBtLBg
Flash with TWRP.
This package will flash every image in the SU4TL-44 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, revert to stock by following section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Thanks to @firstEncounter for letting me incorporate his flashable zip into this package.

Will have to download this later. Looked to go back to stock and wait for mm to come out.
Sent from my XT1254 using Tapatalk

Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?

schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
No it won't relock boot loader just installed it you will not be rooted and twrp will ask you if you want to root before reboot if you click no and want to at a later point just go back into boot loader by doing vol down power combo from power off and select open boot loader and when you click to reboot it will ask you again if you want to root then you can just slide to install

schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
Correct

Can I install viper and su along with this?

MazinDLX said:
Can I install viper and su along with this?
Click to expand...
Click to collapse
Sure. Just flash the rom first and the mods second.

TheSt33v said:
Sure. Just flash the rom first and the mods second.
Click to expand...
Click to collapse
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol

MazinDLX said:
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
Click to expand...
Click to collapse
I've never tried to install an image via ADB before. Did you mount the image elsewhere and extract the system folder, and then ADB-pushed that? If not, your bootloop is probably because there's just a big, unextracted system.img on your system partition, and not the actual files within it. Why not just flash it with TWRP? When I tested it, I flashed it via TWRP and it worked.
If you really don't want to flash it via TWRP for some reason, you can extract the system.img from the zip and flash it using fastboot (fastboot flash system system.img).
EDIT: Oh wait, I think I understand now. You just used ADB to put the zip on your phone, and then you installed it with TWRP. Got it. Well my next question is why use ADB at all? Why not just plug in your phone while it's booted into TWRP and use the native MTP to transfer files?

Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.

The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.

MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
This package only flashes /system. CM flashes its own boot.img, which is why this isn't working for you. I'll try to find some time tonight to add in the other images in the stock firmware to this package. Sorry about that.

firstEncounter said:
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
Click to expand...
Click to collapse
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?

TheSt33v said:
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
Click to expand...
Click to collapse
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.

MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.

firstEncounter said:
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
Click to expand...
Click to collapse
I'm not entirely sure how to write a script to flash those in TWRP. For boot and system, it's easy because the devices that they are flashed to match the names used by fastboot. Bootloader and radio seem to be a little different though. When I list the contents of /dev/block/bootdevice/by-name, there is no "motoboot" or "radio," which is what fastboot uses when you flash these. I do see "aboot" and "modem," and I'm pretty sure those are the targets I'm looking for, but I don't want to go flashing things unless I'm 100% sure. Since there's not a huge demand for figuring that out, and boot + system is all people will need in 99% of cases, I'll leave them out. Thanks though!

Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?

MazinDLX said:
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
Click to expand...
Click to collapse
No, but I appreciate the thought. Donate to this guy instead. He does way more than me and also needs it way more than me: http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945

TheSt33v said:
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
Click to expand...
Click to collapse
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.

bigv5150 said:
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
Click to expand...
Click to collapse
Awesome! That's why we do this

Factory Reset while rooted?

Can someone correct me if I'm wrong here, but if I have TWRP installed, and I do a factory reset, whether from within booted system or via TWRP, all I should need to do is simply reinstall magisk manager to get root back, correct?

You would have to re-root your phone.

Did you get answer to this question?

Just installing magisk manager apk will be enough.
---------- Post added at 10:16 PM ---------- Previous post was at 10:14 PM ----------
equlizer said:
You would have to re-root your phone.
Click to expand...
Click to collapse
I have not tried this but masgisk patches the boot and factory reset does not changes anything on boot and system partition so I don't think rooting required

Just install the Magisk
Just install the Magisk again