Hi guys, in the last days I had lost my root after the annoying security patch that have affected many of us.
Re-rooting with CF Auto Root seems to be ineffective for devices that have lost the stock boot image backup, as explained by Chainfire here: https://plus.google.com/+Chainfire/posts/XMFgencRR11
In theory, fixing root is as simple as flashing the new SuperSU v2.74 BETA ZIP file in TWRP, or using the updated CF-Auto-Root for your device.
In practice, this will not work for a fair share of users. To re-systemless-root using SuperSU ZIP's or CF-Auto-Root, if you have already been rooted, requires the stock boot image to be restored. Both methods create a backup of the stock boot image before applying root. During testing of this fix however, it became clear that a lot more users than I had expected managed to somehow lose this backup (clearing cache, factory reset, etc).
If this backup is no longer on your device, neither flashing the SuperSU ZIP nor re-applying CF-Auto-Root will fix the issue, as both installations will fail.
Click to expand...
Click to collapse
There is a solution here but before that I want to be sure that the stock boot image isn't on my device.
I have only carried two factory reset before rooting with CF Auto Root and never after so in theory I still have the backup of the stock boot image maked from CF Auto Root during my first root on my phone, is that correct or have I misunderstood?
Can I use the latest CF Auto Root (BETA-SuperSU-v2.74) with Odin like in my first root in order to try that or I could have problems?
Thank you very much for your help, I'm pretty new in the Android world and my english is not so good...
Related
I am caught in a bootloop after attempting to root using the following process.
Using Odin3 v3.10.6, I flashed the following:
n915t-cwm-recovery-6.0.5.1(1128).tar - THIS MAY HAVE BEEN AN ERROR. SHOULD I HAVE USED "openrecovery-twrp-2.8.1.1-trltetmo.img.tar"
I did a full backup to my phone's external SD card from cwm-recovery-6.0.5.1.
I then flashed both the files below without rebooting in between. I did not wipe any cache or data.
Emotion-TW-nightly-r23-RC1-SM-N915T
UPDATE-SuperSU-v2.46
The phone locked when I rebooted and would not move past the first black screen.
I pulled the battery and rebooted to recovery.
I did a restore of my backup that appeared to complete successfully.
I got a message asking to root the phone. I said yes, then rebooted.
Now stuck in a bootloop.
Hoping I can recover from this?
Root only with extra Kernel
When recovery asks to install root at the end, hit no. Thats your issue. You already installed supersu, so you've already got root. Personally I prefer stock kernel, with the latest beta supersu, you can still get root. With Universal init.d app, you can still get init.d support. With a custom build of xposed for Samsung lollipop, you can still get xposed. There's even a special version of viper audio. So yeah all you lose is the overclock ability.
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
rootnooby said:
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
Click to expand...
Click to collapse
There have been reports that the emotion r23 kernel is finicky, some work soem dont. Try another kernel or older version. That could be toir problem.
Sent from my SM-N915T using Tapatalk
TWRP 3.0.2-0
SuperSu Pro 2.78
Android 6.0 Marshmallow build MPH24.49-18
I have systemless rooted my phone as per the instructions at http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
although, it didn't work without some tweaking... Unfortunately I don't remember what steps I took to get it working.
I am not sure of the process form here. Now that I have root, am I supposed to flash boot_orig.img permanently or just when I want to update?
I have tried:
fastboot flash boot boot_orig.img
but I loose wifi and can't download.
I have tried letting the OTA fail with the boot.img flashed, then reflashed with boot_orig.img and tried to install the update zip file via TWRP, but that fails.
I made a TWRP backup before I started rooting and for every major step after that, so I can start fresh if need be.
[EDIT]
I noticed on this thread, http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 , the following comment:
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with each other. The installer for this experiment will not clean up old root files.
- Flash stock /system (and /vendor and /oem, if present)
- Flash the attached boot image
- Flash the attached SuperSU ZIP in TWRP
Click to expand...
Click to collapse
Could this be the problem? If so, How do I "flash stock /system (and /vendor and /oem, if present)"?
Any help appreciated...
Hi guys,
yesterday I rooted my galaxy S7 sm-g930f.
Everything worked fine and in a few minutes later I was back on stock fw with twrp and magisk root. But unfortunately I lost my IMEI and have no backup of this.
I read that I can resolve it by flashing factory binary.
Can anyone guide me through the steps I have to do? I think I'm able to manage it but wondering if there are any files I do need for my fw version or can i simple download any factory binary?
Thanks in advance
Catarrer
Flash firmware with a newer modem version compared to the one in the custom rom you were using (not factory/combination). Use the same CSC, the stock recovery might be required to apply CSC.
If that doesn't work, wipe data (backup photos and all that).
Backup EFS in TWRP, nothing else unless sure.
Hi Bryan48765,
Thanks for your reply.
I'm downloading atm the newest fw which is available for my device. (May be take a while with 2k dsl...)
I'm going more concrete about the steps I did:
I activated the dev options, switched on the oem unlock and then switched to download mode.
Installed the latest twrp with the latest Odin version.
First I rooted my device then with chainfires supersu, but it doenst show up as rooted (rootchecker) so I flashed back a boot loader for my device which I downloaded here. Unfortunately i don't know any more which one...
After flashing the vootloader I installed magisk and everything was fine... and then a few hours later i recognised that mobile network isn't working. A few looks later I saw that there was no imei... so I don't know if it was working before flashing the boot loader or the error occurred afterwards.
I'll try tomorrow to flash the downloaded fw.
Do I get the single csc file for my current version or do I need to download the whole fw? (Takes about 5h)
Thanks in advance
Cayarrer
Thank you!
I'm now back to stock fw and have my imei back! Thank you so much!
At weekend I will try to root again. Do I need to pay attention to anything to not lose my imei again?
I would follow these steps:
Flash latest twrp for my device without auto reboot, boot directly into recovery and flash there the no-verity file and then the magisk. Am I right or do I need some more or less?
You guys at sea are so amazing! Thank you!
Catarrer2 said:
Thank you!
I'm now back to stock fw and have my imei back! Thank you so much!
At weekend I will try to root again. Do I need to pay attention to anything to not lose my imei again?
I would follow these steps:
Flash latest twrp for my device without auto reboot, boot directly into recovery and flash there the no-verity file and then the magisk. Am I right or do I need some more or less?
You guys at sea are so amazing! Thank you!
Click to expand...
Click to collapse
Backup the EFS, and store it in the cloud (not public), maybe encrypt the zip it is stored in. Only if a lot of firmware changes and data wipes don't return the imei, restore the backup. The restoration could also affect some modem settings, battery wear info, and it might not be restored correctly.
Unlock the bootloader before flashing the latest twrp. RMM serms to not apply here.
If the phone is encrypted (should be visible in the security settings) twrp might show that it "failed to mount /data", and it's normally where the root zip is stored. Alternatively, move the root zip and others to the external sdcard, though with root+encryption there might or might not be a risk for a type of brick.
Encryption is disabled by formatting /data and flashing a zip that disables it.
no-verity-opt-encrypt might already be in magisk but flash it anyway and if it fails return to the stock kernel ("boot" in twrp)
I'm new here so I'm not sure if this is the right place for this, but here goes. I've been trying to root my '19 Galaxy Tab A T290 [T290XXU3CUF8] for a couple months now on and off. I manage to get a success message from Odin when flashing TWRP but when I try to reboot into it, it goes straight back to the OEM recovery. I have the bootloader unlocked. I have read every forum and website I could find, but to no avail. I've tried different versions of Odin and the TWRP for my model. I'd imagine once I get TWRP flashed I'll be able to successfully install SuperSU. I've read to take the battery out after getting the success message from Odin but the battery isn't removable in my model. Any help would be greatly appreciated.
SuperSU doesn't root Android: it's an application which lets you manage root permissions for apps which require root access.
Android is rooted when SU-cmdlet - by whatever method - got added to Android and is system-wide accessible.
BTW: TWRP isn't needed at all to root Android.
jwoegerbauer said:
SuperSU doesn't root Android: it's an application which lets you manage root permissions for apps which require root access.
Android is rooted when SU-cmdlet - by whatever method - got added to Android and is system-wide accessible.
BTW: TWRP isn't needed at all to root Android.
Click to expand...
Click to collapse
I'm obviously not very good with Android. Do you have any suggestions for me ? From what I've read, it sounded like, among other methods, I needed to flash SuperSU via TWRP in order to get root.
Hi there, I'm having no luck finding a solution to my problem anywhere.
I'm using a Galaxy S7 running Oreo (I know, old school), and like many phones, it came with a bunch of apps that can't be uninstalled unless you have root access. So, I installed TWRP, and then Magisk v23, and then I installed a root uninstaller in order to remove the apps in question.
However, I use Revolut and an app for the bank I'm with, and so while my device is rooted, I am locked out of both.
What I want is to have the disable-only apps gone, and my device unrooted and back to normal so I can use Revolut and said banking app.
I believe uninstalling Magisk should unroot the device, but without Magisk installed, I can't boot into the system because of TWRP and the whole dm-verity thing. So, I want to replace TWRP with the stock recovery, which, if I'm correct, should achieve the desired outcome.
I downloaded the exact firmware for my phone from sammobile, and the recovery file can be extracted from it easily, but I don't really know how to go about flashing said file, or even if I can. Odin isn't working for me.
I tried flashing the whole "AP" file via Odin (the latest version), but that restored the device back to it's factory state, disable-only apps and all.
So can anyone help me with this? Or is what I want to do here even possible? I'd really appreciate some input / advice. Thanks!
P.S. maybe you can tell, but I'm kind of a noob, so apologies if I'm overlooking something obvious.
Android's recovery where it doesn't matter whether it's Stock or Custom can't be used to unroot Android if it got rooted by TWRP and/or Magisk this because phone's boot.img got tampered by those: you'ld have to completely re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
Okay then, thanks for explaining.
Just to be clear, what you're saying is that it isn't possible to unroot a device and then restore just its stock recovery (to replace TWRP). You cannot undo modifications made to boot.img and therefore must re-flash the stock firmware?
What I do with unwanted system apps on other android phones is to remove the .apk from /system by booting into recovery and using the shell/adb with u**x commands (actually move them somewhere they can't be seen by the O/S with mv command).
Also when faced with dm-verity, Magisk just modified the boot.img
and changes fstab to take out verify from system mount & patches init and removed /verity_key.
I was able to uninstall Magisk (only phone mod was unlocked boot loader allowing custom boot over usb).