Database Develop

[Tutorial][How to] Unlock Bootloader and Install Custom Recovery and Root

Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
{
"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"
}
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.

Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.

littleromeo said:
Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.
Click to expand...
Click to collapse
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.

nice guide ..
but I guess "add adb and fastboot to system path " shall be made optional .. this will make guide little simpler and shorter ..

Hey
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??

tanuj123 said:
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??
Click to expand...
Click to collapse
I have used this method myself, but I am also the OP so.... :victory:

Iam in a weird situation , I did flash many times before but I dont know how it made my device like this ... THE PROBLEM IS WITH DRIVERS and also SDcard
First I unlocked my bootloader then flashed cm11 on it ( Which was on lollipop official) and I forgot to download gapps so in connected my phone to pc only to find my computer doesnt recognise my phone it make sound but nothing shows up I tried clicking MTP again and again but nothing happens , WHEN I TRIED ADB it shows no devices in the list , I took out the sd card to copy files manually and the sd card says its write protected ..... GUYS HELP @stirredo

What are you using to read your SD card on your computer?
If you are using SD card adapter, make the sure write lock is turned off.

Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging @stirredo
Sent from my Xperia P using XDA Free mobile app

Kaushik124 said:
Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging
Sent from my Xperia P using XDA Free mobile app
Click to expand...
Click to collapse
That is the same issue faced by me .

Saurabh K said:
That is the same issue faced by me .
Click to expand...
Click to collapse
Did you find any solution
Sent from my Xperia P using XDA Free mobile app

Not yet, but trying....
Sent from my Sparkle V

thanks for this awesome tutuorial.... But i have a problem in unlocking the tutorial
The problem is that how can i unlock my bootloader when oem unlocking is turned off...
Recently i tried to flash CM12.1 on my YU YUNIQUE YU4711 without turning on OEM unlocking and now I am stuck at the Fastboot mode so i cant start up my phone.... So i wanted to know that how i can unlock the bootloader when OEM unlocking is turned off..
PS- I cant even go to recovery moded
thanks in advance

Format Userdata
stirredo said:
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.
Click to expand...
Click to collapse
I did got stuck at bootloader when I dedn't format Userdata. Thanx for the tip.
---------- Post added at 03:01 PM ---------- Previous post was at 02:53 PM ----------
When I opened SuperSu after installing SuperSu through recovery, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
What do I do now?

stirredo said:
Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.
Click to expand...
Click to collapse
bro, my bootloader is already unlocked, so i was using the flash recovery command directly, and i was unable to flash recovery, everytime i go into recovery it opens stock recovery, what should i do to flash recovery now, no method is working, is it compulsary to unlock bootloader every time flashing recovery, mine is already unlocked, but cant able to flash recovery, please help ,its urgent.

I am on a custom ROM right now( Resurrection ) and have unlocked the bootloader
Can I relock the bootloader using Androidone tool
Will it format userdata?
Can I keep the Custom ROM after relocking?
Please help
Device-Mi-498

hi my device is not boot after restart.always need to run fastboot continue. have you any idea how to resolved ?

my phone showing device not found error in ADB driver installer. actually phone is unable to start, it is continuously looping in start logo

is the fastboot format userdata command required? what will happen if i fail to issue the fastboot format command following fastboot oem unlock command?

hello i want the unlocked bootloader file for my Micromax e313 please send me the link to get it please help me

Moto E5 XT1944-3 Nora, is there a way to root?

I've checked the forum beforehand to see if there's a way to root, and yeh, there is, but a lot of them say "XT1944-2 and XT1944-4 only" but mine is XT1944-3 and honestly I'm afraid i'll ruin my phone, I've been rooting my phones since 2014ish but this has to be the most complicated phone I'd ever have to deal with, I love it the way it is but I just miss root and xposed a lot, please

andienchancer said:
I've checked the forum beforehand to see if there's a way to root, and yeh, there is, but a lot of them say "XT1944-2 and XT1944-4 only" but mine is XT1944-3 and honestly I'm afraid i'll ruin my phone, I've been rooting my phones since 2014ish but this has to be the most complicated phone I'd ever have to deal with, I love it the way it is but I just miss root and xposed a lot, please
Click to expand...
Click to collapse
Try this -- even in the event it doesn't work, it is virtually completely safe and runs no risk of bricking your device. First, of course, you will need to unlock your device's bootloader. If you haven't already done so, let me know and I can provide you some guidance. Visit this link for instructions and support on unlocking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Next, download a recent firmware package for your device. You can find one at http://mirrors.lolinet.com. Extract the boot.img file from the package and save it to your device. On your device, download the Magisk Manager application. Select install, then select the "Patch Boot Image" option, and navigate to the saved boot.img file. Once Magisk patches your boot image, save the patched image to your PC or laptop in your adb/fastboot directory (assuming you have adb/fastboot set up on your PC. If not, see my link at the end of this post to download it. Also, if you haven't done so, install the latest Motorola Device Manager on your PC from Motorola's official website. It will ensure that current USB device drivers are installed on your PC/laptop. Visit this link to download the latest version: https://support.motorola.com/us/en/solution/MS88481 ). Now boot your device into fastboot mode, connect your device to your PC, open a command window in your adb/fastboot path, and execute this command:
fastboot devices
If you are properly connected, an alphanumeric string will be returned via the command window, which is your device serial number. Now execute these fastboot commands:
fastboot flash boot patched_boot.img
fastboot reboot
** NOTE: It is completely normal for your device to boot loop a couple of times during the initial boot sequence. This shouldn't occur during the second and subsequent boots.
Upon reboot, open the Magisk Manager app again and you should have systemless root installed. If, however, anything goes south and you get stuck in a boot loop, you can always save face by flashing the stock boot image from the firmware package by:
fastboot flash boot boot.img
fastboot reboot
This exact method has been confirmed to achieve systemless root on a number of the Moto E5, E5 Plus & E5 Play variants, without the need for installing TWRP custom recovery. In essence, if your device has an unlockable bootloader, this should work.
Minimal ADB & Fastboot v1.4.3: https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk

It gives me bootloop, can I do it flashing twrp and the zip file?

reserved

Moto E5 XT1944-3 Nora solution
andienchancer said:
It gives me bootloop, can I do it flashing twrp and the zip file?
Click to expand...
Click to collapse
i can find solution in this post, just install twrp until, password encryption dont show.

LenovoTech said:
Try this -- even in the event it doesn't work, it is virtually completely safe and runs no risk of bricking your device. First, of course, you will need to unlock your device's bootloader. If you haven't already done so, let me know and I can provide you some guidance. Visit this link for instructions and support on unlocking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Next, download a recent firmware package for your device. You can find one at http://mirrors.lolinet.com. Extract the boot.img file from the package and save it to your device. On your device, download the Magisk Manager application. Select install, then select the "Patch Boot Image" option, and navigate to the saved boot.img file. Once Magisk patches your boot image, save the patched image to your PC or laptop in your adb/fastboot directory (assuming you have adb/fastboot set up on your PC. If not, see my link at the end of this post to download it. Also, if you haven't done so, install the latest Motorola Device Manager on your PC from Motorola's official website. It will ensure that current USB device drivers are installed on your PC/laptop. Visit this link to download the latest version: https://support.motorola.com/us/en/solution/MS88481 ). Now boot your device into fastboot mode, connect your device to your PC, open a command window in your adb/fastboot path, and execute this command:
fastboot devices
If you are properly connected, an alphanumeric string will be returned via the command window, which is your device serial number. Now execute these fastboot commands:
fastboot flash boot patched_boot.img
fastboot reboot
** NOTE: It is completely normal for your device to boot loop a couple of times during the initial boot sequence. This shouldn't occur during the second and subsequent boots.
Upon reboot, open the Magisk Manager app again and you should have systemless root installed. If, however, anything goes south and you get stuck in a boot loop, you can always save face by flashing the stock boot image from the firmware package by:
fastboot flash boot boot.img
fastboot reboot
This exact method has been confirmed to achieve systemless root on a number of the Moto E5, E5 Plus & E5 Play variants, without the need for installing TWRP custom recovery. In essence, if your device has an unlockable bootloader, this should work.
Minimal ADB & Fastboot v1.4.3: https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk
Click to expand...
Click to collapse
LenovoTech said:
Try this -- even in the event it doesn't work, it is virtually completely safe and runs no risk of bricking your device. First, of course, you will need to unlock your device's bootloader. If you haven't already done so, let me know and I can provide you some guidance. Visit this link for instructions and support on unlocking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Next, download a recent firmware package for your device. You can find one at http://mirrors.lolinet.com. Extract the boot.img file from the package and save it to your device. On your device, download the Magisk Manager application. Select install, then select the "Patch Boot Image" option, and navigate to the saved boot.img file. Once Magisk patches your boot image, save the patched image to your PC or laptop in your adb/fastboot directory (assuming you have adb/fastboot set up on your PC. If not, see my link at the end of this post to download it. Also, if you haven't done so, install the latest Motorola Device Manager on your PC from Motorola's official website. It will ensure that current USB device drivers are installed on your PC/laptop. Visit this link to download the latest version: https://support.motorola.com/us/en/solution/MS88481 ). Now boot your device into fastboot mode, connect your device to your PC, open a command window in your adb/fastboot path, and execute this command:
fastboot devices
If you are properly connected, an alphanumeric string will be returned via the command window, which is your device serial number. Now execute these fastboot commands:
fastboot flash boot patched_boot.img
fastboot reboot
** NOTE: It is completely normal for your device to boot loop a couple of times during the initial boot sequence. This shouldn't occur during the second and subsequent boots.
Upon reboot, open the Magisk Manager app again and you should have systemless root installed. If, however, anything goes south and you get stuck in a boot loop, you can always save face by flashing the stock boot image from the firmware package by:
fastboot flash boot boot.img
fastboot reboot
This exact method has been confirmed to achieve systemless root on a number of the Moto E5, E5 Plus & E5 Play variants, without the need for installing TWRP custom recovery. In essence, if your device has an unlockable bootloader, this should work.
Minimal ADB & Fastboot v1.4.3: https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk
Click to expand...
Click to collapse
I can confirm that the procedure works for Moto E5 Play XT1920-18.

Lenovo A7020a48/Vibe K5 note [LP/MM]ROOT 10000% Success

ROOT Vibe K5 Note LP or MM​
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device/software.
* Same statement for XDA.
*/
Finally I got the method to root Lenovo Vibe K5 Note/A7020a48. If you are the one who is tired of searching how to root your device then you are at right place
But before we get started here are the things that you need (only for marshmallow user, lollipop user need only 1 thing which is given in method section)
Requirements​
1. Your Device (of course)
2. Your Current Stock Rom's Firmware(You can easily get it in firmwarefile.com)
3. A Working PC (first check whether you can successfully connect your device to your pc or not)
4. ADB and Fastboot Tools
5. A working Brain
BONUS:-You can use this method to root any (5.1+) device (if it has general unlocking system, This method is supported by 95% devices).
Now It's Time To Rock
METHOD for Lollipop users​
Download and install kingroot, open it and follow the tutorial given in that app
METHOD for Marshmallow Users​
1. Make complete backup of your data, Everything except ext. storage of your device will be erased.
Now Follow the steps from 2 to 11 to unlock bootloader (you can skip it if you already unlocked it)
2. Go to your phone settings>About phone, tap on build no. 7 times and then go back you will see a new { } developer option just above the about phone option
3. Go to developer option and enable OEM unlocking and USB Debugging
4. Connect your device to your pc and install adb and fastboot tool system wide
5. Open command prompt or power shell
Note- Windows 10 users have to write .\ as prefix before every command.
6. Type
Code:
adb devices
You will see a prompt on device, just click on always allow this computer and press ok or allow whatever given there. You will see your a long set of random Numbers and letters after that if its written device then your phone is successfully connected to your pc.
7. After that type
Code:
adb reboot bootloader
Your phone will reboot into bootloader mode
8.Type
Code:
fastboot getvar all
There you see at last some lines which tells you about your bootloader status if you see Unlocked = no then your bootloader is locked and if it says Unlocked = yes then it is unlocked and if it is unlocked then you can stop here
Now for those who has a locked bootloader
9. Type
Code:
fastboot oem unlock
(In some devices which is shipped with android 6.0 or higher you may have to write fastboot flash unlock don't write this command for your Vibe K5 note/A7020a48)
10. Most Important step Type
Code:
fastboot format userdata
. If you skip this you may get bootloop (I skipped that and got bootloop)
11. Type again
Code:
fastboot getvar all
Now you will see Unlocked=yes and Congrats!!! you has unlocked your phone's bootloader
12. Disconnect your device and press and hold power button until it reboots
Now follow the steps to root your device
13. Now from your stock firmware file extract boot.img which is given in the folder named firmware and copy it any where in your device
14. Install magisk manager from here -> Official website
15. After opening the app you'll see it is written that Magisk not installed click on the install button and select patch boot.img option,
16. Now select your boot.img file which you have extracted from your firmware file. After selection it will start to patch that boot.img and store patched_boot.img file in download folder of your device internal storage, copy that file at any folder in your pc (not in desktop)
17. Now go to the folder where you copied that patched_boot.img file and press right click on your mouse while holding shift button of your keyboard (Shift + Right click in simple words) and you will see an additional option of open command window/powershell here click on that and connect your device with your pc.
18. Before getting started with commands follow step 2 and 3 again
19. Repeat step 6 and 7
20. After going into bootloader mode Type
Code:
fastboot flash boot patched_boot.img
(in this code boot is partition and patched_boot.img is file name which you are going to flash).
21. Disconnect your phone ,press and hold powerkey until it reboots
Congrats Device ROOTED!!!​

#reserved

But there's a much simpler method to get root access with a single click. i cant able to attach photos.

did not work
Shubham1815 said:
#reserved
Click to expand...
Click to collapse
bro after entering the cmd fastboot oem unlock my lenovo vibe k5note displayed
fastboot mode
unlock not allowed
now what should i do ......plz help

Tried but not work for MM. The bootloader cannot be unlocked. Maybe your bootloader is different from the others, would you share it out?

mihir999 said:
bro after entering the cmd fastboot oem unlock my lenovo vibe k5note displayed
fastboot mode
unlock not allowed
now what should i do ......plz help
Click to expand...
Click to collapse
Do you enabled allow oem unlocking?

Shubham1815 said:
Do you enabled allow oem unlocking?
Click to expand...
Click to collapse
I enabled oem unlocking but still it shows "unlock not allowed"

Does this really works?? I want to try it

Did you actually unlock bootloader and root the device ? As far I know, in all other threads, none has confirmed any method.

After "fastboot getvar all" command, nothing happens. (PC => waiting for device.. PHONE => stuck at "Fastbood Mode"text)
Same for "fastboot oem unlock" command
I really want to permanent root for => LENOVO K5 NOTE (a7020a48). Years gone but no luck !
If your method is true then please answer us :crying:

Got stuck at "Unsupportive project for unlock" on my vibe K5note. Any help here please?

so . for those who are stuck at fast boot try and install the driver from this link :
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
this didn't work for me and i had to download and install "rescue and smart assistant" from the lenovo website
Rescue and Smart Assistant (RSA) - Lenovo Support AU
support.lenovo.com
once downloaded and installed , i could update the "Android" driver from device manager --> selecting the moto interface (not the composite one) instead the google one ( step by step : youtube.com/watch?v=nQjg6ePnGAc )
Once that's done , reboot to fastboot via adb
Now when I type fastboot devices I can finally see my device
however... i was getting " (bootloader) Unsupportive project for unlock "
no luck . . .
Edit:
if you however do have an OTG cable maybe try this method :
GitHub - BiltuDas1/unlock-Bootloader: Unlock Bootloader of any Device using PC or Android.
Unlock Bootloader of any Device using PC or Android. - GitHub - BiltuDas1/unlock-Bootloader: Unlock Bootloader of any Device using PC or Android.
github.com
good luck

any luck guys!?!?! or should i completey give up )

[GUIDE] How to unlock bootloader in the Moto E6 Plus + Install TWRP, with Windows and Linux

Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device,
* I will laugh at you.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
Links of download at the end of the post.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK WITH WINDOWS
Prerequisites:
A computer with Windows (bruh)
ADB and Fastboot installed
Have installed the device drivers to be detected in fastboot mode.
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.​​Now it only remains to flash the GSI.​
​
Spoiler: PROCESS OF THE UNLOCK WITH LINUX
Prerequisites:
A computer with Linux (bruh)
ADB and Fastboot installed
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still.
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.​​Now it only remains to flash the GSI.​
​If you don't know which GSI to try first, I recommend one from Phhusson, Ermitain or Andy.
NOTE: The system will be encrypted, and in this build of TWRP the encryption is not support so the files of internal storage will appear with numbers and letters random, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
NOTE 3: The GSI architectures for each variant are: A64 AB for 32/2 and ARM64 AB for 64/4.
NOTE 4: If you are going to flash a GSI with GApps you will first have to flash a vanilla Phhusson GSI and start in it, after that you have to flash the GSI with GApps WITHOUT wipes and you can use it normally
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1916 version)
ADB and Fastboot (Windows only): https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/drive/folders/19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-?usp=sharing
Credits:
@eluallen to do the first guide of how to unlock the bootloader and vbmeta file.
@Siddk for the recovery.
@LichtEstarossx for lk file and give some development to pokerp ;-;.

Fastoh said:
Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device,
* I will laugh at you.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK IN WINDOWS
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI
If you don't know which try first with the GSI of Phhusson or Lineage of Andy
Spoiler: PROCESS OF THE UNLOCK IN LINUX
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI.
if you don't know which try first with the GSI of Phhusson or Lineage of Andy
NOTE: The system will be encrypted, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1924 version)
ADB for Windows: https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/folderview?id=19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-&usp=sharing
Click to expand...
Click to collapse
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help

ShotRomsS6edge said:
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help
Click to expand...
Click to collapse
Ahí te dice en la imagen, las GSIs compatibles son las que son A64 xd // There it tells you in the image, the compatible GSIs are those that are A64 xd

Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.

simbanono said:
Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.
Click to expand...
Click to collapse
What is missing are the drivers, try to download them from this link (is the link that came in the flash tool zip xd): https://androiddatahost.com/276a2

Fixed already ty

.

somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c

cyanogenmodricky said:
somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c
Click to expand...
Click to collapse
mmmmm, maybe downgrading to the oldest firmware version you can find

Fastoh said:
mmmmm, maybe downgrading to the oldest firmware version you can find
Click to expand...
Click to collapse
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c

cyanogenmodricky said:
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c
Click to expand...
Click to collapse
try the version of sp flashtool that uses LMSA
in the log it says which version

Fastoh said:
try the version of sp flashtool that uses LMSA
in the log it says which version
Click to expand...
Click to collapse
ohh ok, i will try it and i tell you if works :3

well i get make downgrade to the lowest version i found, now i can't unlock the bootloader with
fastboot flashing unlock_critical
it gives me "waiting device" :c
edit: i install adb, fastboot and moto drivers, now when i wirte fastboot flashing unlock appears "unknow command"

hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version

Alejandro2810 said:
hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version
Click to expand...
Click to collapse
what SO do you use? windows or linux? because in windows the fastboot mode did not work either ;-;

Fastoh said:
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Click to expand...
Click to collapse
But... How remove battery if this not removable?..

Mortyk said:
But... How remove battery if this not removable?..
Click to expand...
Click to collapse
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus

Fastoh said:
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus
Click to expand...
Click to collapse
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?

Mortyk said:
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?
Click to expand...
Click to collapse
mmmm, look first trying with lmsa to have as it tells you to do the firmware re-installation, then do the same steps you did in the LMSA but in the flashtool

If you want to downgrade you have to do it with the firmware of the e6s because if you do it with the e6 plus your phone will have birck.

How To Guide (Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet

Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Warning
As stated by @beatbreakee , do not flash anything on a T-Mobile related device.
Please read beatbreakee's comment regarding this.
Warning
This has only been tested on Android 13. This guide may not work for other Android versions.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Android 13
Spoiler: Step 1 - Unlocking Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"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"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Spoiler: Step 2 - Flashing TWRP
Step 2 - Flashing TWRP:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
This is not a bootable image. You must flash. fastboot boot img will not work
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.img
Code:
fastboot flash recovery_b twrp.img
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Spoiler: Step 3 - Flashing Magisk
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
5. Tap System
You should now enter the device
3.C - Installing Magisk APK
Install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Spoiler: Fixing Data Backup [Optional]
If you encounter a createTarFork() exited with error 255, do the following:
1. Reboot into TWRP
2. Select File Manager
3. Navigate to /data
4. Copy /data/fonts into /sdcard/
5. Copy /data/nandswap into /sdcard/
6. Delete /data/fonts
7. Delete /data/nandswap
The error should now be resolved
The deleted files should not cause any issues. If any issues do occur, then promptly restore them using the backups made to /sdcard/.
Spoiler: Bypassing Safetynet [Optional]
Step - Bypassing Safetynet:
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
F - Test Safetynet
1. Install YASNAC
2. Grant Super User rights
3. Select "Run Safetynet Attestation"
If both checks pass, you successfully have passed Safetynet!

PlasmaTornado said:
Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings -> About -> Tap on Build Number 7 times
2. Open Developer Settings
3. Enable OEM Unlocking
4. Enable Android Debugging Bridge (ADB)
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
View attachment 5792895
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot oem unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Then finally:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Step 2 - Flashing TWRP Image:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
! It is HIGHLY recommended that you boot into the twrp.img before flashing to ensure that TWRPworks . I did not, but I recommend you do. !
To test this, enter the following command:
Code:
fastboot boot twrp.img
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.image
Code:
fastboot flash recovery_b twrp.image
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
You should now enter the device
3.C - Installing Magisk APK
If for some reason the Magisk Installer did not install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Click to expand...
Click to collapse
Good post but one problem...to unlock is " fastboot flashing unlock"

Canuck Knarf said:
Good post but one problem...to unlock is " fastboot flashing unlock"
Click to expand...
Click to collapse
Of course! Thank you, used to the old way of unlocking

I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?

kouzelnik3 said:
I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?
Click to expand...
Click to collapse
Following the method created by @dladz should still work perfectly fine!
There could still be issues with this TWRP as this is not an official image.
AFAIK Switching ROM is still untested, but decryption, backups and flashing are all confirmed working, which for me makes me feel significantly more comfortable

I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!

kouzelnik3 said:
I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!
Click to expand...
Click to collapse
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!

PlasmaTornado said:
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!
Click to expand...
Click to collapse
I will try factory wipe...flash flash from 2213...to 2215...might work

Canuck Knarf said:
I will try factory wipe...flash flash from 2213...to 2215...might work
Click to expand...
Click to collapse
Fantastic news. Let us know the results!

i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. AND my 10T and 10 Pro BOTH have been fully bricked, then formatted and flashed thru an authorized MSM Account.... Doing an ERASE ENTIRE FILE SYSTEM, thru msm, did not get rid of this file, so i doubt a twrp level wipe will do it either... MAYBE an "unlock Critical" in Fastboot, followed by a "Fastboot wipe", "DM-verity disable", and "VB-Meta erasure" MIGHT take out this crazy security system, but i know this .... if you flash an original FW using TWRP, it has protections in it to keep IT (twrp) from being overwritten, so you might find yourself in bootloop territory if you region hop.... cuz the fw might notice the changes to the partitions... For now, until someone is brave enough to challenge the Android 12 kernel and remove these trapdoors, I would just be happy you have TWRP, and wait for the person who finds and slays the Tmobile Dragon hidden in our phones! But this is truly an android 12 function that was put in place for Carrier and Manufacturer benefit ONLY. Another strike against 1+

beatbreakee said:
i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. So this is truly an android 12 function that was put in place for Carrier benefit ONLY. Another strike against 1+
Click to expand...
Click to collapse
Absolutely despicable and such an anti-consumer technique.
This stands against everything OnePlus was. It's sad to see OnePlus turn into such an anti-developer phone
A Carrier should never have this much power over a device. It is absurd

heres a google drive link to my account if anyone wants to see a video of what you will go thru if triggered!
feel free to share or re-upload the link/video to anywhere... ppl need to know this is happening thanks to Tmobile and Oneplus collaboration. I have not seen any reference to another carrier inside any of the device policy files, and my phone was restored to a NON TMO branded build of android 12 for the 2217 NA model, so it should NOT have even recognized the TMO policies cuz i even used a new sim card after the MSM Unbrick, and it still instantly locked in less than a second of plugging it in... heres the vid
https://drive.google.com/file/d/17H6YpGrUCe1Y7PoFji4gperdpTHNX5AI/view?usp=sharing

also everyone should know, that EVERY fw on the internet no matter whether it is labeled, 2213, or 2215... 2217, as well as 2413-2419 ALL have EVERY other model's manifest built in and all of the restrictions / bloatware that each region comes with, saved into the OFP extracted files.... so there really is nothing that expressly was bricking your phones by simply flashing a different labeled FW..... the brick came from the manifest reading the region identifiers that the manifests are labeled under.... it is a file that is again picked by some random hidden check inside the TMO EFS, and as soon as your phone tries to boot the newly flashed FW, the TMO Lock is what bricks your phone, to either a bootloop state, or if you continue to force a flash by using Fastboot , you will have a non responsive phone, thanks to this stupid security issue. If unresponsive, the only way out is MSM Tool... and i can help you locate your test points if your buttons dont work.
I cannot publicly post a picture nor a description of where the test points lie inside the 10T , because i already got a cease and desist letter from BBK and i dont know if they have said anything to the mods here about posting Undisclosed hardware access points.... but ive been a member here almost 10 years, and i aint risking a ban from a tattle tale company! There are test points on the 10 t though,.. just well hidden!
The 2nd pic is of the 2217 Unpacked OFP , yet the build prop shows a 2210-2211 base in one and a 2413-2415 base in the.... with NO 2217 in either prop,or manifest file, yet when my phone was flashed back from Brick status, THIS is the FW that was used, and my phone identifies as a 2217 NA now..... can oneplus be any more clear that they have completely turned against us, by straight SHOWING US that they are being super cryptic and sneaky in something as common as the BUILD.PROP files?!?

The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?

kouzelnik3 said:
The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?
Click to expand...
Click to collapse
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )

Canuck Knarf said:
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )
Click to expand...
Click to collapse
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.

kouzelnik3 said:
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.
Click to expand...
Click to collapse
Yeah i hear you but I'm not sure if this a bootable version or a just install version....I will try it on mine to see if i get the same as you

Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works

Canuck Knarf said:
Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works
Click to expand...
Click to collapse
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?

kouzelnik3 said:
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?
Click to expand...
Click to collapse
It appears the image is not bootable. As stated, this is the one thing I didn't try.
I have amended the guide. Thank you