Database Info

Help unlocking bootloader

I am trying to unlock the bootloader of my oneplus one, when using the oneplus one toolbox ive put phone into fastboot and clicked unlock bootloader but it just reboots my phone and does not change anything, ive tried doing fastboot oem unlock through cmd it says its successful but still does not change anything???

i realized that why nothing was changing was because it was already unlocked, now i have flashed supersu but i dont have root access when i open titanium it says that i can't get root access???

Did you install TWRP? You need that as well to get root.

Stop using the toolbox and do things manually, that's probably what's causing your problems. There's a guide in my signature.
Transmitted via Bacon

[Q] Nexus 5 6.0.1 (MMB29Q) not rooting & no SuperSU

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

Question about T-Mobile Root and TWRP

So I've been following this bounty for the LG G5 very closely and I think it's awesome we've achieved Root finally for the LG G5.
I already did the fastboot OEM Unlock but looking all the instructions, I'm starting to get confused.
What is the best order I should proceed in, in order to make sure my phone doesn't get bricked or something if I screw up?
Prior to the LG G5, I had an HTC One M8, I always went in this order:
1) OEM Unlock
2) Unlock Bootloader
3) Custom recovery
4) ROOT
5) Custom ROM
I hope I listed that correctly.
So the only step I have done on my LG G5 is the "fastboot oem unlock"
So does that mean I now have to unlock the Bootloader? If so, where are the resources for that? I have only been able to find the Custom Recovery of TWRP installation instructions, nothing prior to that.
Final question, on this page it says at the top,
WARNING: The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
Click to expand...
Click to collapse
So does that mean I have to root my device first? and if I do that, what if it bricks or gets stuck, then I'm hosed right?
I just need a more clear explanation on how to proceed with this because this is my first LG Root and usually HTC's Rooting methods were a bit more simpler.
Thanks!

When you did fastboot oem unlock that was unlocking the bootloader. Now you simply need to use the tot file you can find in the developer section to get twrp and the use the supersu and dm-verity zips in there and you will be rooted and ape to go from there. No new roms at the moment but you can install xposed and the g4 tweaks box will allow a lot of the custom options you can get in a Rom.

rooted latest version of 8, got FRP error on reboot, fixed. How to get rid of this?

I rooted my s7, latest version of 8.0 United Kingdom (g930fxxu4esae build r16nw.g930fxxs5esf6). I used TWRP and magisk.
All was well until I rebooted, then got the dreaded "custom binary blocked by frp lock". I was able to take the stock rom and install the AP file, and now it's working again except that of course root is gone. I suspect that if I attempt to root again, I will run into the same error on a reboot.
I've done some googling but haven't found anything really reliable sounding about getting around this problem.
EDIT: UPDATE: I've flashed the latest version of BTU on phones 1 and 2. I've successfully rooted phone 1 and it seems to be sticking. Phone 2 I'm still working on, it doesn't have to be rooted though as it's more of a backup for gaming. Thanks again to everyone in this thread for all the good advice and info.

You are going to have to re flash you current firmware unrooted and before you root, enable OEM unlocking in developer options AFTER setting up your google account(you have to use the same google account as you did before), unfortunately there is no way of force enabling OEM unlock with a flashable zip on the s7, well least to my knowledge. FRP lock is googles factory reset protection, which stops people from factory resetting a phone and then just use their google account instead of the one they don't know the password too, and it stops custom binaries like trwp from booting and even a stock binary that has been rooted from booting because it thinks you could be trying to bypass FRP.
Enabling OEM unlocking with disable FRP lock on the device, allowing you to use custom binary and boot normally without the checks.

Viper4060 said:
You are going to have to re flash you current firmware unrooted and before you root, enable OEM unlocking in developer options AFTER setting up your google account(you have to use the same google account as you did before), unfortunately there is no way of force enabling OEM unlock with a flashable zip on the s7, well least to my knowledge. FRP lock is googles factory reset protection, which stops people from factory resetting a phone and then just use their google account instead of the one they don't know the password too, and it stops custom binaries like trwp from booting and even a stock binary that has been rooted from booting because it thinks you could be trying to bypass FRP.
Enabling OEM unlocking with disable FRP lock on the device, allowing you to use custom binary and boot normally without the checks.
Click to expand...
Click to collapse
Correct basically turn FRP lock off it's a pain in the ass.
Also @kettir this is the final release of BTU not the one you have in your post 》》https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXU5ESD2/270504

cooltt said:
Correct basically turn FRP lock off it's a pain in the ass.
Also @kettir this is the final release of BTU not the one you have in your post 》》https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXU5ESD2/270504
Click to expand...
Click to collapse
Thanks for more great advice and info. It appears that now the requirements are:
Download the latest BTU as per your note because I like it better
Flash it to attain a "stock" system.
Go through the minimum setup after reboot and get developer options.
Set up google account
Enable OEM unlocking (and USB debugging of course)
flash TWRP
go into recovery immediately
Use TWRP to flash magisk
go back into download mode immediately
flash only the AP from the stock firmware
And this might, possibly, achieve root with magisk, while keeping the stock bootloader. That is, if I understand what TWRP and magisk are actually doing to the system. I.e., TWRP replaces the system part that handles recovery, while magisk roots the phone without changing the system, so that TWRP is the problem for FRP.

Question about low level of android

Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check) and absolutely no problem, everything is in order.
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !