Related
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?
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
Ran into problems with my phone the other day and had to do a wipe, upon reboot, it says I am not rooted (with root checker). Upon checking I am still Unlocked/S-off, but am unable to gain root. SuperSU says there is no SU binary, and when I try to push SU.img all I get is "error: device '(null)' not found". But, if I do a device check it shows that it is connected.
I have tried everything I can think of, starting from the very beginning and trying to reroot all over again, but it won't let me push the SU.img file. Any help would be greatly appreciated.
ShiftyBob said:
Ran into problems with my phone the other day and had to do a wipe, upon reboot, it says I am not rooted (with root checker). Upon checking I am still Unlocked/S-off, but am unable to gain root. SuperSU says there is no SU binary, and when I try to push SU.img all I get is "error: device '(null)' not found". But, if I do a device check it shows that it is connected.
I have tried everything I can think of, starting from the very beginning and trying to reroot all over again, but it won't let me push the SU.img file. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using TWRP to install SuperSU flash able?
The_scam said:
Have you tried using TWRP to install SuperSU flash able?
Click to expand...
Click to collapse
Every link I have found is dead. Do you have one you could send me, or point me to an active link?
ShiftyBob said:
Every link I have found is dead. Do you have one you could send me, or point me to an active link?
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/
The_scam said:
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
Flashed it using TRWP, still no luck. Other than adding/deleting apps, I literally haven't changed anything since I rooted it a year ago (I'm still running 6.0).
I'm out of ideas...
ShiftyBob said:
Flashed it using TRWP, still no luck. Other than adding/deleting apps, I literally haven't changed anything since I rooted it a year ago (I'm still running 6.0).
I'm out of ideas...
Click to expand...
Click to collapse
Just wipe all your data and run an Ruu
The_scam said:
Just wipe all your data and run an Ruu
Click to expand...
Click to collapse
I'll give it a shot. Also worth noting is that when I rooted a year ago, I immediately made a Nandroid backup (as I always do). When restoring from the backup, it puts my phone back in the same state it was at the time I made the backup... except for having root.
ShiftyBob said:
I'll give it a shot. Also worth noting is that when I rooted a year ago, I immediately made a Nandroid backup (as I always do). When restoring from the backup, it puts my phone back in the same state it was at the time I made the backup... except for having root.
Click to expand...
Click to collapse
The root functionality lives (AFAIK) with the kernel in the boot partition. Restoring your backup would only affect your system and data partitions. Somehow when you did the original wipe it must've given you the stock kernel/boot partition. I agree that starting over with an RUU and going from there is probably your best option. You can probably restore a data backup when you're done though.
Hi,
I have a VZW Quark that's been unlocked with Sunshine and rooted and running fine on custom ROM's for a year. Today I did a factory reset and complete wipe and reinstalled RR Rom and GApps etc. However, on reboot, it only goes back to recovery (TWRP 3.1.1-0). I faced this the last time as well and managed to find the fix by googling it but can't seem to get to it now. It was a quick fix and then it booted to system fine and I cannot remember it. Can anyone help! Thanks.
Rikhit said:
Hi,
I have a VZW Quark that's been unlocked with Sunshine and rooted and running fine on custom ROM's for a year. Today I did a factory reset and complete wipe and reinstalled RR Rom and GApps etc. However, on reboot, it only goes back to recovery (TWRP 3.1.1-0). I faced this the last time as well and managed to find the fix by googling it but can't seem to get to it now. It was a quick fix and then it booted to system fine and I cannot remember it. Can anyone help! Thanks.
Click to expand...
Click to collapse
Someone else had this issue and they solved it by flashing the latest @bhb27 modded TWRP. You say you have TWRP 3.1.1, but is it from the TWRP website or from @bhb27? Flash this one below to make sure.
twrp-3.1.1-mod_2-quark.img
https://androidfilehost.com/?w=files&flid=39562
Once they flashed it, they were able to boot to system, then they booted back to TWRP (on purpose) -- and then upon subsequent reboots everything was fine.
See here:
mpro420 said:
@bhb27 Im face a problem, since I do a clean install build 08/23, when my phone restart, it always boot into TWRP, and I need to boot to bootloader and press START to start system normally.
Maybe Im doing something worng due the install process, (full wipe include internal storage, flash Crdroid, flash Gapps, reboot), I try to flash boot.img and new TWRP 3.1.1 recovery.img, but got a same results.
Please help, thanks a lot.
我從使用 Tapatalk 的 DROID Turbo 發送
Click to expand...
Click to collapse
bhb27 said:
You may not be using the TWRP made by me, check TWRP thread and use the twrp-3.1.1-mod_2-quark.img version that is in the afh mirror folder if you are not using that... also try to update the ROM as 8/23 is one month old on updates...
Click to expand...
Click to collapse
mpro420 said:
Thank you!!
After flash the TWRP 3.1.1-mod 2, my phone booting is back to normal. :good
ps: I want to donate to your hard work, but I dont had a Paypal account, its there other way I can buy you a beer?
我從使用 Tapatalk 的 DROID Turbo 發送
Click to expand...
Click to collapse
bhb27 said:
Mod TWRP can cleanup the "android to recovery commands" the process was changed in nougat and official or old version don't have the new support...
From outside of Brazil that is the only option that I can received and use what I have received...
:good:
Click to expand...
Click to collapse
Hello everyone,
So today, I decided to flash the Adaptive Brightness Mod.
So what I did, I booted into newest TWRP, I flashed Adaptive Brightness Mod. Hitted reboot.
It didn't boot, so what I did is I flashed DP3 again. The system booted, so I thought "Yea **** that mod".
So I booted into TWRP again and tried to root again using magisk. I got again in a boot loop.
Does anyone have a solution? I really want to have root access.
Friendly regards,
Crewz
ItsCrewz said:
Hello everyone,
So today, I decided to flash the Adaptive Brightness Mod.
So what I did, I booted into newest TWRP, I flashed Adaptive Brightness Mod. Hitted reboot.
It didn't boot, so what I did is I flashed DP3 again. The system booted, so I thought "Yea **** that mod".
So I booted into TWRP again and tried to root again using magisk. I got again in a boot loop.
Does anyone have a solution? I really want to have root access.
Friendly regards,
Crewz
Click to expand...
Click to collapse
Try flashing Magisk 16.7
flashing magisk in twrp gave me nothing but trouble so now i install twrp and then fastboot from a patched boot to get magisk installed.
manasgirdhar said:
Try flashing Magisk 16.7
Click to expand...
Click to collapse
Yea I tried that, didnt work
RiTCHiE007 said:
flashing magisk in twrp gave me nothing but trouble so now i install twrp and then fastboot from a patched boot to get magisk installed.
Click to expand...
Click to collapse
No idea what a Patched Boot is xD
ItsCrewz said:
Yea I tried that, didnt work
Click to expand...
Click to collapse
Did you trying wiping system, and then flash ROM, TWRP, reboot, and then try Magisk?
ItsCrewz said:
No idea what a Patched Boot is xD
Click to expand...
Click to collapse
patched boot with magisk
manasgirdhar said:
Did you trying wiping system, and then flash ROM, TWRP, reboot, and then try Magisk?
Click to expand...
Click to collapse
I didn't because its an pain to reinstall all apps and place them in the correct folder :/
ItsCrewz said:
I didn't because its an pain to reinstall all apps and place them in the correct folder :/
Click to expand...
Click to collapse
Yeah, I can understand. I normally have a titanium backup. Maybe someone else will have a better helpful idea
manasgirdhar said:
Yeah, I can understand. I normally have a titanium backup. Maybe someone else will have a better helpful idea
Click to expand...
Click to collapse
Yea I have an titanium backup of apps. But u still need to replace them in correct order.
I hope someone has an other idea.
ItsCrewz said:
Yea I have an titanium backup of apps. But u still need to replace them in correct order.
I hope someone has an other idea.
Click to expand...
Click to collapse
Order shouldn't really matter in a batch restore
manasgirdhar said:
Order shouldn't really matter in a batch restore
Click to expand...
Click to collapse
I mean. Like, I need to remake how my homescreen was made
ItsCrewz said:
I mean. Like, I need to remake how my homescreen was made
Click to expand...
Click to collapse
Wouldn't that be already backed up in the launcher data?
You shouldn't be that mad because of your homescreen set-up getting wiped! Yesterday I ****ed up encryption after trying to go back to Oxygen OS 5.1.11 from Havoc OS (which has August Security Patch), I couldn't boot the device up and TWRP and all my files were encrypted. After hours of trying and flashing, I had no other choice than formatting all my data. Including internal storage. And because I'm dumb, I didn't do a back up of my data for 3 month, so now I have 3 month old data on my phone.
So don't care about your homescreen set-up, as long as you have your pictures/music/data on the phone.
Btw, I'm not sure if I have a solution for you, but can you explain what exactly is the issue now? So you can boot up in the system without magisk installed but with it, you can't?
ItsCrewz said:
Yea I tried that, didnt work
Click to expand...
Click to collapse
You can't flash Magisk 16.7 from TWRP. It causes issues more times then not. You need to flash TWRP 16.4 (1642) then let the Magisk manager update to 16.7.
Magisk 16.7 will often give you an error on boot which looks like a vendor mismatch message. I stick with 16.4.
the reason it fails only with root is because the mod he installed is still installed. It only turns on when you have root. remove mod and problem fixed. also, reflashing rom does not remove magisk mods. only uninstalling mod will fix this or a full format.
the mod lives in /data.
memocatcher said:
You shouldn't be that mad because of your homescreen set-up getting wiped! Yesterday I ****ed up encryption after trying to go back to Oxygen OS 5.1.11 from Havoc OS (which has August Security Patch), I couldn't boot the device up and TWRP and all my files were encrypted. After hours of trying and flashing, I had no other choice than formatting all my data. Including internal storage. And because I'm dumb, I didn't do a back up of my data for 3 month, so now I have 3 month old data on my phone.
So don't care about your homescreen set-up, as long as you have your pictures/music/data on the phone.
Btw, I'm not sure if I have a solution for you, but can you explain what exactly is the issue now? So you can boot up in the system without magisk installed but with it, you can't?
Click to expand...
Click to collapse
Hi can you tell me the steps you did to revert back to stock oos rom please. I am struggling with this same exact problem since 2 days and i don't know what else i could try so if you could tell me how you solved this issue ! Thanks
vinct94 said:
Hi can you tell me the steps you did to revert back to stock oos rom please. I am struggling with this same exact problem since 2 days and i don't know what else i could try so if you could tell me how you solved this issue ! Thanks
Click to expand...
Click to collapse
Do you have a USB drive with USB C connector?
It is a lifesaver
Why cant you flash 16.7 again. That's the only one I flash in my TWRP and I never have issues.