Develop Bugs

[Guide] Unlock/Root/Update/Relock for BQ Aquaris X2 pro (zangyapro)

Introduction
I'm writing this thread to summarize useful information about the BQ Aquaris X2 pro such as:
preliminary actions (adb and fastboot configuration)
unlocking the bootloader
flash a factory image
root the device (currently without TWRP)
updating the device without losing root
relocking the bootloader
I own this phone since July 2018. I started writing my notes in August 2018 in the form of a Google document (link here). I shared this document with some telegram groups and some people I know.
Now I that I think it can be more useful to summarize all my notes here on XDA so that all interested people can access it.
DISCLAIMER:
By attempting any of the processes listed in this thread you accept full responsibility for your actions. I have no responsibility about your actions.​
1) Preliminary actions
1.1) Developer options, USB debugging and Unlock OEM
The first thing you need to do is to enable Developer options, USB debugging and Unlock OEM. Hence:
enable “Developer options” by hitting 7 times on the build number (Got to settings --> about phone)
enter the new menu “Developer options” and,
enable “USB debugging”
enable “Unlock OEM”
1.2) Download and configure abd and fastboot
All steps listed in this guide will require the use of Google Platform tools. I suggest the use of the one provided by Google here: https://developer.android.com/studio/releases/platform-tools.
Download the one for your operating system:
View attachment 4655394
Be sure that your terminal can access adb and fastboot from every position by configuring the PATH. I'm use to configure the PATH on the fly when I need it. As I said before, I work on Linux/macOS where you can set the PATH by:
opening a terminal and running:
Code:
export PATH=$PATH:path_to_platform_tools
2) Unlock the bootloader
Unlocking the booloader will wipe your phone. So backup your data first.
The good news here is that this phone can be handled like a Nexus/Pixel phone. Therefore, the procedure to unlock the bootloader is straightforward:
do all stuff at point 1.1 and 1.2
open a terminal
plug your phone to the PC
reboot into the bootloader
Code:
adb reboot bootloader
run the code:
Code:
fastboot flashing unlock
now you have to wait until your phone reboots. It takes a while, don't panic!!! When the phone is on the initial screen turn it off and reboot into the bottloader again by holing 'power + volume down'.
run the code:
Code:
fastboot flashing unlock_critical
it's done. Your bootloader is completely unlocked. Now, you only have to wait again for the reboot.
3) Flash a factory image
As you probably know, BQ releases a factory image at each update at this link factory images. Factory images are very useful to perform a very clean install. Are you experiencing some issues with your phone and none of the trick you tried solved it? If it is a software issue a clean flash with a factory image will likely remove the issue.
Keep in mind that by flashing a factory image you will wipe also the userdata partition. So backup your data first. Now let's see how to flash the factory image:
you need an unlocked bootloader (see previous sections)
download the factory image from this link
unzip the archive
open a terminal at this folder
be sure to have abd and fastboot properly configured (see previous sections)
run the script to flash all (*):
Code:
./sdm660_fastboot_all_images.sh
wait the end of the process. The phone will reboot.
(*) on Windows you have to deal with the file sdm660_fastboot_all_images.bat. I suppose it's similar but I've never done it on Windows.
4) Obtain ROOT privileges
Nowadays, the most common tool to obtain root privileges is Magisk. Many people here know very well what Magisk is and how to install it with TWRP. However, TWRP is not yet ready for BQ Aquaris X2 pro, hence, we must follow the procedure for installing it without the custom recovery.
When I wrote the document in August I find very informative this guide by @nathanchance. It's for the pixel 2XL but, as I told you before, it works perfectly also for the BQ Aquaris X2 pro (zangyapro). So here I summarize what @nathanchance already posted. All credits must go to him.
Here you have the steps:
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Please note that it exists also a specific thread where the author also provides the patched boot.img files for download. Hence, you can start from point 6 without patching the boot.img by yourself. Take care of selecting the right one. Here you have the thread link.
5) Update the ROM without loosing root
To the best of my knowledge, the only way to update keeping root is by using the factory images provided by BQ.
Download the factory image of the latest firmware (link)
Extract the file zip and upload the file boot.img on your phone
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt and then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Place the file patched_boot.img in the folder of the BQ firmware unzipped at point 2
Make a copy of the file sdm660_fastboot_all_images (.sh in Mac/Liux and .bat on Windows).
Rename the file, I called it sdm660_fastboot_upgrade.sh
Change the following lines (this will preserve root privileges on your phone):
Code:
fastboot flash boot_a boot.img # <-- delete this line
fastboot flash boot_a patched_boot.img # <-- add this line
Delete the following line (this will prevent your data to be wiped):
Code:
fastboot flash userdata userdata.img # <-- delete this line
Run from your terminal
Code:
./sdm660_fastboot_upgrade.sh (or bat)
I think that one can also update using the OTA. This will make you lose the root privileges and therefore, you will have to repeat the procedure at section 4. I've never tested this so, if you decide to do it, you are on your own.
6) Relock the Bootloader
By relocking the bootloader you will lose all your data, hence, backup them first.
To relock the bootloader you only need the following commands:
Code:
fastboot flashing lock_critical
fastboot flashing lock
Each command will wipe your data and will reboot the phone. Be patient waiting for the reboot and do not panic.

Reserved.
(work in progress)

First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
3. Open Magisk Manager and click the Install button.
Click to expand...
Click to collapse
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
with this I can patch the boot image successfully
But unfortunately I can not run the "sdm660_fastboot_upgrade.sh.bat" it does not recognize my device.
When checking the commands in the batch I found that my device is acting really strange, sometimes giving different errors for the same command like:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
Setting current slot to 'a'...
FAILED (remote: Invalid Slot)
finished. total time: 0.004s
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
also strange:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot flash boot patched_boot.img
target didn't report max-download-size
sending 'boot' (50749 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...

raudidroid said:
First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
Click to expand...
Click to collapse
Thanks. I was not aware of this. And now I can't check this on my device because I started using GPay and I prefer to stay with no root and locked bootloader.
Maybe I will play again with the bootloader when TWRP for this device will be released. If it will

got it running!
raudidroid said:
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...
Click to expand...
Click to collapse
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Short moments of panic due to boot-loop included (I flashed a defective boot image [vmware drag and drop files obviously did not copy the whole file] )
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)

Hey @raudidroid, when I answered to you the first time I did not read all the message or you edited it later. Only now I'm reading the issues you faced.
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Click to expand...
Click to collapse
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)
Click to expand...
Click to collapse
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.

luk.giak said:
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Click to expand...
Click to collapse
I was using CMD / Command Prompt on win10, but maybe I have to many ADBs/Drivers/... installed. got a really weird behavior...
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
Click to expand...
Click to collapse
without root it wouldn't work, i got "no permissions (user in plugdev group; are your udev rules wrong?)"
with root everything ran smoothly
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.
Click to expand...
Click to collapse
Oh! Yep, that sounds like it would have been the better way to do it
Thanks for your post and your answers.
BTW: half-OT do you know any way to get netflix running after the rooting?

For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.

AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.
Click to expand...
Click to collapse
Your welcome!

For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.

AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.
Click to expand...
Click to collapse
Thanks for sharing.
I'm on PIE as well. Today I flashed the factory image to make a clean install.

Hello, maybe someone can be of help to my situation.
I had my phone rooted in the last firmware version (1.7.3), and I was getting notifications to update to Android 9 pie for some time, however I was waiting to have some time to spare and first backup my files and do a factory update to pie and then root.
However, last nigh without warning my phone just rebooted and updated to pie, (firmware ver 2.0.2) and I lost root obviously. However, all my files, apps, etc were intact.
So today I decided to root my phone again. I download the firmware zip from BQ's site and then used Magisk (ver. 19.2) to patch the boot.img.
I rebooted to fastboot and did "sudo fastboot flash magisk_patched.img", and rebooted but the phone got stuck in the logo screen.
Then I used method 5 of this tutorial and ran ./sdm660_fastboot_upgrade.sh (with the mentioned modifications), however it bootlooped again. Then I flashed the original boot img and my phone booted just fine again, I tried to patch the img again, did again step 4 and it bootlooped again.
Any clues on how to successfully root ? Never had any problems updating and rooting from firmware 1.4.0 to 1.7.3.
Thank you for your time

(GUIDE) Unlocking bootloader, Rooting - from start to finish UPDATED.

Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the bootloader unlocking and root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods but I can confirm that this 100% works
NOTE* This guide is intended for all OnePlus 8 devices but the boot image files are for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
It is possible to extract the boot IMG from any firmware using the payload extractor tool which can be found online, then change the commands to reflect the files you obtain, for the sake of clarity I'll be using 10.5.12
Hope this helps.
Pre-requisites
A European variant of the Oneplus 8 Pro: IN2023
Running the following firmware: 10.5.12 IN11BA
ADB Access to your phone
A decent amount of charge, eg: 80%
A Windows 10 based computer
The cable that came with your phone
Obtaining ADB access to your device using your computer
1. Connect your phone to your computer using the cable that you charge it with
2. Allow it to see the device, if it automatically installs the driver (which it should) then you're good to go, if not then install the driver you can obtain from the drive which will appear on screen within "This PC" (i won't detail this as it's pretty self explanatory)
3. On your phone Open settings and navigate to "About phone"
4. Click "Build number" several times (5) then enter your PIN, this will enable "Developer Options"
5. Back out, then click "System"
6. Scroll down to "Developer Options" and open it.
7. Scroll down to "USB Debugging" and turn it on (if at this point you are prompted with a dialogue box asking for authorization then please check the box and allow it, also turn on) also turn on "OEM Unlocking" in the same section and agree to any prompts.
8. On your computer Download this folder https://drive.google.com/drive/folders/1S-yNzdvOvdZzPuxhYuEuwnelzfdEd0K2?usp=sharing
This is adb and fastboot so you can talk to your phone via your PC.
9. Move it to the root of the C: drive, so it looks like this in the filepath
C:\Android
10. Navigate to the folder and perform the following:
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
11. In the window type the following command
adb devices
press enter
If you are now prompted with an authorization dialogue on your phone, please check the box and allow it.
You should see a readout of a device followed by a code, you now have ADB access and can continue.
Unlocking the bootloader
NOTE* THIS WILL WIPE YOUR ENTIRE DEVICE, IT'S UP TO YOU IF YOU WANT TO BACK UP OR NOT. I WOULD RECOMMEND DOING SO
1. Connect your phone to your computer
2. On your computer Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
3. Type the following command into the window
adb reboot bootloader
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
4. On your computer Type the following command into the window
fastboot oem unlock
press enter
NOTE* THIS IS THE PART THAT WIPES YOUR PHONE IF YOU WANT TO BACK OUT, NOW IS THE TIME TO DO SO, ONCE STARTED DO NOT DISCONNECT THE CABLE OR FORCE A SHUTDOWN FOR ANY REASON THIS COULD RESULT IN A BRICKED DEVICE
5. Your phone will warn you and go through a set of screens, please agree and move forward until the device reboots
You have just unlocked the bootloader to your phone
Once the device has booted, set it up again and then follow the steps to unlock "developer options" and "USB Debugging" once more.
Installing Magisk Manager and obtaining Root access
Before you begin, please follow these two steps to install the magisk manager
Magisk manager
i) On your computer download this folder https://drive.google.com/drive/folders/1VH_2Ql6L5580rVYvRZ5l8t7cX2XENEAG?usp=sharing and move the file inside to your internal storage on your phone, the file is called "MagiskManager-v7.5.1.apk"
ii) On your phone using a file manager navigate to where you moved the file and open it, this will install the Magisk Manager used to manage root access, open the Magisk Manager once, you'll see it does not have root access.
Rooting
1. On your computer Go here https://drive.google.com/drive/folders/189DlZH1NSMrgVF996S7y3q5_IG9RAFIr?usp=sharing and download the folder
2. Copy the file inside the folder which is called "magisk_patched.img" to C:\Android
3. Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
4. Type the following into the window
adb reboot fastboot
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
On your computer
5. There are two options for rooting, the first is to boot it first, this is safer as it is not permanent and a reboot will rejoice the booted image, the second is to flash it, this is a one step option but if the image isn't right then you could end up in a bootloop so id recommend the first.
Type the following into the window
To boot:
Fastboot boot magisk_patched.img
(Your phone will reboot automatically)
To flash:
fastboot flash boot_a magisk_patched.img
press enter
then
fastboot flash boot_b magisk_patched.img
press enter
then
NOTE* THIS WILL FLASH THE PATCHED BOOT IMG TO BOTH SLOTS, THIS IS WHAT I DID, I HAVEN'T EXPLORED IF ONE SLOT IS ADEQUATE OR NOT, IT MAY BE POSSIBLE TO ONLY FLASH THE BOOT.IMG TO ONE SLOT BUT AS I HAVEN'T I CAN'T ADVISE.
6.. Once complete, type in the following command
fastboot reboot
press enter, your device will reboot
7. On your phone open up "Magisk Manager" you should now have two green ticks signifying that you now have root access.
NOTE* If you booted the image then simply click the top install option then go to install directly, this will make root permanent.
That's it, you've now unlocked your bootloader and rooted using the most current boot img at the time of writing.
------------------------------------------------------------------------------------------------------------------------------------
Please don't quote the entire thread!!!!!
If i've missed anything out or anyone notices a mistake please let me know and i'll amend accordingly.
Alternate second guide here on post #55 thanks to @flushell
https://forum.xda-developers.com/showpost.php?p=83534273&postcount=55

dladz said:
Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods.
NOTE* This guide is intended for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
Hope this helps..
Click to expand...
Click to collapse
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though

pyry666 said:
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though
Click to expand...
Click to collapse
Ok so by not specifying a slot you are flashing to both afaik
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.

dladz said:
Ok so by not specifying a slot you are flashing to both.
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.
Also please don't quote the entire guide it makes reading threads awful, edit your post please.
Click to expand...
Click to collapse
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too

pyry666 said:
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too
Click to expand...
Click to collapse
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?

dladz said:
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?
Click to expand...
Click to collapse
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now

pyry666 said:
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now
Click to expand...
Click to collapse
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway

dladz said:
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway
Click to expand...
Click to collapse
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues

pyry666 said:
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues
Click to expand...
Click to collapse
Or just follow the above guide if you meet the requirements
Command for swapping slot is
fastboot --set-active=a
Or b

Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?

N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Bootloader unlock works same no matter what model you are using. You can just boot twrp and flash magisk from there

N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.

dladz said:
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.
Click to expand...
Click to collapse
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?

N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So in order.
1 Download the full ROM for your device and region.
2 Open it in on a computer and extract the bin file called payload, it'll be about 2.4GB.
3 Then copy it to the payload dumper input folder and run the exe
4 You'll get the boot image as well as some other files, copy the boot image to your phone and patch it using magisk.
5 Then pull the output magisk patched.img to your adb folder and flash to slot A or B or both. I did both

N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So how did it go?? All good?

dladz said:
So how did it go?? All good?
Click to expand...
Click to collapse
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!

I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file

A.Priori said:
I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file
Click to expand...
Click to collapse
Well done, always good to come back from the dead

N'ash said:
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!
Click to expand...
Click to collapse
Yea that annoys me too.
There will be a way I'd imagine, but you wouldn't want to get that script wrong..
Might look into getting that gone, HTC had this too as do a few devices.
Possible a precious guide for an older device may work but using it to test would be a risk..

After doing this, is it still possible to install official OS builds from OnePlus whenever a new build comes out? Either via a zip or OTA?
For instance when 10.5.13.IN11BA comes out or whatever?

Rooting 7T without TWRP / Pre-patched Magisk boot.img for 10.0.13.HD65AA (Global)

For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.

I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?

>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.

This will delete all the data from the phone + bootloader needs to be unlocked?

Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).

GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!

Will this work for 10.0.13 tmobile ? Thanks

gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.

GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.

TWRP won't download

I tried countless methods to download TWRP on my Nokia 6.1 (TA-1043), but the closest I got was getting stuck on the TWRP logo. The phone has the stock rom btw.

epicAndroid08 said:
I tried countless methods to download TWRP on my Nokia 6.1 (TA-1043), but the closest I got was getting stuck on the TWRP logo. The phone has the stock rom btw.
Click to expand...
Click to collapse
Hi,
If your intent to use TWRP is to Root Nokia 6.1 device, please avoid flashing the TWRP as it can brick your device. I too tried 'n' number of TWRP images, but nothing worked and ultimately every time, I had to flash my STOCK ROM to get back into my device and the recovery.
However, if you're using it to simply obtain root, follow the below-mentioned steps that helped me root my device after struggling for nearly 2-days.
Here's how I did it:
NOTE: I used Magisk instead of TWRP to obtain Root.
The actual steps that you need to follow are:
Install adb & fastboot" + "Nokia USB" & other relevant drivers on your system.
Unlock the Nokia Bootloader using adb (Follow this Techmesto Guide for exact steps.)
Use this another Techmesto guide to download the latest version of Magisk apk on your system. Then, install it on your device.
Check your device settings to know which version is patched (Follow the guide link in the previous step).
Download the relevant magisk_patched image file and paste it within the adb folder.
Now, run the following two commands in your command prompt:
Code:
fastboot flash recovery <magisk_patched_filename.img
fastboot boot <magisk _patched_filename.img
Wait for the device to boot up normally. Once done, fire up the pre-installed Magisk apk and hit the "Install" button. [Install >> Install >> Direct Install]
Let the flash process complete, & once its done, simply reboot your device.
You have now successfully Rooted your Nokia 6.1 device.
Let know if the above steps helped you.
Cheers,
Manu

How To Guide [ROOT] [FLASH STOCK]

DISCLAIMER:
Please post failures and successes. Keep it relevant, everything else to the DMs please. It makes it easier for others to Q&A. Everyone thanks you for your understanding.
***IF YOU ARE NEW BEWARE!!! BEFORE YOU CHANGE ANYTHING MAKE A BACKUP. LET THIS APPLY TO EVERYTHING. WHENEVER THE OPTION TO BACKUP IS AVAILABLE IT WOULD BE WISE TO DO SO. FAILURE TO BACKUP YOUR DEVICE WILL RESULT IN LOSS OF DATA***
ALL LINKS ALLOWED, APPROVED AND/OR UTILIZED BY XDA. SPECIAL THANKS TO ALL THE DEVS WHO CREATED THE TOOLS WITHOUT WHICH THIS WOULD NOT BE POSSIBLE. I DIDN'T BUILD ANY SOFTWARE MENTIONED IN THIS POST. IF YOU BRICK YOUR PHONE, DO NOT BLAME ME. I'M NOT TELLING YOU HOW TO DO IT, BUT NARRATING A GUIDE TO HOW I DID IT. YOU HAVE BEEN WARNED
REVVL V+ 5G TMOBILE VARIANT ANDROID 11
IT SHOULD BE NOTED THAT SOME PEOPLE ARE REPORTING LOSING WIFI AFTER ROOT, AS HAVE I. I HAVE NOT YET FIGURED OUT HOW TO FIX THIS. I'M THANKFUL FOR ANY ASSISTANCE. FLASHED STOCK BOOT_A DIDN'T FIX IT, ONLY FLASHING BACK TO STOCK ROM. ON ANOTHER IDENTICAL PHONE DIDN'T LOSE WIFI. YOUR GUESS IS AS GOOD AS MINE. LOOKING INTO IT, NO PROMISES
Without further ado, let's start at the unboxing.
1) PREP PHONE:
power on. navigate to settings>about phone and tap "build number" seven times to enable developer options.
navigate to settings>system>developer options and enable "USB Debugging" and "OEM unlock"
FIRST disconnect the device from your comp THEN power the device off.
2) DONWLOAD PYTHON & DRIVERS:
Python
BE SURE TO TICK THE BOX THAT SAYS ADD PYTHON TO PATH and install.
Download and install mediatek drivers from here:
Mediatek USB drivers
Download and install UsbDk from here:
UsbDk
Download MTK client from here:
MTK client
and extract to the desktop. Open the folder and move everything to
C:>Users>[username]>AppData>Local>Programs>Python>Python310
In the 310 directory press Alt + D to highlight your directory path and type CMD and hit enter. This opens a command prompt in the Python310 directory.
In cmd type this command without "":
"python setup.py install"
Go make a sandwich. Preferably turkey with mustard.
When you finish your sandwich, come back and type this command without "":
"python -m pip install -r requirements.txt"
Do not exit the command window.
3) BOOT INTO B ROM MODE:
This is kind of tricky when you don't know it. The screen will will be black. Sometimes, the device will not even vibrate. There's no sunbathing android, no "No Command", no fastboot, no download mode, no recovery- nothing, nada, zip, zilch, goose egg.
Make sure you unplug the device entirely from charger and pc BEFORE you power off. Now that you properly powered off, hold ONLY BOTH volume + - keys while you connect it to your PC. Try to be quick about it. DO NOT TOUCH THE POWER KEY. Continue to hold the volume keys until you know your device connected. When you hear your device connected jingle immediately let go. The screen will remain blacked out and unresponsive. It's normal.
Let's make sure we did it right. Enter the following command without ":
"python mtk e metadata,userdata,md_udc"
Disconnect and power on. If the device has been reset, then you have confirmation.
4) PREP PHONE AGAIN (STEP 1):
5) UNLOCK BOOTLOADER:
Enter the following command without ":
"python mtk da seccfg unlock"
~To relock the bootloader in the future use command "python mtk da seccfg lock". If you flash a custom recovery/ROM and want to return to stock, then you must unroot with magisk first, then flash stock ROM with SP flash tool at the end of this post~
Power on. On the splash screen you will see system type:
"Orange State
Your device is corrupted. Device has been unlocked and cannot be trusted. Press Power key to boot.
Will Reboot in 5 seconds."
This will happen each time you boot the device because your bootloader is now unlocked.
6) PREP PHONE AGAIN (STEP 1):
7) ENABLE ADB FASTBOOT COMMANDS:
Download sdk platform tools here:
sdk platform tools
Extract.
Navigate to the platform tools folder and type Alt+D to highlight directory and type CMD to open a cmd window in platform tools.
Connect device to pc and choose file transfer.
Enter the following command without ":
"adb devices"
A prompt will appear on your phone, click allow.
Enter the following command (again) without ":
"adb devices"
First you'll see a random, arbitrary number. Second time you should see your device serial number and "Authorized", "Allowed", or "Device".
Keep this cmd window open.
8) DOWNLOAD MAGISK AND PATCH BOOT IMG:
Download Magisk from here:
Magisk
Move it to your phone and install. You'll need to allow the installation from unknown sources.
Download firmware from here:
T-Mobile_REVVL_V%252B_5G.zip
Unzip and move boot_a to the downloads folder on your phone.
On your phone, open Magisk and click install and choose boot_a.
Make sure magisk_patched file is in your phone's download folder.
In your platform tools cmd window enter the following command without ":
"adb pull /sdcard/Download/magisk_patched_[numbers].img"
9) ENTER FASTBOOT MODE:
Disconnect device and power off. Hold Vol - and power to enter fastboot mode.
Connect device to PC.
10) ACHIEVE ROOT:
***NOTE: IN THIS STEP YOU MUST LOCATE THE PATCHED FILE ON YOUR PC AND COPY AS PATH. PASTE IT IN THE CMD WINDOW IN PLACE OF "[path to patched file]"***
In the platform tools cmd window enter the following command without ":
"fastboot flash boot [path to patched file]"
Now that you've achieved root, you can play around a little bit. But be careful what you go deleting if you get debloat happy like me and delete your NVRAM & wifi. Just in case you do, here's how to return to stock.
NVRAM backup. This video makes it look easy as pie. (It IS easy)
NVRAM Backup Tutorial
Now we have to bypass DA else SP flash tool will not be able to flash ROM.
Open cmd window and type the following without "":
"python -m pip install pyusb pyserial json5"
Then, update by entering the following command without "":
"python.exe -m pip install --upgrade pip"
Download LIBUSB:
LIBUSB
Run LIBUSB Win 32 filter installer and select Mediatek driver
Enter B ROM mode and connect to PC
Navigate to bypass tool and open "brom.bat"
Close cmd...
Run "flash_tool.exe" in sp flash folder
Options>options>connection tick UART
That's it. Now you can flash with sp flash without encountering error
Here is a helpful link that came from a senior mod:
mtk tool
Download SP Flash tool here:
SP Flash
Extract and launch flash_tool application
Download scatter mt6833 here:
MT6833_scatter.txt
Download bypass tool from here:
bypass tool
download rom2box:
rom2box
Download OTA and use a payload dumper to extract boot and scatter. You can also get DA, but it does nothing. You must bypass DA in order to flash ROM.
OTA
THIS SECTION IS FOR LATER REFERENCING, DISREGARD ANYTHING BELOW THIS
[A13 ota news https://www.t-mobile.com/support/devices/software-updates/t-mobile-revvl-v-plus-android-update]
[Twrp https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/?_ga=2.195721068.1777813512.1675477697-1767133243.1662515191]
~fastboot set_active other
~fastboot flash recovery_a twrp file
~fastboot flash recovery_b twrp file
[Sprout https://dl.twrp.me/sprout/]
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
https://www.mediafire.com/download/sxq4cz8bddmr49
https://www.mediafire.com/file/irigs9iviy3sobw/T-Mobile_REVVL_V%2B_5G.zip/file
https://download1526.mediafire.com/ih0pus48i1kg/mwl6h20noutg005/revvplus.zip
[Patched boot_a pending verification https://forum.xda-developers.com/attachments/magisk_patched-25100_hiu69-img.5648347/]
[FLASH STOCK MODEM FILE]
My next guide will be how to use assurance wireless with ANY phone. I'm using assurance wireless on my Oneplus N200 (DE2118).

Hi. I read many posts of yours regarding the REVVL V+ 5G, I was encouraged by your progress, and took comfort that someone else had some of the same struggles that I did. I was able to unlock the bootloader, I was able to root the phone (using an img file posted by someone else here; I hadn't yet read your root recipe), but I was no longer able to connect to wifi. (is this familiar?) In trying to undo the mess, I ended up making my phone unbootable.
I wanted to install stock ROM from scratch. I read your instructions, but there's no scatter file in the ROM that you posted. So I'm confused.
I figured that I could install the stock ROM zip via TWRP; I googled and found a TWRP for "Sprout" (the codename of our device), but for the life of me I couldn't install it on my phone, no matter what I tried.
You're ahead of me here; perhaps you can get me on track. Right now, my phone isn't booting at all.
Thank you!

smuskat said:
Hi. I read many posts of yours regarding the REVVL V+ 5G, I was encouraged by your progress, and took comfort that someone else had some of the same struggles that I did. I was able to unlock the bootloader, I was able to root the phone (using an img file posted by someone else here; I hadn't yet read your root recipe), but I was no longer able to connect to wifi. (is this familiar?) In trying to undo the mess, I ended up making my phone unbootable.
I wanted to install stock ROM from scratch. I read your instructions, but there's no scatter file in the ROM that you posted. So I'm confused.
I figured that I could install the stock ROM zip via TWRP; I googled and found a TWRP for "Sprout" (the codename of our device), but for the life of me I couldn't install it on my phone, no matter what I tried.
You're ahead of me here; perhaps you can get me on track. Right now, my phone isn't booting at all.
Thank you!
Click to expand...
Click to collapse
Hey, I finished the guide. You can return to stock following the guide above. As you may have noticed I edited this message instead of posting again. It's okay, cause I brought good news, right? Cheers

R41N MuTT said:
i totally forgot, yeah, i will look up the proper method to install twrp. it's supposed to be easy. i thought i was going to have to port twrp-and i still might- so i'm looking into it. i need to flash twrp myself. there is supposed to be a way to use rom2box or spflash or twrp or something to make a flashable zip. i don't know if that's a thing. it seems to me somebody needs to build a preinstaller that automatically flashes each img. for you. like a 1 click. if we can get twrp on this, that's the next step. to make a flashable zip. or somehow one click installer. i imagine if i did, it would only work for this phone, but could be modified for similar devices. i know tcl has a software like that. they plug a phone up and click one button. on their end it's one folder and that program does the rest. that program is what i want to write. reverse engineer this shiz and get a complete understanding of it. i know good and well the folks at tcl aren't sitting on a cmd window using adb to flash dozens of duplicate images time and time again for each device they build. it's screw it together, plug it up, click a button and test. they already have all the files preloaded and they have a preinstaller that pretty much instantly flashes the software. damn, wouldn't it sure be nice to have? but i don't foresee anybody leaking it any time soon. maybe if you have the cheese
Click to expand...
Click to collapse
Download TWRP for sprout
Download TWRP Open Recovery for sprout
dl.twrp.me

smuskat said:
Download TWRP for sprout
Download TWRP Open Recovery for sprout
dl.twrp.me
Click to expand...
Click to collapse
Did you see this? https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/

R41N MuTT said:
Did you see this? https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/
Click to expand...
Click to collapse
I looked; our REVVL does not seem to be listed in the list of supported devices.
smuskat said:
I looked; our REVVL does not seem to be listed in the list of supported devices.
Click to expand...
Click to collapse
And may I ask for a clarification, please: You wrote above, "the firmware links i sent you- there should be at least 2 different ones, and an OTA... well, if you open the root folder and type 'scatter.txt' in the search bar it will pop up." In your post, I see 2 links to firmware; one is called https://www.mediafire.com/download/sxq4cz8bddmr49l, and one is called https://www.mediafire.com/file/irigs9iviy3sobw/T-Mobile_REVVL_V%2B_5G.zip/file. I downloaded both. I clicked on the downloaded file, and in the search bar, I searched for "scatter.txt", and got no results. What am i doing wrong? Thanks

smuskat said:
I looked; our REVVL does not seem to be listed in the list of supported devices.
Click to expand...
Click to collapse
It needs to be ported still. Unless it's already ported I'm working on it now. Nightmare. I'm trying to follow a guide on here about porting TWRP... Going slow...
OTA
https://r4---sn-npoldn76.gvt1.com/packages/data/ota-api/package/72d80093722599cd459bca02504f22cbf3421dd2.zip?mh=Rs&pl=21&cm2rm=sn-8qj-i5ozd7r,sn-i3bdr7s&req_id=37ad1f0feba7fd94&cmsv=e&ipbypass=yes&rm=sn-8qj-i5olz7l&redirect_counter=3&cms_redirect=yes&mip=117.4.250.39&mm=34&mn=sn-npoldn76&ms=ltu&mt=1672034446&mv=m&mvi=4
Firmware
T-Mobile REVVL V+ 5G
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Here is the link to the scatter.txt for mt6833 (revvl v+).
MT6833_Android_scatter.txt
Shared with Dropbox
www.dropbox.com
Tmobile just recently announced the release of the a13 update. It's supposed to be before the end of february.
Software Updates
Visit T-Mobile Support for help with phones & internet devices, plans & services, billing, and more!
www.t-mobile.com
Message edited at completion of guide. Irrelevant content removed.

After installing the modified boot img with fastboot my phone bricked and i cant fix it, it just crashes on boot and loops back whenever i try to normal boot.
If there's any help you can offer I'd appreciate it.

vinnie215215 said:
After installing the modified boot img with fastboot my phone bricked and i cant fix it, it just crashes on boot and loops back whenever i try to normal boot.
If there's any help you can offer I'd
Click to expand...
Click to collapse
Edited: guide complete. Try it now.

R41N MuTT said:
When your phone boots up do you see system font on the screen? It should prompt you to press power to boot normally, otherwise it will continue to reboot. It's because the bootloader is unlocked and you must press power to acknowledge this or else the phone will boot loop. Does this help? If not, get another phone and download magisk and try to patch boot_a again. You can use another device to do all those steps to get the file ready. Pull it, plug in your revvl v+ again and try flashing it. You can also try a different copy of the firmware, I linked 3. You can also flash stock boot_a and boot_b and that should get you going. I'm still figuring this device out. I advise you reach out to somebody who has a lot of experience flashing a/b partition scheme devices, namely mediatek. Project oppo. My only other suggestion is to flash the stock firmware using adb fastboot commands. In the forums you can find a guide to flashing a/b... So, just to be clear, recite to me exactly what you did up to the point it boot loops. And tell me is there system type on the screen when it boots?
Click to expand...
Click to collapse
So i Followed the guide exactly and everything seemed to work fine until i flashed the img modified by magisk. Fastboot said it moved and wrote successfully.
Then when i rebooted and hit the power button again to bypass the 'orange' warning instead of starting into a factory reset phone, it flashes the backlight and starts booting again.
Im also unable to get into recovery, fastboot mode is all that works now. I've tried to flash the stock boot_a img but not the boot_b, do you think that would help?
I'm gonna make a new img with my s9 and try that as you suggested.
Edit:
Well i might be handicapped.
I had 2 phones here, the V+ and the 6 pro.
Turns out i did youre walkthrough on the revvl 6 pro. It did unlock it, but obviously when i flashed the boot.img for the V+ it bricked. And i cant find the backup anywhere.
In short thanks for your time, I'm afraid all i did was waste it :\

vinnie215215 said:
So i Followed the guide exactly and everything seemed to work fine until i flashed the img modified by magisk. Fastboot said it moved and wrote successfully.
Then when i rebooted and hit the power button again to bypass the 'orange' warning instead of starting into a factory reset phone, it flashes the backlight and starts booting again.
Im also unable to get into recovery, fastboot mode is all that works now. I've tried to flash the stock boot_a img but not the boot_b, do you think that would help?
I'm gonna make a new img with my s9 and try that as you suggested.
Edit:
Well i might be handicapped.
I had 2 phones here, the V+ and the 6 pro.
Turns out i did youre walkthrough on the revvl 6 pro. It did unlock it, but obviously when i flashed the boot.img for the V+ it bricked. And i cant find the backup anywhere.
In short thanks for your time, I'm afraid all i did was waste it :\
Click to expand...
Click to collapse
Edited to remove irrelevant content. Guide complete. Try it again. If your phone will not hard reboot, try adb reboot bootloader. All activity should cease and your device should promptly enter fastboot.

i started messing with this phone on my own until ididn't have right stock firm. is alot steps get this phone rooted.

contevo said:
i started messing with this phone on my own until ididn't have right stock firm. is alot steps get this phone rooted.
Click to expand...
Click to collapse
I couldn't agree more. Lol. I'm actively editing the content to condense it. I'm also working on porting TWRP. I've done some other things to save a few steps, like patching boot_a and putting it on Dropbox so all you'll have to do is download it and flash it. When a13 OTA gets captured it'll get better

{
"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"
}
i get this error when loading the scatter file ad i'm using the latest version
v5.1924

R41N MuTT said:
I couldn't agree more. Lol. I'm actively editing the content to condense it. I'm also working on porting TWRP. I've done some other things to save a few steps, like patching boot_a and putting it on Dropbox so all you'll have to do is download it and flash it. When a13 OTA gets captured it'll get better
Click to expand...
Click to collapse
can you help

pickymarker said:
can you help
Click to expand...
Click to collapse
Currently working on it. I've asked a couple ppl for help. Either they'll post here, or I'll update you. Stand by

okay

can it be done today

/

comm-ents said:
I am able to unlock the bootloader, then my phone just hangs at the boot screen, but I can can lock it again Now it just boots with the orange warning and it doesn't matter after that if it is locked or unlocked
The android version is still 11 with a security update from Dec 5, 2022.
I am just curious if there is a way to revert back to a previous version that might just work like the version listed for download. There could also be differences in the boot file that is in the firmware zip file from what is on my phone so patching and installing a different version won't work.
Maybe just waiting until the next version is releases would be the best option?
Click to expand...
Click to collapse
Perhaps that. In fact, that's what I'm waiting on- the a13 update. I intend to capture the OTA and follow the spflash walkthrough. Then I can update this how to where it'll work for everybody. I have 4 people right now with boot issues after root that go beyond WiFi, and they all 4 can't get spflash to work. It's bugging the crap out of me, I haven't been able to figure out what to do to fix it. I'm still waiting on some other folks I've reached out to, if they ever have the time...