Related
Just bought S6 G920T so i'm still new to all the bootloader security issues, i flashed TWRP yesterday and got stuck on bootloop after that. Bootloop was fixed after flashing Twisted v4 rom. I set up everything including fingerprint and when i restarted the phone it gave the error "Custom Binary blocked by FRP".
Currently i am trying to revive the phone, about to flash 6.0.1 PK5 firmware.
Now i have a few questions, please answer whichever you can:
- In case flashing 6.0.1 fails the next solution is to flash 7.0 firmware, is it possible to flash Twisted v4 (6.0.1) after that? Or i have to go with Nougat roms only?
- What should i know to avoid ever having another FRP lock again with a custom rom? Dont set up fingerprint? Or enable OEM unlock option is enough?
- Any way to permanently disable this Custom Binary lock security feature?
I want to use Twisted v4 with root and fingerprint if possible (dont need Samsung Pay). Sorry if this is a repost, i tried gathering whatever info i could on this issue but still confused on these questions. Thanks in advance! :highfive:
EDIT: Looks like this forum is dead, so i'll just answer my own questions from what i learned today with first hand experience for the next confused soul.
- Flashing 6.0.1 PK5 firmware fixed the FRP lock issue (if you were on newer firmware you will need to flash that one or higher)
- Enable Developer Options by clicking Build Number a few times, in Developer Options allow OEM unlock to avoid "Custom Binary FRP lock"
Now i am using Twisted v4 with root and fingerprint enabled, TWRP is installed and no issues till now.
If root/TWRP is what you're after, is the Tmobile version the friendliest S6 to get?
RunNgun42 said:
If root/TWRP is what you're after, is the Tmobile version the friendliest S6 to get?
Click to expand...
Click to collapse
Yes. The TMobile Galaxy S6 is the last Galaxy model with an unlocked bootloader.
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
killerxda said:
Just bought S6 G920T so i'm still new to all the bootloader security issues, i flashed TWRP yesterday and got stuck on bootloop after that. Bootloop was fixed after flashing Twisted v4 rom. I set up everything including fingerprint and when i restarted the phone it gave the error "Custom Binary blocked by FRP".
Currently i am trying to revive the phone, about to flash 6.0.1 PK5 firmware.
Now i have a few questions, please answer whichever you can:
- In case flashing 6.0.1 fails the next solution is to flash 7.0 firmware, is it possible to flash Twisted v4 (6.0.1) after that? Or i have to go with Nougat roms only?
- What should i know to avoid ever having another FRP lock again with a custom rom? Dont set up fingerprint? Or enable OEM unlock option is enough?
- Any way to permanently disable this Custom Binary lock security feature?
I want to use Twisted v4 with root and fingerprint if possible (dont need Samsung Pay). Sorry if this is a repost, i tried gathering whatever info i could on this issue but still confused on these questions. Thanks in advance! :highfive:
EDIT: Looks like this forum is dead, so i'll just answer my own questions from what i learned today with first hand experience for the next confused soul.
- Flashing 6.0.1 PK5 firmware fixed the FRP lock issue (if you were on newer firmware you will need to flash that one or higher)
- Enable Developer Options by clicking Build Number a few times, in Developer Options allow OEM unlock to avoid "Custom Binary FRP lock"
Now i am using Twisted v4 with root and fingerprint enabled, TWRP is installed and no issues till now.
Click to expand...
Click to collapse
Sorry I missed your post man. I am still rocking my S6 with Twisted Nougat so I could have helped ya out. I do not use the fingerprint option however.
cwhiatt said:
Sorry I missed your post man. I am still rocking my S6 with Twisted Nougat so I could have helped ya out. I do not use the fingerprint option however.
Click to expand...
Click to collapse
Its ok bro, experience is the best teacher
don’t mean to hijack, but
Saw this now after I posted and you’re saying it’s dead (which sucks, but oh well)
Which version were you on before flashing entirely?
Any chance you could lemme know what to google to grab the 6.01 fw? I’ll try that out I guess.
I’m having frp lock and can’t even flash anything it seems, but I’ll try anything.
killerxda said:
Just bought S6 G920T so i'm still new to all the bootloader security issues, i flashed TWRP yesterday and got stuck on bootloop after that. Bootloop was fixed after flashing Twisted v4 rom. I set up everything including fingerprint and when i restarted the phone it gave the error "Custom Binary blocked by FRP".
Currently i am trying to revive the phone, about to flash 6.0.1 PK5 firmware.
Now i have a few questions, please answer whichever you can:
- In case flashing 6.0.1 fails the next solution is to flash 7.0 firmware, is it possible to flash Twisted v4 (6.0.1) after that? Or i have to go with Nougat roms only?
- What should i know to avoid ever having another FRP lock again with a custom rom? Dont set up fingerprint? Or enable OEM unlock option is enough?
- Any way to permanently disable this Custom Binary lock security feature?
I want to use Twisted v4 with root and fingerprint if possible (dont need Samsung Pay). Sorry if this is a repost, i tried gathering whatever info i could on this issue but still confused on these questions. Thanks in advance! :highfive:
EDIT: Looks like this forum is dead, so i'll just answer my own questions from what i learned today with first hand experience for the next confused soul.
- Flashing 6.0.1 PK5 firmware fixed the FRP lock issue (if you were on newer firmware you will need to flash that one or higher)
- Enable Developer Options by clicking Build Number a few times, in Developer Options allow OEM unlock to avoid "Custom Binary FRP lock"
Now i am using Twisted v4 with root and fingerprint enabled, TWRP is installed and no issues till now.
Click to expand...
Click to collapse
p4cm4n88 said:
Saw this now after I posted and you’re saying it’s dead (which sucks, but oh well)
Which version were you on before flashing entirely?
Any chance you could lemme know what to google to grab the 6.01 fw? I’ll try that out I guess.
I’m having frp lock and can’t even flash anything it seems, but I’ll try anything.
Click to expand...
Click to collapse
You can download the PK5 Firmware here > https://www.sammobile.com/firmwares/galaxy-s6/SM-G920T/TMB/confirm/G920TUVU5EPK5/113173/
OR...you can try to use Samsung Kies or Samsung Smartswitch to restore your phone back to stock. You'll need the model and serial number which you can get by booting to Download mode and then pressing the home button. Once you get back up and running on stock firmware you can enable developer options then USB debugging and OEM unlock.
Once you have those taken care of you can root, install TWRP, Xposed, and flash Twisted Nougat.
hate to be annoying, but is there a better place to find this rather than a place that will take 12 hours to dl?
cwhiatt said:
You can download the PK5 Firmware here >
OR...you can try to use Samsung Kies or Samsung Smartswitch to restore your phone back to stock. You'll need the model and serial number which you can get by booting to Download mode and then pressing the home button. Once you get back up and running on stock firmware you can enable developer options then USB debugging and OEM unlock.
Once you have those taken care of you can root, install TWRP, Xposed, and flash Twisted Nougat.
Click to expand...
Click to collapse
p4cm4n88 said:
hate to be annoying, but is there a better place to find this rather than a place that will take 12 hours to dl?
Click to expand...
Click to collapse
Like I said u can try using Kies or Smartswitch. I have used Kies successfully on a handful of S6s without issue. Otherwise I could probably download it tomorrow at work and send you a link.
Sent from my [device_name] using XDA-Developers Legacy app
No worries. I’ll do it overnight. Thanks
Also Odin 3.10.6 started being able to flash where 3.12.? Failed.
I got the baseband you have in your sig I just installed. Still have FRP tho and was told to wait 72 hours.
Mean time my fiancé just bought an iPhone instead.
cwhiatt said:
Like I said u can try using Kies or Smartswitch. I have used Kies successfully on a handful of S6s without issue. Otherwise I could probably download it tomorrow at work and send you a link.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
p4cm4n88 said:
No worries. I’ll do it overnight. Thanks
Also Odin 3.10.6 started being able to flash where 3.12.? Failed.
I got the baseband you have in your sig I just installed. Still have FRP tho and was told to wait 72 hours.
Mean time my fiancé just bought an iPhone instead.
Click to expand...
Click to collapse
Been away from xda for a while so didnt see your post. Instead of sammobile you can usuallly find firmware on androidfilehost. If you were on 6.0.1 before then you should be able to flash this file:
https://androidfilehost.com/?fid=745425885120707260
if that doesnt work then 7.0 file should work (basically you need the same version that was flashed or updated version, older versions not allowed):
https://androidfilehost.com/?fid=961840155545571517
ONLY FOR Qualcomm SM-G9650
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This will trip knox to 0x1, your phones warranty will be voided, flash at your own risk. Also, this process will wipe your personal data!
HOW TO INSTALL:
0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled. Also make sure you run CROM from the galaxy apps store to unlock the bootloader.
1. Boot into download mode by pressing: bixby, volume down and power
2. Download the latest Odin version, open it
3. Download the recovery file from below and put it into the AP tab
4. Untick "auto reboot" in odin and flash the file
5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop).
6. In order to fully and properly root, you will need to flash my kernel found here and flash Magisk.
7. To disable encryption you need to flash this RMM_patch+forceencrypt_remover.zip for pie or multidisabler.zip and forceencrypt_disabler_q.zip for Android 10 and format data. (can opt out of the forceencrypt_disabler if you want but internal storage will be inaccessable)
DOWNLOAD:
https://twrp.me/samsung/samsunggalaxys9plusqcom.html
BUGS:
- Samsung encryption is NOT supported
DONATION:
Via PayPal
https://www.paypal.me/klabit87
Contributors
klabit87
travis
Source Code: https://github.com/klabit87/twrp_android_device_samsung_star2qltechn
Version Information
Status: Stable
Current Stable Version: 3.3.1-1
Stable Release Date: 5-22-2019
Sent you a donation to your PayPal.
You have no idea how much pain and suffering you have saved me. And the fact that you don't even have a device makes it all the more awesome. Thank you!
I already have OEM unlock, but when aim doing your procedure, Odin screen show a message lakie " i cant flash unofficial binaries"
partcyborg said:
Sent you a donation to your PayPal.
You have no idea how much pain and suffering you have saved me. And the fact that you don't even have a device makes it all the more awesome. Thank you!
Click to expand...
Click to collapse
I saw that and seriously thank you so much!! There will be a Qualcomm section opening soon for Snapdragon variants. I have SM-9600 already in there for TWRP. I need to update it I know. I will get to it this week. I also need to get the devices officially supported and forked over to TEAMWIN that will get done too when I can get the time.
Best regards,
Travis82
fe.floresy said:
I already have OEM unlock, but when aim doing your procedure, Odin screen show a message lakie " i cant flash unofficial binaries"
Click to expand...
Click to collapse
You might haven't installed the CROM app for unlocking.
Amijaz said:
You might haven't installed the CROM app for unlocking.
Click to expand...
Click to collapse
I have the app, and shows me an error when i try to unlock.
fe.floresy said:
I have the app, and shows me an error when i try to unlock.
Click to expand...
Click to collapse
Ohh, I don't know what's the exact problem. However, could you please try once again with the Samsung account removed?
Amijaz said:
Ohh, I don't know what's the exact problem. However, could you please try once again with the Samsung account removed?
Click to expand...
Click to collapse
the same problem.... in download mode, it apear a message... only official release binaries are allowed to be flashed
I have a doubt..
Can I install this in a SM-G9650 (star2qltezh) ?
fe.floresy said:
the same problem.... in download mode, it apear a message... only official release binaries are allowed to be flashed
Click to expand...
Click to collapse
Buddy I meant, were you able to disable the CROM lock after removing the Samsung Account. Without getting the device unlocked by CROM service app you wouldn't be able to flash custom binaries.
Thanks
Greetings, this are AWESOME NEWS!!!
I have a Mexican S9+ (From Movistar, SM-G9650) and I already OEM unlocked the phone: https://www.dropbox.com/s/ts78hdnp4j9jffu/1OEMUNLOCK.jpg?dl=0
When I run CROM, I get the following error: https://www.dropbox.com/s/ftrpjn0uj9w9dew/1CROMERROR.jpg?dl=0
I tried disabling my Samsung Account on the device and I still get the same error, what else can I try in order to succesfully flash TWRP?
Keep up this awesome work, travis, you are the best!!! =D
Edit: This is the "Download Mode" status:
RPMB fuse blown
RPMB PROVISIONED
CURRENT BINARY : Samsung Official
SYSTEM STATUS : Official
FRP LOCK : OFF
OEM LOCK : OFF
WARRANTY VOID : 0x0
RP SWREV : B2(2,2,2,2,2) K2 S2
SECURE DOWNLOAD : ENABLED
DID : 20208BF42A92AB11
Bump. D=
Kimbaroth said:
Bump. D=
Click to expand...
Click to collapse
Edit: I think I have the answer...
I can't find the CROM Service in the Galaxy App Store on my firmware (ZTO, Brazil). Even tho I'm OEM unlocked and I installed the CROM Service apk, I still have that issue, so the main question here is:
On what Galaxy App Store the CROM Service is available to download? I believe that if I install that firmware and download the CROM Service directly from the original Galaxy App Store, the program will succesfully unlock my phone.
Can anyone please help me with that question???
Best regards!
Kimbaroth said:
Greetings, this are AWESOME NEWS!!!
I have a Mexican S9+ (From Movistar, SM-G9650) and I already OEM unlocked the phone: https://www.dropbox.com/s/ts78hdnp4j9jffu/1OEMUNLOCK.jpg?dl=0
When I run CROM, I get the following error: https://www.dropbox.com/s/ftrpjn0uj9w9dew/1CROMERROR.jpg?dl=0
I tried disabling my Samsung Account on the device and I still get the same error, what else can I try in order to succesfully flash TWRP?
Keep up this awesome work, travis, you are the best!!! =D
Edit: This is the "Download Mode" status:
RPMB fuse blown
RPMB PROVISIONED
CURRENT BINARY : Samsung Official
SYSTEM STATUS : Official
FRP LOCK : OFF
OEM LOCK : OFF
WARRANTY VOID : 0x0
RP SWREV : B2(2,2,2,2,2) K2 S2
SECURE DOWNLOAD : ENABLED
DID : 20208BF42A92AB11
Click to expand...
Click to collapse
Hi Kimbaroth,
I think I'm in the same situation.
CROM give me an error.
Dev Options > OEM unlock (restarted and factory reseted the phone after that).
Now I need to wait one week?
(soory for my bad english)
travis82 said:
I saw that and seriously thank you so much!! There will be a Qualcomm section opening soon for Snapdragon variants. I have SM-9600 already in there for TWRP. I need to update it I know. I will get to it this week. I also need to get the devices officially supported and forked over to TEAMWIN that will get done too when I can get the time.
Best regards,
Travis82
Click to expand...
Click to collapse
That is great news. Looking forward to it
Is adb still not working in this TWRP version? It does not seem to work for me
marcelo-cps said:
Hi Kimbaroth,
I think I'm in the same situation.
CROM give me an error.
Dev Options > OEM unlock (restarted and factory reseted the phone after that).
Now I need to wait one week?
(soory for my bad english)
Click to expand...
Click to collapse
I believe your device is already OEM unlocked, the only difference is that when the option pops again, it will show the option as unlocked.
We need a fix for the CROM Service unlocker, I really need to fix this issue. If you find something, please let us know.
Best regards!
Kimbaroth said:
I believe your device is already OEM unlocked, the only difference is that when the option pops again, it will show the option as unlocked.
We need a fix for the CROM Service unlocker, I really need to fix this issue. If you find something, please let us know.
Best regards!
Click to expand...
Click to collapse
I'm in the same boat, OEM Unlocked, but CROM does not work, it just fails. I do not know if we have to wait until we see the "OEM Unlock" in developer's options and them we can run CROM.
MCR31 said:
I'm in the same boat, OEM Unlocked, but CROM does not work, it just fails. I do not know if we have to wait until we see the "OEM Unlock" in developer's options and them we can run CROM.
Click to expand...
Click to collapse
If you check my post above, you can confirm that "that" doesn't affect the CROM Service at all: https://www.dropbox.com/s/ts78hdnp4j9jffu/1OEMUNLOCK.jpg?dl=0
As I stated, I believe that the CROM Service only work if you download it directly from the Samsung App Store (and not just install the APK that is posted here).
The CROM Service app is not listed at least in my App Store (As I said, I'm currently using the ZTO firmware), so maaaaaaaybe if we flash another region firmware, it will work! The real question is... what firmware do we install??? CHC??? (Open China).
Please help ussssssssss!!!
Kimbaroth said:
If you check my post above, you can confirm that "that" doesn't affect the CROM Service at all: https://www.dropbox.com/s/ts78hdnp4j9jffu/1OEMUNLOCK.jpg?dl=0
As I stated, I believe that the CROM Service only work if you download it directly from the Samsung App Store (and not just install the APK that is posted here).
The CROM Service app is not listed at least in my App Store (As I said, I'm currently using the ZTO firmware), so maaaaaaaybe if we flash another region firmware, it will work! The real question is... what firmware do we install??? CHC??? (Open China).
Please help ussssssssss!!!
Click to expand...
Click to collapse
I think we need Chinese BT....
I red that CROM only works on chinese samsungs... so, maybe we need to install it.
https://forum.xda-developers.com/showpost.php?p=74419608&postcount=25
MCR31 said:
I'm in the same boat, OEM Unlocked, but CROM does not work, it just fails. I do not know if we have to wait until we see the "OEM Unlock" in developer's options and them we can run CROM.
Click to expand...
Click to collapse
MCR31 said:
I think we need Chinese BT....
I red that CROM only works on chinese samsungs... so, maybe we need to install it.
https://forum.xda-developers.com/showpost.php?p=74419608&postcount=25
Click to expand...
Click to collapse
So, flashing a chinese firmware will not fix it, right? D=
ONLY FOR Qualcomm SM-G9600
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This will trip knox to 0x1, your phones warranty will be voided, flash at your own risk. Also, this process will wipe your personal data!
HOW TO INSTALL:
0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled. Also make sure you run CROM from the galaxy apps store to unlock the bootloader.
1. Boot into download mode by pressing: bixby, volume down and power
2. Download the latest Odin version, open it
3. Download the recovery file from below and put it into the AP tab
4. Untick "auto reboot" in odin and flash the file
5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop).
6. In order to fully and properly root, you will need to flash my kernel found here and flash Magisk.
7. To disable encryption you need to flash this RMM_patch+forceencrypt_remover.zip for pie or multidisabler.zip and forceencrypt_disabler_q.zip for Android 10 and format data. (can opt out of the forceencrypt_disabler if you want but internal storage will be inaccessable)
DOWNLOAD:
https://twrp.me/samsung/samsunggalaxys9qcom.html
BUGS:
- Samsung encryption is NOT supported
DONATION:
Via PayPal
https://www.paypal.me/klabit87
Contributors
klabit87
Source Code: https://github.com/klabit87/twrp_android_device_samsung_starqltechn
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 5-22-2019
Good job, as always you do high quality projects.
With GPU prices increasing exponentially over the past few months, it’s been hard to price out a good phone. This particular phone took us nearly a year to see; getting all the parts together was a challenge. (TK, our video producer, delivered the last piece of the puzzle after the Consumer Electronics Show in January.)
Our goal was to show what a decent budget can get you in an Samsung Galaxy S9 Plus, and what kind of performance you can expect from it. Thanks to Travis, Samsung and XDA, we were able to do just that.
Cheers,
Cricrocra.
solid thank you,
work on S9 9600 snapdragon "128gb" ? "C9600ZCU1ARBE" ?
Please Test this new build (June 14th 2018) HKT. https://github.com/travismills82/tw...n/raw/master/twrp-3.2.1-0-starqltechn.img.tar
alittle off topic, but I still dont have OEM Unlock option in Dev mode ive had the s9 more than 7 days. any ideas on what's wrong with that?
So is there no hope for usa unlock?
kushman said:
So is there no hope for usa unlock?
Click to expand...
Click to collapse
USA Models are never bootloader unlockable for S7/8/9 so nope. ONLY SM-G9650 and SM-G9600 are bootloader unlockable models for snapdragon S9/+. Amazon is your friend or newegg.
Where can I find CROM? Can't find it in the Galaxy apps store.
travis82 said:
USA Models are never bootloader unlockable for S7/8/9 so nope. ONLY SM-G9650 and SM-G9600 are bootloader unlockable models for snapdragon S9/+. Amazon is your friend or newegg.
Click to expand...
Click to collapse
Can we possibly Odin a sd stock from another company that's has oem unlock option? Is there a way to get hotspot that what I'm looking for. Is there a way to to about how we've seen for vzw where its stock rooted and inject three odin I mainly just need hotspot and bloat removed that is it any idea how to do so
i have OEM onlock and CROM service, but it doesnt work. I delete my samsung account too, but i have the same error.
help!
Thanks bro!!!!
Thanks for this amazing dev work @travis82
You mentioned the stock kernel but I am confused where to find it. I looked at the threads you have started and found out the combo firmware thread. Do I have to download the kernel from that thread and do I have to extract the img file and then use it? Or am I missing something here. I'm in a bit of a pickle here with my device right now and your reply will help me a lot. Thanks!
droidextra said:
Thanks for this amazing dev work @travis82
You mentioned the stock kernel but I am confused where to find it. I looked at the threads you have started and found out the combo firmware thread. Do I have to download the kernel from that thread and do I have to extract the img file and then use it? Or am I missing something here. I'm in a bit of a pickle here with my device right now and your reply will help me a lot. Thanks!
Click to expand...
Click to collapse
Stock kernel is included in the rom naturally.
travis82 said:
Stock kernel is included in the rom naturally.
Click to expand...
Click to collapse
Okay, my bad
I meant to ask about the stock patched kernel.
fe.floresy said:
i have OEM onlock and CROM service, but it doesnt work. I delete my samsung account too, but i have the same error.
help!
Click to expand...
Click to collapse
I have the same prob, I just activated the OEM unlock, my phone wype my data. Now I want to run CROM, but it fails so, no Idea.....
MCR31 said:
I have the same prob, I just activated the OEM unlock, my phone wype my data. Now I want to run CROM, but it fails so, no Idea.....
Click to expand...
Click to collapse
Well, I just waited to see the "OEM Unlock" Bootloader on the developer options, and I skept the CROM app, and on Odim I just Installed TWRP without any issues.
The prob was when I boot into TWRP and tried to install the custom kernel, TWRP couldn't see my internal storage just tell me "0Mbs" I do not have an extarnal SD card, so I couldn't install the kernel, I restarted the phone with a Data error, so I just format data and back to normal state. I have an 9600 Latin America Version, and I didn't need the CROM apk. Maybe is there a way to fix TWRP to "see" the internal storage.
Bear in mind, this is TWRP 3.2.1-0 and it is so slow that is barely usable
How enable OEM Unlock ? Qualcomm SM-G9600
How enable OEM Unlock ? Qualcomm SM-G9600
MCR31 said:
I have the same prob, I just activated the OEM unlock, my phone wype my data. Now I want to run CROM, but it fails so, no Idea.....
Click to expand...
Click to collapse
adolfomcd said:
How enable OEM Unlock ? Qualcomm SM-G9600
Click to expand...
Click to collapse
you just activate developer option, and after 7 days using your phone, you will see inside developer options the "OEM Unlock" option, just activate it, your phone will wipe all your data partions, and after it boots, you just wait 7 days more, when you see the option "OEM Unlock" activated in developers options, you jusr run odin and install recovery, you do not need CROM (If you phone is latin america version), if it's china, just run CROM.
I read through quite a few post here to get everything sorted out and in order to save every one some time here is a summary of all the info I have gathered so far, and my way to thank the forum for offering me so many helpful tips. I'll try to keep this thread updated as information comes in.
All credit goes to their respective owners, I am only aggregating all the information here.
Current status on BL Unlock:
China version: OEM unlock not greyed out, direct BL unlock possible
EU/NA version (L09/L29/L0C): OEM unlock greyed out in developer options, BL unlock possible via FunkyHuawei method by upgrading to .170.
UPDATE 2019/01/02: Some users reported they have already received the .171 update from carrier (https://forum.xda-developers.com/showpost.php?p=78571337&postcount=6), if that is the case you can skip the FH Method part and go directly to unlock BL.
Note: Currently .170 is not GooglePay certified, so Google Pay won't work on this, if you must have Google pay please wait for your carrier to update to some version that support OEM unlock (tap build number 7x to get Developer Options in Settings -> System -> About Phone and then go to Settings -> System -> Developer Options and see if Enable OEM Unlock option is enabled).
Also current recovery install requires you to boot into recovery (Power and volume up with phone disconnected from USB) every single time if you want root, which is not perfect.
The only time you'd be required to wipe your phone is right after your BL is unlocked with fastboot OEM unlock, please make sure you have a backup before doing that step.
Where to get unlock code?
In order to get BL unlocked, you need both allow OEM unlock option NOT greyed out (i.e., you can enable it) AND a BL unlock code. BL unlock code can only be purchased either from FunkyHuawei (55 USD one time for BL unlock code only or if you buy an unlimited pass 132USD for unlimited flashing + BL unlock code (note that it is locked to your phone and can not be transferred)), or MinistryOfSolutions (30 Euro, https://ministryofsolutions.com/huawei-bootloader-unlock-service-all-new-models-new-firmwares, BL unlock code only).
FunkyHuawei Method (for non-China version)
1. Create an account in https://funkyhuawei.club/membersarea, buy 1 credit (if you just want to download .170 firmware, each credit cost 18USD).
2. Go to Select Firmware tab, use LYA-Global if you don't see the exact model. Then select .171 version.
3. Follow instructions here: https://pastebin.com/raw/Db5ZSyqu, you must download the specific HiSuite version (9.0.2.301）and the specific installer executable. Run the executable FHHiSuiteInstaller.exe as administrator (right-click and choose Run As Administrator) <- must run as admin since it will need to modify your host file. Make sure the script runs without error.
3.1 (Additional step for L0C): Edit the c:\users\YOURHOMEFOLDER\appdata\local\hisuite\userdata\updatedogdev\hisuiteconfig.xml file and change LYA-L29 to LYA-L0C everywhere it occurs and save the file. (Thanks to FunkyHuawei Support for pointing this one out).
4. Put the phone into fastboot mode (adb reboot-bootloader or with the phone off connect the usb cable while holding volume down, or boot the phone holding volume down with USB cable connected to PC).
5. Go to HiSuite on your PC and click on System Recovery (furthest to the right towards the bottom of the main screen), and let it do the magic. You will see some cmd windows pop up however it should get to the download progress with a percentage pretty fast, if you don't see that pop up then please check to make sure you have at least one credit in the FH Select Firmware tab and you have installed the specific versions of HiSuite and ran the installer as admin in Step 3.
6. Once everything is completed please verify to see if your firmware version is .171.
Unlock Bootloader
Again, get the BL code and go to Settings -> System -> Developer Options and make sure Enable OEM Unlock option is enabled. Also check to make sure you have everything backed up. Also enable USB Debugging in the same screen as well.
Rest is pretty standard:
Code:
adb devices (will bring up the authorization window on your phone, click on Always Trust)
adb reboot-bootloader
fastboot devices (make sure the device is in fastboot mode)
fastboot oem unlock *UNLOCK CODE*
at this point there will be a format operation performed on the phone, if it didn't complete successfully don't worry, your phone is wiped. During the boot you should see a black window with yellow text of warnings to tell you your phone is unlocked and not secured.
Go through all the steps to initialize the phone, turn on Developer options again, and enable USB Debugging again.
Root
1. Download and install Magisk Manager from this XDA post: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Switch channel, go to Magisk Manager -> Settings -> Update Channel , set it to Custom, and the URL is https://bit.ly/2N8UVlq (at the moment, per https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337). Go back to main screen and down swipe to refresh, it should say Latest Version > v18.0.
3. You will need to find the stock RECOVERY_RAMDIS.img file, I used HW Firmware Finder (https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146) to help me with the task, however I couldn't find the L0C update file and ended up using L09 update file instead, which appear to work. I also couldn't find the update.zip for .171 so I ended up using the latest full update version that was available to me (http://update.hicloud.com:8180/TDS/...69/g1750/v181585/f1/full/update_full_base.zip).
4. Unzip the file, drag out UPDATE.APP file in the zip package, and opened it with Huawei Firmware Extractor (I used 0.9.9.5 in this thread: https://forum.xda-developers.com/showthread.php?t=2433454). Extract and open the UPDATE.APP in update file. If you get a checksum error make sure to uncheck both of the verify checksum in Settings -> Extract.
5. Now you should see a RECOVERY_RAMDIS.img file, right click and extract it.
6. Send the RECOVERY_RAMDIS.img file back to your phone (anywhere is fine), go back to Magisk Manager -> Install -> Patch boot, get the patched_boot.img file from the phone back to the PC.
UPDATE 2019/01/02: @pvillasuso was kind enough to post the ramdisk image (both original and Magisk modified) for Mate 20 Pro LYA-L09 (Firmware version .171):https://forum.xda-developers.com/showpost.php?p=78575496&postcount=13, obviously use it at your own risk.
7. Go to fastboot mode again:
Code:
adb devices
adb reboot-bootloader
fastboot devices
fastboot flash recovery_ramdisk "PATH_TO_patched_boot.img"
fastboot reboot
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Boot up and if you go to Magisk now you should be able to see Magisk installed with Installed Version same as Latest Version.
Congrats you are now rooted!
In future you will need to boot into recovery each time to maintain root (which requires you to turn phone off and power + vol up), if you prefer not to do so @ThatsJustLogic suggested you can use the app https://forum.xda-developers.com/showpost.php?p=78569733&postcount=2 to add a one-click reboot from your dropdown menu.
Credits:
@ThatsJustLogic - Figured out the installation steps to patch ramdisk: https://forum.xda-developers.com/showpost.php?p=78554707&postcount=125
@duraaraa - Guy behind FunkyHuawei for figuring out the .171 upgrade and make everything works smoothly https://forum.xda-developers.com/mate-20-pro/how-to/unlock-rebrand-unbrick-update-t3855065
@mutahharbashir - Guy behind MinistryOfSolutions for the unlock BL code.
And creators of Magisk, HWFirmwareFinder, HWUpdateExtractor.
zhuanyi said:
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Click to expand...
Click to collapse
To stop you needing to do this on every boot this app: https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials allows you to add a "Reboot Recovery" button to your notification tray so its just a one tap reboot instead of holding volume up when you want to reboot after applying a change or something its something small but it saves some hassle.
Awwsome, thank you so much. Now I can finally use Google pay on global firmware 9.0.0.171. It's working perfectly
This is amazing development
Hi, can someone post his oeminfo?
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Thank you for the guide.
Can we re-brand from Chinese to international now?
thunderpossuem said:
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Click to expand...
Click to collapse
How come? Can you post a screenshot with developer options on yhe screen?? Oh, you have. Can this mean that we will be able to unlock bootloader for free when v168 update arrives to other countries??
Sent from my LYA-L29 using XDA Labs
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
That's just what i thought
Sent from my LYA-L29 using XDA Labs
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
pvillasuso said:
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
Click to expand...
Click to collapse
The patched file will work for anyone who has the mate 20 pro and the same FW version as you. Theres no extra steps it just removes the finding the FW, extracting and patching the image yourself They will still need magisk and the canary channel.
If you are going to share I would specify Firmware version and attach a non patched one incase people have issues and want to revert.
My phone model : Mate 20 Pro LYA-L09 (Firmware version 9.0.0.211)
patched_boot.img > https://www.mediafire.com/file/fp3jk281d47bh6k/patched_boot.img/file
Apply on your own risk , worked for me !
Hi, glad to hear that even L0C model has to the chance to root. Just wondering after flash the global .171 version which should solve the OEM greyed-out problem, the next step is to purchase a BL unlock code? And is there a chance that after BL and FRP unlocked. My model (LYA-L0C) can be rebrand to another one?
deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
Indeed it is 18 USD saved, also hopefully it is more compatible with your phone.
Can you give an example of your path to "PATH_TO_patched_boot.img"
I must be getting syntax incorrect for the file in internal storage download folder, and I have tried everything with and without / leaving out folders.
is this ota proof?
Some rooting questions....
Hi.
I will try to be brief and on topic. Feel free to remove post if not according to Xda forum rules.
Long story short. I am an heavy iOS user from the apple jailbreak scene. I am no developer (only user) and now I have taken the big step from IOS to Android.
Huawei mate 20 pro broke my curiosity. I have always "jailbroken" my iPhone since 2007 and now I am considering root of my HM20PRO.
I have some questions before I try this and brick my phone.
I have Norwegian model, LYA-L29 with 9.0.0.153 (c432) software. (BL unlock greyed out here as well)
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
Hope that someone can take the time to help me with my questions.
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
sorry for the noob questions, but I am new with this so thanks...
Regards,
Kenneth - Trondheim, Norway
PS:I have to say the switch from iOS to android and Huawei mate 20 pro have been great so far (except new replacement phone on the first day with green screen on BOE screen.) Now all is good.
Main reasons to root android?
I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
fromiOS2Android said:
Hi.
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
Main reasons to root android? I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
Click to expand...
Click to collapse
Hi, first of all, welcome to Android
My advice is to NOT root until you got an answer to all your questions
I'll let some pros answer the technical questions on the partitions) but here's what I can tell you:
- Main reason to root for me is adblockers and (not a must though) custom roms.
- There is a function within magisk to hide root from apps.
- On the fixes, yes, 171 is the one that allows root and that's also the latest one with all the fixes.
- Once you root you stay rooted, you don't have to repeat the whole process at every boot.
- From what I read in several threads, right now you can't revert to older firmwares. Also, the 171 seems to be market specific, what I will do is to wait until the update gets rolled out in my market by Huawei, I read that the unlock bootloader option is then available officially.
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
charliebigpot said:
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
Click to expand...
Click to collapse
Using Magisk Hide on Google Pay will prevent it from detecting root, however if SafetyNet fails then it probably still won't work.
There are a few Magisk modules that can (apparently) force SafetyNet to pass, however I haven't ever used any of them.
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
ZeroXO said:
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
Click to expand...
Click to collapse
Okay I was thinking I might of missed something. The patch for oem issue I thought covered that.
Is the unknown (bat) firmware the one I need to flash to stock?
Sent from my OnePlus6T using XDA Labs
TheLogicalGamer said:
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
Click to expand...
Click to collapse
Using odin 13.1.3 is recommended.
As you have the N950F, it is part of the multi OXM CSC, so you can flash the filmware for you country and carrier if desired (N950F)
If you want to root, I suggest just flashing a custom rom or kernel, as they have been patched for the RMM KG state issue.