I'm having issues with my OPO root. I unlocked my bootloader, flashed TWRP and rooted by installing SuperSU through a zip. All was good and root was working yesterday.
I haven't done any Android updates, but my root is gone! If I open the SuperSU app it does this (see screenshot in attachments)
I tried reflashing the zip through TWRP but the same happens after rebooting.
Any ideas?
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Reinstall busybox.
https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Sent from N5 or OPO
oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Why on earth did you uninstall Busybox in the first place?
Sent from my Evita
Same problem here.
My OpO was rooted and after uninstalling busybox i have the same issue.
Superuser says no su binaries
i tried flashing again an again. Flash works fine but always the same message no su binaries ..
Busybox was stuck on loading data, that's why i uninstall it .
Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.
wacky.ddw said:
Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.
Click to expand...
Click to collapse
Don't restore system data when switching ROMs.
Sent via Bacon
timmaaa said:
Don't restore system data when switching ROMs.
Sent via Bacon
Click to expand...
Click to collapse
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.
You guys are totally out of a clue.
First: why do you uninstall busybox? Read twice, flash once. If you knew what busybox is for you probably would avoid such errors. Don't tweak your devices if you're not savvy of what you're doing or xda forum will always be cluttered by such threads.
Second: System options backed up can screw up your phone if they do not apply to the ROM just installed causing various problems if not bootloops. DO NOT RESTORE EM. NO WAY.
Hope this helps.
PS: Install busybox from play store to solve the issue.
wacky.ddw said:
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.
Click to expand...
Click to collapse
Read what you just wrote and tell me again that you don't want to restore system data.
Sent via Bacon
DuckMcQUack said:
PS: Install busybox from play store to solve the issue.
Click to expand...
Click to collapse
It don't works, install ok but Busybox crash when i open it
ahytes said:
It don't works, install ok but Busybox crash when i open it
Click to expand...
Click to collapse
Personally i would just clean flash again from the start...
Inviato dal mio One utilizzando Tapatalk
Hi, I have the same problem.
I tried to reflash SuperSU, but not working.
BusyBox was uninstalled from my pocket :crying:
What should I do ?
See post right above yours.
Transmitted via Bacon
Sorry.
But I only flashed the zip version of BusyBox, and it work now.
Brigitte-Bedo said:
Sorry.
But I only flashed the zip version of BusyBox, and it work now.
Click to expand...
Click to collapse
I have this same problem as OP. Ok well since the app keeps crashing on startup, flashing a zip seems like a good idea. Where did you find this zip file?
Same Problem
I lrooted my opo and flashed Sabermods Cm Lollipop and am also getting the same notification, any root needed apps are telling me the phone isnt rooted?? I also tried installing this busybox but wont work cause the phone is coming up as unrooted?
Has anyone a straight answer for this dilemma that doesnt include a full wipe/flash rom again...?
http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
---------- Post added at 10:06 PM ---------- Previous post was at 10:04 PM ----------
mindblizzard said:
http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
Click to expand...
Click to collapse
Had this problem to, try to uninstall supersu etc. Flash latest su and problem fixed, im on slimLP rom
Ok, I can't seem to get back root either. I had root and was running ParanoidAndroid. I wiped clean, flashed Cyanogen 12 nightly, flashed Gapps, wiped cache/dalvik. Everything rebooted into Lollipop fine, but I've lost root and can't seem to figure out how to re-root. I flashed the most recent SuperSU (2.46) via TWRP with no luck. Keeps saying I need to re-root first. Any ideas?
Related
Just updated my Nexus 5 using the OTA thread that went through fine,
I then proceeded to update SuperSU using the following link: http://download.chainfire.eu/supersu which was the update v1.99r3.
Using TWRP I flashed this and root is working for most apps i have tested: titanium, adblock, root explorer. So root is back.
However whenever I load up SuperSU I keep getting the following message: "The SU binary needs to be updated. Continue?"
So of course I have done this and let it use TWRP to flash. Let the phone boot up and upgrade the app as it needed. However on next load up of the app it asks to do the same yet again.
I feel as though I'm forgetting something as it's been a while since I've done this. ( use to live on flashing when i had my SII)
My Nexus is Stock ROM. CF-Auto Rooted. TWRP Recovery. Nothing else is modified.
Help would be appreciated, even though I don't go into supersu all that often anyways.
Cheers all.
What if you upgrade it using the "normal" method?
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
brichardson1991 said:
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
Click to expand...
Click to collapse
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
rootSU said:
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
Click to expand...
Click to collapse
How odd like I said my apps are all receiving their root permissions...
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
brichardson1991 said:
How odd like I said my apps are all receiving their root permissions...
Click to expand...
Click to collapse
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Have you tried other binary download?
brichardson1991 said:
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
Click to expand...
Click to collapse
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
brichardson1991 said:
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
Click to expand...
Click to collapse
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
rootSU said:
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Click to expand...
Click to collapse
It does seem that way Titanium has backed up an app just now, adblock has updated and Nova is hiding the time on the first screen.
rootSU said:
Have you tried other binary download?
Click to expand...
Click to collapse
No, I shall give a older one a try.. Tried 1.97 as well and to no luck.....
rootSU said:
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
Click to expand...
Click to collapse
This failed to do anything just got the install failed again.
rootSU said:
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
Click to expand...
Click to collapse
I assume this would override TWRP recovery?
brichardson1991 said:
I assume this would override TWRP recovery?
Click to expand...
Click to collapse
Yes it would. You can always flash back to twrp afterwards
rootSU said:
Yes it would. You can always flash back to twrp afterwards
Click to expand...
Click to collapse
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
brichardson1991 said:
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
Click to expand...
Click to collapse
Good news. The latest version of Philz, s it is CWM based - uses the latest Cyanogen sources to build. I update the CM sources everytime I build Philz so hopefully there should be fewer issues when new stuff comes out.
Hello guys!!!, Today I get the new OTA with the firmware 05Q and I install it. I see in the forum a version of 05Q rooted LINK HERE
I only want to ask if anyone know another way of get root actually or if I should wait until our amazing toolkits for 1+1 get updated.
Thanks i nadvance!!! :cyclops:
You can gain root following, This thread. If you already have a custom recovery install, might be easier to install the pre-rooted 05QA. I went the second route.
P.S. That toolkit will root 05QA, just does not have the new firmware to go back to stock.
I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!
Istvan_86 said:
I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!
Click to expand...
Click to collapse
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.
rraquib said:
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.
Click to expand...
Click to collapse
Really thanks again mate!! I do it, like you, as soon as possible.
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.
rraquib said:
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.
Click to expand...
Click to collapse
You said that flashing entire ROM would be easier, it isn't. All that's need to get root is to flash the SuperSU zip. He's already on 05Q so flashing the ROM zip is completely and utterly pointless. It's like telling someone who's run out of petrol to install a entirely new petrol tank that's full of petrol (when all that's actually needed is the fuel).
It doesn't matter what someone thinks might be the solution, if you're going to answer in the q&a section you need to give the best and easiest solution.
The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )
timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
+1
only SU from TWRP
plato79 said:
The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )
Click to expand...
Click to collapse
Install a newer version
#stayparanoid
Sorry guys for don´t answer your comments, I have been working out of my country for a couple of weeks.
I get root on 05Q with just flashing SuperSU 2.46 from recovery. Easy and fast, just that.
Anyway you have my thanks in your respective buttons.
EDIT: If moe people with doubts read this. I use the info on this post. http://forum.xda-developers.com/showthread.php?t=2788632
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Bebout said:
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Click to expand...
Click to collapse
You might have a system app removed or missing
Or maybe you have done something with the build prop as well if thats messed with that will also throw an error out.
If you read closely it should tell you what the error is
xxbabiboi228xx said:
You might have a system app removed or missing
Click to expand...
Click to collapse
I really hope not. How do I go about finding out if I'm missing a system app? I've already done a factory reset along with unrooting via SuperSU's app.
Bebout said:
I really hope not. How do I go about finding out if I'm missing a system app? I've already done a factory reset along with unrooting via SuperSU's app.
Click to expand...
Click to collapse
It should tell you the error after you try flashing the ota you may have to use the .kdz method
xxbabiboi228xx said:
It should tell you the error after you try flashing the ota you may have to use the .kdz method
Click to expand...
Click to collapse
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.
Bebout said:
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.[/QUOTE
Your telling me you removed root ? But you never had twrp as your recovery ?
Click to expand...
Click to collapse
xxbabiboi228xx said:
Bebout said:
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.
Click to expand...
Click to collapse
Your telling me you removed root ? But you never had twrp as your recovery ?
Click to expand...
Click to collapse
I fixed it. I rooted the device and flashed the v10i recovery image for TWRP that I found and I'm now going to update to v10j via the kdz, as you suggested. Thank you.
Bebout said:
I fixed it. I rooted the device and flashed the v10i recovery image for TWRP that I found and I'm now going to update to v10j via the kdz, as you suggested. Thank you.
Click to expand...
Click to collapse
No problem glad i could assist u in your problem
Why not get TWRP again and flash @GameTheory's v10j pre-rooted stock rom, it's not like you're going to see anything special with that update it's the last one before MM:
http://androidcreations.weebly.com/flashable-update-zip.html
Bebout said:
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Click to expand...
Click to collapse
well even if you Remove root via SuperSU that doesn't mean your SYSTEM is unmodified, the only way to get back to FULL Unmod. software is by following my steps of restoring back to stock, here is the link
http://forum.xda-developers.com/android/development/rom-lg-g-stylo-h631-ms631-v10j-stock-t3211563
P.S. You need to have TWRP for this so Re-Root and Re-Flash TWRP and follow steps
Hi,
Because I couldn't wait until the cos13 ota hit my area.
I downloaded the cos13 incremental update zip file (link from this thread) https://forums.oneplus.net/threads/cos-13-the-perfect-os-for-oneplus-one-i-love-it.441003/
I first confirmed that I was on the correct version for it to update (cos 12.1.1 YOG7DAS2K1)
Everything went well, it updated, but now the phone is stuck on the bootlogo really long, then starts optimising the apps reboots and does this again.
also the new bootlogo has this mod ready thing at the bottom now (not sure if that's normal)
I can still boot into the stock recovery and fastboot mode, but can't seem to acces the file system on my pc.
Any help on getting this thing working again would be great!
Thanks in advance
-Isaac
easiest way is to factory reset from recovery, if you can afford it.
First off it is stuck on boot animation, wipe data (factory reset) from recovery and you're good to go hopefully
Transmitted via BACON
ipsmaxes said:
Hi,
Because I couldn't wait until the cos13 ota hit my area.
I downloaded the cos13 incremental update zip file (link from this thread) https://forums.oneplus.net/threads/cos-13-the-perfect-os-for-oneplus-one-i-love-it.441003/
I first confirmed that I was on the correct version for it to update (cos 12.1.1 YOG7DAS2K1)
Everything went well, it updated, but now the phone is stuck on the bootlogo really long, then starts optimising the apps reboots and does this again.
also the new bootlogo has this mod ready thing at the bottom now (not sure if that's normal)
I can still boot into the stock recovery and fastboot mode, but can't seem to acces the file system on my pc.
Any help on getting this thing working again would be great!
Thanks in advance
-Isaac
Click to expand...
Click to collapse
For whatever reason...Cyanogen decided to make Google APP mandatory to run COS 13. If you remove the app or disable it you'll get a magnificiente bootloop. Maybe you removed Google App?
Hi it my case too. And I did disable some anoying Google apps.
mathsjob said:
Hi it my case too. And I did disable some anoying Google apps.
Click to expand...
Click to collapse
In my experience, it's Google App the only one causing problem, I removed Google Play Books, Play Videos, Play Music, Google+, etc. and not a problem
Any way to solve this issue ? Wipe data, partition and Media does nothing.
Is reflashing CM12 from ADB works ?
mathsjob said:
Any way to solve this issue ? Wipe data, partition and Media does nothing.
Is reflashing CM12 from ADB works ?
Click to expand...
Click to collapse
I fixed the problem dirty flashing again the ROM but if you already wiped data and flashed again the ROM, you may have another different problem causing the bootloop.
Maybe I can try to flash ROM again... But as I Wiped Data, I don't have the ROM available in my OPO and I don't know how to flash using another method
mathsjob said:
Maybe I can try to flash ROM again... But as I Wiped Data, I don't have the ROM available in my OPO and I don't know how to flash using another method
Click to expand...
Click to collapse
Did you wipe media storage??
Do you have TWRP installed?? There is an option to ABD sideload a ROM
brath23 said:
Did you wipe media storage??
Do you have TWRP installed?? There is an option to ABD sideload a ROM
Click to expand...
Click to collapse
Yes I wiped data, cache(first try) and media after that (was not a good idzea)... I don't have anything special installed, only stock software
mathsjob said:
Yes I wiped data, cache(first try) and media after that (was not a good idzea)... I don't have anything special installed, only stock software
Click to expand...
Click to collapse
If you don't have TWRP recovery, you could try to fastboot this ROM: http://builds.cyngn.com/factory/bacon/cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18.zip
There are plenty of guides to do this, even some scripts to make the process kind of automatic.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
More guides on XDA:
http://forum.xda-developers.com/showpost.php?p=63294096&postcount=4
And some script to make the process easier.
https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/
Make sure you choose your Oneplus ONE version correctly (16GB/64GB)
Thanks a lots for your quick answers, I will try using your ADB process.
Hey so yeah I already factory reset from recovery,
I didn't wipe my data yet because I still want to recover some files from the phone.
and yeah I did have almost every google app disabled (not removed).
after a factory reset these are normally activated again though? so idk what's up with that.
also does somebody know a way to retreive all files from the phone, through adb maybe? since I can't acces the file system on my pc rn
I'm gonna try to fastboot that rom you linked later (after I attempt to recover my files)
brath23 said:
For whatever reason...Cyanogen decided to make Google APP mandatory to run COS 13. If you remove the app or disable it you'll get a magnificiente bootloop. Maybe you removed Google App?
Click to expand...
Click to collapse
I did it yesterday
A disaster....
tommy92tc said:
I did it yesterday
A disaster....
Click to expand...
Click to collapse
Once you disable wake up, keep awake, Google Now, location history and a lot of permissions more for Google App, Cyanogen OS 13 runs pretty good
brath23 said:
Once you disable wake up, keep awake, Google Now, location history and a lot of permissions more for Google App, Cyanogen OS 13 runs pretty good
Click to expand...
Click to collapse
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
ipsmaxes said:
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
Click to expand...
Click to collapse
Same here, and no way to dirty flash the rom to get out of bootloop, I had to wipe everything
ipsmaxes said:
It's kinda 'mean' that they force you to have these on. Once I have my phone up and running again on cos13 and I disable the google app it's just instantly going to bootloop once I reboot?
if so, I imagine alot more people are gonna have trouble with this
Click to expand...
Click to collapse
Yes, it happened to me. Then I dirty flashed again the ROM, but I was having bootloop as well . I had to remove again Google APP from TWRP Explorer (I think it's called Velvet in /system/priv-app), reboot again in another bootloop and dirty flashed again the ROM. Lost a lot of time but I didn't want to lost /data and setup everything again.
Once you disable an APP is saved in some file in /data partition so simply dirty flashing ROM won't solve it.
---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------
tommy92tc said:
Same here, and no way to dirty flash the rom to get out of bootloop, I had to wipe everything
Click to expand...
Click to collapse
I was able to fix it without wipe.
Steps to fix bootloop after disabling Google APP
Enter TWRP and remove /system/priv-app/Velvet folder in File Manager
Reboot system. It will go into bootloop again but at least it will remove Google APP from the list of disabled apps
Enter TWRP again and dirty flash ROM again.
Reboot and it should be ok
brath23 said:
Yes, it happened to me. Then I dirty flashed again the ROM, but I was having bootloop as well . I had to remove again Google APP from TWRP Explorer (I think it's called Velvet in /system/priv-app), reboot again in another bootloop and dirty flashed again the ROM. Lost a lot of time but I didn't want to lost /data and setup everything again.
Once you disable an APP is saved in some file in /data partition so simply dirty flashing ROM won't solve it.
---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------
I was able to fix it without wipe.
Steps to fix bootloop after disabling Google APP
Enter TWRP and remove /system/priv-app/Velvet folder in File Manager
Reboot system. It will go into bootloop again but at least it will remove Google APP from the list of disabled apps
Enter TWRP again and dirty flash ROM again.
Reboot and it should be ok
Click to expand...
Click to collapse
Genius!!!!
Unfortunately it's too late, I already reinstalled all the apps and everything, now I have a clean system so I'll stay with that.
However it's a good way to restore, I'll remind it if anyone else will need it
Hello, I got Samsung J-7108 and I got stuck in bootloop after flashing Xposed Framework with flashfire... I am sure I downloaded the right version for my CPU, the latest one. I flashed the original firmware, but it doesn't work. I don't have a custom recovery, what can I do? Help, please.
Speeder12321 said:
Hello, I got Samsung J-7108 and I got stuck in bootloop after flashing Xposed Framework with flashfire... I am sure I downloaded the right version for my CPU, the latest one. I flashed the original firmware, but it doesn't work. I don't have a custom recovery, what can I do? Help, please.
Click to expand...
Click to collapse
Did you ever figure out how to fix this issue? Was very curious about this Flashfire.
Paul R
try to flash boot.bin for your phone ,, extract it from stock room and convert ti from bin to tar and flash it
Thank you for your replies. I had to do a factory reset, nothing else helped. So I tried it again, I flashed the Xposed V86 with flashfire, worked fine for two days, than the phone went to bootloop again. I guess I will not deal with xposed anymore, it is a good thing, but doesn't really work as it should.
Okay, so I have a update: Phone works fine for two days. I turn it on and everything seems fine, but... after two days of using it goes to bootloop again no matter what I do. I tried flashing original firmware, works fine for two days, than bootloop again, tried factory resetting, wiping cache and so on, still the same, works, but goes to bootloop every two days when I try to turn it on. Help, please.
Any ideas?
Try to flash the xposed uninstaller zip
messi2050 said:
Try to flash the xposed uninstaller zip
Click to expand...
Click to collapse
I did many times, never helped
Speeder12321 said:
I did many times, never helped
Click to expand...
Click to collapse
I think that u will need to flash twrp then wipe the system/data partitions and reflash stock rom ( note that this may break your phone )
I found out, that stock firmware works fine, but whenever I give it a root access, it stucks in bootloop after 2 days of using the phone... is there anything else I can try before wiping data partitions?
Speeder12321 said:
I found out, that stock firmware works fine, but whenever I give it a root access, it stucks in bootloop after 2 days of using the phone... is there anything else I can try before wiping data partitions?
Click to expand...
Click to collapse
which root method u are using
messi2050 said:
which root method u are using
Click to expand...
Click to collapse
I am using a pre-rooted firmware.
I guess that XPosed changed the values of some System files and uninstaller does no job in changing them back to how they were before. Question is: There's no custom recovery availible for Chinese model of J7, so is there a possibility to delete System using a Root file explorer? Which has access to System partition?
messi2050 said:
which root method u are using
Click to expand...
Click to collapse
When I do factory reset in recovery on rooted firmware, it works again, but like I said, just for two days? How is that even possible? Factory reset should delete everything including changes that xposed made, shouldn't it?
Speeder12321 said:
When I do factory reset in recovery on rooted firmware, it works again, but like I said, just for two days? How is that even possible? Factory reset should delete everything including changes that xposed made, shouldn't it?
Click to expand...
Click to collapse
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
ashyx said:
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
Click to expand...
Click to collapse
I don't think so, I used prerooted firmware for months and never had a single problem... everything started to go wrong after flashing xposed.. So how can be SuperSU a problem if it used to work fine before?
EDIT: And no, I didn't receive security policy update.
EDIT2: But thanks a lot for your advice, I will try to update SuperSU... Is it okay if I flash newer superSU with flashfire, when my current one is installed as a system app or do I need to do something before flashing the new one?
Speeder12321 said:
I don't think so, I used prerooted firmware for months and never had a single problem... everything started to go wrong after flashing xposed.. So how can be SuperSU a problem if it used to work fine before?
EDIT: And no, I didn't receive security policy update.
EDIT2: But thanks a lot for your advice, I will try to update SuperSU... Is it okay if I flash newer superSU with flashfire, when my current one is installed as a system app or do I need to do something before flashing the new one?
Click to expand...
Click to collapse
Use the uninstaller in SuperSU settings.
ashyx said:
Use the uninstaller in SuperSU settings.
Click to expand...
Click to collapse
It is installed as a system app, so I will need to do a full unroot. And if I do full unroot, I won't be able to flash the new one with flashfire, because it needs root access, what now ?
EDIT: Okay, I managed to update SuperSU to version 2.78 SR1, I will post an update if it fixed my issue, thanks
ashyx said:
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
Click to expand...
Click to collapse
Thank you sooooooo so much, it fixed my issue