If I only unlocked the bootloader and installed TWRP, will Safety Net detect it and fail the test?
No
Related
Has anyway found a way to Root the OnePlus One without having to flash a custom recovery with the new 33R OTA?
(yes I didn't check the CM recovery)
*But after I updated to the 33R update I still had root access intact, despite gaining root by boot and not having unlocked the bootloader under 33R. The problem was I did a factory reset and obviously it reflashed the newer bootloader and I lost root access (yes stupid)
This can no longer be done 'fastboot boot twrpimgname.img' with the 33R update ;
Aren't One Plus all about give you the power so why did they go ahead and block boot custom recovery that worked before ??
This is the under 33R OTA =
C:\adb>adb reboot bootloader
C:\adb>fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
downloading 'openrecovery-twrp-2.7.1.1-bacon.img'...
OKAY [ 0.402s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.404s
Seems the have patched being able to boot a custom recovery without unlocking the boot loader
Yes I realized the the 'Update CM recovery' option but not after I updated to 33R (my oneplus was rooted without having to unlock the boot loader)
I did do a Nandriod backup of course before the 33R OTA.
The nandriod backup is rooted without having to unlock the bootloader via this ' fastboot boot twrpimgname.img '
Is their no way yet to boot a custom recovery without unlocking the boot loader ? Does one have to wait for a update twrp recovery to boot not flash ?
The question is: WHY?
the locked bootloader is locked because it allows only booting a signed recovery, if you use a custom-unsigned-by-manufacturer recovery there is no sense in keeping the bootloader locked.....
OnePlus knows that 90% of the users are rooting and unlocking, so there is no sense to keep it unlocked.... in case of necessity, you can relock the bootloader !!!
Anyway, you wrote in the wrong section !!!
mcbyte_it said:
The question is: WHY?
the locked bootloader is locked because it allows only booting a signed recovery, if you use a custom-unsigned-by-manufacturer recovery there is no sense in keeping the bootloader locked.....
OnePlus knows that 90% of the users are rooting and unlocking, so there is no sense to keep it unlocked.... in case of necessity, you can relock the bootloader !!!
Anyway, you wrote in the wrong section !!!
Click to expand...
Click to collapse
What area is the right one, my bad.
Also asking if their is a way around the 33R to boot custom recovery
Why though?? You don't need to boot to a custom recovery. Just unlock the bootloader, it doesn't void your warranty. You have absolutely nothing to lose by doing it, and absolutely nothing to gain by leaving it locked.
Transmitted via Bacon
timmaaa said:
Why though?? You don't need to boot to a custom recovery. Just unlock the bootloader, it doesn't void your warranty. You have absolutely nothing to lose by doing it, and absolutely nothing to gain by leaving it locked.
Transmitted via Bacon
Click to expand...
Click to collapse
Just an innocent wipe... and he only wants root.
Yeah and the right way to get root is to unlock your bootloader, install TWRP, and flash SuperSU.
Back stuff up, unlock bootloader, restore stuff. It's stupid to try to 'hack' into the world's easiest phone to root.
Transmitted via Bacon
go back to 25R an root it
then untick the update recovery in develop settings
install recovery twrp
now remember to have the update recovery
install the 33R
with twrp an in the end choose fix permissions
now u can download from phone it will come up to fully root
just hit fully root an install with twrp
it will download root
an restart in recovery wait fore it to finnish an u are now rooted on 33R
Have you tried towelroot? https://towelroot.com/
-fluffy- said:
go back to 25R an root it
then untick the update recovery in develop settings
install recovery twrp
now remember to have the update recovery
install the 33R
with twrp an in the end choose fix permissions
now u can download from phone it will come up to fully root
just hit fully root an install with twrp
it will download root
an restart in recovery wait fore it to finnish an u are now rooted on 33R
Click to expand...
Click to collapse
How's he meant to go back without an unlocked bootloader??
Transmitted via Bacon
THEEEK METHODS TO ROOT YOUR DEVICE
1. vulnerable apps like kingroot(recommended), vroot/iroot, framaroot, towelroot
2. By odin flashing on Samsung and nexus
3 By unlocking bootloader and installing custom recovery then flashing super su beta.zip
........to be continue
I’m currently using NRT 2.1.4 and i’ve tried rooting my device a few times now and it never installs SuperSU and I can’t boot into TWRP as it shows the android laying down w/ the red exclamation, which is odd since it does go into TWRP during the process of rooting...
But I do not have TWRP installed because of the NRT process
Steps I have taken:
Unlock Bootloader
Flash stock + Unroot (Latest version MMB29Q)
Root & Custom Recovery
When I do the root step, it boots into bootloader, goes in a temporary twrp, then launches normally and says to update SuperSU binaries and check busybox, but neither SuperSU or busybox get added into my app list
It also sometimes says ADB recovery device not found on some attempts..
Is there any way for me to root my Nexus 5?
I have repeatedly flashed the stock with the newest version and still haven’t been able to root.
I have tried relocking the bootloader and unlocking it, but upon unlocking it again, it says that it's already unlocked...?
(Bootloader shows LOCK STATE - unlocked when trying to relock bootloader)
I have been able to root my Nexus 7 2013, but can't seem to get my Nexus 5 to work..
How about flashing TWRP via fastboot, then use the volume/power button to immediately boot into TWRP, and then flash supersu?
The bootloader will not relock?
audit13 said:
How about flashing TWRP via fastboot, then use the volume/power button to immediately boot into TWRP, and then flash supersu?
The bootloader will not relock?
Click to expand...
Click to collapse
Yeah, I don't know why, when I try to OEM lock and unlock it says it's already unlocked, which is odd.
But I did the TWRP via fastboot and installed SuperSU that way, thanks.
Glad it worked for your phone.
Help me to unlock bootloader and root
Hello Guys, I want to unlock the bootloader on my N5. My phone is in Android Ver 6.0.2 with Feb patch(Build Number MMB29Q). Please help me in doing so. Also i would root my device, i would prefer TWRP. Please anybody...
Boot the phone into fastboot, connect the phone to your computer, and use fastboot commands to unlock the bootloader, flash TWRP, and flash supersu for root.
Unlocking the bootloader will wipe the phone.
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Hello! I have an unlocked bootloader on my Z3 and am currently on 5.0.2 (.28) Lollipop. I rooted it with Kingo Root. I am on the step where i am trying to flash a recovery. I have tried manually to flash a twrp.img via fastboot, via NUT's automatic installer, and both don't seem to work. Although they push the files on the phone and say success, I cannot boot into recovery, it flashes red for 2 seconds and skips to OS. I tried also downgrading to 4.4, but giefroot fails to work for some reason. What am I doing wrong?
flash FOTA recovery!
So I recently found a few articles that say it's possible to install Magisk w/o a root or custom recovery.
Example:
https://forum.xda-developers.com/lg-g6/how-to/guide-insatll-magisk-root-recovery-t3900475?&cf=1
I also happen to have a Samsung Note Pro 12.2 (905v) that has a Verizon locked bootloader.
I am trying to use this method of installing Magisk on it, however I can't get the Adb to recognize the tablet. So my questions are,
Does the Verizon lock down the ability to connect via ADB?
Has anyone successfully installed Magisk in the above method on a Samsung Verizon device? and of so how?
Bonus Question(s): is there a way to wipe the entire tablet and bootloader and start from a blank motherboard without killing it?
Or
Can you boot from SD card?[/SIZE]
Sorry, I miss read the guides I was reading. (ADHD excitement/rabbit hole issues). Can't install Magisk w/o unlocked bootloader