I'm pretty sure no no roms for the Fire will pass safetynet, due to the necessary permissive kernel. I tried installing Magisk via Flashfire, which bootloops as expected. Has anyone had success getting their ROMed Fire to pass Safetynet?
Would it be possible to bake Magisk into a Rom?
funkybrunk said:
I'm pretty sure no no roms for the Fire will pass safetynet, due to the necessary permissive kernel. I tried installing Magisk via Flashfire, which bootloops as expected. Has anyone had success getting their ROMed Fire to pass Safetynet?
Would it be possible to bake Magisk into a Rom?
Click to expand...
Click to collapse
Possible - yes (anything is possible). But doubt you'll see any immediate effort in that direction.
I do not believe this is possible. Magisk is a system-less root, so it installs itself into the /boot volume. These tablets have a locked bootloader, so any tampering with the /boot volume will throw off the bootloader, resulting in the bootloop you're seeing. This is the same reason we can't install a custom kernel, as that would throw off the checksum of the /boot.
I use Fire Nexus ROM, which has SuperSu built into the ROM. The ROM uses a stock /boot, and a custom /system that is specifically written to be compatible with the stock /boot & kernel. Does that make sense?
crazyates said:
I do not believe this is possible. Magisk is a system-less root, so it installs itself into the /boot volume. These tablets have a locked bootloader, so any tampering with the /boot volume will throw off the bootloader, resulting in the bootloop you're seeing. This is the same reason we can't install a custom kernel, as that would throw off the checksum of the /boot.
I use Fire Nexus ROM, which has SuperSu built into the ROM. The ROM uses a stock /boot, and a custom /system that is specifically written to be compatible with the stock /boot & kernel. Does that make sense?
Click to expand...
Click to collapse
Make a ton of sense. But it might be possible of a method of signature forging was identified as happened with 3rd gen HDX devices before a full bootloader unlock became available. Of course, discovering the 11th planet in our solar system within the next 5 years is equally likely - but hey, anything is possible!
Yeah, 100% right, no magisk due to the locked bootloader and signed boot.img. magisk needs to unpack/modify/repack the boot image. Should have thought it through before I started the thread. Just trying to get Mario to run on my kid's tablet.
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.
Hey guys, I have a 64GB stock T-Mobile Galaxy S6 that I have (somewhat) debloated and so far the battery is okay.
I've heard promising reviews about XtreStoLite G920T Pure Edition ROM.
First, I want to make a backup of the STOCK ROM I currently have, but IIRC, you cannot back it up unless you root first?
I was looking into PingPongRoot so I could go back to stock just in case anything would happen but I need to know how to back it up first.
Second, I want to install the ROM and I'm pretty sure I'm correct. Do I need Odin if I use PingPongRoot?
Third, I want to install Ktoonzes kernel as well but I don't know anything about that.
So, pretty much I need help with:
1. Backup current stock ROM before rooting
2. Root with PingPong
3. Install XtreStoLite
4. Install Ktoonzes
Also, if there is anything else I should be cautious of let me know. Thanks guys!
While all of this info is easily accessible, in the spirit of giving... Here you go.
To backup, you need root.
Install SuperSu from play store, open SuperSu at least one time, then download Ping Pong Root APK and run it. It may take two tries, that's normal.
Then, to back up, either install TWRP with Flashify (downloadable from Play Store) or via Odin (Either method will trip Knox in bootloader and void Samsung warranty, will not harm phone in any way) and back up
To install ROM, Flash in TWRP recovery (if you installed TWRP in last step Knox is already tripped)
Then, use TWRP to flash Ktoonzes kernel (I recommend letting ROM boot at least once fully then going back to recovery to flash kernel)
norcalsfinest said:
While all of this info is easily accessible, in the spirit of giving... Here you go.
To backup, you need root.
Install SuperSu from play store, open SuperSu at least one time, then download Ping Pong Root APK and run it. It may take two tries, that's normal.
Then, to back up, either install TWRP with Flashify (downloadable from Play Store) or via Odin (Either method will trip Knox in bootloader and void Samsung warranty, will not harm phone in any way) and back up
To install ROM, Flash in TWRP recovery (if you installed TWRP in last step Knox is already tripped)
Then, use TWRP to flash Ktoonzes kernel (I recommend letting ROM boot at least once fully then going back to recovery to flash kernel)
Click to expand...
Click to collapse
jeffreylin_ said:
If you don't want to void your warranty, you could back up using Chainfire's FlashFire, but note that it is an app and therefore you need to have a semi-working system to restore! Which is fine since you can flash stock using Odin, then root using PingPong and install FlashFire again. Just slightly more of a hassle.
Click to expand...
Click to collapse
Thanks guys!
jeffreylin_ said:
If you don't want to void your warranty, you could back up using Chainfire's FlashFire, but note that it is an app and therefore you need to have a semi-working system to restore! Which is fine since you can flash stock using Odin, then root using PingPong and install FlashFire again. Just slightly more of a hassle.
Click to expand...
Click to collapse
So wait... flashfire and pingpong root i can flash a new rom without tripping knox????
frettfreak said:
So wait... flashfire and pingpong root i can flash a new rom without tripping knox????
Click to expand...
Click to collapse
Yes, only if you don't flash a kernel with the new ROM. You have to edit the zip and remove the boot.IMG , then edit the updater script to remove the command to wipe and flash boot.img. if this sounds too difficult to you don't try it
norcalsfinest said:
Yes, only if you don't flash a kernel with the new ROM. You have to edit the zip and remove the boot.IMG , then edit the updater script to remove the command to wipe and flash boot.img. if this sounds too difficult to you don't try it
Click to expand...
Click to collapse
So how do you flash a custom ROM without a custom recovery? Recovery trips Knox...
I'm gonna need to look into this one. Been a while since I did anything with a Samsung device.
Marine6680 said:
So how do you flash a custom ROM without a custom recovery? Recovery trips Knox...
I'm gonna need to look into this one. Been a while since I did anything with a Samsung device.
Click to expand...
Click to collapse
I don't think chain fire has been to open about how flashfire works (not a problem his choice). So if you want a good idea how it works look into safestrap, I'm sure it's close other than the fact safestrap doesn't need a app in a working system.
ThePagel said:
I don't think chain fire has been to open about how flashfire works (not a problem his choice). So if you want a good idea how it works look into safestrap, I'm sure it's close other than the fact safestrap doesn't need a app in a working system.
Click to expand...
Click to collapse
Needs a zip without the kernel... I remember seeing a ROM that mentioned not having a kernel, I guess for this reason.
I don't think any of the t-mobile ROMs come setup like that though. So I would need to go through the trouble of repackaging the ROMs myself.
May not bother and just trip the counter and flash normal. Custom kernels are often the way to go for battery life and performance.
Marine6680 said:
Needs a zip without the kernel... I remember seeing a ROM that mentioned not having a kernel, I guess for this reason.
I don't think any of the t-mobile ROMs come setup like that though. So I would need to go through the trouble of repackaging the ROMs myself.
May not bother and just trip the counter and flash normal. Custom kernels are often the way to go for battery life and performance.
Click to expand...
Click to collapse
Oh I thought you meant how flashfire boots into its recovery mode without tripping knox, yeah custom kernels and recoveries will trip knox but if the demand is high enough there are ways to use custom kernels without flashing them and someone is bound to bring it to the s6, but I'm sure the demand has to be high enough.
ThePagel said:
Oh I thought you meant how flashfire boots into its recovery mode without tripping knox, yeah custom kernels and recoveries will trip knox but if the demand is high enough there are ways to use custom kernels without flashing them and someone is bound to bring it to the s6, but I'm sure the demand has to be high enough.
Click to expand...
Click to collapse
Its an interesting alternative to full root flashing. Preserving the warranty is good for some people.
Ever since I did pingpong root, I have been having odd issues with pandora bluetooth streaming to my car. Hopeing a custom ROM will solve this.
I think I already know the answer, but with a £550 device I'd rather double-check with the experts.
Is there any reason that I should not boot temporarily to TWRP to install SuperSU 2.62 ("fastboot boot twrp.img")? I don't believe that a permanent TWRP installation is a necessity, and if I understand Chainfire's comment correctly:
http://forum.xda-developers.com/apps/supersu/chainfire-systemless-root-android-6-0-t3271137
leaving the device as stock as possible, including stock recovery, means an easier upgrade path for OTAs. The best of both worlds - regular OTA security updates plus root.
Any reason that this would not work, and more importantly any reason that it might risk the integrity of my N6? I don't want an expensive paperweight...
Thanks...
dahawthorne said:
I think I already know the answer, but with a £550 device I'd rather double-check with the experts.
Is there any reason that I should not boot temporarily to TWRP to install SuperSU 2.62 ("fastboot boot twrp.img")? I don't believe that a permanent TWRP installation is a necessity, and if I understand Chainfire's comment correctly:
http://forum.xda-developers.com/apps/supersu/chainfire-systemless-root-android-6-0-t3271137
leaving the device as stock as possible, including stock recovery, means an easier upgrade path for OTAs. The best of both worlds - regular OTA security updates plus root.
Any reason that this would not work, and more importantly any reason that it might risk the integrity of my N6? I don't want an expensive paperweight...
Thanks...
Click to expand...
Click to collapse
having root = no ota, so having twrp is besides the point. anyways, twrp is one of the mist useful tools to have if you mod your device. you can make, and restore, a nandroid backup. if you make a mod, and it messes up, you probably wont noot anymore, but a nandtoid backup restored will bring your device back to how it was.
Yes, thanks, Simms, I get all that, but it's not really answering my question. Is there any problem with using temporary TWRP to install SuperSU?
Also if you read Chainfire's comment he makes it clear that his systemless root doesn't prevent OTA, whereas having a non-stock recovery might.
dahawthorne said:
I think I already know the answer, but with a £550 device I'd rather double-check with the experts.
Is there any reason that I should not boot temporarily to TWRP to install SuperSU 2.62 ("fastboot boot twrp.img")? I don't believe that a permanent TWRP installation is a necessity, and if I understand Chainfire's comment correctly:
http://forum.xda-developers.com/apps/supersu/chainfire-systemless-root-android-6-0-t3271137
leaving the device as stock as possible, including stock recovery, means an easier upgrade path for OTAs. The best of both worlds - regular OTA security updates plus root.
Any reason that this would not work, and more importantly any reason that it might risk the integrity of my N6? I don't want an expensive paperweight...
Thanks...
Click to expand...
Click to collapse
Don't usually encourage use of toolkits but Wug's toolkit includes and option to do this kind of one time boot, I don't know off the top of my head what actual process it uses for that or I'd just tell you that. But yea I'd just recommend leaving TWRP on and after first flashing it and booting into it twrp should prompt you something along the lines of keeping /system mounted as read-only, do that and make a backup including the "system image" and boot. Then in Advanced>uncheck "mount system as read-only."
Whenever an ota rolls around you can go back into twrp and restore that boot and system-image backup when you boot up android will replace twrp with stock recovery and the ota should work.
Thanks again - I appreciate the answer, but again it doesn't really answer my question. I've been using TWRP for years and I'm well aware of its benefits. What I want to know if there's any problem with using it as a one-off to install SuperSU, leaving stock recovery in place when I reboot so that TWRP can't interfere with the OTA.
I'm also very well aware of NRT, which again I've used for years and have donated to several times (excellent program), but I don't need it when "fastboot boot recovery twrp.img" will do the job faster.
Am I not explaining myself properly?
dahawthorne said:
Thanks again - I appreciate the answer, but again it doesn't really answer my question. I've been using TWRP for years and I'm well aware of its benefits. What I want to know if there's any problem with using it as a one-off to install SuperSU, leaving stock recovery in place when I reboot so that TWRP can't interfere with the OTA.
I'm also very well aware of NRT, which again I've used for years and have donated to several times (excellent program), but I don't need it when "fastboot boot recovery twrp.img" will do the job faster.
Am I not explaining myself properly?
Click to expand...
Click to collapse
nah there should be no problem with that.
theres no issue with it, just keep your bootloader unlocked, or you can have issues in the future. btw..
fastboot boot recovery recoveryname.img as opposed to fastboot flash
Thanks, both - I appreciate the help.
Just in case anyone might find the confirmation useful, yes, it did work. I used "fastboot boot twrp.img" to install SuperSU 2.62-3 and it's all working fine. If I understand Chainfore correctly in the link quoted above, using SuperSU's "full unroot" will allow the next OTA, then I can repeat the fastboot install, which should be far simpler than overwriting the system.img.
why would you want an OTA? this is XDA Developers, the worst ROM here is better than ANY OTA that you can have, plus you get it sooner and can try them all and have a backup of your favorite one. This sort of thing always makes me laugh!
I am glad to have brought some laughter and joy into your life. Though I hope that you can find better in your real life, right...?
buschris said:
why would you want an OTA? this is XDA Developers, the worst ROM here is better than ANY OTA that you can have, plus you get it sooner and can try them all and have a backup of your favorite one. This sort of thing always makes me laugh!
Click to expand...
Click to collapse
For noobs, Android Pay is one reason they may want to stick with factory stock with OTA capabilities. Systemless root is not easy for noobs to grasp.
After installing the latest Concept (3571), I unlocked my bl (which I'd locked previously), installed TWRP and then flashed the DRM-fix for Concept. My phone's working fine, but now when I power up I get a red warning with the wording: "Your device is corrupt. It can't be trusted and may not work properly."
How serious is this? Is this just the way that MM reacts to unlocked boot loaders, non-stock recovery or other such mods?
If it's just a warning message, I'm not worried, but I thought I'd check with you folks.
Thanks.
varxx said:
After installing the latest Concept (3571), I unlocked my bl (which I'd locked previously), installed TWRP and then flashed the DRM-fix for Concept. My phone's working fine, but now when I power up I get a red warning with the wording: "Your device is corrupt. It can't be trusted and may not work properly."
How serious is this? Is this just the way that MM reacts to unlocked boot loaders, non-stock recovery or other such mods?
If it's just a warning message, I'm not worried, but I thought I'd check with you folks.
Click to expand...
Click to collapse
Relocking the boot loader did not get rid of the message. For now, I'm going to live with it, as I'm hoping it's an inconsequential warning.
Unless someone knows better, I don't plan to remove TWRP or undo the DRM fix, one or both of which are probably what's prompting this message.
[Aside: Looks like I've become my own best friend. Now if I can get myself to pick myself up at the airport next week....]
I found this:
http://www.droid-life.com/2015/07/27/operating-system-warnings-may-soon-come-to-your-boot-screen/
which suggests that this is just a routine warning that tweakers should expect to encounter.
After I blew away my DRM keys because of ignoring this sort of warning, I've become a little more paranoid.
Still, I'd like to hear anyone's thought. Actually, I don't want to hear your thoughts. That sounds horrifying. I'd like to read your opinions on this matter.
Thanks.
varxx said:
I'd like to read your opinions on this matter.
Thanks.
Click to expand...
Click to collapse
I guess it's because TWRP has modified /system partition on it's first boot. Upon my first flashing of Concept rom (~2 months ago) and flashing TWRP along with SuperSU it did show that warning, but that's because I let TWRP modify /system partition rather than keeping it read-only.
Just yesterday I went on to flash Concept again (coming from 5.1.1 which was flashed through Flashtool as well) when I booted into recovery (flashed using fastboot) I denied TWRP's request to modify /system, and before flashing anything in recovery I have made sure that /system is read-only (In TWRP -> Mount), that was highlighted by Russel in Concept rom thread.
No warning for now, and I guess it won't show up anyway. I don't think you should worry about it though.
Cirra92 said:
I guess it's because TWRP has modified /system partition on it's first boot. Upon my first flashing of Concept rom (~2 months ago) and flashing TWRP along with SuperSU it did show that warning, but that's because I let TWRP modify /system partition rather than keeping it read-only.
Just yesterday I went on to flash Concept again (coming from 5.1.1 which was flashed through Flashtool as well) when I booted into recovery (flashed using fastboot) I denied TWRP's request to modify /system, and before flashing anything in recovery I have made sure that /system is read-only (In TWRP -> Mount), that was highlighted by Russel in Concept rom thread.
No warning for now, and I guess it won't show up anyway. I don't think you should worry about it though.
Click to expand...
Click to collapse
O.K., that makes sense. I guess MM has added security features, because I've been using TWRP off and on for a long time but have never seen this. I'm reassured that someone else feels it's not serious.
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