Database Users

[Q] Lost Root after OTA update. How to properly re-root without messing the system?

Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help

First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ

I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade

I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?

Easily got my root back using Wugfresh toolkit.

Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.

[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.

gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.

[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something

gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.

If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app

i337m gets auto-unrooted everytime I do system update of nightly version

As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?

khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.

Entropy512 said:
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.
Click to expand...
Click to collapse
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?

khunkami said:
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?
Click to expand...
Click to collapse
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
If you install a TWRP image using heimdall or odin it should persist - the dd method listed in http://teamw.in/project/twrp2/124 should work too. (i337 is the AT&T/Rogers Note2, right?)
Omni shouldn't be flashing recovery on this device (Omni only changes recovery on devices that can't change kernel without changing recovery - like the I9100/I777/N7000 and many Sonys), but even if it is, it should be flashing a TWRP build...

Entropy512 said:
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
Click to expand...
Click to collapse
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,

Gertlily said:
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,
Click to expand...
Click to collapse
I am just curious. Why does Omni Rom unroot the device after system-update?

khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It is not only the issue on OmniROM but on (almost) every ROM, I've had the same on cyanogen and Samsung Stock.. So flashing it yourself is better.. Hope this bug will get fixed somewhere in the future.
Bye,
Sent from my Nexus 7 using Tapatalk

khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It's because Omni doesn't have root yet. It's on the to do list. The easiest way is to install SuperSU to system, then install the back up script. That way you'll keep root through updates.

khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.

AKdballs said:
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.
Click to expand...
Click to collapse
You shouldn't be using CF-Auto-Root if you have a custom recovery (which you need in order to install Omni). Just flash SuperSU in recovery.

I knew something wasn't quite right but I did it that way because it works. I have downloaded su onto the SD card, as well as the latest nightly build of Omni. Can I install the new nightly with TWRP, and add su as a second zip to install at the same time? Or should I flash them separately?
Sent from my SGH-I337M using xda app-developers app

Issue updating to Android 5.0

I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4

Your build.prop isn't standard, get the original one, or just use the factory image to update.

Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..

Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.

inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?

CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app

inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?

CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app

I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.

After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk

Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?

[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.

Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.

[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).

I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?

[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.

charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!

mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.

charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...

Never mind

Unable to update after root

Hi
I am running on LMY47V, Version 5.1.1.
About 2 days ago i got an update of 20 MB which got downloaded into my device but failing to apply.
Whenever i Click the Restart and Install button the device gets restarted and goes into ClockworkMod Recovery v6.0.4.7 asking to fix the root access which is possibly lost . I tried both the options Yes and No then the device gets started with no update.
Then the same notification comes in asking me to Restart and Apply.
I have rooted and applied CM Recovery recently and this never happened to me before rooting.

It is normal that OTA updates do not work when rooted. There are a few workarounds, but they are not super easy (you can normally install the updates manually using adb-tools if I remember correctly).
adithyagem said:
About 2 days ago i got an update of 20 MB which got downloaded into my device but failing to apply.
I have rooted and applied CM Recovery recently and this never happened to me before rooting.
Click to expand...
Click to collapse

Yeah, to use the OTA updates you need to be completely stock. Stock ROM, locked bootloader, no root and stock recovery.

theminikiller said:
Yeah, to use the OTA updates you need to be completely stock. Stock ROM, locked bootloader, no root and stock recovery.
Click to expand...
Click to collapse
Bootloader does not have to be locked, but you are correct about everything else.

ariesgodofwar said:
Bootloader does not have to be locked, but you are correct about everything else.
Click to expand...
Click to collapse
Oh, that's good to know.

I went through this over the weekend (flashing back to stock in order to get the OTA update).
I cannot say enough good things about this Nexus Root Toolkit by WugFresh: http://www.wugfresh.com/nrt/
Made it super simple for me to flash back to stock, get that OTA update, and then flash TWRP right back (so that I could enable 4G/LTE again).

Arson Smith said:
I went through this over the weekend (flashing back to stock in order to get the OTA update).
I cannot say enough good things about this Nexus Root Toolkit by WugFresh: http://www.wugfresh.com/nrt/
Made it super simple for me to flash back to stock, get that OTA update, and then flash TWRP right back (so that I could enable 4G/LTE again).
Click to expand...
Click to collapse
I strongly recommend you learn how to use fastboot. You would not have had to flash back to stock to update. You could have flashed the system and boot images and been done with it. NRT is a good tool but you have much more flexibility if you understand what you're doing with fastboot.
Sent from my Nexus 9 using XDA Free mobile app

[(GUIDE)] Lg V410 kitkat return to stock w/o pc.

So here's my little guide on returning your v410 to stock unrooted from kitkat.
First of all download the stock rooted rom by @timmytim
http://forum.xda-developers.com/g-p...-v410-onlykot49i-v4101d-4-4-2-rooted-t3040208
Next download the stock recovery img.
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
Have flashify installed
Busy box app by stericson installed, I have pro.
Boot into twrp
Flash stock rom. Do not wipe anything!!
Reboot
Wait for apps to optimize.
Upon reboot flash the stock recovery via flashify. Once succeeded just press the home button to exit out!!
Open busy box wait for it to load and choose uninstall, normal uninstall not smart.
Reboot
Upon reboot open up su. Do not update binary!!
Scroll through settings and tick Full Unroot, select yes and wait.
Once uninstalled it will exit out on it's own
Reboot
Download root checker and check, you should be unrooted and able to factory reset or whatever you choose.
You removed busy box so there should be no traces of root.

Has anyone tried this? I'm desperate to get back on stock OTA/unrooted, this tablet has just been too laggy for my liking on any custom ROM. I'm currently on CM nightlies, on LL.....

So this works fine, I said "screw it" last night and flashed it. I decided to keep root though......so I just went from CM Nightlies on LL....back to KK. Oh man I missed KK. :silly: :good:
Only thing is, I went into bootloop after flashing the ROM, so I booted into TWRP and did a full wipe (minus external SD), did a factory reset.....and flashed it again. Booted up fine, and with an hour I was getting a prompt for an OTA being available.

ok, i followed your guide here and several others on the interweb. I am stumped. I am trying to install the update, but when I do i get that updates are not for rooted devices.
I did do a full unroot via supersu and flashed the stock recovery. When I put it in download mode, it says that it is still rooted. What did I do wrong?
little background, this all started when i was stock rooted and running xposed and twrp, and accidentally allowed my kid to install an update with out looking and got stuck in a twrp bootloop. flashed test build and then I am here. Any help would be appreciated.

any updates?
joeclark said:
ok, i followed your guide here and several others on the interweb. I am stumped. I am trying to install the update, but when I do i get that updates are not for rooted devices.
I did do a full unroot via supersu and flashed the stock recovery. When I put it in download mode, it says that it is still rooted. What did I do wrong?.
Click to expand...
Click to collapse
Hey did the same and i'm now in the same predicament. i know its been a while but did u manage to figure it out by any chance?

Nope still sitting on my desk as a mouse pad
sent from a device using an app

LXative said:
So this works fine, I said "screw it" last night and flashed it. I decided to keep root though......so I just went from CM Nightlies on LL....back to KK. Oh man I missed KK. :silly: :good:
Only thing is, I went into bootloop after flashing the ROM, so I booted into TWRP and did a full wipe (minus external SD), did a factory reset.....and flashed it again. Booted up fine, and with an hour I was getting a prompt for an OTA being available.
Click to expand...
Click to collapse
did you have a Sim card in it?
---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------
joeclark said:
ok, i followed your guide here and several others on the interweb. I am stumped. I am trying to install the update, but when I do i get that updates are not for rooted devices.
I did do a full unroot via supersu and flashed the stock recovery. When I put it in download mode, it says that it is still rooted. What did I do wrong?
little background, this all started when i was stock rooted and running xposed and twrp, and accidentally allowed my kid to install an update with out looking and got stuck in a twrp bootloop. flashed test build and then I am here. Any help would be appreciated.
Click to expand...
Click to collapse
ok so there is a zip for stock non testbuild. But how did the device pop up with a update wouldn't it not update if you had a custom recovery