Related
I have a stingray, Moto Xoom running Team eos 4 (build 197). I was trying to update the binary in SuperSU and when it failed I no longer had root access. SuperSU 1.51 is installed, the superuser binary is installed, busybox binary and Busybox applets are installed. Root access is "not available".
I have TWRP installed and have back ups of a previous build (190)
Any ideas how I can recover from this?
dweezle said:
I have a stingray, Moto Xoom running Team eos 4 (build 197). I was trying to update the binary in SuperSU and when it failed I no longer had root access. SuperSU 1.51 is installed, the superuser binary is installed, busybox binary and Busybox applets are installed. Root access is "not available".
I have TWRP installed and have back ups of a previous build (190)
Any ideas how I can recover from this?
Click to expand...
Click to collapse
Usually when this happens to me (Wingray) I would reflash the ROM and check if root access is back. If it's not (Usually is), I would restore to previous build, wipe /system along with cache and davlik-cache and flash the ROM again. If root's still unavailable, I would attempt a clean flash (Wipe Data/Factory Reset, wipe Cache, wipe Davlik-cache, wipe System, flash ROM&GAPPS) and check again. Finally, if it's still not available, I would unroot, lock bootloader, return to stock, unlock bootloader, and root again.
Or you can disregard everything I said above, restore your backup, and stay on it
dweezle said:
I have a stingray, Moto Xoom running Team eos 4 (build 197). I was trying to update the binary in SuperSU and when it failed I no longer had root access. SuperSU 1.51 is installed, the superuser binary is installed, busybox binary and Busybox applets are installed. Root access is "not available".
I have TWRP installed and have back ups of a previous build (190)
Any ideas how I can recover from this?
Click to expand...
Click to collapse
Thanks, re-flashing the same build fixed it.; However, if I open superSU, it still wants to update the binary, if I use either of the 2 methods it has to update, it loses the root access again.
Did you attempt to update the binary using one of the two methods after reflashing the same build? In my experience, the update is usually successful after reflashing. Try updating the binary and report if root access remains or is lost.
XxAlmightyxX said:
Did you attempt to update the binary using one of the two methods after reflashing the same build? In my experience, the update is usually successful after reflashing. Try updating the binary and report if root access remains or is lost.
Click to expand...
Click to collapse
Immediately after re-flashing the same build (197), wiping Dalvik and cache, I checked for root using one of the root checker apps. Root was successful and root access was restored. I then opened SuperSu and got the notice saying binary needed updating. If I used, what they called the "normal" method the installation failed. If I use the CWM/TWRP method, the xoom reboots into TWRP and then does something that has text flash by, too fast too read, and reboots into the system. At that point root access is gone.
Try a clean flash and see if root access is kept or lost.
XxAlmightyxX said:
Try a clean flash and see if root access is kept or lost.
Click to expand...
Click to collapse
I got root access back by reflashing the last Team Eos 4 stingray ROM, 197. But, I am still unable to update the binaries in SuperSU. There seem to be a lot of folks that run into this issue with SuperSU.:crying:
Hi,
I rooted my OPO a few days ago and installed the unofficial CM12 Lollipop based build using TWRP and everything worked just fine.
Now a few hours ago I downloaded OnePlus' official Lollipop ROM and flashed the recovery after wiping data, cache and dalvik cache. Having done so and booted the phone I went back to recovery to flash Gapps only to realize TWRP wasn't available anymore. The screen showed android's recovery interface with touch disabled. I attempted to install Gapps after copying that to the phone's memory but failed to do so.
When I scroll down using the volume rocker and attempt to "apply update from sdcard" I get an error message saying:
"E:error opening /data/media/0: Permission denied
-- No package file selected. "
Now without Gapps I do not have access to Google Play Services, sync, backup of contacts or even the Play Store.
I tried rooting the phone again, flashing TWRP etc. But no matter how many times I try the phone just won't show TWRP in recovery
So now I'm stuck with a phone without any Gapps and no Play Store from which to download even the most basic apps. APKs can't be installed either because there's no app to open them.
Can anyone help me please?
What Official Lolipop ROM ? Maybe ask in the appropriate ROM thread ?
Cholerabob said:
What Official Lolipop ROM ? Maybe ask in the appropriate ROM thread ?
Click to expand...
Click to collapse
The one OP posted on their site:
https://forums.oneplus.net/threads/rom-official-5-0-android-lollipop-alpha.223252/
To the OP, reflash TWRP and then flash the GApps again
Are you able to access the phone through ADB or FASTBOOT?
nboorla said:
Hi,
I rooted my OPO a few days ago and installed the unofficial CM12 Lollipop based build using TWRP and everything worked just fine.
Now a few hours ago I downloaded OnePlus' official Lollipop ROM and flashed the recovery after wiping data, cache and dalvik cache. Having done so and booted the phone I went back to recovery to flash Gapps only to realize TWRP wasn't available anymore. The screen showed android's recovery interface with touch disabled. I attempted to install Gapps after copying that to the phone's memory but failed to do so.
When I scroll down using the volume rocker and attempt to "apply update from sdcard" I get an error message saying:
"E:error opening /data/media/0: Permission denied
-- No package file selected. "
Now without Gapps I do not have access to Google Play Services, sync, backup of contacts or even the Play Store.
I tried rooting the phone again, flashing TWRP etc. But no matter how many times I try the phone just won't show TWRP in recovery
So now I'm stuck with a phone without any Gapps and no Play Store from which to download even the most basic apps. APKs can't be installed either because there's no app to open them.
Can anyone help me please?
Click to expand...
Click to collapse
You'll have to install TWRP again using fastboot.
I did the same as you. I used one of the toolkits it can be done quite easily just take your time. You can actually Google Play store apk in the browser and install it.
I'd just open developer options enable debugging and plug the phone in your PC and allow drivers to install.
Then download one of the toolkits and install TWRP your bootloader should still be unlocked.
Once I found the toolkit the other night and installed it I was up and running in minutes.
Solved
Thank you all for the swift replies. I tried flashing TWRP multiple times but couldn't get it done. Then I chanced upon this link in another thread.
account[.]onepluscontent[.]com/downloads/tools/oneplus-one-reflash[.]zip
It's a zip file from OnePlus which when extracted will give you drivers (I didn't need them) and a ReadMe file that explains how to get the OPO back to just the way it was when you unboxed it. It's incredibly simple and hardly takes any time. After that I was able to easily flash TWRP and root the phone.
nboorla said:
Thank you all for the swift replies. I tried flashing TWRP multiple times but couldn't get it done. Then I chanced upon this link in another thread.
account[.]onepluscontent[.]com/downloads/tools/oneplus-one-reflash[.]zip
It's a zip file from OnePlus which when extracted will give you drivers (I didn't need them) and a ReadMe file that explains how to get the OPO back to just the way it was when you unboxed it. It's incredibly simple and hardly takes any time. After that I was able to easily flash TWRP and root the phone.
Click to expand...
Click to collapse
The same tool can be found on XDA:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
nboorla said:
Thank you all for the swift replies. I tried flashing TWRP multiple times but couldn't get it done. Then I chanced upon this link in another thread.
account[.]onepluscontent[.]com/downloads/tools/oneplus-one-reflash[.]zip
It's a zip file from OnePlus which when extracted will give you drivers (I didn't need them) and a ReadMe file that explains how to get the OPO back to just the way it was when you unboxed it. It's incredibly simple and hardly takes any time. After that I was able to easily flash TWRP and root the phone.
Click to expand...
Click to collapse
Well done.
I know you will note the ROM you flashed is an Alpha ROM. So though 'official', is still very new, as the OP advised.
Fresh ROMs can be a lot of fun to bug hunt, and a lot of time to work through, until the components are ripe, when they have heightened depth, balance, finesse, intensity and end, where the ROM has become pure, vibrant, opulent and mature; a ROM that is seamless.
The dream.
nboorla said:
Hi,
I rooted my OPO a few days ago and installed the unofficial CM12 Lollipop based build using TWRP and everything worked just fine.
Now a few hours ago I downloaded OnePlus' official Lollipop ROM and flashed the recovery after wiping data, cache and dalvik cache. Having done so and booted the phone I went back to recovery to flash Gapps only to realize TWRP wasn't available anymore. The screen showed android's recovery interface with touch disabled. I attempted to install Gapps after copying that to the phone's memory but failed to do so.
When I scroll down using the volume rocker and attempt to "apply update from sdcard" I get an error message saying:
"E:error opening /data/media/0: Permission denied
-- No package file selected. "
Now without Gapps I do not have access to Google Play Services, sync, backup of contacts or even the Play Store.
I tried rooting the phone again, flashing TWRP etc. But no matter how many times I try the phone just won't show TWRP in recovery
So now I'm stuck with a phone without any Gapps and no Play Store from which to download even the most basic apps. APKs can't be installed either because there's no app to open them.
Can anyone help me please?
Click to expand...
Click to collapse
Did you unmount system before installing?
Save time and flash to stock CM11S
For anybody that is stuck in this situation as I was too. Just load the stock CM11S and perform this through fastboot.
Example >fastboot update cm-11.0-XNPH44S-bacon-signed-fastboot.zip
Hi Guys,
Yesterday I updated to CM13 Nightly without wiping and doing it right, because I do have a very customized UI and didn't want to lose, since the backups doesn't keep everything inthe right place (at least for me!)
ANYWAY I installed CM13 and booted the system, everything was OK, but the phone appeared not be rooted, well I needed to reflash the SU binary, so I did, but in superexcited manner, got an old version (1,51 ) and apparently it has messed everything up… Now the phone is still not rooted, all the Apps close frequently, Superuser Access Management doesn't work, I can't even remove it (only deactivate), I tried to flash the UPDATE-SuperSU-v2.46.zip too, it made my phone hang in CM Logo·…I can literally boot the TWRP Recovery and Wipe everything and make a tidy install but I DON'T WANT! I'D RATHER TO REPAIR !
What are your certain solutions? please reply If you KNOW how to FIX such cases… No randomly try this try that, Thank you all!
Summary:
Oneplus One: CM12.1 dirty update → CM13/ Superuser/root access has been overwritten/damaged
First attempt made me install an older su binary v1.51 (don't know why!) and it is stuck into my system, doesn't let to uninstall or update (from apps manager/Play Store)
Reflashed the current version (su 2.45) and can't boot up (CM logo)
Can reboot recovery / Don't want to Wipe
Did you flash v6.0 gapps immediately after flashing the ROM?
You're not supposed to flash SuperSU with MM, it comes fully prerooted.
SimonTS said:
Did you flash v6.0 gapps immediately after flashing the ROM?
You're not supposed to flash SuperSU with MM, it comes fully prerooted.
Click to expand...
Click to collapse
yes I did, but Superuser (#) needed to update and it couldn't neither normal nor in recovery, so i downloaded the latest binary and flashed it manually… but they seem not matching probably
Simple answer - clean flash and start again, with no SU and the correct gapps.
SimonTS said:
Simple answer - clean flash and start again, with no SU and the correct gapps.
Click to expand...
Click to collapse
It will be the last option.
As mentioned above, i will try to keep my data
Magisk 17 (Stable) was just released. I am uninstalled 16 via the official uninstall. I then rebooted to TWRP and flashed 17. The phone kept going back to recovery. I uninstalled and reinstalled 16 and I'm back up. Anyone else get 17 to work on the latest OOS?
same here, can not get it to work
I downloaded it, then flashed it in twrp, but i never uninstalled the older version, I just flashed over the older one. Mine booted up fine,
I'm on OOS 5.1.11
Updated from 16.7 beta to 17.0 via Magisk Manager (direct installation).
Everything worked fine, except the warning pop-up on boot that was also on 16.7.
I was on Magisk 16.4. After installed v17, root was broken. I had to uninstall it and redo V16.4.
I wound up having to wipe data. Now 17 seems to be OK. Time will tell.
Even after running the uninstaller and reinstalling 16, after about 5 minutes running fine, the system would just randomly reboot.
Be prepared if you install 17, you may have to wipe data
Mike02z said:
I wound up having to wipe data. Now 17 seems to be OK. Time will tell.
Even after running the uninstaller and reinstalling 16, after about 5 minutes running fine, the system would just randomly reboot.
Be prepared if you install 17, you may have to wipe data
Click to expand...
Click to collapse
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Rebel7022 said:
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Click to expand...
Click to collapse
I tried flashing right over 16.0. It just kept dumping me back into TWRP.
Rebel7022 said:
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Click to expand...
Click to collapse
I did that. That is always the way I update it as well. It just booting back into TWRP.
1N1ghth4wk said:
Everything worked fine, except the warning pop-up on boot that was also on 16.7.
Click to expand...
Click to collapse
In Magisk Manager select Uninstall -> Restore images -> Flag the option "Preserve AVB 2.0/dm-verity" -> install -> direct install -> reboot.
Warning pop-up should not appear anymore
Mike02z said:
I tried flashing right over 16.0. It just kept dumping me back into TWRP.
Click to expand...
Click to collapse
Flash a kernel, I like ex kernel , It probably will fix it
I just let the Magisk app update itself and direct install the update and reboot. I always do that, works fine.
Sent from my ONEPLUS A6003 using Tapatalk
brossovitch said:
I just let the Magisk app update itself and direct install the update and reboot. I always do that, works fine.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Same for me, and everything works fine with the latest version.
I am on H2 os ob 02, Magisk 16.7.
I got message to update Magisk aplication. I did, then, message to update to Magisk 17.
Everything works fine.
I just let it update the Magisk Manager and now i'm without root (no idea how i ended like this i swear i just updated the Manager) and the Manager doesn't have the ability to install Magisk directly, just download zip only or patch boot image. Guess i'm up to reinstall TWRP and flash the Magisk zip manually, right?
Flashed Directly over 16.7 (H2os beta 2) without wipe or issues :good:
Happened to me too I got stuck in bootloop to twrp didnt need to wipe data. I used flash all partitions fastboot.bat from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 to get back to normal without losing data. I had to reinstall twrp and magisk though. Now I'm on magisk 17.0 all fine.
So I do it just let it update the Magisk Manager. CustomRom AospExtended ROM V5.8
And running
Also got stuck in a bootloop after installing 17 over 16. Using the uninstaller fixed the issue, and when I re-tried installing 17 in TWRP it worked fine.
Installed 16.4 yesterday and it would not pass Safety Check, got the notification to install 17 which I did via the app
Installed without a hitch and Safety Check all passed with no issues
Woke up this am to an OOS update and remembered that there's a process to go through to not lose root and magisk, so I look up the thread and follow the simple directions.
Allow the OTA but do not reboot.
Go into Magisk and install again to internal
Stay in Magisk and install to inactive slot
Reboot
I did exactly that and upon reboot, my phone booted to my lockscreen pic and just flashes every second. Even in safe mode it bootloops at a flashing lockscreen.
I followed exactly what I was supposed to do, so is there a step missing? Or was I not supposed to take the OOS update that was being pushed today?
I can access TWRP still, and I do have a full backup available if I need it, but I'd much rather figure out how to move forward.
Thanks for any help you can give me!
OnePlus 7 Pro
stock ROM
TWRP & rooted
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
FlipmodeBG said:
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
Click to expand...
Click to collapse
What exactly did you do to uninstall magisk from TWRP? I don't know how to do this...
Did you go into TWRP file manager and just delete /data/adb/magisk folder?
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
FlipmodeBG said:
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
Click to expand...
Click to collapse
Thanks for that, didn't work for me though. I keep bootlooping at insecure bootloader warning.
I have messed something up pretty bad, after the last reboot, I'm met with the Qualcomm CrashDump mode -- dmverity device corrupted force dump
kernel_restart
Now I'm stuck, because I've tried to recover my backup, it goes through the process at just over 1000 seconds, has no errors or failures but still won't boot.
I need some help here.
Nevermind, I have to have this phone back up and running ASAP, so I used MSM Tool and started over. I figured spending a few hours setting it back up from scratch was the best way forward at this point.
I'm unclear on what caused this problem... maybe I had a magisk module that didn't disable, or maybe I forgot to disable a substratum layer or something, but I really borked myself all because of an OTA update.
Any further advice on what I might have done or what might have corrected it will still be appreciated because I'm sure there will be another OTA someday and I'd really like to avoid this happening again.
Thanks!
What I do when there is a new Ota is
download the update from the updater app
remove any passwords or finger prints
reboot to twrp
install the Ota
do no reboot
install twrp installer
do no reboot
install magisk
wipe dalvick
reboot
check if Magisk is installed and if not reboot back into twrp and install Magisk again
Hi. Magisk 20.4 not working my device. Has anyone managed to get it working?