[Q]G930T finally rooted! But still secureboot locked... - T-Mobile Samsung Galaxy S7 Questions & Answers

I have finally rooted G930T but...because of the secureboot i still cannot do anything else...
Is it possible to disable secureboot now that i am rooted???

Zizzy2020 said:
I have finally rooted G930T but...because of the secureboot i still cannot do anything else...
Is it possible to disable secureboot now that i am rooted???
Click to expand...
Click to collapse
Unfortunately the bootloader is still locked, therefore you can't flash a custom recovery in order to disable encryption and DMV.
Until a real bootloader unlock or some other bypass is found, the only solution is to flash a boot root kernel (boot.img), then run the root.bat script to install SuperSU manager.

Related

Does SafetyNet detect bootloader unlock? How about SuperSU systemless root?

I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
NegativeOne said:
I am on the Google variant. I'm curious whether simply unlocking the bootloader will prevent me from using Android Pay (and similarly protected apps). And same question for SuperSU systemless root?
As a bonus, if I were to unlock, root, modify a file (like hosts), then unroot and relock, would it complain?
Click to expand...
Click to collapse
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
ndarkside93 said:
If you modify the system and relock the bootloader, you risk bricking the device entirely, if it won't accept fastboot commands
Click to expand...
Click to collapse
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Sent from my sailfish using XDA Labs
nednednerb said:
First question, I think on some firmware, custom Kernel with root is allowing Android Pay for some users on some carriers. I wouldn't universalize, you have to try.
However, only unlocking bootloadet doesn't work, but in addition a custom kernel can fix what breaks is needed.
Second question:
EXACTLY: the bootloader detects changes in the system partition away from pure stock, so if you change things, that signals "corruption" to the bootlader so it will PREVENT boot and as ndarkside says, RISK OF BRICK
Click to expand...
Click to collapse
Very true, but on the pixel with the November update, safety net checks for bootloader unlock, but I think Franco kernel can hide it to pass the check, if there is no root.

Xposed help

First of all didn't realize I posted this in the wrong area last time, my bad.
Device SMG930V
ROOT yes
ROOT method ENG BAT AP then root script
Android 7.0
Security patch latest
Question
Is there any possible way to install xposed to hide root so I can play south park? I've checked a root method post that claims you can but the root method sent my phone in a boot loop, a very fast loop.. So the rest seems fishy, can anyone confirm a xposed installation for my device? Please and thank you!
Xposed modifies the boot image which requires an unlocked bootloader, the G930V is snapdragon and has the bootloader locked, so you can't put Xposed on the 930V
Xposed also trips safetynet worse than root, it wouldn't hide anything.
You can check if Magisk Hide can be installed on snapdragon models, but from memory that too also needs an unlocked bootloader.
Crap, so is there a successful way to hide the root from certain apps yet? Are hands are tied if a game detects root
Beanvee7 said:
Xposed modifies the boot image which requires an unlocked bootloader, the G930V is snapdragon and has the bootloader locked, so you can't put Xposed on the 930V
Xposed also trips safetynet worse than root, it wouldn't hide anything.
You can check if Magisk Hide can be installed on snapdragon models, but from memory that too also needs an unlocked bootloader.
Click to expand...
Click to collapse

Can't flash recovery with FRP unlocked

I just updated my Honor8 (FRD-L04) to OTA B389 by restoring stock Recovery and using the built-in system updater. But now when I try to flash TWRP back to recovery, I get that damned "FAILED (remote: Command not allowed)" error.
Bootloader is unlocked.
FRP is unlocked.
I can toggle FRP lock on/off in dev options, doesn't seem to make any difference. Did Huawei screw the pooch with their FRP implementation?
relock the BL and unlock it again,
Rommco05 said:
fastboot recognize phone?
Click to expand...
Click to collapse
Fastboot always shows correct phone/state info.
shashank1320 said:
relock the BL and unlock it again,
Click to expand...
Click to collapse
Which means the phone will wipe itself, which I was really hoping to avoid for an OTA update...
While I'm sure you're right, it really seems like something is wrong with the system if that is what's required. Is this a Huawei-specific issue, or are all phones with FRP like that now?
Florp said:
Which means the phone will wipe itself, which I was really hoping to avoid for an OTA update...
While I'm sure you're right, it really seems like something is wrong with the system if that is what's required. Is this a Huawei-specific issue, or are all phones with FRP like that now?
Click to expand...
Click to collapse
If FRP is locked, you can flash anything but in your case it is unlocked still you cant..hoping relocking and unlocking BL should give you access to OEM unlock option in developer settings and thus unlock your FRP as well.

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).
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 !
oops I created another thread by editing my old one. Sorry.
isman77 said:
oops I created another thread by editing my old one. Sorry.
Click to expand...
Click to collapse
Hi
You are going to be flogged! [emoji6]
Envoyé de mon GM1913 en utilisant Tapatalk
isman77 said:
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).
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 !
Click to expand...
Click to collapse
Just use MSMtool to reflash your phone. The links are in the guides section
isman77 said:
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).
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 !
Click to expand...
Click to collapse
From what I've seen from a few people on here, nolimits doesn't really do anything useful. Debloat a few apps but everything else it doesn't isn't that good, apparently. I used it before and thought it was good. But I'm pretty sure I get better battery and performance on stock with a custom kernel and used something else to debloat.
Also, as some else suggested, MSM tool is great to get back to stock with everything proper.
Thank you for your answers @Jinsuke32 and @GeekMcLeod
I would like to know if you can use MSM Tool with a locked bootloader and does this tool erase all data during flash?
isman77 said:
Thank you for your answers @Jinsuke32 and @GeekMcLeod
I would like to know if you can use MSM Tool with a locked bootloader and does this tool erase all data during flash?
Click to expand...
Click to collapse
Not sure if it can be used with locked bootloader. But it erases everything.
GeekMcLeod said:
Not sure if it can be used with locked bootloader. But it erases everything.
Click to expand...
Click to collapse
Ok, thanks for your quick response.

How to unlock Samsung A01

I need some help unlocking the bootloader on my Samsung A01. The instructions say to enable developer mode — basic stuff — and then enable USB debugging and OEM Unlocking. You guessed it: the OEM Unlock option just ain't there. I tried the trick with chaging the date and checking for updates, but it didn't help. Please, can anyone give me some help that will actually fix the problem? I just want to root this damn thing.
To root phone's Android unlocking phone's bootloader is NOT required.
xXx yYy said:
To root phone's Android unlocking phone's bootloader is NOT required.
Click to expand...
Click to collapse
Ok then. How do I do it? All the other guides tell me I have to. And how would I install TWRP, which I definitely want to do?
Every guide I look at tells me I have to unlock the bootloader first.
You do NOT need to root your phone's Android to install TWRP - a custom recovery, but you will need to unlock the bootloader. Take note that Android OS has nothing to do with phone's bootloader, that Android OS gets launched by bootloader if device didn't get tampered.
xXx yYy said:
You do NOT need to root your phone's Android to install TWRP - a custom recovery, but you will need to unlock the bootloader. Take note that Android OS has nothing to do with phone's bootloader, that Android OS gets launched by bootloader if device didn't get tampered.
Click to expand...
Click to collapse
Ok, how do I just root for now? I want Magisk. I'm trying to install it with ADB, but I'm getting Error 21.
Furthermore, how do I unlock the bootloader when the system doesn't want to give me the OEM Unlocking option?
You do NOT need to root your phone's Android before to install Magisk: you typically root Android OS by means of Magisk.
You install Magisk via TWRP what requires an unlocked bootloader. You unlock a phone's bootloader via FASTBOOT tool what requires OEM Unlock option got activated before applying the bootloader-unlock.
xXx yYy said:
You do NOT need to root your phone's Android before to install Magisk: you typically root Android OS by means of Magisk.
You install Magisk via TWRP what requires an unlocked bootloader. You unlock a phone's bootloader via FASTBOOT tool what requires OEM Unlock option got activated before applying the bootloader-unlock.
Click to expand...
Click to collapse
So basically until I can use the OEM Unlock option, I can't do a darn thing, can I?
So how do I get it?
I'm going to ask for help on this again. I've been around the forum, I've looked for anything I could find, and I'm still no closer to getting this thing solved.

Categories

Resources