Database Info

I can't lock the bootloader. HELP!!!

Hi guys, I need help, because I can't relock my bootloader. I have Honor 8 L09C432
I was on Carbon ROM and I had TWRP installed, and I wanted to go back to stock ROM, so I followed a procedure that I found in a comment on some thread.
( This is a screenshot of a comment that I followed, if that means anything to you ) https://forum.xda-developers.com/attachment.php?attachmentid=4385584&stc=1&d=1515621906
I successfully returned to EMUI 5.0 and I'm currently on B360, and I wanted to update to B381. I got an OTA, I downloaded it, but installation failed, and that's, I guess, because the bootloader is unlocked.
I tried to lock the bootloader with some adb commands:
-adb devices ( my device would appear )
-adb reboot bootloader
-fastboot oem lock * Bootloader code *
and then I would get a message that says " FAILED (remote: Command not allowed) "
( Here's also a screenshot of that too ) https://dl.xda-developers.com/4/3/8/5/5/8/5/Capture2.PNG?key=L_OuO3DslYw7HJaIJW-mGw&ts=1515622403
I enabled USB Debugging and OEM unlock options in Developer options, but it still doesn't work...
If someone's knows why this is happening, or how can I update the phone without even locking, I would really appreciate that, thank you in advance, and If I didn't mention something that may be important, please tell me, so I can help you to help me

Use fastboot oem relock instead of lock.
Note that relocking isn't the same as locking, for that you'd have to flash something like MM via dload which automatically locks the bootloader. Some other official packages might work, too
Edit: Also you need to be in fastboot mode to actually use the fasboot commands. (power+vol. down)
I'm not sure if an unlocked bootloader should actually break the OTA but it's been a while.
You can just download the flashable (for TWRP) versions from FF ( the full ota mf-pv) and use those otherwise
Sent from my OnePlus5 using XDA Labs

I tried Fastboot oem relock too, but that also didn't work, and I was in fastboot mode when I typed in the commands. I don't have TWRP since I installed stock ROM ( EMUI ). I guess you are suggesting that I should downgrade to MM, so then the bootloader will be locked? Still, thank you for your time and help!

You don't need to lock the bootloader in order to take an update. However, you must have the stock boot and recovery .img loaded for it to work. Here is a link for instructions on how to do this. Keep in mind that my instructions only talk about extracting the boot.img, but in your case it is probably best to extract both the boot and recovery.img just like the video shows. Use the B360 firmware to extract the files from. This will ensure all of your partitions are stock and that will hopefully allow you to take the update OTA.

sic0048 said:
You don't need to lock the bootloader in order to take an update. However, you must have the stock boot and recovery .img loaded for it to work. Here is a link for instructions on how to do this. Keep in mind that my instructions only talk about extracting the boot.img, but in your case it is probably best to extract both the boot and recovery.img just like the video shows. Use the B360 firmware to extract the files from. This will ensure all of your partitions are stock and that will hopefully allow you to take the update OTA.
Click to expand...
Click to collapse
I'll try this method, thank you very much for your help and time :angel:

[GUIDE] Upgrade/Downgrade between Nougat and Oreo

WARNING: This guide is tested on Nokia 6 TA-1000 only!
ALWAYS DO BACKUP BEFORE PERFORM ANYTHING!
Use Titanium Backup, Internal Backup Tool or...whatever.
中文版教程：http://bbs.dospy.com/viewthread.php?tid=17830185&bbsid=1021&page=1
Click to expand...
Click to collapse
You can download the required firmware I mentioned there:
https://forum.xda-developers.com/nokia-6/how-to/nokia-6-ta-1000-homebrew-stock-android-t3752006
PART 1: Preparation
1. Install OST LA 6.0.4 and patch it. DO NOT INSTALL OST LA 6.1.2 I MENTIONED BEFORE.
2. DO FULL BACKUP, DO FULL BACKUP, DO FULL BACKUP!
PART 2: Downgrade bootloader
If you're running Android O that comes from OTA Update, that means the bootloader must be downgraded before downgrade your phone to Nougat.
If you've already have old bootloader, skip this part.
Click to expand...
Click to collapse
To downgrade the bootloader, you need to download this OTA package:
https://ota-filesite.c2dms.com/SWUpdate/500000748
To prevent from FIH removed this OTA package, I mirrored this OTA package.
You need to enter stock recovery manually.
Power off your phone, then connect your phone to a charger.
When you see the charging logo, press and hold Volume Up and Power key.
If you see "No command" displayed, release both keys, then press Volume Up while holding Power key. This will pop up a menu.
Click to expand...
Click to collapse
In some cases, you may get stuck at stock recovery.
Pick "Install update from ADB", then use adb sideload command to push this OTA package to your phone.
Code:
adb sideload D1C-331G-0-00CN-B01-331F-0-00CN-B01-update.zip
After this update installed, your phone will reboot once, then get stuck at recovery. Your bootloader has been downgraded now.
PART 3: Install homebrew "Stock" firmware
Download the firmware from the link above.
D1C-331G-0-00CN-B01.7z - Nougat 7.1.1 with December 2017 Update
D1C-332A-0-00WW-A01.7z - (Hong Kong/Taiwan Variant, Full Google Play Service included) Nougat 7.1.1 with July 2017 Update
D1C-5210-0-00CN-B03.7z - Oreo 8.0.0 with January 2018 Update and old bootloader
D1C-5550-0-00CN-B02.7z - Oreo 8.1.0 with March 2018 Update and old bootloader (made from leaked OTA)
Extract the firmware archive into a new directory, for example, I extracted it to D:\D1C-331G-0-00CN-B01.
Open OST LA from INSTALLATION DIRECTORY DIRECTLY. Load the mlf file in extracted directory.
If your phone get stuck at recovery, pick "Reboot to bootloader", then connect your phone to PC.
If your phone is already powered off, just connect it to PC directly.
Click "Next" if it's usable. Otherwise, click "Edit Phone Information", after "Boot FTM Mode Fail" prompts, you can click "Next" now.
This will flash the firmware to your phone. If the procedure unexpected interrupted because of your phone doesn't cooperate properly (e.g. Your phone suddenly reboots to OS), close the OST LA, then press and hold both Volume keys and power key to force power off your phone, then flash it again.
When the progress bar is going to complete and your phone is booting (NOKIA logo is displayed on the screen), the flash procedure is already completed.
In most cases, if your phone prompts md5 checksum fail after flashing, this is also expected. You can close OST LA, unplug the phone, then reboot the phone with [Volume Up] and [Power] key.
PART 4: Full userdata erase
If your phone can boot into OS normally, skip this part.
Click to expand...
Click to collapse
Because the encrypt algorithm is different between Nougat and Oreo, you must do full userdata erase or the phone will get stuck at NOKIA logo.
Enter Download(Fastboot) mode again with the method you're familiar with.
Open OST LA, load the firmware, then click "Edit Phone Information".
If you've already know how to obtain the service permission, you can just type this command instead:
Code:
fastboot oem dm-verity (md5 checksum of your phone's serial number)
Then type this command:
Code:
fastboot format userdata
You also need to flash TWRP to do another format procedure, which the procedure I've given in this topic:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-flash-custom-recovery-root-t3702354
After you enter the recovery, tap "Wipe" (清除), "Format data partition" (格式化 Data 分区), then type "yes" to proceed.
NOTE: Root package included in recovery isn't compatible with Android Oreo.
Click to expand...
Click to collapse
You can reboot your phone to the OS now. If the phone get stuck at Powered by Android logo, just do PART 3 again.

I successfully sucessfully fw (Oreo) through OST 6.0.4 and have installed TWRP on Oreo.
But the Root package does not work.
I'm testing with the zip install package via TWRP as the MODs for example (Emoji package, Font, ...) Hope it works.

I can't flash your firmware "Nougat 7.1.1 with December 2017 Update"
stuck on writing md5, what's wrong ?

hawwin88 said:
I can't flash your firmware "Nougat 7.1.1 with December 2017 Update"
stuck on writing md5, what's wrong ?
Click to expand...
Click to collapse
You can use a text editor (do not use notepad) to edit the md5.dat, and modify the checksum to expected checksum displayed on the phone, then flash again.
I'll reupload the correct package soon.

anyone tested on t 1021

Can we get root access and xposed on oreo or is it still unavailable?.

Please I am begging the senior members please, someone should help me..my phone has been bricked for 2 months now..my Nokia 6 ta-1003.. it's stuck on QLD 900E... PLEASE HOW DO I resolve this myself...I have been without a phone since... someone should help me out of this nightmare..it doesn't come on,just only shows the notification lights and QLD 900E on device manager... awaiting a positive response..thanks

TA-1021 Downgrade help
is this method useful for nokia 6 TA-1021??????

hikari_calyx said:
You can download the required firmware I mentioned there:
https://forum.xda-developers.com/nokia-6/how-to/nokia-6-ta-1000-homebrew-stock-android-t3752006
PART 1: Preparation
1. Install OST LA 6.0.4 and patch it. DO NOT INSTALL OST LA 6.1.2 I MENTIONED BEFORE.
2. DO FULL BACKUP, DO FULL BACKUP, DO FULL BACKUP!
PART 2: Downgrade bootloader
To downgrade the bootloader, you need to download this OTA package:
https://ota-filesite.c2dms.com/SWUpdate/500000748
To prevent from FIH removed this OTA package, I mirrored this OTA package.
You need to enter stock recovery manually.
In some cases, you may get stuck at stock recovery.
Pick "Install update from ADB", then use adb sideload command to push this OTA package to your phone.
Code:
adb sideload D1C-331G-0-00CN-B01-331F-0-00CN-B01-update.zip
After this update installed, your phone will reboot once, then get stuck at recovery. Your bootloader has been downgraded now.
PART 3: Install homebrew "Stock" firmware
Download the firmware from the link above.
D1C-331G-0-00CN-B01.7z - Nougat 7.1.1 with December 2017 Update
D1C-332A-0-00WW-A01.7z - (Hong Kong/Taiwan Variant, Full Google Play Service included) Nougat 7.1.1 with July 2017 Update
D1C-5210-0-00CN-B03.7z - Oreo 8.0.0 with January 2018 Update and old bootloader
D1C-5550-0-00CN-B02.7z - Oreo 8.1.0 with March 2018 Update and old bootloader (made from leaked OTA)
Extract the firmware archive into a new directory, for example, I extracted it to D:\D1C-331G-0-00CN-B01.
Open OST LA from INSTALLATION DIRECTORY DIRECTLY. Load the mlf file in extracted directory.
If your phone get stuck at recovery, pick "Reboot to bootloader", then connect your phone to PC.
If your phone is already powered off, just connect it to PC directly.
Click "Next" if it's usable. Otherwise, click "Edit Phone Information", after "Boot FTM Mode Fail" prompts, you can click "Next" now.
This will flash the firmware to your phone. If the procedure unexpected interrupted because of your phone doesn't cooperate properly (e.g. Your phone suddenly reboots to OS), close the OST LA, then press and hold both Volume keys and power key to force power off your phone, then flash it again.
When the progress bar is going to complete and your phone is booting (NOKIA logo is displayed on the screen), the flash procedure is already completed.
In most cases, if your phone prompts md5 checksum fail after flashing, this is also expected. You can close OST LA, unplug the phone, then reboot the phone with [Volume Up] and [Power] key.
PART 4: Full userdata erase
Because the encrypt algorithm is different between Nougat and Oreo, you must do full userdata erase or the phone will get stuck at NOKIA logo.
Enter Download(Fastboot) mode again with the method you're familiar with.
Open OST LA, load the firmware, then click "Edit Phone Information".
If you've already know how to obtain the service permission, you can just type this command instead:
Code:
fastboot oem dm-verity (md5 checksum of your phone's serial number)
Then type this command:
Code:
fastboot format userdata
You also need to flash TWRP to do another format procedure, which the procedure I've given in this topic:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-flash-custom-recovery-root-t3702354
After you enter the recovery, tap "Wipe" (清除), "Format data partition" (格式化 Data 分区), then type "yes" to proceed.
You can reboot your phone to the OS now. If the phone get stuck at Powered by Android logo, just do PART 3 again.
Click to expand...
Click to collapse
Hi, i have Oreo 8.1 install in my ta 1003, initially it was a ta 1000 but i did flash the ta 1003 rom after down grading the bootloader with help of another thread. I want try out this Home brew rom and am not sure how to go about. The ta 1003 has issues with the network, like the VoLTE option is not working.

I cant get to stock recovery manually, I tried holding power and up volume but still not working. I'm using TA 1039 with Android 8.1.
What should i do?
hikari_calyx said:
PART 2: Downgrade bootloader
To downgrade the bootloader, you need to download this OTA package:
To prevent from FIH removed this OTA package, I mirrored this OTA package.
You need to enter stock recovery manually.
In some cases, you may get stuck at stock recovery.
Pick "Install update from ADB", then use adb sideload command to push this OTA package to your phone.
Code:
adb sideload D1C-331G-0-00CN-B01-331F-0-00CN-B01-update.zip
After this update installed, your phone will reboot once, then get stuck at recovery. Your bootloader has been downgraded now.
Click to expand...
Click to collapse

Sorry, just one question.
If the TWRP already has those partitions decrypted, can the userdata partition be safely restored after updating from Nougat to Oreo?

does anyone have the OTA package backed up? https://ota-filesite.c2dms.com/SWUpdate/500000748 doesn't work anymore

Dantheman221 said:
does anyone have the OTA package backed up? https://ota-filesite.c2dms.com/SWUpdate/500000748 doesn't work anymore
Click to expand...
Click to collapse
Change c2dms into oss-cn-hangzhou.aliyuncs :
https://ota-filesite.oss-cn-hangzhou.aliyuncs.com/SWUpdate/500000748

Hello
After updating to Android 9, I lost dm-verity command and TWRP. Fastboot says it's an invalid command now. Help?
Edit: Okay, flashed old bootloader and got dm-verity back. Unlocked bootloader, now am stuck on recovery, won't boot to 7.1.1 OS. Help?

LOSQ/LiR - LineageOS 17.1/18.1-UNOFFICIAL-GSI

For those who want to try LineageOS 17.1/18.1-UNOFFICIAL-GSI . IMO stable enough to be used as your daily driver.
LOSQ/LiR is not developed nor maintained by me!
Credits: @eremitein
Requirements: basically full stock EMUI 9.1, with stock recovery_ramdisk.
Note: I prefer to install in fastboot mode, it's quick, easy and most importantly, safe.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Install arm64-b.. only!
1. LOSQ - LineageOS 17.1-[10]-unofficial-GSI
with the GAPPS
GAPPS
without GAPPS
Vanilla
-----------------------
LiR- LineageOS 18.1-unofficial-[11]-GSI
Download
2. Extract the ROM .img file from the compressed file.
3. Flash extracted losq/lir... .img from fastboot , use command
fastboot flash system (file_name).img
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot .
NFC patch:
https://forum.xda-developers.com/t/losq-lineageos-17-1-unofficial-gsi.4219291/post-84394147
Magisk root (23.0):
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ),
- download and install Magisk manager-23.apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
- Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1):
- copy TWRP file to the SD card, and also copy to the SD card patched Recovery_ramdisk:
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
- flash TWRP - run command
fastboot flash recovery_ramdisk (TWRP's_name).img
- boot into TWRP, select storage - SD Card, select "Install image", find TWRP-9.1.img file and mark eRecovery, swipe. Go back, find magisk_patched-23.img file, mark Recovery, swipe. Go back to the TWRP's main menu, select Reboot > Recovery. Done.
Note: you then need to boot your phone every time via Recovery. It'll boot into android as normal but with root.
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
To remove Magisk reinstall stock recovery_ramdisk via TWRP or fastboot , download Here
How to boot into TWRP:
- Turn off your phone, connect to the PC (or charger), then press and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset).
Tips:
https://forum.xda-developers.com/t/treble-gsi-favorite-gallery-camera-and-file-manager.4246019/

I have tried this rom - but without the magisk as I don't really care for root.. However.. This rom still has one big missing feature.. Fingerprint unlock. I can go to register fingerprint. Add the finger multible times to complete the circle.. however.. every time it misses just the last part - it will fail. If anyone has a fix for this I would be happy to use this as my daily driver as it works just fine.

whitetigerdk said:
This rom still has one big missing feature.. Fingerprint unlock
Click to expand...
Click to collapse
I'm afraid you're wrong... It works perfectly for me.

Can confirm that so far everything works flawless. Fingerprint sensor is working on the phone too.
Thank you Alf.
Just two additional questions:
How will updates be perform in future?
How to switch from LOS 16 to this rom - the other P20 lite we have is still on v.16?
Cheers
Horqai

horqai said:
How will updates be perform in future?
Click to expand...
Click to collapse
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
horqai said:
How to switch from LOS 16 to this rom
Click to expand...
Click to collapse
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!

-Alf- said:
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
Click to expand...
Click to collapse
Ugh, is there a way to install emui 9 without it locking my bootloader? I unlocked my bootloader via the @huaweihax method.

[/QUOTE]
XRealX said:
Ugh, is there a way to install emui 9 without it locking my bootloader?
Click to expand...
Click to collapse
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
XRealX said:
I unlock my bootloader via the @huaweihax method.
Click to expand...
Click to collapse
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method

OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
Click to expand...
Click to collapse
There's no way I'm paying for unlocking!
The huaweihax method works this way: you give some information about your device and you flash a slock file to the ramdisk. It unlocks your phone.
To prevent EMUI 9 from re-locking your device, you can flash a zip file to have a custom bootloader unlock code.
Btw, I have hyperlinked the thread that describes this in the "thingy" word.
I guess that custom code should work even if my device is re-locked.

I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone

I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone

How can I repair the factory erecovery I am using the phenix program but it gives me recovery error

itrisev said:
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
Click to expand...
Click to collapse
Sorry, this is not the DC-Phoenix support chat, let's please remember to keep conversations and comments in this thread about LOSQ - LineageOS 17.1, thanks...

Thanks @-Alf-
I followed all your advice in the LOS 16 thread to get 16 installed, but couldn't get gapps to work. So I thought lemme give LOS 17 a shot since it includes gapps, and it works great! However I get the same issue with fingerprint as @whitetigerdk. During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work. Try again or use a different finger". I can provide a screenshot but it's literally just that text.
Apart from that everything seems to work fine. Haven't installed magisk yet, will do that next.

An3skmbi said:
During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work.
Click to expand...
Click to collapse
-Alf- said:
Tested on 9.1.0.132.
Click to expand...
Click to collapse
-Alf- said:
Clean OS
Click to expand...
Click to collapse
-Alf- said:
Install Service ROM using dload method (9.1.0.132 recomm.)
Click to expand...
Click to collapse
Most of custom ROMs require lower build number, on latest build number may or may not work correctly.
If you have followed this guide to the letter and it didn't work, i'm afraid I cant help you .
I've not had any major issue with this LineageOS.
P.S.:
If all this has worked on my device, it does not mean that it goes with everyone else, and vice versa (we are talking about Huawei devices ).

@-Alf- Thanks, that might be it. I'm on firmware 9.1.0.200(C185E4R1P8T8) as that was the recommended one for LOS 16. Let me give it a shot with 132, will update with results.
Edit: With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.

An3skmbi said:
With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
Click to expand...
Click to collapse
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
IMO you can get it via paid service only, for 17euros , hm...look here
.132
The difference between .132 and .200 is google patch - may 2019 vs. july 2019.

-Alf- said:
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
Click to expand...
Click to collapse
What about this one? http://huawei-firmware.com/rom/huawei-p20-lite/ane-lx1/42056
It doesn't have a dload folder, it's just the update.zip basically, so I'm not sure how to flash it only unlocked my phone yesterday, not used to huawei roms yet.
Edit: they explain how here, you create the dload folder manually.

An3skmbi said:
they explain how here, you create the dload folder manually.
Click to expand...
Click to collapse
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .

-Alf- said:
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
Click to expand...
Click to collapse
What do you mean really reliable when the guide is for Android 6? Is there a way to flash the 132 ROM from huawei-firmware?
Also, magisk installation worked perfectly by following your instructions. I can pass safety net with the universal safetynet fix module and got google play certification with the props module.
Is there a way to now boot into TWRP (erecovery)? Currently when booting it doesn't show the option to hold volume up to enter erecovery, it immediately says your phone is booting now. The only way to get into TWRP is to fastboot flash recovery twrp, do stuff there, then flash magisk_patched-ane-v21 over recovery and reboot.
Edit: I captured a logcat while getting the fingerprint enrollment error, there are some exceptions about the enrollment, not sure if that could mean something to the devs to help fix it?

An3skmbi said:
Is there a way to flash the 132 ROM from huawei-firmware?
Click to expand...
Click to collapse
Nope.
An3skmbi said:
Is there a way to now boot into TWRP (erecovery)?
Click to expand...
Click to collapse
Oops I thought I mentioned it in my post, mea culpa.
You have two options:
1. Turn off phone, connect to PC (or charger), then pres and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
2. Restart phone, when appears the yellow warning on screen, press Volume up, hold for ~ 2 sec,
release the button and immediately press and hold again for 2 sec, repeat it 6-7 times, the device will reboot into Stock Recovery , then you can do normal restart - Reboot system now.

How To Guide Asus ROG phone 5: unlock bootloader and root guide

Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations

Check pm's.

m8822 said:
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
Click to expand...
Click to collapse
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.

also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help

sabnack said:
also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help
Click to expand...
Click to collapse
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill

hilary trump said:
Do you know any module to hide that pill
Click to expand...
Click to collapse
I'm sorry i don't know but i will gladly look into that issue as soon as i can boot my phone, currently i'm stuck in a bootlop and my phone doesn't get recognised. i put all my hopes in the unbrick tool at this point, whenever it will be out.
I will let you know

hilary trump said:
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill
Click to expand...
Click to collapse
the root guide worked on another rog 5, however mine is completely nricked and i myslef is waaiting for unbrick tools

sabnack said:
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.
Click to expand...
Click to collapse
Connect your phone with the side port it will work.

sorankira said:
Connect your phone with the side port it will work.
Click to expand...
Click to collapse
yes it did work, i flashed every partition and now i'm locked again, recovery doesn't work, could you please dump yours and post it ? hope i'm not asking too much.
EDIT: nevermind i finally solved it, i flashed a raw img of the system, it works now, thanks for your time

m8822 said:
Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations
Click to expand...
Click to collapse
Mine causes bootloop

sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
What ? Why!
what happened? Did you get this after unlocking the bootloader or after boot.img?
My troubkeshooting will consiste of flashing raw, but i am not sure if that will lock your bootloader

sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.

sabnack said:
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.
Click to expand...
Click to collapse
I fixed the bootloop but without root access

sorankira said:
I fixed the bootloop but without root access
Click to expand...
Click to collapse
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.

sabnack said:
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.
Click to expand...
Click to collapse
Yes i used this method, and causes bootloop sadly.

sorankira said:
Yes i used this method, and causes bootloop sadly.
Click to expand...
Click to collapse
oh ! dammit it's weird... you could try to patch the boot image with another phone.
or maybe the update file isn't right for your phone. i don't get it

Somebody successfully succeeded with the bootloader & Rooting this Asus ROG 5 phone?

my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)

miguel.jackass said:
my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)
Click to expand...
Click to collapse
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money

m8822 said:
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money
Click to expand...
Click to collapse
I updated the firmware to the latest official version, extract the boot.img from the last official firmware, and installed the official unlock tool from the ASUS website, I just had to follow the tutorial.

Is possible to root Xcover Pro?

Hello,
I have unlocked the bootloader. I tried to do the steps with Magisk, this is it:
-Install Magisk.
-Patch AP.
-Copy it to PC.
-ReFlash with ODIN.
But when I do that, I got errors during installation on Download mode and the phone bricks. So I don't know if I am doing something wrong or happens that this device can't be rooted.
I have been searching but can't find any reliable information about, could you please give me some information or help?
Thank you!

Bump!

Got this error following installation instructions:
ODIN MODE (AVB Fail)
vbm*** Error verifying vbmeta image: HASH_MISMATCH (3)
vbmeta: VERIFICATION_DISABLED bit is set
CUSTOM VBMETA
VBMETA G715FNXXU8CUE1, 4000301 4R

Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
tys0n said:
It's pretty simple and straight forward. I won't go in on details about odin, drivers etc as there's many guides about that already.
Or join the A40 tg group for any assistance with firmware, odin etc.
You'll need to unlock bootloader first, and it will TRIP KNOX.
Please read up on what it means before you proceed if you're not sure about it. It can't be reversed.
Download and install latest Magisk manager to your phone. https://github.com/topjohnwu/Magisk/releases
Download and install 7zip ZS to your pc. https://github.com/mcmilk/7-Zip-zstd/releases
Get the firmware for your phone and extract the AP file from the firmware zip. (Use samfirm or frija for fast download)
Open the AP*.tar.md5 with 7zip ZS and click on the boot.img.lz4, then drag the boot.img out of there.
Copy the boot.img to your phone, open Magisk Manager and click install, and again install, then "select and patch a file".
Browse to the boot.img you just copied to your phone and let Magisk do it's magic.
You'll find a magisk_patched.img in your download folder when it's done.
Copy it over to your pc, rename it to boot.img and make a .tar archive with boot.img in it.
Open Odin, put the tar in AP slot, connect your phone in download mode and hit start in Odin.
Open Magisk Manager again once the phone is booted to finish the setup.
Done.
Click to expand...
Click to collapse
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.

Awesome! The bad thing is that I already sold Xcover Pro because I need root yes or yes but well, I hope it will be useful for people in the future! Maybe even somebody try to port LineageOS.

d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later

-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?

-SpaceCowboy- said:
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?
Click to expand...
Click to collapse
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far

On my rooted SM-G715FN, I have:
CURRENT BINARY: Custom (0x3)
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF(U)
Secure Download: Enabled
Click to expand...
Click to collapse
In Developer Options, I have `OEM Unlocking` enabled.
iBowToAndroid said:
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far
Click to expand...
Click to collapse
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.

d5sword said:
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.
Click to expand...
Click to collapse
Because his phone is not SM-G715FN

The ADB removal method worked for me. There's a "Debloat" text file up on GitHub that makes this a breeze.
Link: https://github.com/khlam/debloat-samsung-android tellthebell
Once in debug mode, USB connected, and drivers installed:
ADB shell < commands.txt
Obviously, the text file must reside in the same folder as ADB.

travis659 said:
El método de eliminación de ADB funcionó para mí. Hay un archivo de texto "Debloat" en GitHub que hace que esto sea muy sencillo.
Enlace: https://github.com/khlam/debloat-samsung-android tellthebell
Una vez en modo de depuración, USB conectado y controladores instalados:
Shell ADB <comandos.txt
Obviamente, el archivo de texto debe residir en la misma carpeta que ADB.
Click to expand...
Click to collapse
i think only working in snapdragon devices, no? the Xcover use Exynos

d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
Just wanted to say a huge thank you to yourself and tys0n.
I purchased an Xcover Pro brand new from Microless global for an absolute steal...as in a price that was simply too good to be true. It was only upon setting up the device that I realised why they were offering such a low price.
The device was encumbered by an unavoidable corporate knox enrollment service. Sadly I suspect most people who purchase from them won't realise just how much control of their device they are handing to some random company if they just press OK during setup, but I wasn't having it. Ignoring the enrolment promp was not possible; you couldn't even access the home button or recent button until you'd authorised under knox and handed control of the device over to some faceless entity.
Thanks to the efforts of those in this thread I have been able to unlock BL, root the SM-G715FN/DS and freeze all of the knox bull****. The device now belongs to me.
The only thing I'd like to ad for those that come here looking for answers is that the process above is spot on, but I had to use this tool to create my .tar file. Simply creating a .tar archive with the .img file in it wasn't good enough for my device; it rejected that as an unauthorised file.
Use this tool once you've patched the boot.img with magisk and renamed it.
[Script][Tool] how to create a tar.md5 file from img For Odin
for how want to use Odin to flash the ClockWorkMod Recovery img or any image files like "boot.img", this is a tool to create a tar.md5 file from the img file. unzip the file tool, and put your img files into the same directory of the batch file...
forum.xda-developers.com
Props to mkh.mourad and testament to the usefulness of XDA that a file from 2013 got me over the line.
I'm certainly no developer, but given the relative ease with which we got this far, I hope it's not too far down the road until we get TWRP and can start mucking around with some roms. Please post here if you have any ideas. This device has real potential as a very long term solution.

Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.

TomasNM said:
Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.
Click to expand...
Click to collapse
The "KG" status must be in "checking" so that you can flash a custom binary, you must leave the phone on 168 hours in a row with an internet connection otherwise it will not disappear

SpaceCowboy,
thank you for the advice, I waited a bit and today I managed to root the phone successfully.
However, I tried to install some Magisk modules and the phone stuck on initial screen (Samsung Galaxy Xcover Pro), even not get to the "SAMSUNG" screen.
Only solution was to wipe all data in recovery.
Any ideas how to install Magisk modules without risk?

Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.

Psyckosama said:
Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.
Click to expand...
Click to collapse
What's your Baseband Version?

iBowToAndroid said:
What's your Baseband Version?
Click to expand...
Click to collapse
g715u1uescbuj1

Psyckosama said:
g715u1uescbuj1
Click to expand...
Click to collapse
OEM unlock doesn't exist on US models. This model is bootloader unlockable via paid 3rd party services, but only up until bootloader revision 7. Since you're fully updated, you have revision 12