Develop Bugs

[HOW TO] Unlock Bootloader & Root GSM Nexus (4.0.x devices only)

I know there a few tutorials already on here, however it seems quite a lot of people are eitiher asking questions about the ADB method, or cannot understand other methods. So i'll try and put it all in one easy to follow tutorial. This is for the latest version on Android 4.0.x.
For this method we are going to use Paul O'Briens Superboot.
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Click to expand...
Click to collapse
APPLY THIS AT YOUR OWN RISK!
Download the latest version of Superboot: DOWNLOAD
You might need the drivers, however its worth getting them anyway as you'll probably need them in the future: DOWNLOAD DRIVERS
If you get you might need the USB drivers: DOWNLOAD
Windows
1) Extract the contents of the above file into C:\root
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up cmd and navigate to by typing to following (Hit enter after each line):
cd C:/
cd root
6) Unlock your bootloader by typing - this will wipe your device!:
fastboot-windows oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, double click:
install-superboot-windows.bat
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
Linux
1) Extract the contents of the above file into a folder
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up terminal and navigate to the folder used in step 1
6) Unlock your bootloader by typing - this will wipe your device!:
./fastboot-linux oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, type the following (Hit enter after each line):
chmod +x install-superboot-linux.sh
./install-superboot-linux.sh
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
OS X
1) Extract the contents of the above file into a folder
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up terminal and navigate to the folder used in step 1
6) Unlock your bootloader by typing - this will wipe your device!:
./fastboot-mac oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, type the following (Hit enter after each line):
chmod +x install-superboot-mac.sh
./install-superboot-mac.sh
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
If i've missed any steps out such as downloading drivers etc, let me know what to add in etc. I did mine on OS X and it didn't require me to install anything extra
Update: it would appear some people are having issues with 4.1 rooting. I'll see what I can find an then update it. For the time being, just reflash the vanilla install and you should be fine. I'd imagine there's an incompatibility between this root and 4.1

Very nice indeed, might be worth doing a tutorial on how to return to stock if there isn't already one out there somewhere. Not many people know that it's possible to Fastboot OEM lock, I've tried it

Yeah I'm going to wait until there's a proper system.img about.
I got mine back to stock, however it was a complete bodge and highly advised against.
Locking the boot loader is the easy bit. It's going back to the default rom
Sent from my iPad 2 using Tapatalk

...but this should be moved to general i think. This subforum will br crowded next months.
sent from a kanged gt-i9000 using Tapatalk

It's based on development so I don't see why. General is anything to do with the phone. Unlocking and rooting is the first step of development
Sent from my iPad 2 using Tapatalk

Thank you for your work.
Just a small correction for your original post.
Instead of
fastboot-windows oem unlock
it's actually:
.\fastboot-windows oem unlock

Cheers. I'll edit that. Didn't work for me like that when I did it on a windows PC, however I'll add it in
Sent from my iPad 2 using Tapatalk

Maybe it worth to mention in the first post that many ppl (including me) had issues with this process, because we had no proper drivers installed first, and for that the solution was installing the newest PDAnet software. After that everything went pretty well.

Aylarth said:
Maybe it worth to mention in the first post that many ppl (including me) had issues with this process, because we had no proper drivers installed first, and for that the solution was installing the newest PDAnet software. After that everything went pretty well.
Click to expand...
Click to collapse
Ah yes. Added
Sent from my Galaxy Nexus using Tapatalk

I'm very new to this so prepare for a stupid question!
I'm trying to run this on a Mac, and when I'm trying to run fastboot oem unlock I get the following:
/Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac: No such file or directory
What could cause this?

helen_xxxx said:
I'm very new to this so prepare for a stupid question!
I'm trying to run this on a Mac, and when I'm trying to run fastboot oem unlock I get the following:
/Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac: No such file or directory
What could cause this?
Click to expand...
Click to collapse
Have you navigated to the folder where the files are located? Stupid question but not sure what you've done
Sent from my Galaxy Nexus using Tapatalk

Evostance said:
Yeah I'm going to wait until there's a proper system.img about.
Click to expand...
Click to collapse
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.

Evostance said:
Have you navigated to the folder where the files are located? Stupid question but not sure what you've done
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.

Oppressa said:
Thank you for your work.
Just a small correction for your original post.
Instead of
fastboot-windows oem unlock
it's actually:
.\fastboot-windows oem unlock
Click to expand...
Click to collapse
I am pretty sure you don't need the .\ on Windows? Only Mac & Linux.

StuMcBill said:
I am pretty sure you don't need the .\ on Windows? Only Mac & Linux.
Click to expand...
Click to collapse
Thats what I thought. Worked without the .\ for me at work as its just an exe

helen_xxxx said:
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.
Click to expand...
Click to collapse
OK, If you files are in the folder r2-galaxynexus-superboot, open terminal and just type (after each line hit enter):
cd /Users/
cd extra_ham/
cd r2-galaxynexus-superboot
./fastboot-mac oem unlock
chandlerweb said:
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.
Click to expand...
Click to collapse
I tried that system.img and it bricked my phone. Couldn't get it to launch, it just hung on the animation. I did a boot to CWM, messed with some stuff and then the phone randomly launched. Its not a stock image, missing all the Google apps etc and the Gallery doesn't work. I think for now though, its the closest thing to a stock image we have

Brilliant thank you, will give it a try.
Think I need to tune up on Unix....

helen_xxxx said:
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.
Click to expand...
Click to collapse
On OSX you can just drag the fastboot-mac file from finder into the terminal window and it will automatically fill in the path for you, then type the rest of the unlock command and hit enter

chandlerweb said:
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.
Click to expand...
Click to collapse
The Droid with triangle actually is stock recovery. When you see it just press power + volume down.
Sent from my Galaxy Nexus using XDA App

I hope the LTE version is as easy to root/unlock as this.
Knowing Verizon though...probably not.

[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

Rooting pixel 2xl

I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks

grunt0300 said:
I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?

Badger50 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes it is.

grunt0300 said:
Yes it is.
Click to expand...
Click to collapse
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?

What happens when you run the fastboot command "fastboot flashing unlock"?

Badger50 said:
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?
Click to expand...
Click to collapse
Sorry, i've been trying to root this phone all afternoon and i'm burnt out. Maybe tomorrow. Thanks

OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.

grunt0300 said:
OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.
Click to expand...
Click to collapse
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.

Az Biker said:
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.
Click to expand...
Click to collapse
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?

grunt0300 said:
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?
Click to expand...
Click to collapse
Like @Az Biker said, follow the guide in his signature :good:

Badger50 said:
Like @Az Biker said, follow the guide in his signature :good:
Click to expand...
Click to collapse
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.

grunt0300 said:
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.
Click to expand...
Click to collapse
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.

Az Biker said:
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.
Click to expand...
Click to collapse
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.

grunt0300 said:
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.
Click to expand...
Click to collapse
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679

Badger50 said:
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679
Click to expand...
Click to collapse
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?

grunt0300 said:
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?
Click to expand...
Click to collapse
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.

Badger50 said:
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.
Click to expand...
Click to collapse
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.

grunt0300 said:
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.
Click to expand...
Click to collapse
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.

Az Biker said:
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.
Click to expand...
Click to collapse
Did i mention that i already have android 10 on the phone?

grunt0300 said:
Did i mention that i already have android 10 on the phone?
Click to expand...
Click to collapse
The guide process works the same for 9x and Android 10.
In the guide, it is stated:
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash Cust Kernel (I use Flash -not supported after 3.19 Nov 2018 or Sultan Kernel or Elemental X (EX) kernel) BE SURE TO SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
I guess I'm confused as to why you are simply not just following the guide from step one.........

How to root a OnePlus 7T Pro with Magisk, For Noobs!

In this guide, ill be showing you how to root your device using Magisk. This is done at your own risk, i am not responsible for corrupted images, bricked devices etc.
*NOTE: This guide is for the OnePlus 7T Pro only*
What you will need:
A windows PC - idk buy one lol?
Platform tools SDK - https://developer.android.com/studio/releases/platform-tools
USB cable that came with the phone
Magisk Manager APK - https://magiskapp.com/apk/
Your phones current software boot.img! You can either get this from the vendors website, or if you are running a custom OS, you should already have the file.
*Ill be assuming you are familiar with cmd, fastboot commands, and that your bootloader is already unlocked, and you are running a custom recovery! For a guide on how to do the last two things, part of my last guide can help you - https://forum.xda-developers.com/t/how-to-install-android-12-derpfest-for-noobs.4385171/ *
Step 1: Download the magisk apk from the website and install it to your device. After this, copy over the boot.img file that is from your current rom into the downloads folder of your phone! Now, open up magisk manager, and press install beside the 'Magisk' Section on the home screen. Then press 'Select and Patch a FIle'. Now you can select the boot.img file and let Magisk do its thing.
Step 2: Once that process has been completed, you should have a file beginning with 'magisk_patched....img' in your downloads folder. Copy that file over to the platform tools folder in your computer. Now boot your phone into fastboot mode and connect it to your computer. Then on your computer, go to where you placed the magisk_patched file and in the search bar in file explorer type cmd. This should open a cmd window. Then type 'fastboot reboot fastboot' in order to enter your phone into fastbootd mode.
Step 3: Type 'fastboot flash boot 'PATH TO MAGISK_PATCHED FILE'
Let this run and once its done, reboot your phone.
Go to Magisk and Voila you should be rooted!
If you have any questions please dont hesitate to ask!
If i have made any mistakes in this guide, or you guys think i should make any changes, let me know, im new to this!

Thnx for the post , and confirming that this worked perfectly with OP7T PRO Android 11 official ROM

Do I assume correctly that I would wipe everything?
astroarchcraft said:
In this guide, ill be showing you how to root your device using Magisk. This is done at your own risk, i am not responsible for corrupted images, bricked devices etc.
*NOTE: This guide is for the OnePlus 7T Pro only*
What you will need:
A windows PC - idk buy one lol?
Platform tools SDK - https://developer.android.com/studio/releases/platform-tools
USB cable that came with the phone
Magisk Manager APK - https://magiskapp.com/apk/
Your phones current software boot.img! You can either get this from the vendors website, or if you are running a custom OS, you should already have the file.
*Ill be assuming you are familiar with cmd, fastboot commands, and that your bootloader is already unlocked, and you are running a custom recovery! For a guide on how to do the last two things, part of my last guide can help you - https://forum.xda-developers.com/t/how-to-install-android-12-derpfest-for-noobs.4385171/ *
Step 1: Download the magisk apk from the website and install it to your device. After this, copy over the boot.img file that is from your current rom into the downloads folder of your phone! Now, open up magisk manager, and press install beside the 'Magisk' Section on the home screen. Then press 'Select and Patch a FIle'. Now you can select the boot.img file and let Magisk do its thing.
Step 2: Once that process has been completed, you should have a file beginning with 'magisk_patched....img' in your downloads folder. Copy that file over to the platform tools folder in your computer. Now boot your phone into fastboot mode and connect it to your computer. Then on your computer, go to where you placed the magisk_patched file and in the search bar in file explorer type cmd. This should open a cmd window. Then type 'fastboot reboot fastboot' in order to enter your phone into fastbootd mode.
Step 3: Type 'fastboot flash boot 'PATH TO MAGISK_PATCHED FILE'
Let this run and once its done, reboot your phone.
Go to Magisk and Voila you should be rooted!
If you have any questions please dont hesitate to ask!
If i have made any mistakes in this guide, or you guys think i should make any changes, let me know, im new to this!
Click to expand...
Click to collapse

Hello, up to step 3 everything was fine. I let it run its thing, and reboot, BUT it became stuck in fastboot, forever. What can I do? I tried to wipe data and everything, but it's still stuck. Is there anything I can do?
Okay, so I manage to get my phone unbricked and is now running TWRP, which it was not before doing this. Am I correct to assume that doing all this without TWRP breaks the phone?

powerfulnacho said:
roidHello, up to step 3 everything was fine. I let it run its thing, and reboot, BUT it became stuck in fastboot, forever. What can I do? I tried to wipe data and everything, but it's still stuck. Is there anything I can do?
Okay, so I manage to get my phone unbricked and is now running TWRP, which it was not before doing this. Am I correct to assume that doing all this without TWRP breaks the phone?
Click to expand...
Click to collapse
Same here, not work too.
For OxygenOS latest, in Android 12.
--- EDIT ---
Personally I install TWRP to do mostly backups, if needed.
But you have to use this twrp for Android 12 :
OnePlus 7T Android 12 TWRP?
Hello! I'm very new to building custom recoveries, and haven't even completed a successful build yet. I have a OnePlus 7T model HD1905 (aka North American model/Global) running OOS 12. I've tried to find guides on how to make a TWRP recovery, but...
forum.xda-developers.com
For the moment, after flash boot.img builded by Magisk is not work. But i dont try with this twrp. I dont now if this have a link...

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...