Related
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
My XT1540/rooted/stock 6.0 ROM/ stock recovery now has an update available. I assume I can not accept this system update, even if I un-root my device. I do have a pre-rooted TWRP back up. I can reload that image, but my concern is the best way to get all my apps and data reloaded. I do have TB backups, but I thought that may not be a good option after system update. I am looking for advise how to proceed getting the latest system update and preserving all my current apps and data.
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.
MrTooPhone said:
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.
Click to expand...
Click to collapse
I dislike TiBU... It is best to reinstall from scratch each time if possible, if not, this is a simple security update to TWRP should suffice.
Magisk is good, and it appears to be the root method most ROMs are going to because with Magisk Hide and a few tweaks that are built in, the device can still pass SafetyNet API checks, and there is no special process for systemless installing (it is the only way it can be done with Magisk). But if you are on SuperSU now and want to restore the data partition, do NOT switch that way... Get clean ROM and flash Magisk then install Magisk Manager. It has it's own community here: https://forum.xda-developers.com/apps/magisk
I am not saying Magisk is superior, but it is quite versatile and most ROMs seem to be switching to it so devices can pass SafetyNet checks.
I was also thinking this would be simple. Pleasant surprise after almost a year and a half to get a security update. So I uninstalled SuperSU (Tried Full Unroot option & it failed, so then just uninstalled the app.....Looks like I may still be rooted), re-installed the stock recovery, and with absolutely no other modifications to this phone, performed the update. So it failed. I thought I was able to do this on my Nexus 4, but that was a while back, and I always did it with a file, not OTA; maybe that was just OS update, who knows. I was just looking for some security peace of mind while waiting for Nougat to become a bit more stable. If I am going to have to go through hoops to do this, then I guess I will just wait; not going to go through this twice. Besides, will it be another year for the next security update; heck, they are already 1 or 2 months behind already.
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Oh well. On a side note, always grateful for making Nandroid backups before I start playing around with anything though. Things were acting up after haphazardly trying various SuperSU options, so I had to do a restore.
These constant OTA update messages every few minutes that I have to keep canceling are brutal! I might have to install an app to kill them.
Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Are you saying OTA updates can be flashed successfully without unrooting.
MrTooPhone said:
Are you saying OTA updates can be flashed successfully without unrooting.
Click to expand...
Click to collapse
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?
Rohi09 said:
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?
Click to expand...
Click to collapse
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.
MrTooPhone said:
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.
Click to expand...
Click to collapse
you can flash unsu zip or magisk Uninstaller and try to install ota via flashfire, won't hurt trying, might save you some time.
acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?
MrTooPhone said:
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?
Click to expand...
Click to collapse
Another simple Google question...
Open TWRP, go to Wipes - Advanced, and select Cache and Dalvik cache (a misnomer today, it should be called ART cache) and swipe to wipe, then reboot.
Thanks to @acejavelin recommendations, I have successfully applied the latest system update to my XT1540. My steps were as follows:
Booted to TWRP (3.0.2-r5.img)
restored original pre-rooted ROM
rebooted, accepted system updates
backed up new pre-rooted ROM
installed SuperSU 2.62-3, rebooted
updated SuperSU to 2.79 via Playstore
restored /data partition from last saved rooted ROM
wiped Dalvik/ART Cache
Reboot system
took a while, a couple of minutes on “Hand stitched by Peter Crawly”, several minutes optimizing apps. The phone booted succesfully then I got an error message the update failed (which I hit OK) But looking at about phone, latest security patch is listed. Phone looks configured (apps, data, configuration) exactly as it was prior to the update.
Rebooted phone, all still seems fine.
Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file
bradmoss said:
Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file
Click to expand...
Click to collapse
Your are not going to see an img file. Once booted into TWRP, select Restore, navigate and select your original ROM. Those files you have listed are within the restoration directory that you select with TWRP. Just select the directory with TWRP.
Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!
no idea? Am I the sad owner of a bricked phone?
bradmoss said:
no idea? Am I the sad owner of a bricked phone?
Click to expand...
Click to collapse
You could try a factory reset if you're not worried about losing your data. A factory reset solves most of the problems, though I'm a little doubtful because a factory reset won't uninstall the new update (given that it installed in the first place).
bradmoss said:
Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!
Click to expand...
Click to collapse
If it boots to TWRP, sounds like you didn't have a clean pre-root ROM as you did not have stock recovery. Did you try deleting Dalvik and ART cache?
Hi I just got this hh yesterday and it's already android 8.1 oreo. How to flash costum recovery TWRP?
Flash this one first, but only the recovery, not the boot part. https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
After that, boot into TWRP, and select to use an image, flash this one choosing 'recovery' image https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Note that in order to install some things, supersu or magisk most importantly, but anything that goes on the /data partition, you must explicitly format the data partition, then flash what you want, then reboot. This will factory reset the phone with the exception of what you just flashed. Once you've rebooted, there aren't any TWRPs that can decrypt the data partition so you won't be able to flash anything else or back up /data. It will get you rooted and if you have magisk then you can get xposed from within the magisk manager app.
Good luck.
PantsDownJedi said:
Flash this one first, but only the recovery, not the boot part. https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
After that, boot into TWRP, and select to use an image, flash this one choosing 'recovery' image https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Note that in order to install some things, supersu or magisk most importantly, but anything that goes on the /data partition, you must explicitly format the data partition, then flash what you want, then reboot. This will factory reset the phone with the exception of what you just flashed. Once you've rebooted, there aren't any TWRPs that can decrypt the data partition so you won't be able to flash anything else or back up /data. It will get you rooted and if you have magisk then you can get xposed from within the magisk manager app.
Good luck.
Click to expand...
Click to collapse
So, it is just 1 time TWRP and it will factory reset my phone?
eBuzz_Recon said:
So, it is just 1 time TWRP and it will factory reset my phone?
Click to expand...
Click to collapse
Yes, pretty much.
You have to format the data partition from TWRP in order to have it in a state where TWRP can read or write to it as it isn't yet encrypted. Doing that is a factory reset. After you boot again, the ROM will encrypt the data partition, so unless someone builds a TWRP that can read the encrypted partition in this Oreo build, it will be like that.
Until there's a new build of TWRP, you need to do that format of data to install something from TWRP. You can try installing magisk and let it fail, it might patch the kernel, before failing, and then let you install the magisk manager separately but probably not. Perhaps if you go to that thread and explain, someone can clarify and there might be something you can remove from the magisk install script if it fails when data can't be mounted, so that the kernel will still be patched to accept root. As for xposed, you can install it from magisk manager and most other stuff can be done from the phone while its running.
PantsDownJedi said:
Yes, pretty much.
You have to format the data partition from TWRP in order to have it in a state where TWRP can read or write to it as it isn't yet encrypted. Doing that is a factory reset. After you boot again, the ROM will encrypt the data partition, so unless someone builds a TWRP that can read the encrypted partition in this Oreo build, it will be like that.
Until there's a new build of TWRP, you need to do that format of data to install something from TWRP. You can try installing magisk and let it fail, it might patch the kernel, before failing, and then let you install the magisk manager separately but probably not. Perhaps if you go to that thread and explain, someone can clarify and there might be something you can remove from the magisk install script if it fails when data can't be mounted, so that the kernel will still be patched to accept root. As for xposed, you can install it from magisk manager and most other stuff can be done from the phone while its running.
Click to expand...
Click to collapse
I don't understand the part of kernel patching. Why would I need to patch the kernel? Is there any chance for fail when I try flashing magisk?
Sorry for my noobinity.
eBuzz_Recon said:
I don't understand the part of kernel patching. Why would I need to patch the kernel? Is there any chance for fail when I try flashing magisk?
Sorry for my noobinity.
Click to expand...
Click to collapse
The magisk and supersu scripts do that automatically. As for why, I don't remember, but there's information on it here most likely
https://forum.xda-developers.com/an.../test-disable-defex-security-samsung-t3851487
It has to do with the implementation of security features that Samsung includes. Remember that rooting is in itself an exploit. Those features see something with elevated permissions and are programmed to believe that it isn't meant to be there.
As for failure, you can always reflash the whole ROM with Odin if it doesn't go well, and if that doesn't work, then yes you have a real problem at that point. The link I just put above is perhaps a place to ask which could have better information.
My OnePlus 7 Pro is rooted at 9.5.8 trying to update to 9.5.9
When i try to install OTA it removes TWRP as it would but i can't boot into the system again without booting into TWRP and switching back to slot A. And when i boot to the system settings say that update failed.
I've tried different update methods like
Install update (dont reboot) - Magisk install inactive slot
Download update zip with oxygen updater app - boot into recovery twrp - flash update zip
I rooted my phone a few days ago and for some reason it won't update and i'm stuck on 9.5.8
Slot b is also not readable. SDCARD shows 0mb
What I do is:
Download and install the update
Don't reboot
Then back out and go to magisk downloads
Search for twrp retention and install
Don't reboot
Then back out to magisk main screen and select the first install option
Then select install and then the 4th option ota install slot
Now reboot
Yayodroid said:
What I do is:
Download and install the update
Don't reboot
Then back out and go to magisk downloads
Search for twrp retention and install
Don't reboot
Then back out to magisk main screen and select the first install option
Then select install and then the 4th option ota install slot
Now reboot
Click to expand...
Click to collapse
Tried this too.
When I install oxygen update zip through TWRP and I reboot it goes over to slot b where I can't boot to the system and when I go back to slot a and boot to system update failed
First i disable all magisk modules then I download the full 2gb update, go into twrp, flash the update, flash twrp.zip then flash magisk.zip. Reboot and then re-enable the modules.
if you have Magisk module OOSNativeCallRecorder, you need to remove that module. If still issues then remove all modules.
Guide how to remove magisk modules via TWRP
equlizer said:
First i disable all magisk modules then I download the full 2gb update, go into twrp, flash the update, flash twrp.zip then flash magisk.zip. Reboot and then re-enable the modules.
Click to expand...
Click to collapse
This doesnt work. After flashing it reboots to slot b and update failed
Bradl79 said:
if you have Magisk module OOSNativeCallRecorder, you need to remove that module. If still issues then remove all modules.
Guide how to remove magisk modules via TWRP
Click to expand...
Click to collapse
Okay, this is weird
I chose to remove magisk, twrp and go back to stock with locked oem. Installed the new update perfectly fine. Then I regretted it. So I rooted my device again and set it up only to look under device info where it says that I now have 9.5.8. So basically my phone downgraded itself after rerooting and unlocking bootloader.
I'm now stuck in 9.5.8
PikachuLover said:
Okay, this is weird
I chose to remove magisk, twrp and go back to stock with locked oem. Installed the new update perfectly fine. Then I regretted it. So I rooted my device again and set it up only to look under device info where it says that I now have 9.5.8. So basically my phone downgraded itself after rerooting and unlocking bootloader.
I'm now stuck in 9.5.8
Click to expand...
Click to collapse
Probably switched back to old slot.
Bradl79 said:
Probably switched back to old slot.
Click to expand...
Click to collapse
So I should just try and flash the update, twrp and magisk in this order on the slot I am using now?
Having same problem. No work around?
The best way to update? Personally, I recommend taking full manual control of the update process. Use TWRP to update your ROM (that includes stock OOS) when you want to, and when you need to fix stuff.
- Flash ROM
If you are on slot A and flash a ROM, it goes to slot B.
- Flash TWRP installer zip
Keeps TWRP on both slots, patches boot.img
- Reboot to TWRP, not system
- Flash ROM again
This installs the ROM to the other slot, so now both slots are updated
- Flash TWRP installer zip again
Keeps TWRP on both slots, patches boot.img
- Flash Magisk
Patches the TWRP-patched ROM, allowing it to boot.
- Wipe dalvik
You can wipe data and dalvik instead for a clean flash
- Now reboot to system
Consider flashing BOTH slots (A and B) whenever you update OOS, for two reasons.
First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base.
The second reason is more compelling: the way the data partition changes encryption every update has nearly obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!
reaper000 said:
.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!
Click to expand...
Click to collapse
I was actually going to do this permanently for better performance, I did test it out for a while and definitely noticed things faster, boot is quicker, battery lasted longer also.
I just hate all the work required to keep decrypt between updates.
I wish Google allowed us to choose whether we want encryption or not.
This maybe a silly question and the form trolls may come out. However ??, decrypting, will we have to do it to both slots? A and B? Or will twrp take care of decrypting both slots. Coming from a one plus 5 we didn't have to deal with this whole slot a and b. Boy what a headache.
virtyx said:
I was actually going to do this permanently for better performance, I did test it out for a while and definitely noticed things faster, boot is quicker, battery lasted longer also.
I just hate all the work required to keep decrypt between updates.
I wish Google allowed us to choose whether we want encryption or not.
Click to expand...
Click to collapse
I'm thing about decrypting, if you don't mind, can you let me know what you mean by all that work?
On the 5t, after decrypting, I just had to make sure to flash no verity script in twrp and that was all.
harpin14789 said:
I'm thing about decrypting, if you don't mind, can you let me know what you mean by all that work?
On the 5t, after decrypting, I just had to make sure to flash no verity script in twrp and that was all.
Click to expand...
Click to collapse
He likely means backing up and starting fresh. I hated that process on my oneplus 5 but after works it was great. This whole slot A and B, is a pesky little bugga.
Yayodroid said:
What I do is:
Download and install the update
Don't reboot
Then back out and go to magisk downloads
Search for twrp retention and install
Don't reboot
Then back out to magisk main screen and select the first install option
Then select install and then the 4th option ota install slot
Now reboot
Click to expand...
Click to collapse
This is what I did as well. Worked beautifully.
harpin14789 said:
I'm thing about decrypting, if you don't mind, can you let me know what you mean by all that work?
On the 5t, after decrypting, I just had to make sure to flash no verity script in twrp and that was all.
Click to expand...
Click to collapse
I manually decrypted
I don't know if the zip works on the 7 Pro
I'd update via twrp
Flash twrp
Flash magisk (after echo KEEPVERITY=FALSE > /data/.magisk)
ADB pull both fstab files in vendor/etc to my pc
And change fileencryption to encryptable and move back
I always kept the fstab files on my internal storage so I didn't need a PC but I always did just incase.
What happens if you have and F2FS formatted /data and
A custom kernel?
Thanks in advance
reaper000 said:
The best way to update? Personally, I recommend taking full manual control of the update process. Use TWRP to update your ROM (that includes stock OOS) when you want to, and when you need to fix stuff.
- Flash ROM
If you are on slot A and flash a ROM, it goes to slot B.
- Flash TWRP installer zip
Keeps TWRP on both slots, patches boot.img
- Reboot to TWRP, not system
- Flash ROM again
This installs the ROM to the other slot, so now both slots are updated
- Flash TWRP installer zip again
Keeps TWRP on both slots, patches boot.img
- Flash Magisk
Patches the TWRP-patched ROM, allowing it to boot.
- Wipe dalvik
You can wipe data and dalvik instead for a clean flash
- Now reboot to system
Consider flashing BOTH slots (A and B) whenever you update OOS, for two reasons.
First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base.
The second reason is more compelling: the way the data partition changes encryption every update has nearly obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!
Click to expand...
Click to collapse
I am wondering if there is any possible way to get a custom recovery (Even if not TWRP) installed onto my pixel 3a running stock 10? I'm rooted, and am concerned about installing xposed modules without any form of recovery. If there isn't any way to get a recovery, is there a method to maybe disable exposed during boot to prevent a bootloop?
Thanks.
dev1334 said:
I am wondering if there is any possible way to get a custom recovery (Even if not TWRP) installed onto my pixel 3a running stock 10? I'm rooted, and am concerned about installing xposed modules without any form of recovery. If there isn't any way to get a recovery, is there a method to maybe disable exposed during boot to prevent a bootloop?
Thanks.
Click to expand...
Click to collapse
Simply said, no. the only working recovery is TWRP. And it only works on Android 9. Also its not installed, you can just boot it and not all features work. Accessing /system is out of the question, because Google introduced some security stuff which makes it read only.
I mean, when you want to test out some specific modules, just backup all your stuff and try out all the modules you need. In the worst case you would have to flash the factory image and restore your data...
I used xposed a lot in the past but im not missing it for a long time. Which are the modules you want to install?
bejunk said:
I mean, when you want to test out some specific modules, just backup all your stuff and try out all the modules you need. In the worst case you would have to flash the factory image and restore your data...
Click to expand...
Click to collapse
Before completely re-flashing, one can try this adb command to remove all magisk modules right?
adb wait-for-device shell magisk --remove-modules