I suppose most of you have XZDR for either LP or KK, and are on a locked bootloader.
There's the thing about XZDR compared to other phones' recoveries - XZDR doesn't seem to be on its own partition, so when you mess up a few things, your recovery becomes inaccessible. This is... rather problematic, but it'd be nice to have a list of things to pay attention to when it goes wrong. From my own experience, I've discovered the following things:
Losing functional root access
Losing system r/w access
For the rest, it seems less problematic. Xposed bootloops don't affect XZDR, so you can recover from it easily.
Recovering from a bootloop without XZDR access is pretty easy. You can flash the same version of your ROM in Flashtool without wiping data. It'll be reset to stock /system, but your apps will be kept. After that you can do the Kingroot+XZDR+SuperSU thing again to re-gain functional root access.
Related
Yes I have read the FAQ, and I still think this is possible, if you install via custom recovery.
Currently the flashable zip generation requires root access. If there is any way to generate that flashable zip file without root then only a custom recovery would be required to install Xposed, as a custom recovery can write to /system without needing root. Since I am currently installing root only to install Xposed and then immediately removing it I would greatly appreciate an install option that doesn't require me going through the rooting process.
So my request is for the two recovery installation options not require root to generate the zip file. Thank you.
Open recovery, flash ZIP file.
You don't need at all.
That part I know. Once I have the flashable zip file I am fine. However, on my phone I cannot create the flashable zip file without root. It just fails. Hence my request.
Stupid question, but can you install recovery without root?
ldeveraux said:
Stupid question, but can you install recovery without root?
Click to expand...
Click to collapse
Yes, some manufacturers include recoveries pre-installed, but those often have restricted functionality.
Also, recovery can be installed on some phones without root with the use of a PC (again, it's brand-dependant).
And finally, a few (too few) manufacturers ship their devices with unlocked bootloader which means you can do anything you want with them.
XspeedPL said:
Yes, some manufacturers include recoveries pre-installed, but those often have restricted functionality.
Also, recovery can be installed on some phones without root with the use of a PC (again, it's brand-dependant).
And finally, a few (too few) manufacturers ship their devices with unlocked bootloader which means you can do anything you want with them.
Click to expand...
Click to collapse
Yep. I personally have an HTC device and they allow anyone to unlock their bootloader by filling out a form on their website. Once the bootloader is unlocked no root is required to flash a custom recovery. That is how I typically run my device no root but custom recovery. Occasionally, I revert to stock recovery to install a system update. Then I run into this issue where I have to root just to reactivate Xposed, then unroot again. I would much prefer to avoid the root/unroot part of reactivating Xposed.
I'm hoping that since it is only creating the zip file that I am asking about this is a quick and easy change.
XspeedPL said:
Yes, some manufacturers include recoveries pre-installed, but those often have restricted functionality.
Also, recovery can be installed on some phones without root with the use of a PC (again, it's brand-dependant).
And finally, a few (too few) manufacturers ship their devices with unlocked bootloader which means you can do anything you want with them.
Click to expand...
Click to collapse
In Moto G you can install a custom recovery and mount /system and /data (I need a custom recovery to flash SuperSU.zip), so, I think it's possible.
XspeedPL said:
Yes, some manufacturers include recoveries pre-installed, but those often have restricted functionality.
Also, recovery can be installed on some phones without root with the use of a PC (again, it's brand-dependant).
And finally, a few (too few) manufacturers ship their devices with unlocked bootloader which means you can do anything you want with them.
Click to expand...
Click to collapse
Not the stock recoveries, installed recoveries. I didn't think you could install TWRP or CWM without root.
ldeveraux said:
Not the stock recoveries, installed recoveries. I didn't think you could install TWRP or CWM without root.
Click to expand...
Click to collapse
Have you heard of flashtool or Odin?
Using flashmode/fastboot you can do more than with root.
ldeveraux said:
Not the stock recoveries, installed recoveries. I didn't think you could install TWRP or CWM without root.
Click to expand...
Click to collapse
I have installed both without root multiple times. Here are a few guides.
Nexus Devices (Note rooting comes after custom recovery is installed.)
General Advice (Note: First option requires root, second two do not.)
In general as long as you can unlock your bootloader no root is required. I have only ever purchased Android devices that let me unlock the bootloader, so I have always gone that route.
Again for my feature request though I just want the flashable zip generation to not require root. That (hopefully minor) change would allow a completely root free use of Xposed. Which would be wonderful for me.
Stock recovery will only flash officially signed packages. If you have a custom recovery, you can easily gain root access. So what point would it serve?
mattdm said:
Stock recovery will only flash officially signed packages. If you have a custom recovery, you can easily gain root access. So what point would it serve?
Click to expand...
Click to collapse
That question makes no more sense to me than a comment that Xposed does nothing more than a custom ROM, and if you can install Xposed you can install a custom ROM so what is the point of Xposed?
However, I will provide a few of my answers to your question pick your favorite.
Requiring root without needing to doesn't serve any point so why require it?
Root is required "because it replaces a file in /system/bin". However, on my phone /system/bin is write protected by the kernel, so root does not grant write access to /system/bin only recovery does, So why is root required to create a zip file that I install via recovery?
I like to be able to run apps that don't work if you are rooted. (DRM protected movies, corporate apps, etc.) so rooting causes me problems, and fully unrooting afterwards is a bit of a pain. (I have had to develop a custom script to do it efficiently.)
So, I just did some more searching and discovered that I'm not the only one who wants this. jurben requested this back in September and even wrote up the code to make it possible.
So, I went ahead and turned it into a Pull Request on GitHub. Hopefully it gets accepted.
Yesterday I unlocked my bootloader, so the system made a whole reset, and I was stuck on an 14.5.A.0.270 stock with no root.
I downloaded a "advanced kernel" with root & recovery that killed my system, and I reflashed again the 14.5.A.0.270 stock (it's aliveeee!).
Now, I am wondering if there is an easy way of achieving root (unlocked bootloader) without having to download + reflash thousands of things... Maybe an advanced kernel for this rom would work? I tried to generate one with NUT's kernel builder but it does not seem to work...
Kingroot does not do the trick either...
Any assistance?
Hi,
I'm on the same system as you are (.270) and rooted my device with the Kingroot method. At first I've thought it had failed, however after exiting the app and giving two or three more tries it did the work, I suggest you doing the same .
Then with root access I was able to backup the TA partition, unlock bootloader, flash a custom kernel with TWRP and CWM Recoveries to root device again with SuperSU instead of KingUser (I've opened data usage and wasn't quite happy when I've seen that KingUser had used my data without my knowledge).
All the best,
~Lord
"And people think so supersonic and they make their bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10
I did as you said, test again, and it worked. With that and the scritp to replace Kinguser by Super su, I was ready to go.
Also, I really do not trust kinguser that much, it does quite a share of weird internet connections...
Thanks!
I rooted my Z3C some time ago with the instructions from this forum and kept it through various updates. Once PoGo (yes, I know...) added checks through Google SafetyNet I removed the root (SuperSU - Complete Unroot) and got the CTS validation back again (double checked with the example app from the play store)
Although I removed the root, the recovery is still there so I could reinstall it, when I need it again w/o going through the whole downgrading-upgrading process again which would mean I'd loose all my data/settings.
Now there where 2 maintenance updates from Sony (11th Oct, 12th Oct) and after the 2nd PoGo wouldn't start any more. Checking with the SafetyNet helper shows that CTS validation fails.
Does anyone experience similar issues? How could I solve this? Is SafetyNet e.g. detecting the custom recovery (TWRP)? I already searched for remaining *su* files but found none (only .superSU files which I removed)
I thought about reflashing the FTF. If I don't repartition I won't loose my recovery, right? Or should I also exclude the system partition?
My Idea for that is, that systemless SU changes the boot partition which might get detected. SO flashing the FTF should solve that.
Any help is appreciated.
Not exactly the same, but my few cents:
I have been running SLiMM Rom from the forums. Also I used root when I needed it and removed it to play PoGo.
After the update this week, PoGo would not start anymore although I am unrooted.
As I did not use the Root "features" much (mostly another hosts.txt to block adds) I decided to go back to a Stock Rom.
After flashing the Stock .291 ftf everything went back to normal. I did a full wipe and installed it "clean".
PoGo starts again now...
However, I'd rly like to know which feature or whatever SafetyNet is checking.
I have been thinking about rooting the Stock Rom again to regain adblock... But due to your description it seems to lead to a fail again.
same issue, im using stock rom .575 and i flash TWRP with this way and i cant play:c
using Z3C LB
@Ministry87 Did your FTF flash? Or what would I need to check/uncheck to keep it?
Also: If I reflash the FTF, is it enough to NOT check the 2 WIPE options to make sure my data is not erased? Or does it still erase something?
Ministry87 said:
Not exactly the same, but my few cents:
I have been running SLiMM Rom from the forums. Also I used root when I needed it and removed it to play PoGo.
After the update this week, PoGo would not start anymore although I am unrooted.
As I did not use the Root "features" much (mostly another hosts.txt to block adds) I decided to go back to a Stock Rom.
After flashing the Stock .291 ftf everything went back to normal. I did a full wipe and installed it "clean".
PoGo starts again now...
However, I'd rly like to know which feature or whatever SafetyNet is checking.
I have been thinking about rooting the Stock Rom again to regain adblock... But due to your description it seems to lead to a fail again.
Click to expand...
Click to collapse
I think it maybe has to do with GMS Optimizer included in SLiMM ROM
There is a thread or two for this or a similar variant from the US, but none of the files work on the UK model, most at least work, but don't go into recovery mode making using them pretty useless, one boots into recovery but has no GUI meaning aside from ADB commands, nothing can be used there either.
Is there anyone actively developing these phones anymore? If so, could you look into knocking a build up for these phones?
I have a stock 6.0.1 recovery partition if that will help the process.
I have a few phones that are on 5.1, but these have the same problem as the above, although these phones can be rooted, without recovery root access gets wiped every boot even though the bootloaders have been unlocked. And the process is a pain, root with kingroot, remove it from device administrators, start a terminal and run a script which occasionally works, or reboots the phone depending on how it's feeling at the time. With a working TWRP I can force the SuperSU zip and all will be good in the world, or at least my little bit of it.
Kind regards
Ian
Hello all,
I want to flash a mod.zip (in my case it is the v4a rootless driver) on my unrooted redfin with A12.
As you might know there is no TWRP right now for our Pixel 5 with A12, therefore I qm looking for other ways to flash this particular zip file.
I am trying to remove root from my device as it makes life more complicated which is not really necessary.
So is there any way to flash a mod.zip on an unlocked device without using a custom recovery?
Thanks in advance!
No. Only a custom recovery can be used to flash something, and a custom recovery requires unlocked bootloader.
It IS possible to install a Magisk module by temporarily booting a Magisk patched boot image, but again that requires an unlocked bootloader, and I don't think Magisk can install modules without root. Even if it could, root would still be required in order to load said modules.
If this driver doesn't require root, I would imagine it can be installed from within V4A.
The problem here is that Android checks for signatures which are only known by the makers of the phone. So that only developers of the phone can push updates. Custom recovery just bypasses the check which helps you flash anything
Android 11 + root is working wonderfully.
We have permanent TWRP.
I don't believe nandroid backups work but haven't tried really yet.
If you are only routing for V4A, I guess it comes down to is it worth it for you, as I haven't known a way to use V4A on A12 while un-rooted.
Best of luck.
andybones said:
I don't believe nandroid backups work but haven't tried really yet.
Click to expand...
Click to collapse
I can confirm that as of a few days ago, TWRP didn't create a working Nandroid backup for me even though it finished the process and prompted "success"!
Before I started to mess around with my phone, I created a Nandroid copy thinking if anything happens, I can always restore using this backup. I was so disappointed after I soft bricked my phone but my Nandroid copy was useless to save me. As a result, I flashed with a Google ROM for the 1st time in my Android ownership without root.
In the past 6 months, I've had to combat Google 3 times to pass SafetyNet. Though I could get it to work on the 1st 2 times, it was a lot of time investment since I had to research for a solution. The 3rd time I bricked my phone and had to factory reset the phone and start over.
If Google keeps beefing up SafetyNet every few months, this cat and mouse game is simply too time-consuming to make up for the convenience of a rooted phone.
Passing safety net is easy. Just install magisk canary it's just that easy. But the only thing is that magisk hide is not there in canary