Running a custom flavor of AOSP. Just wondering why my phone isn't vulnerable to that exploit? Is it do to being a custom ROM , supersu?
If you're on a build from the past few days it's likely that your rom includes cyanogenmod's fix for the exploit.
Okay, I was wondering.
Related
I'm on the latest official OTA of 4.2.1
Do I need to unlock the bootloader to root?
I read this http://forum.xda-developers.com/showthread.php?t=2187982
and I'm still not sure whats happening... Do I need to downgrade to root, and do I need to unlock the bootloader to flash TWRP?
I know a bit of what I'm doing as I have rooted and flashed roms on an htc desire and a samsung s2x (t989).
On 4.2.1 theres the occasional hiccup and freezes when I use chrome... Is this still an issue in the custom roms? Also my Settings app crashes when I try to load the "Running" tab in the apps section of settings lol
Can someone point me in the right direct?
Chris9446 said:
I'm on the latest official OTA of 4.2.1
Do I need to unlock the bootloader to root?
Click to expand...
Click to collapse
Well, you have two basic options:
Get root without unlocking.
That is good, if you want to stick with stock ROM, but want to run Apps that need root access.
Or if you don't want to unlock for any reason.
More details in this thread: [JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
Unlock and install the patched TWRP for -4.2.
This will allow you to root stock ROM easily or you can install custom ROMs.
Be careful: You have the boot loader 4.2, which means you need to pick the patched TWRP for that boot loader and you need to pick one of the ROMs supporting the 4.2 boot loader.
People have bricked their TF300Ts not using the patched TWRP -4.2 version.
There are currently only two ROMs available, but more should be coming soon, as Asus has finally released the new kernel source code.
If your preferred custom ROM supports only the 4.1 boot loader, you need to downgrade. Or just wait a little, as you like...
I read this http://forum.xda-developers.com/showthread.php?t=2187982
and I'm still not sure whats happening... Do I need to downgrade to root, and do I need to unlock the bootloader to flash TWRP?
Click to expand...
Click to collapse
No and yes.
You can use the tool from the tread above just get root; no downgrading, no unlocking.
But yes, if you want to install TWRP, you need to unlock your device first.
You only need to downgrade for installing a custom ROM that does not (yet) support the 4.2 boot loader.
On 4.2.1 theres the occasional hiccup and freezes when I use chrome... Is this still an issue in the custom roms? Also my Settings app crashes when I try to load the "Running" tab in the apps section of settings lol
Click to expand...
Click to collapse
I have not used stock ROM for a while, but generally people report that most custom ROMs run much smoother than stock Asus ROM:
I would suggest downgrading ti the 4.1.1 bootloader, as there is a much larger variety or ROMS available.
f69m said:
Well, you have two basic options:
Get root without unlocking.
That is good, if you want to stick with stock ROM, but want to run Apps that need root access.
Or if you don't want to unlock for any reason.
More details in this thread: [JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
Unlock and install the patched TWRP for -4.2.
This will allow you to root stock ROM easily or you can install custom ROMs.
Be careful: You have the boot loader 4.2, which means you need to pick the patched TWRP for that boot loader and you need to pick one of the ROMs supporting the 4.2 boot loader.
People have bricked their TF300Ts not using the patched TWRP -4.2 version.
There are currently only two ROMs available, but more should be coming soon, as Asus has finally released the new kernel source code.
If your preferred custom ROM supports only the 4.1 boot loader, you need to downgrade. Or just wait a little, as you like...
No and yes.
You can use the tool from the tread above just get root; no downgrading, no unlocking.
But yes, if you want to install TWRP, you need to unlock your device first.
You only need to downgrade for installing a custom ROM that does not (yet) support the 4.2 boot loader.
I have not used stock ROM for a while, but generally people report that most custom ROMs run much smoother than stock Asus ROM:
Click to expand...
Click to collapse
Thanks was a lot of great information! I rooted my pad and did a few speed optimization things such as re-trimming and now its much smoother! Maybe I'll try a custom rom later but as for now, I'm happy with the updates that Asus provides
cmendonc2 said:
I would suggest downgrading ti the 4.1.1 bootloader, as there is a much larger variety or ROMS available.
Click to expand...
Click to collapse
I'll keep that in mind but I believe there should be more soon as f69m, stated that asus release the kernel for 4.2
I signed that petition in your signature as well
I'd say go for the 'full experience'. Having an unlocked device also allows you to reflash ROMs at will and can also help in a pinch when it comes to backups/restores. Also, if you happen to lose root, it's easily re-rootable through the bootloader.
I'd just be careful of the current TWRP 4.2.1 recovery blob. I just flashed the one released this morning and I am currently getting this weird double screen thing. Best bet is to sit tight at the moment; an update should be out shortly.
danjng said:
I'd just be careful of the current TWRP 4.2.1 recovery blob. I just flashed the one released this morning and I am currently getting this weird double screen thing. Best bet is to sit tight at the moment; an update should be out shortly.
Click to expand...
Click to collapse
Well, stay away from the TWRP 2.5.0.0-4.2 provided in some thread today, but TWRP 2.4.4.0-4.2 should still be working fine.
Sent from my TF300T using Tapatalk HD
So I've seen a few threads asking a similar thing but since they're quite old, I'd like to ask again.
Quick info about my setup:
running stock ROM, MOB30H
system-less root
system-less Xposed
kernel: ElementalX
TWRP recovery
I was hoping I'll be able to install OTAs with less hassle thanks to up-to-date SuperSU and a special version of Xposed. I indeed have received an OTA today - a small update, I believe 9 MB. When I tried to install it though, TWRP booted up and nothing happened.
Does someone run a similar setup? Have you been able to install an OTA after flashing stock recovery (which I guess is what needs to be done to install OTAs)? Would I have to reflash SuperSU and/or Xposed?
Stock Nexus 5X Kernel + SafetyNet Patch
Current version: android-msm-bullhead-3.10-nougat-mr1.1
Suitable for build: N4F26T
I compiled the stock kernel for the Nexus 5X and applied the SafetyNet patch by sultanxda.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is for Android 7.1.1, build N4F26T!!!! This will not work on any prior build.
- All stock features that came with the N4F26T build will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the kernel included in the N4F26T build, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Extract <boot_image>.img from zip file
- Test it with: fastboot boot <boot_image>.img
- Once you know it works, flash with command: fastboot flash boot <boot_image>.img
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
And otherwise, I'm not a professional developer, just a hobbyist. Please don't ask me for a ton of help, I only created this kernel because I want to run completely stock, but still use Android Pay while having an unlocked bootloader in case I ever decide to root my device in the future. I will try to maintain this kernel with each new release until I lose interest
(shamelessly copied from Sakete's kernel for the Pixel/Pixel XL. Thanks for the inspiration, Sakete!)
It will work on Rooted Android 7.1.1 NMF26F ?
AFK269 said:
It will work on Rooted Android 7.1.1 NMF26F ?
Click to expand...
Click to collapse
You'll have to test it and let me know as I'm not using it on a rooted phone
If your root method trips SafetyNet then this kernel is useless to you, as it will only bypass the unlocked bootloader check and not the root check.
Well I tried to install your kernel and it is missing files and will not install. I wish there was a way to just flash the bypass of safety net with any kernel that you wanted to use.
weaselskhs said:
Well I tried to install your kernel and it is missing files and will not install. I wish there was a way to just flash the bypass of safety net with any kernel that you wanted to use.
Click to expand...
Click to collapse
Can you clarify? Did you flash with fastboot? What steps did you use?
Bootloop while installing unpacked .img file using TWRP. PixelROM 7.1.1, SuperSU v2.78 SR2
doggie13_ said:
Bootloop while installing unpacked .img file using TWRP. PixelROM 7.1.1, SuperSU v2.78 SR2
Click to expand...
Click to collapse
I wouldn't expect this kernel to work with custom ROMs.
Well that makes sense as I am also running Pixel Rom 7.1.1 and super su
It'd be super cool if this patch worked with PixelRom
Is there a specific reason this doesn't work with custom ROMs?
19lmyers said:
Is there a specific reason this doesn't work with custom ROMs?
Click to expand...
Click to collapse
Well for starters there is code missing from the stock kernel to work properly with the pixel rom. Which begs the question why you would want to flash the stock kernel on a pixel rom when you can use other custom kernels. I believe that Franco's kernel has the safetynet patch included.
Thanks to share
Hi,
Will this work for 6p?
Thanks
turbo81 said:
Hi,
Will this work for 6p?
Thanks
Click to expand...
Click to collapse
No. It's only for Nexus 5X (Bullhead).
Subbed. I'll be waiting for the N4F26I build. I miss using Android Pay.
Does anyone know if there is or will be a patch for the nexus 6p?
drew_t said:
Does anyone know if there is or will be a patch for the nexus 6p?
Click to expand...
Click to collapse
If you want use Franco.Kernel ... He has already did this. Find it at N6P thread, not here.
apatal said:
Subbed. I'll be waiting for the N4F26I build. I miss using Android Pay.
Click to expand...
Click to collapse
+1
I am waiting for N4F26I build.
Updated OP for N4F26I. Unfortunately, my 5X started bootlooping (hardware issue) so I don't have the device to test it with anymore
Updated for N4F26O.
It has been a long time since a last rooted my Nexus 5 device. Therefore and for some other reasons i flashed a new custom rom from screw'd android.
The lastest official image of 30th april. So now Android 7.2.1 is working very well on my phone. But how can i simply root my android phone
now?
(In early times i used Nexus Root Toolkit but for some reasons this doesn't work i think with this custom rom..., or im not able to do it..)
Hopefully someone who has still a good overview can give me a short explanation.
thx.
Flash Magisk v12.0 in recovery, or just flash supersu.
7.2.1 lol
lol 7.1.2 -> no i got root, flashing supersu zip file.
one question i got information that a new OTA update by LEAN screw'd is available.
There stand with root i can directly update, but i can not get information if data / app will be lost?
Do you know how this would/should be handled?
Are there any news about an official (or unofficial) TWRP for this device? It's out now til October 2019 and I get the feeling there ain't much development for it.
It's rootable by patching the boot.img with magisk but without a custom recovery it's a risky thing because there isn't a nandroid to go back to or even to use TWRP's file manager to delete a faulty module or something like that.
I won't buy a device without any development so are there any devs that are willing to build a custom recovery first and maybe custom ROMs later?
Have the kernel sources been published by Motorola?
Wolfcity said:
Are there any news about an official (or unofficial) TWRP for this device? It's out now til October 2019 and I get the feeling there ain't much development for it.
It's rootable by patching the boot.img with magisk but without a custom recovery it's a risky thing because there isn't a nandroid to go back to or even to use TWRP's file manager to delete a faulty module or something like that.
I won't buy a device without any development so are there any devs that are willing to build a custom recovery first and maybe custom ROMs later?
Have the kernel sources been published by Motorola?
Click to expand...
Click to collapse
Answering myself, there is an unofficial TWRP now:
https://forum.xda-developers.com/mo...covery-unofficial-twrp-recovery-moto-t4059137
Sent from my Moto G5 Plus using XDA Labs