Verify Modified Vendor image works for Realme 3 [Tester Required]

Verify Modified Vendor image works for Realme 3 [Tester Required] - Oppo Realme 3 Guides, News, & Discussion

Note: Testing is already done by haditriw, please ignore the below message, this is just for future reference
These tests are for noobs, so that they can contribute to the development of Realme 3.
I have made these tests very easy to execute, you just have to connect the phone and double click the file to run the test automatically.
The reason why I am not doing these tests is because, a single hard brick stops the development for this phone for 2-3 weeks, as I have to give my phone to service center and wait for the phone to be returned back. I hope that people are ready to take the risk and do the testing, instead of just questioning about why there is no magisk or twrp for this phone.
----------------------------------------------------------------------------------------------------------------------------------------------
Test ID: 1
Test Name: Verify modified vendor image works for Realme 3
Test Description: This test will help me to know, that vendor image can be modified and in turn will help in TWRP development for this phone.
Pre-conditions:
1. Bootloader unlocked, if not yet unlock, please refer: https://forum.xda-developers.com/realme-3/how-to/bootloader-unlock-realme-3guide-t3920394
2. Windows PC/Laptop
Test Steps:
1. Download and extract the Flash_Vendor_A16_Realme3.7z from here:
2. Power off your phone
3. Press volume down + power button together for some time, your phone will now boot in Fastboot mode.
4. Connect the phone to windows pc/laptop.
5. Go inside the Flash_Vendor_A16_Realme3 Folder and double click Flash_Modified_Vendor_A16.bat to run the test.
Expected Result:
The phone should boot normally to the OS
Actual Result:
[This is required from tester, just post the result in this thread or you can also pm me]
Questions:
Q. How can I revert back to stock state after the test?
A. The tester can flash the stock vendor by double clicking Flash_Stock_Vendor_A16.bat
Q. My device got bricked, what should I do?
A. If it’s just bootloop, then flash the stock vendor by double clicking Flashstockvendor.bat. If it’s not powering on, then it means it got hard bricked, just go to your nearest service center and tell them that the phone is not working after software update and tell them that this is just software problem. They will flash the image back and give you within 2 weeks.
Test Designed by: Fawaz Ahmed
Test Designed Date: 26-Jun-19
Test File Link: https://www.androidfilehost.com/?fid=6006931924117903211

Testing done by @haditriw

Bugs lockscreen not worked!

Related

Unlock Bootloader Application & Tutorial for Realme 2 Pro

This post was originally written and posted by Alessio from Realme forums
Hello Realme Fans
Here's how to unlock the bootloader (called in-depth test in the tutorial) on your Realme 2 Pro.
First, please read the “Disclaimer” carefully
【Disclaimer】
1. After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you proceed
2. The in-depth test may have unforeseeable impacts on your phone
3. Some functions may not operate properly because of third-party firmware, such as the photo-taking function of the camera. It may also cause device damage
4. Personal and confidential information on the phone may leak, and security compromised
5. The in-depth test may modify some of the system functions, and prevent you from updating the system version to enjoy the latest ColorOS
Second, read the steps below for the in-depth test
Preparation:
Realme 2 Pro - with 60%+ battery
1 x USB Cable
1 x PC/Mac
Step 1. Make sure you have backed up your data, unlocking your phone will erase all of your data
Step 2. Make sure your system version is the official and latest one
Step 3. Provide IMEI and sign up for the in-depth test via the link shared at the bottom of this post. The information will be reviewed by our staff, and the review will take approx 1-7 days. If your smartphone model and version are approved, you will receive an OTA package that supports the in-depth test. Install the OTA.
Step 4. Download and install the unlock tool apk on your phone:
https://download.c.realme.com/osupdate/DeepTesting_realme-release_signed.apk
Install it to apply for the bootloader unlock via the tool.
Step 5. Detailed steps to unlock the bootloader
#1. Open unlock tool.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#2. Click “Start applying”.
#3. Please read the disclaimer in detail, select the checkbox, and submit your application.
#4. The application will be checked by our server.
#5. Within approximately 1 hour, the unlock tool apk will show the status of unlocking - if it shows the unlocking is successful, please proceed to the following step.
#6. You can now click “Start the in-depth test” and press and hold the power key to reboot the device. You will then enter the fastboot mode.
#7. Download and install the fastboot tool on your PC or Mac (check this https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/), use a cable to connect phone and PC. In the Fastboot mode use the engineering command in the picture below to unlock.
#8. On your phone press the volume key to select “Unlock The Bootloader” and press the power key to confirm. The phone will reboot and enter in-depth test mode - all the user data on the phone will be cleared. We recommend you perform a data backup prior to applying
Bootloader appllication form link for the Realme 2 Pro:
https://goo.gl/forms/vDfXHNNt31j8ad5o1
FAQ
Q1: How to relock the bootloader?
#1. Download the unlock tool again to apply to exit in-depth test.
#2. Click “Apply to exit in-depth test” and press and hold the power key to reboot the device, and then you will enter the fastboot mode.
#3. In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
#4. Press the volume button to select the “Lock The Bootloader” option, and press the power key to confirm. The phone will reboot and exit the in-depth test mode, and clear all user data in the phone. We recommend that you perform a data backup prior to applying.
Q2: Are there any risks after unlocking the bootloader?
-> Please be aware that Realme cannot guarantee the full functionality, and will not be responsible, for any third-party unsigned custom ROM being flashed to your device after the bootloader is unlocked. An unsigned third-party custom ROM may not have gone through the thorough tests that we run for each device and software version that we release.
-> A third-party custom ROM may not work properly on your device, and certain functions and services may cease to work. The performance and device data may also be affected, and may damage the device permanently. In the worst case, unlocking the bootloader will cause physical injuries or material damage, for ex. due to the device overheating.
Q3: Will it affect future OTAs after unlocking?
The secure user data partition may also become inaccessible, and you will not be able to get any official software upgrades if you unlock the bootloader. Once re-locked the bootloader, users will receive official OTAs again.
Q4: Will it affect warranty?
Warranty will be fully applied to problems caused by Realme 2 Pro unlocking or flashing a custom ROM.
Q5: How to flash back the official ROM after installing a custom ROM?
Users need to go to a service center to flash the device - FREE of charge. We are developing a tool to flash a stock ColorOS. It will come in Q2 2019.
Q6: When other devices can get bootloader unlock?
Realme 1 will get bootloader unlock in Feb. Other devices are being
Q7: Where are the kernel sources?
https://github.com/sirwhanq/Realme-2-Pro-8.1-kernel-source
Link to original post https://c.realme.com/in/post-details/1085078965883764736

Hello,
I have done the whole process as described.
BUT when I enter this command - fastboot flashing unlock
nothing happens.... it just list down all the usage functions of fastboot and nothing else...
please help.
Has anyone successfully unlocked it yet ?
---------- Post added at 01:12 PM ---------- Previous post was at 01:03 PM ----------
mustali said:
Hello,
I have done the whole process as described.
BUT when I enter this command - fastboot flashing unlock
nothing happens.... it just list down all the usage functions of fastboot and nothing else...
please help.
Has anyone successfully unlocked it yet ?
Click to expand...
Click to collapse
SOLVED !!
for those ppl facing this problem use following command
./fastboot flashing unlock
just add ./ before fastboot

application hang on this since 6 hours..any solution ?

Bayramm said:
application hang on this since 6 hours..any solution ?
Click to expand...
Click to collapse
Follow these steps :
1) Exit the application
2) Start the application again
3) Click on "Query Verification Status"
That's it. It will show if the review is successful or is it still pending.
*i had the same issue. did the above steps and my review was successful*

Sumesh Kharnotia said:
Follow these steps :
1) Exit the application
2) Start the application again
3) Click on "Query Activation Status"
That's it. It will show if the review is successful or is it still pending.
*i had the same issue. did the above steps and my review was successful*
Click to expand...
Click to collapse
thank you,its done.

Facing this issue of write to device failed too many links. Any solutions guys?

You lazy liar
I am in vietnam and had sign up my phone imei last week Thursday (22nd Feb) but until now (1st March) i HAVEN'T receive any f***ing OTA for the unlock, do you know how excited i am thinking i finally can root my phone? Coloros rmx1807_11_a15 imei:862822042098610 give me the damn OTA now!!!!!!!!!

snipereye said:
Follow these steps :
1) Exit the application
2) Start the application again
3) Click on "Query Verification Status"
That's it. It will show if the review is successful or is it still pending.
*i had the same issue. did the above steps and my review was successful*
Click to expand...
Click to collapse
you are great!
Thank you Mate

hari2897 said:
This post was originally written and posted by Alessio from Realme forums
Hello Realme Fans
Here's how to unlock the bootloader (called in-depth test in the tutorial) on your Realme 2 Pro.
First, please read the “Disclaimer” carefully
【Disclaimer】
1. After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you proceed
2. The in-depth test may have unforeseeable impacts on your phone
3. Some functions may not operate properly because of third-party firmware, such as the photo-taking function of the camera. It may also cause device damage
4. Personal and confidential information on the phone may leak, and security compromised
5. The in-depth test may modify some of the system functions, and prevent you from updating the system version to enjoy the latest ColorOS
Second, read the steps below for the in-depth test
Preparation:
Realme 2 Pro - with 60%+ battery
1 x USB Cable
1 x PC/Mac
Step 1. Make sure you have backed up your data, unlocking your phone will erase all of your data
Step 2. Make sure your system version is the official and latest one
Step 3. Provide IMEI and sign up for the in-depth test via the link shared at the bottom of this post. The information will be reviewed by our staff, and the review will take approx 1-7 days. If your smartphone model and version are approved, you will receive an OTA package that supports the in-depth test. Install the OTA.
Step 4. Download and install the unlock tool apk on your phone:
https://download.c.realme.com/osupdate/DeepTesting_realme-release_signed.apk
Install it to apply for the bootloader unlock via the tool.
Step 5. Detailed steps to unlock the bootloader
#1. Open unlock tool.
#2. Click “Start applying”.
#3. Please read the disclaimer in detail, select the checkbox, and submit your application.
#4. The application will be checked by our server.
#5. Within approximately 1 hour, the unlock tool apk will show the status of unlocking - if it shows the unlocking is successful, please proceed to the following step.
#6. You can now click “Start the in-depth test” and press and hold the power key to reboot the device. You will then enter the fastboot mode.
#7. Download and install the fastboot tool on your PC or Mac (check this https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/), use a cable to connect phone and PC. In the Fastboot mode use the engineering command in the picture below to unlock.
#8. On your phone press the volume key to select “Unlock The Bootloader” and press the power key to confirm. The phone will reboot and enter in-depth test mode - all the user data on the phone will be cleared. We recommend you perform a data backup prior to applying
Bootloader appllication form link for the Realme 2 Pro:
https://goo.gl/forms/vDfXHNNt31j8ad5o1
FAQ
Q1: How to relock the bootloader?
#1. Download the unlock tool again to apply to exit in-depth test.
#2. Click “Apply to exit in-depth test” and press and hold the power key to reboot the device, and then you will enter the fastboot mode.
#3. In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
#4. Press the volume button to select the “Lock The Bootloader” option, and press the power key to confirm. The phone will reboot and exit the in-depth test mode, and clear all user data in the phone. We recommend that you perform a data backup prior to applying.
Q2: Are there any risks after unlocking the bootloader?
-> Please be aware that Realme cannot guarantee the full functionality, and will not be responsible, for any third-party unsigned custom ROM being flashed to your device after the bootloader is unlocked. An unsigned third-party custom ROM may not have gone through the thorough tests that we run for each device and software version that we release.
-> A third-party custom ROM may not work properly on your device, and certain functions and services may cease to work. The performance and device data may also be affected, and may damage the device permanently. In the worst case, unlocking the bootloader will cause physical injuries or material damage, for ex. due to the device overheating.
Q3: Will it affect future OTAs after unlocking?
The secure user data partition may also become inaccessible, and you will not be able to get any official software upgrades if you unlock the bootloader. Once re-locked the bootloader, users will receive official OTAs again.
Q4: Will it affect warranty?
Warranty will be fully applied to problems caused by Realme 2 Pro unlocking or flashing a custom ROM.
Q5: How to flash back the official ROM after installing a custom ROM?
Users need to go to a service center to flash the device - FREE of charge. We are developing a tool to flash a stock ColorOS. It will come in Q2 2019.
Q6: When other devices can get bootloader unlock?
Realme 1 will get bootloader unlock in Feb. Other devices are being
Q7: Where are the kernel sources?
https://github.com/sirwhanq/Realme-2-Pro-8.1-kernel-source
Link to original post https://c.realme.com/in/post-details/1085078965883764736
Click to expand...
Click to collapse
is that void guarantee?

I got stuck on Waiting for device.. nothing happens

worked like a charm. thanks!

FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed

CMD says Waiting for any device and nothing happens
I have done the whole process as described.
BUT when I enter this command - fastboot flashing unlock or ./fastboot flashing unlock
It says Waiting for any device and nothing happens
What mistake i'm doing
Please someone help me
Thank you very much in advance

RMX1807 unable to unlock bootloader
hari2897 said:
This post was originally written and posted by Alessio from Realme forums
Hello Realme Fans
Here's how to unlock the bootloader (called in-depth test in the tutorial) on your Realme 2 Pro.
First, please read the “Disclaimer” carefully
【Disclaimer】
1. After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you proceed
2. The in-depth test may have unforeseeable impacts on your phone
3. Some functions may not operate properly because of third-party firmware, such as the photo-taking function of the camera. It may also cause device damage
4. Personal and confidential information on the phone may leak, and security compromised
5. The in-depth test may modify some of the system functions, and prevent you from updating the system version to enjoy the latest ColorOS
Second, read the steps below for the in-depth test
Preparation:
Realme 2 Pro - with 60%+ battery
1 x USB Cable
1 x PC/Mac
Step 1. Make sure you have backed up your data, unlocking your phone will erase all of your data
Step 2. Make sure your system version is the official and latest one
Step 3. Provide IMEI and sign up for the in-depth test via the link shared at the bottom of this post. The information will be reviewed by our staff, and the review will take approx 1-7 days. If your smartphone model and version are approved, you will receive an OTA package that supports the in-depth test. Install the OTA.
Step 4. Download and install the unlock tool apk on your phone:
https://download.c.realme.com/osupdate/DeepTesting_realme-release_signed.apk
Install it to apply for the bootloader unlock via the tool.
Step 5. Detailed steps to unlock the bootloader
#1. Open unlock tool.
#2. Click “Start applying”.
#3. Please read the disclaimer in detail, select the checkbox, and submit your application.
#4. The application will be checked by our server.
#5. Within approximately 1 hour, the unlock tool apk will show the status of unlocking - if it shows the unlocking is successful, please proceed to the following step.
#6. You can now click “Start the in-depth test” and press and hold the power key to reboot the device. You will then enter the fastboot mode.
#7. Download and install the fastboot tool on your PC or Mac (check this https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/), use a cable to connect phone and PC. In the Fastboot mode use the engineering command in the picture below to unlock.
#8. On your phone press the volume key to select “Unlock The Bootloader” and press the power key to confirm. The phone will reboot and enter in-depth test mode - all the user data on the phone will be cleared. We recommend you perform a data backup prior to applying
Bootloader appllication form link for the Realme 2 Pro:
https://goo.gl/forms/vDfXHNNt31j8ad5o1
FAQ
Q1: How to relock the bootloader?
#1. Download the unlock tool again to apply to exit in-depth test.
#2. Click “Apply to exit in-depth test” and press and hold the power key to reboot the device, and then you will enter the fastboot mode.
#3. In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
#4. Press the volume button to select the “Lock The Bootloader” option, and press the power key to confirm. The phone will reboot and exit the in-depth test mode, and clear all user data in the phone. We recommend that you perform a data backup prior to applying.
Q2: Are there any risks after unlocking the bootloader?
-> Please be aware that Realme cannot guarantee the full functionality, and will not be responsible, for any third-party unsigned custom ROM being flashed to your device after the bootloader is unlocked. An unsigned third-party custom ROM may not have gone through the thorough tests that we run for each device and software version that we release.
-> A third-party custom ROM may not work properly on your device, and certain functions and services may cease to work. The performance and device data may also be affected, and may damage the device permanently. In the worst case, unlocking the bootloader will cause physical injuries or material damage, for ex. due to the device overheating.
Q3: Will it affect future OTAs after unlocking?
The secure user data partition may also become inaccessible, and you will not be able to get any official software upgrades if you unlock the bootloader. Once re-locked the bootloader, users will receive official OTAs again.
Q4: Will it affect warranty?
Warranty will be fully applied to problems caused by Realme 2 Pro unlocking or flashing a custom ROM.
Q5: How to flash back the official ROM after installing a custom ROM?
Users need to go to a service center to flash the device - FREE of charge. We are developing a tool to flash a stock ColorOS. It will come in Q2 2019.
Q6: When other devices can get bootloader unlock?
Realme 1 will get bootloader unlock in Feb. Other devices are being
Q7: Where are the kernel sources?
https://github.com/sirwhanq/Realme-2-Pro-8.1-kernel-source
Link to original post https://c.realme.com/in/post-details/1085078965883764736
Click to expand...
Click to collapse
i got this issue while trying to unlock the bootloader
(C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s)
please help me on this
thanks

stuck in fastboot
all command's are working and i m in fastboot mode but it's option are keep changing and not selectable. i got the command to unlock bootloader in my phone but i can't click in unlock bootloader it's keep moving to both option. please help asap thankyou....

Is it possible to unlock bootloader from android 10?
santor said:
worked like a charm. thanks!
Click to expand...
Click to collapse
Is that possible to unlock bootloader while on stock realme2 pro rom(droid 10)..

babu.123 said:
i got this issue while trying to unlock the bootloader
(C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s)
please help me on this
thanks
Click to expand...
Click to collapse
This is the thing that keep happening to me as well. I'm on Realme UI v.1
Please let me know what is happening anyone who knows. Thanks.

Can't enter to FASTBOOT
hari2897 said:
This post was originally written and posted by Alessio from Realme forums
Hello Realme Fans
Here's how to unlock the bootloader (called in-depth test in the tutorial) on your Realme 2 Pro.
First, please read the “Disclaimer” carefully
【Disclaimer】
1. After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you proceed
2. The in-depth test may have unforeseeable impacts on your phone
3. Some functions may not operate properly because of third-party firmware, such as the photo-taking function of the camera. It may also cause device damage
4. Personal and confidential information on the phone may leak, and security compromised
5. The in-depth test may modify some of the system functions, and prevent you from updating the system version to enjoy the latest ColorOS
Second, read the steps below for the in-depth test
Preparation:
Realme 2 Pro - with 60%+ battery
1 x USB Cable
1 x PC/Mac
Step 1. Make sure you have backed up your data, unlocking your phone will erase all of your data
Step 2. Make sure your system version is the official and latest one
Step 3. Provide IMEI and sign up for the in-depth test via the link shared at the bottom of this post. The information will be reviewed by our staff, and the review will take approx 1-7 days. If your smartphone model and version are approved, you will receive an OTA package that supports the in-depth test. Install the OTA.
Step 4. Download and install the unlock tool apk on your phone:
https://download.c.realme.com/osupdate/DeepTesting_realme-release_signed.apk
Install it to apply for the bootloader unlock via the tool.
Step 5. Detailed steps to unlock the bootloader
#1. Open unlock tool.
#2. Click “Start applying”.
#3. Please read the disclaimer in detail, select the checkbox, and submit your application.
#4. The application will be checked by our server.
#5. Within approximately 1 hour, the unlock tool apk will show the status of unlocking - if it shows the unlocking is successful, please proceed to the following step.
#6. You can now click “Start the in-depth test” and press and hold the power key to reboot the device. You will then enter the fastboot mode.
#7. Download and install the fastboot tool on your PC or Mac (check this https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/), use a cable to connect phone and PC. In the Fastboot mode use the engineering command in the picture below to unlock.
#8. On your phone press the volume key to select “Unlock The Bootloader” and press the power key to confirm. The phone will reboot and enter in-depth test mode - all the user data on the phone will be cleared. We recommend you perform a data backup prior to applying
Bootloader appllication form link for the Realme 2 Pro:
https://goo.gl/forms/vDfXHNNt31j8ad5o1
FAQ
Q1: How to relock the bootloader?
#1. Download the unlock tool again to apply to exit in-depth test.
#2. Click “Apply to exit in-depth test” and press and hold the power key to reboot the device, and then you will enter the fastboot mode.
#3. In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
#4. Press the volume button to select the “Lock The Bootloader” option, and press the power key to confirm. The phone will reboot and exit the in-depth test mode, and clear all user data in the phone. We recommend that you perform a data backup prior to applying.
Q2: Are there any risks after unlocking the bootloader?
-> Please be aware that Realme cannot guarantee the full functionality, and will not be responsible, for any third-party unsigned custom ROM being flashed to your device after the bootloader is unlocked. An unsigned third-party custom ROM may not have gone through the thorough tests that we run for each device and software version that we release.
-> A third-party custom ROM may not work properly on your device, and certain functions and services may cease to work. The performance and device data may also be affected, and may damage the device permanently. In the worst case, unlocking the bootloader will cause physical injuries or material damage, for ex. due to the device overheating.
Q3: Will it affect future OTAs after unlocking?
The secure user data partition may also become inaccessible, and you will not be able to get any official software upgrades if you unlock the bootloader. Once re-locked the bootloader, users will receive official OTAs again.
Q4: Will it affect warranty?
Warranty will be fully applied to problems caused by Realme 2 Pro unlocking or flashing a custom ROM.
Q5: How to flash back the official ROM after installing a custom ROM?
Users need to go to a service center to flash the device - FREE of charge. We are developing a tool to flash a stock ColorOS. It will come in Q2 2019.
Q6: When other devices can get bootloader unlock?
Realme 1 will get bootloader unlock in Feb. Other devices are being
Q7: Where are the kernel sources?
https://github.com/sirwhanq/Realme-2-Pro-8.1-kernel-source
Link to original post https://c.realme.com/in/post-details/1085078965883764736
Click to expand...
Click to collapse
At step #6. My phone is reboot and show a message in black sreen " Oppo Verify Pass - fastboot unlock_verify ok". I can't enter to Fastboot mode.
Please help me resolve this problem!!!

hari2897 said:
Bootloader appllication form link for the Realme 2 Pro:
https://goo.gl/forms/vDfXHNNt31j8ad5o1
Click to expand...
Click to collapse
Is this link still valid? I'm still waiting to see any updates after filling it up. The Google form link isn't provided at the original source for the write-up.
Hollow192 said:
You lazy liar
I am in vietnam and had sign up my phone imei last week Thursday (22nd Feb) but until now (1st March) i HAVEN'T receive any f***ing OTA for the unlock, do you know how excited i am thinking i finally can root my phone? Coloros rmx1807_11_a15 imei:862822042098610 give me the damn OTA now!!!!!!!!!
Click to expand...
Click to collapse
Well, I guess that answers my questions partially. Hope you guys followed up on this users request.

[17Jun20][Guide] [P/Q]How to root Note10/Note 10+ & Flash TWRP (Exynos only)

How to Root Samsung Galaxy Note 10+ & Flash TWRP (Exynos Only)
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Important : Since android Q, there is changes in rooting process, specially if you needs root with TWRP, So here I am dividing this guide in two parts.
1.Root with self preparing files (No TWRP) - Here you needs to patch stock files yourself. No TWRP installed.
2.Root with TWRP - You needs to just flash pre-patched files, Here you needs to have ROM installed same base as per files available. Though mostly latest verson will be available.
PART 1 : (Root Pie/Q base with magisk with patching files yourself, No TWRP)
Before moving to root device, must read every single instruction given below as any small mistake can lead to fail to achieve root or may brick the device.
A.Preparing Root files
You need to patch file to flash using Odin to root device.
1. Download stock firmware for your device (google search will give you many sites to download it) some common are e.g. Sammobile, Samfirmware tool)
you need to download file according your region and model (Dial *#1234# will give you details of existing firmware, download accordingly)
2. Once you finish download, extract files and keep all files on PC. From extracted files a file with name AP_[device_model_sw_ver].tar.md5 copy to your device.
3.Download Latest Magisk Manager and Install to your device
4.Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (AP_[device_model_sw_ver].tar.md5)
5.Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
6.Copy patched file magisk_patched.tar to Your PC
7.Download latest Odin (one is attached to end of this post) and extract to a folder on PC (I recommend on desktop)
Now next step is to modification on device
B. Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device
C.Installation (Flashing) custom binaries
1. Switch off the device and reboot to download mode (As said earlier) and select volume up to continue
2. Open Odin (downloaded from above instruction) as administrator
Select magisk_patched.tar file you have patched (as above instruction copied to PC) for AP tab of Odin
Select BL,CP and CSC file (Extract from stock firmware you have downloaded) with according respective tab of Odin (This is important, DON'T flash only magisk_patched.tar )
3.From Odin option - uncheck Auto Reboot option
4.Now start flashing and wait till it finish. When you see a PASS sign on Odin, disconnect device.
Now magisk is successfully finished but yet you need to follow instructions below.
D. Factory reset & Boot with magisk
After disconnecting device, keep holding Vol down + Side key to exit from download mode.
Here is very important - when you see device reboot As soon as the screen turns off, immediately press Volume Up + Side Key to boot to recovery partition. continue pressing the volume up button until you see the stock recovery screen.
In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
Select Reboot system now, and immediately press Volume Up + Side Key. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
The device will automatically reboot for the first time it boots. This is completely normal and done by design.After the device is booted up, do the usual initial setup. You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
PART 2 : (Root Q base with TWRP)
This requires to have your device on same base as per base of pre-patch files. I am giving link below of my ROM
http://www.mediafire.com/folder/d4ugie4yadxu6/N975F - Click link - First select your device (N970/N975/N976) - download file Instructions_Root_TWRP_BootloopFix.pdf
This file have complete details about how to root with stock recovery/TWRP. Also all required patched files will be available in "Q" folder of your device section,
Also "Q" folder have file BASE_N97*.txt - Name of this file indicates Model and base used for patched files, you should have same base installed.
Important :
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
For more details read Installation guide by @topjohnwu from Here
All credit and thanks go to
@topjohnwu for magisk & Guide.
geiti94 for TWRP Here OP & Source
ianmacd for latest TWRP - Here OP & Source
Happy rooting!
Xposed
Just tried and eDxposed working fine.
- Install EdXposed installer
- from magisk download install Ritu-core module
- from magisk download install Ritu - EDxposed (yahfa)
Done.
We strongly recommend to make EFS backup as soon as you root device and store it to safer place

Don't you lose some Samsung function when you root and even relock the bootloader?

MrPhilo said:
Don't you lose some Samsung function when you root and even relock the bootloader?
Click to expand...
Click to collapse
Who cares?
Development can't go without this.
We developer need to risk it. No way.

Nice, already patched the rom to flash with odin. What is the button combination for recovery ?
Did that for a friend of mine on the S10e, guess the steps are all the same ??

Nice, so you will start to make roms ?
Keep it coming :laugh:

optx said:
Nice, already patched the rom to flash with odin. What is the button combination for recovery ?
Did that for a friend of mine on the S10e, guess the steps are all the same ??
Click to expand...
Click to collapse
OP updated for combo key

dr.ketan said:
OP updated for combo key
Click to expand...
Click to collapse
Many thanks, now i just have to wait for the Note 10+ to arrive in a few hours :highfive:

dr.ketan said:
Who cares?
Development can't go without this.
We developer need to risk it. No way.
Click to expand...
Click to collapse
Waiting for your guide, twrp, magisk and so on...
I am not developer, just tester, but still need root...

Dr Ketan. Most Welcome My Bro. Follow you since Note 9. U rock my bro :good:

namfat said:
Waiting for your guide, twrp, magisk and so on...
I am not developer, just tester, but still need root...
Click to expand...
Click to collapse
Twrp not available and possible only after samsung release kernel source code. Great news is @ianmacd getting N10 who known for twrp development. :good:

dr.ketan said:
Twrp not available and possible only after samsung release kernel source code. Great news is @ianmacd getting N10 who known for twrp development. :good:
Click to expand...
Click to collapse
That's really good to hear.
With you and the guy you've mentioned we have everything we need.
Cheers!

Did you have the OEM unlock right away in Developer options ? Cant see it on mine...
First Phone ever that has no OEM unlock right away ...

dr.ketan said:
Twrp not available and possible only after samsung release kernel source code. Great news is @ianmacd getting N10 who known for twrp development. :good:
Click to expand...
Click to collapse
OK then, please share root instruction first.
I dont know if N10 have the same problem but it happened with latest base on S10 5G that only using stock recovery if need rooted.
optx said:
Did you have the OEM unlock right away in Developer options ? Cant see it on mine...
First Phone ever that has no OEM unlock right away ...
Click to expand...
Click to collapse
My device have OEM unlock option available. If you dont have, maybe you need to wait for 7 days.

OP Updated with full instruction about how to root.
Kindly go through detail before proceed.

I'm assuming this is for Exynos version ONLY?
No where do I see this prerequisite posted anywhere but has always been in the past.

cpufrost said:
I'm assuming this is for Exynos version ONLY?
No where do I see this prerequisite posted anywhere but has always been in the past.
Click to expand...
Click to collapse
I have added to title but prerequisite is having OEM unlock enable which I believe not having on snapdragon isn't?

dr.ketan said:
I have added to title but prerequisite is having OEM unlock enable which I believe not having on snapdragon isn't?
Click to expand...
Click to collapse
So far with the SD when you go into developer mode there is no OEM unlock and I doubt it will show up later.

Don't know what is wrong. I have OEM turned on, Downloaded latest magisk manager, flashed all 4 parts. It did not work. If I flash stock, all is fine. Any clues ?

Pinu'u said:
Don't know what is wrong. I have OEM turned on, Downloaded latest magisk manager, flashed all 4 parts. It did not work. If I flash stock, all is fine. Any clues ?
Click to expand...
Click to collapse
OEM lock should be turned off AFAIK

Thx, will give it a try after flashing back stock.Irritating that OP says turn on ...

[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware

First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile Stock 10.0.8 to Rooted Global Firmware.
Please take the time to read every step carefully. It'll explain a little bit as to the why behind some of the steps. PM me if I've missed anything.
This has been revamped as some of the steps are no longer required. Devices coming from 10.0.6 and below might have to try a different set of steps. Click here for the post with the old instructions
Requirements:
ADB setup and working
Global Fastboot ZIP Grab the latest version (10.0.8 as of 3/20)
For Root:
Magisk Canery apk
Modded-Boot.img From here or make your own pulling your own boot.img and using magisk to create a modded boot.img file
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin (could also be labeled unlock_token.bin) file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5a. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Global Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.
Code:
flash-all.bat
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 8 and try again.
10. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post).
You're done! Continue on if you want to root your device...
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
If you're interested in root:
11. Boot the device from the modded-boot.img file to give your self temp root. Once this is done, boot the device.
Code:
adb reboot bootloader
fastboot boot modded-boot.img
12. Install Magisk Manager Canary from here
13. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
14. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
15. Once that finishes it'll have you reboot the phone.
16. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post)
=-=-=-=-=-=-=-=-=-=-=-=
Shoutouts will go here soon.

nolimit78 said:
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. This will be a living first post as I'm currently not able to successfully get rooted. The idea of this thread is going from 100% T-Mobile Stock to Rooted Global Firmware. Once I can replicate and get root stable on my phone I will finalize this post. I will also add in shout outs to where I pulled this information from, both thread post and user, as it was through our group that I was able to piece this together. All this will be updated and make to look nice later.
The reason we flash to Indian and then Global is because if you don't, wifi/data and camera will be broken. I can't explain why it works, it just does.
Ok. Now to the good stuff. Please take the time to read every step carefully. It'll explain a little bit as to some of the why behind the steps. PM me if I've missed anything.
Requirements:
ADB setup and working
Global OTA ZIP (download from here)
Indian Fastboot ROM(download from here)
1. Unlock your bootloader. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!).
2. Move the Global Rom.zip file to the root of your OnePlus7T. It'll save you time later. Do this now or there's a later step where I give you the chance.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
4. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5. Reboot your phone into fastboot adb reboot bootloader
6. Extract the Indian Fastboot Rom folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img
7. Open CMD (with admin rights) and navigate to your ADB folder.
Mine would be-- cd c:\adb\
8. flash-all.bat
9. It will also ask you to wipe data. This is your call. If you followed Step 2, this will wipe out this file and you'll need to replace it once your phone has converted.
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says []. This is normal, just ignore it. Once everything settles, the device will reboot by itself. If it doesn't, start over and go back to Step 5 and try again.
10. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
11. You should have already moved the Global OTA to the root of the OnePlus 7t. If you haven't, do so now.
12. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
13. Select the Global OTA file and it'll start to flash from within the update app.
14. Once that finishes it'll have you reboot the phone.
15. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--==
This is where we should be able to root. Once I can verify getting this setup and replicate it I will continue with the tutorial. Hopefully, everyone who reads this will find it helpful.
Click to expand...
Click to collapse
I'm having a issue when inflash globel my phone stays on Indian firmware

Are we 100% sure that WiFi/Data/Camera will be broken if you just go straight to Global? Because just this morning I flashed from TMO 10.0.4 to Global 10.0.6 using the fastboot flashable ROM with perfect VoLTE/WiFi/Camera...
Also fully rooted!
Edit: Updated to 10.0.7, kept root via Magisk Manager install to inactive slot.

Reserved for old instructions. Going from 10.0.7 and up the instructions were changed and certain steps weren't needed, like flashing Indian before Global.
Keeping these here just in case someone purchases a phone with older firmware and doesn't want to wait updating to the latest version.
Requirements:
ADB setup and working
Global OTA ZIP (grab the 10.0.6 from here)
Updated 10.0.7 OTA Build from hereas well
Indian Fastboot ROM(grab the latest from here)
Pre-Rooted 10.0.6 boot.img file here
Magisk Canery apk
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Indian Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.
Code:
flash-all.bat
10. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 5 and try again.
11. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
12. Be sure to copy the Global OTA to the root storage of your OnePlus 7T. If you haven't, do so now.
13. Reboot the phone and boot the Modded-boot.img file from the bootloader
Code:
adb reboot bootloader
fastboot boot modded-boot.img
14. Once the phone boots up, you should now have temp root. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
15. Select the Global OTA file and it'll start to flash from within the update app. Let this finish before proceeding.
16. Install Magisk Manager Canary from here
17. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
18. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
19. Once that finishes it'll have you reboot the phone.
20. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
If you'd like to update to 10.0.7:
1. Download and move the OTA file for 10.0.7 to the root of your OP7T
2. Go to Settings > System > System Updates and look for the gear in the top right.
3. Select Local upgrade and select the update file for 10.0.7.
4. Let it run through and finish, don't reboot.
5. Open Magisk Manager
6. Update and select direct install to inactive boot partition to update.
7. Once this finishes, reboot and you're now on 10.0.7 rooted.
=-=-=-=-=-=-=-=-=-=-=-=

nolimit78 said:
Yup, tried to be slick by going straight to Global and ran into this problem. Data worked for me but Camera was super unstable and Wifi was the only solid no that I got. Required more research to discover that this issue is avoided by flashing the indian rom first.
Tell me more about this. What steps did you take to do this? I'm thinking that once you flash the global ROM to reboot, and then use the a image-new.img that boots a temp-magisk to then use magisk canary to install magisk on the inactive slot (should be a right?)
Click to expand...
Click to collapse
Hmm I'll watch and see if my Camera is unstable but it seems fine so far.
To root I flashed (not booted) a 10.0.6 Magisk patched boot img (fastboot flash boot patched_boot.img) that someone posted in the "how to patch boot with Magisk" thread and installed Magisk Manager Canary.
I used Oxygen Updater to local update to 10.0.7 (it says 10.3.0 because of a typo from OnePlus, see another thread. It says 10.0.7 in settings) but make sure to download the full 2gb update not the 200 something mb incremental one because it will fail.
Then when the update is done, don't hit reboot, go to Magisk Manager, make sure you're set to the Canary channel (unless you patched the boot img yourself with something else) and install and choose inactive slot. Then you can hit reboot in Magisk.

Perfect, means I was thinking correctly with an extra unneeded reboot. Updated info in OP.

Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-free-op7t-sim-unlocking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything

Once converted to Global oos, will it support Dual SIM?

ysfk7 said:
Once converted to Global oos, will it support Dual SIM?
Click to expand...
Click to collapse
Yes it will support dual SIM as long as you have the dual SIM tray.

rgreen83 said:
Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/one...cking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/one...us-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/and...ctory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything
Click to expand...
Click to collapse
FYI link to fastboot rom is broken.

Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
Sorry bout that, crosspost fail

Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
I clicked on it and it worked, but I didn't check through mobile. Can you show me what happens when you try?

There is no link to request unlock file from OnePlus. Also will regular global OTA updates work? Or will I have to manually update every time?

Will this work for McLaren 5g?

I just followed the instructions in post#7 and was able to do this successfully as well (direct Tmobile->Global, without the Indian version flash in between). Note that the phone will reboot sometime in the middle of the flash, do NOT manually go into the phone and reboot yet again, just wait for it to complete.

Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?

tkoreaper said:
Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?
Click to expand...
Click to collapse
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+

cm0002 said:
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+
Click to expand...
Click to collapse
i guess thats why i can unlock the bootloader and convert the Tmo 6T without asking the unlock_code.bin from oneplus. thank you kindly for the info

I got the unlock bin today I just flashed via fastboot received message the bootloader is unlocked, but the device status still states locked?

nolimit78 said:
...
4. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
...
Click to expand...
Click to collapse
So OEM Unlock button suppose to be OFF or ON?

[Guide] Root Galaxy A10 Magisk prenormal rmm/kg state (October Patch- later)

Hi All this is just a quick tutorial to help you all root your devices, on later firmwares
This 100% works ive done it over and over without any problems. I am currently on october patch latest firmware for my A105FN. As you may know Samsung have now added extra security meaning even if you have already unlocked your bootloader after you patch the firmware with magisk, flash patched firmware and reboot you will be greeted with that dreadfull message, Only official binaries allowed and your device will be locked and wont boot untill you reflash stock firmware again. The below will help get you out of the prenormal kg state, and save's you a 7 days waiting period as we dont have any TWRP available for our device at this time. Also note due to the extra security magisk cant be flashed with the whole firmware no more, as each time you flash the firmware your back at square 1.
Note: You will need 7-zip - google is your freind
1. Download odin: https://odindownloader.com/download/odin3-v3-13-3.
2. download the latest stock firmware for your device via SamMobile
3. Download latest Magisk Manager - https://www.google.co.uk/amp/s/forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/amp/
4. Flash latest firmware via odin and let device boot up and finish setting up.
5. Grab Your Firmware AP_A105FXXXX.tar.md5 remove the md5 so its a tar file makes it easier to work with. Copy it to your device storage.
6. Install latest magisk manager, and open check advanced settings to make sure recovery is checked, select install image / patch image and select the AP file you put on your device, magisk will patch and save as magisk_patched on your internal storage. Copy this back to your pc and extract it.
7. Download this https://forum.xda-developers.com/attachment.php?attachmentid=4818715&d=1568308074 thanks to @droidzer1 and extract the vbmeta.img.
8. Make a new folder on you pc it's temporary so you know where your files are. From the Ap magisk_patch.tar you extracted, copy the boot.img, recovery.img, and the downloaded vbmeta.img from step 7. And place them in the new folder you created, using your mouse select all 3 and right click select 7-zip add to archive, select tar format and name it magisk.tar.
9. Now we have all the files ready back to your device, if your bootloader is already unlocked skip this step and move to the next. For those that havent unlocked there bootloader go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it, if the OEM switch is not there proceed to step 10. If it is and you enabled it it might ask you to factory reset if not it will be this way to complete the unlock bootloader.......
switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode, long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
10. Remove any account you have on your device go to settings, look for time and date automatic time zones, turn it off and set date back 8 days from now (example 30th today change date to 22nd) restart device. Now go straight back into automatic time zones settings and turn it back on. Again reboot device, when device reboots turn it off. You can now enter download mode and it should say checking instead of prenormal that means you good to go. Those of you that had no OEM switch in developer mode please now check.... if it's there enable it and go back to step 10 unlocking bootloader then proceed to step 11.
11. Open odin and select in the ap tab the magisk.tar you created earlier. Plug in your usb whilst holding vol-up and vol-down together to boot into download, press vol-up to proceed. Press start on odin and soon as it finishes and device reboots and you see the bootloader message hold power and vol-up until into stock recovery, select wipe factory reset then select reboot device, this the same as soon as you see bootloader unlocked message hold power and the vol-up together this time count to 7.... and release. Phone wont boot it will go blackscreen and reboot, dont worry this is normal, again do the exact same at bootloader unlocked msg screen hold power and vol-up count to 7... release, now phone will boot and you can set it up.
Note: you will need to reinstall magisk manager and on 1st open it will ask do to additional setup, let it do its thing, then device will reboot,
Remeber every time your device reboots you will have to do the power and vol-up to boot system with root.
I hope this guide help you and a big thank you to @afaneh92 for his original guide

thnaks man
how do i install twrp?
if it is possible, can i flash GSI?

tttt7hhhhjjjk said:
thnaks man
how do i install twrp?
if it is possible, can i flash GSI?
Click to expand...
Click to collapse
No the twrp that was made for our device, wont work with new versions of magisk, or any newer firmware we are going to have to wait until the the new kernel source is released by samsung unfortunatly, its impossible to say when or if they do.... so its just root for now.

mikeyb123 said:
No the twrp that was made for our device, wont work with new versions of magisk, or any newer firmware we are going to have to wait until the the new kernel source is released by samsung unfortunatly, its impossible to say when or if they do.... so its just root for now.
Click to expand...
Click to collapse
thanks for the fast reply man :good:

I gave up rooting this phone, ended up bootloop 3 times and always has to flash it to get the phone working again

timba123 said:
Any chimeratool tricks for no oem unlocking in developer options? On a102u1
Click to expand...
Click to collapse
no.. chimera tool cant unlock the bl on usa variants

hello Thanks for this method but not working after install again magisk manager , say app magisk is not installed and not root
When I was creating the magisk_patch file with magisk manager go to advanced settings and check recovery mode
is it correct?

[SOLVED] Help Flashing Lineage OS

EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS

Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.

abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!

I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.

I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.

~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?

abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18

Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.

~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?

vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.

~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.

vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...

~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.

Develop Bugs

welcome