Develop Bugs

LG G3 Root help

Hello, I am running an ATT LG G3 and I have tried every root method and I just can't get past the firmware update stage. I get to the firmware update screen, phone stays on 0%, whatever rooting tool i am using then says that supersu has failed to boot/install/whatever because it has not started within 1 minute. I turn off the phone by taking the battery out and when it boots up I do not have SuperSu. Note, I read somewhere if i get the LED showing a blue and green color then something is wrong? My phone does flash those colors, what should i do.
PS needed info?
ATT LG G3
-D850
-5.0.1
-Note: I also had rooted on kitkat, didnt like it. unrooted and then restored stock lollipop. If that makes a difference

Have you already tried the second method in this thread?...
[GUIDE][ROOT] Newest Root Method for LG devices
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Make sure to download and extract the New_LG_Root_v0.1_by_dig.zip file from the OP, then open a command prompt w/ admin rights from within the extracted directory.

i also had this problem. i tried every root method but nothing worked.
i found a "solution" that said that you need to go back to stuck (android kit kat 4.4.2) and then try to root.
it worked for me.
some says that there is a problem with rooting lollipop. :-\
hope it will work for you too

@redduc900 yes I have, I have not tried it with admin rights yet tho. I will try it and update you. But I am sure that the same firmware update stuck stage will occur.

Post a pic of the command prompt window open, showing the results after entering each of the commands from the second method of that thread.

Unable to root LG G3 V20T
redduc900 said:
Post a pic of the command prompt window open, showing the results after entering each of the commands from the second method of that thread.
Click to expand...
Click to collapse
I also have problems with this, I have V20T version of LG G3 .
The first method didn't work, i get to where i enter download mode manually, then nothing.
The same goes for the second method. when i get to the point where i use the send_command.exe \\.\com3 < root it tells me that it can't open the port.
I've verified that com3 is used. however the device shows up in the device managare with a warning.
This warning is only shown when the phone is in download mode.
Any help with this is appreciated, could this problem be due to the recent security update by LG?
Perhaps downgrading to a more recent version of lollipop (before the september 2015 update) will enable me to root?
......
I solved the problem by upgrading the drivers. I was running driver version 3.14 but when i upgraded to 4.0 i now got the extra diag device on Com4.
Now i could run the send_command with root. I was not able to run the second command to reboot but insetad i pulled the battery and then booted up.
Now i'm root and everything is good
\Mattias

While in Download mode, and after running the ports.bat script, you're entering the COM port that's adjacent to the \Device\LGANDNETDIAG1 entry? Also make sure you have the latest LG drivers installed beforehand...
http://androidxda.com/download-lg-usb-drivers

Where did you find the version 4.0? perhaps that is also a possible issue
MattiasG said:
I also have problems with this, I have V20T version of LG G3 .
The first method didn't work, i get to where i enter download mode manually, then nothing.
The same goes for the second method. when i get to the point where i use the send_command.exe \\.\com3 < root it tells me that it can't open the port.
I've verified that com3 is used. however the device shows up in the device managare with a warning.
This warning is only shown when the phone is in download mode.
Any help with this is appreciated, could this problem be due to the recent security update by LG?
Perhaps downgrading to a more recent version of lollipop (before the september 2015 update) will enable me to root?
......
I solved the problem by upgrading the drivers. I was running driver version 3.14 but when i upgraded to 4.0 i now got the extra diag device on Com4.
Now i could run the send_command with root. I was not able to run the second command to reboot but insetad i pulled the battery and then booted up.
Now i'm root and everything is good
\Mattias
Click to expand...
Click to collapse

How can i exactly run command prompt with admin privileges if i want to shift + MOUSE2 when i open the command prompt within the directory?
Now i have a new problem, great. When i send the first command nothing even happens.
yes i have usb debugging checked
Here is a screenshot of what I get
imgur.com/
CiWWU1Y
*cant post hyper link due to spam issues on the forum?*
redduc900 said:
Post a pic of the command prompt window open, showing the results after entering each of the commands from the second method of that thread.
Click to expand...
Click to collapse

You can get the latest version 4.0.2 of the LGMobileDriver from LG here...
http://www.lg.com/us/support/software-firmware
... and instead of using Shift+Right-click to open a command prompt from within the directory, type CMD from the Start--> Search field, right-click and select Run as administrator. Then just CD to the directory.

Root and Install TWRP on Moto G4 Plus

Hello everyone.... There is no specific post on rooting and unlocking the bootloader here so I thought I'd rather post it....
So let's begin....
mod edit as per original author

Have U Tested it ?????
Does it Work ????
or Just Posting without results ?

Bootloader unlock works.... but I'm still working trying to make Lucky patcher work to confirm root access

cool_sid said:
Bootloader unlock works.... but I'm still working trying to make Lucky patcher work to confirm root access
Click to expand...
Click to collapse
Dont Post Threads which leads to disasters !!!
confirm first and make it live. !!!

No disaster buddy.... you don't understand.... it all works but since I don't have busy box.... it doesn't work for lucky patcher... I'll just install it n also send screenshots of my root access with Root Checker.....
OK?

cool_sid said:
No disaster buddy.... you don't understand.... it all works but since I don't have busy box.... it doesn't work for lucky patcher... I'll just install it n also send screenshots of my root access with Root Checker.....
OK?
Click to expand...
Click to collapse
install root checker nd send it. !!
they dnt need busybox.
and y care for luckypather btw ?

It doesn't work with supersu. Already tested by @yeshwanthvshenoy and phone bootlooped.
Sent from my Moto G (4) using Tapatalk

I don't understand why you people say it.... it booted on my Moto G4 Plus.....

cool_sid said:
I don't understand why you people say it.... it booted on my Moto G4 Plus.....
Click to expand...
Click to collapse
cause after 6.0+ need modifided boot.img

Bootloader unlocked, TWRP done..
Now im doing backup for in case of someting goes wrong... im about to flash superSU and i will tell you if yes or no.. im doing the sacrifice !! LOL

cool_sid said:
Hello everyone.... There is no specific post on rooting and unlocking the bootloader here so I thought I'd rather post it....
So let's begin....
What you need:
1) Laptop/PC with Internet running Windows
2)Moto G4 and Moto G4 Plus USB driver,?*Minimal ADB, and Fastboot tool driver.
3) USB cable
4) Patience
How to unlock the?*bootloader of Moto G4 and Moto G4 Plus
a) Before proceedings make sure that your device is at least 70% charged.
b) Enable USB Debugging by going into Setting> About Phone and tap on build number for 8 times. This should unlock Developer Options. Now get into Developer Options and enable USB Debugging.
c) Install?*Minimal ADB,?*Fastboot Tools, and?*Moto G4 or Moto G4 Plus Driverson your PC.
d) Now go to the folder where Minimal ADB & Fastboot Tools are present (must be somewhere in C drive). Now open Command Prompt by pressingShift Key + Right Mouse Button?*and select Open Command Window here.
e) Now switch off your phone. Then press Volume up + Power Key together. You will get into Fastboot Mode. Now connect it to the PC via USB cable.
f) Now type the following command into the Command Window to check if your phone is properly connected and is detected by PC or not.
fastboot devices
g) Now you need the unlock data to unlock the bootloader. Type the following command into the Command Window
fastbootoemget_unlock_data
h) It will display a long string which you need to copy into notepad, remove all the spaces which are present and save it somewhere.
i) Now go to?*Motorola official website. Create an account if you don’t have any. Log in to the account and go to the Unlock Bootloader option and paste the string which you copied in the notepad earlier.
j) Now click on Can my device be unlocked. Select I Agree and then Request Unlock Code. You should receive a mail from Motorola with similar codes within few minutes.
k) Now copy those codes, open Command Window and type the following commands
fastboot OEM unlock (insert the code without braces)
l) Now you have successfully unlocked the bootloader and now you can install recovery.
Though it's pretty much sufficient but if you ask... I'll post some screenshots of the process as well......
Don't hesitate to ask if stuck anywhere....
???????? Install TWRP ON MOTO G4 PLUS
To install TWRP on moto G4 Plus... Refer to this XDA link
https://www.google.co.in/url?sa=t&s...mQxu4hgzMGQnN1dQQ&sig2=BEagC-mbHleWiRHg85zLyA
How to root Moto G4 And Moto G4 Plus
a) Download?*BETA-SuperSU.zip ?*file and place it into the root of your memory card (Attached along)
b) Get into recovery mode by pressing Power + Volume Down button.
c) Once you are in recovery select Install from SD card option and browse the SuperSU.zip file. Select Yes to install and wait until the flashing is done.
d) Now select Restart option from the recovery and wait for the device to boot up.
Go to Google Play and download the Root Checker app to check the root status. If root checker app says root access available then Enjoy you have rooted your Moto G4 and Moto G4 Plus.
Now you have ROOTED and have installed a custom recovery on your Moto G4 Plus....
Just Hit the thanks if you like the post
Ask me for screenshots if you want them (forgot to take them but will get them u want).......
Click to expand...
Click to collapse
I have no idea how this thread is different from the one over here : http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584/
If you have found the way to root, post it there itself or in the Chainfire's thread, why bother creating a new thread to teach people the same thing again and again? Please try searching before posting.
And these lines my friend clearly say you didn't even attempt to search through :
cool_sid said:
Hello everyone.... There is no specific post on rooting and unlocking the bootloader here so I thought I'd rather post it....
So let's begin....
Click to expand...
Click to collapse

Aaaand it doest work.. my phone was frozen on the motorola logo ..

Sorry m8.... considered...... I didn't know that there was another similar post about moto g4 plus

Is this same for 16 and 32gb versions?

yash989 said:
Is this same for 16 and 32gb versions?
Click to expand...
Click to collapse
both version r same.
but this is risk.
do it on ur own risk.

Closing down thread. Please don't make anyone here as a guinea pig.. Prove it yourself first before releasing the tutorial to the public. You are just causing too much harm..

[GUIDE][TWRP][INE-LX1/2] How to install TWRP and root Huawei Nova 3i/P Smart+

This is a guide on how to unlock the bootloader, install TWRP, and root your Huawei Nova 3i/P Smart+. (INE-LX1/INE-LX2). You need at least $20 to unlock the bootloader.
Thanks for @medoamer for trying this first and helping me out!
Code:
#include <std_disclaimer.h>
/*
* Your warranty will be void if you follow this guide.
*
* Only YOU are responsible for any damage done to your
* device by following this guide. I'm not affiliated with, or
* responsible for any service mentioned below.
*
*/
You will need:
-A working Nova 3i/P Smart+.
-$20/$22/$55 depending on your preferences.
-A Windows PC. (PM me if you have a Linux one, I will update the guide accordingly)
-A working SD card that is tested and working with your phone.
-A reliable USB cable which works for connecting your phone to your PC.
-A backup (optional)
PART 1: Bootloader Unlock
To unlock your bootloader you need a bootloader unlock code. Huawei stopped giving bootloader codes in end of July. But you can buy one in one of the webistes below. You have to send your IMEI to them, and they will generate the unlock code and send it to you. You can see your IMEI at System>>About Phone>>IMEI.
1.) Global Unlocking Solutions for $20/$22
First of all, I know that the website looks super sketchy. But @medoamer, myself, and a lot of other XDA users had success with this method. I spent the extra $2 for the fast service, but it is up to you.
2.) FunkyHuawei for $55
The advantage of FunkyHuawei is that they have a good track record with XDA and other services, a refund policy, and just you know what you are getting into. You can ask for a refund if the code does not work.
3.) Ministry of Solutions for €30
A lot of XDA users had success with this method also. I don't know much information about this method, but the ysay they offer a refund if the code doesn't work.
Got the code? Good. You are mostly done now...
Install ADB and Fastboot. I'm not going to give a guide on how, you can search for it. Download and install Hisuite from here. Connect your phone to your PC, and open a command prompt on your ADB folder. Run,
Code:
adb reboot bootloader
Wait for your device to reboot and show a screen with title "FASTBOOT & RESCUE MODE". In the next command replace <code> with the unlock code you bought. The next step will wipe all the data on your device, so you might want to backup your important data.
Code:
fsatboot oem unlock <code>
Congratulations, you just unlocked the bootloader of your device. Your warranty is legally void now. Reboot the device with the command;
Code:
fastboot reboot
PART 2: Install TWRP and Magisk
First, connect your SD card to your phone, download Magisk ZIP here, and place it in your SD card.
Reboot to Fastboot again with,
Code:
adb reboot bootloader
Download the TWRP image here and copy it your ADB folder. Use this command to flash TWRP.
Code:
fastboot flash recovery_ramdisk twrp-kirin.img
Hold the power button to turn your phone off. Disconnect your phone from your PC. Now hold the power button and Vol. Up button until the Huawei logo appears, then let go of both buttons. The blue TWRP logo should appear and after a second you would see the TWRP menu. If you see the Keep System Read-Only menu, swipe right.
Go to Install>>Select Storage>>Micro SD Card. You should see the Magisk ZIP you placed there earlier. Select it, and Confirm to flash. After the flashing is over, reboot your phone.
Congratulations, now you have a rooted device!
If you need any help along the way, or end up bricking your device, I will help you the best I can.
Good Luck!

Tested procedure on PAR-LX9
I have tried the method in my Nova 3, PAR-LX9, and I confirm that this works.
I did search a little for the TWRP image since I can't access the TWRP image in your link..
If we can place another thread for the PAR-LX9 thread then that will be great.
By the way, this is my first post at xda, hopefully this post complies with the xda's rules
Cheers

codvph said:
I have tried the method in my Nova 3, PAR-LX9, and I confirm that this works.
I did search a little for the TWRP image since I can't access the TWRP image in your link..
If we can place another thread for the PAR-LX9 thread then that will be great.
By the way, this is my first post at xda, hopefully this post complies with the xda's rules
Cheers
Click to expand...
Click to collapse
Hi, Can you share the link where you got the TWRP? Can't seem to find the proper one. Thank you!

TWRP
june.castillote said:
Hi, Can you share the link where you got the TWRP? Can't seem to find the proper one. Thank you!
Click to expand...
Click to collapse
I can't post outside links for now (haven't got to 10 posts); Will try to send you PM
Note that it works in my unit PAR-LX9. If you have a different phone, flash at your own risk.

Has anyone have tried this with Nova 3i INE-LX2? Also do you have steps for Mac? Thanks!

codvph said:
I have tried the method in my Nova 3, PAR-LX9, and I confirm that this works.
I did search a little for the TWRP image since I can't access the TWRP image in your link..
If we can place another thread for the PAR-LX9 thread then that will be great.
By the way, this is my first post at xda, hopefully this post complies with the xda's rules
Cheers
Click to expand...
Click to collapse
friend do you think you could facilitate the twrp link I also have the par-lx9

TWRP
Julioz13 said:
friend do you think you could facilitate the twrp link I also have the par-lx9
Click to expand...
Click to collapse
here... this TWRP is for PAR-LX1, but I've flashed this and is working in my PAR-LX9
remember to backup before flashing...
drive.google.com/open?id=1X3jaCEUDhR08oPlAHbuwzbA07hrPcmoE

Does Phone unlocked mean bootloader unlocked?
https://forum.xda-developers.com/attachment.php?attachmentid=4633403&d=1541248513

talongt said:
Does Phone unlocked mean bootloader unlocked?
https://forum.xda-developers.com/attachment.php?attachmentid=4633403&d=1541248513
Click to expand...
Click to collapse
It SHOULD, but this device has a bug that causes it to br sometimes incorrectly displayed (Unlocked when actually locked)

Do I have to unlock bootloader first, before root it?

pls specify what version of emui to get the unlock codes.
oof, prices went up. how unfortunate.

codvph said:
here... this TWRP is for PAR-LX1, but I've flashed this and is working in my PAR-LX9
remember to backup before flashing...
drive.google.com/open?id=1X3jaCEUDhR08oPlAHbuwzbA07hrPcmoE
Click to expand...
Click to collapse
thanks friend and some page that you recommend to unlock the bootloader?

jioleight said:
pls specify what version of emui to get the unlock codes.
oof, prices went up. how unfortunate.
Click to expand...
Click to collapse
unlocking bootloader is via fastboot, so I don't think the version of EMUI is important
for reference: I unlocked mine back when EMUI was 8.2
---------- Post added at 09:59 AM ---------- Previous post was at 09:57 AM ----------
Julioz13 said:
thanks friend and some page that you recommend to unlock the bootloader?
Click to expand...
Click to collapse
global unlocking solutions.. the link is in the Nova 3i root/twrp guide
forum.xda-developers.com/nova-3/how-to/guide-how-to-install-twrp-root-huawei-t3878946
payment is via paypal.. you can message them via viber or e-mail.. they respond promptly..

Hi, the link to download the TWRP is not working. I need the recovery for INE-LX1, P Smart Plus. Could you help me? I'm trying to root my P Smart Plus.
Thanks in advance.

I'm using par-lx2...
waiting dear dev did some miracle.
firstly I'm hoping unlock bootloader and root, superSU or magisk. then I'm hoping some lineageOS or statixOS.
a moment of silence for my hopes...

No options to unlock bootloader nova 3i
NO OPTIONS TO UNLOCK BOOTLOADER NOVA 3I,
ABOVE LINKS ARE NOT WORKING.
Supersonic27543 said:
This is a guide on how to unlock the bootloader, install TWRP, and root your Huawei Nova 3i/P Smart+. (INE-LX1/INE-LX2). You need at least $20 to unlock the bootloader.
Thanks for @medoamer for trying this first and helping me out!
Code:
#include <std_disclaimer.h>
/*
* Your warranty will be void if you follow this guide.
*
* Only YOU are responsible for any damage done to your
* device by following this guide. I'm not affiliated with, or
* responsible for any service mentioned below.
*
*/
You will need:
-A working Nova 3i/P Smart+.
-$20/$22/$55 depending on your preferences.
-A Windows PC. (PM me if you have a Linux one, I will update the guide accordingly)
-A working SD card that is tested and working with your phone.
-A reliable USB cable which works for connecting your phone to your PC.
-A backup (optional)
PART 1: Bootloader Unlock
To unlock your bootloader you need a bootloader unlock code. Huawei stopped giving bootloader codes in end of July. But you can buy one in one of the webistes below. You have to send your IMEI to them, and they will generate the unlock code and send it to you. You can see your IMEI at System>>About Phone>>IMEI.
1.) Global Unlocking Solutions for $20/$22
First of all, I know that the website looks super sketchy. But @medoamer, myself, and a lot of other XDA users had success with this method. I spent the extra $2 for the fast service, but it is up to you.
2.) FunkyHuawei for $55
The advantage of FunkyHuawei is that they have a good track record with XDA and other services, a refund policy, and just you know what you are getting into. You can ask for a refund if the code does not work.
3.) Ministry of Solutions for €30
A lot of XDA users had success with this method also. I don't know much information about this method, but the ysay they offer a refund if the code doesn't work.
Got the code? Good. You are mostly done now...
Install ADB and Fastboot. I'm not going to give a guide on how, you can search for it. Download and install Hisuite from here. Connect your phone to your PC, and open a command prompt on your ADB folder. Run,
Code:
adb reboot bootloader
Wait for your device to reboot and show a screen with title "FASTBOOT & RESCUE MODE". In the next command replace <code> with the unlock code you bought. The next step will wipe all the data on your device, so you might want to backup your important data.
Code:
fsatboot oem unlock <code>
Congratulations, you just unlocked the bootloader of your device. Your warranty is legally void now. Reboot the device with the command;
Code:
fastboot reboot
PART 2: Install TWRP and Magisk
First, connect your SD card to your phone, download Magisk ZIP here, and place it in your SD card.
Reboot to Fastboot again with,
Code:
adb reboot bootloader
Download the TWRP image here and copy it your ADB folder. Use this command to flash TWRP.
Code:
fastboot flash recovery_ramdisk twrp-kirin.img
Hold the power button to turn your phone off. Disconnect your phone from your PC. Now hold the power button and Vol. Up button until the Huawei logo appears, then let go of both buttons. The blue TWRP logo should appear and after a second you would see the TWRP menu. If you see the Keep System Read-Only menu, swipe right.
Go to Install>>Select Storage>>Micro SD Card. You should see the Magisk ZIP you placed there earlier. Select it, and Confirm to flash. After the flashing is over, reboot your phone.
Congratulations, now you have a rooted device!
If you need any help along the way, or end up bricking your device, I will help you the best I can.
Good Luck!
Click to expand...
Click to collapse

@Supersonic27543 your TWRP link posted in OP to 4PDA is dead, as seen in screenshot..
 @daveyannihilation why did you delete my previous post?

hinxnz said:
@Supersonic27543 your TWRP link posted in OP to 4PDA is dead, as seen in screenshot..
@daveyannihilation why did you delete my previous post?
Click to expand...
Click to collapse
Dude what the fudge are you talking about? I haven't deleted any post of yours.

daveyannihilation said:
Dude what the fudge are you talking about? I haven't deleted any post of yours.
Click to expand...
Click to collapse
Hey sorry bout that man, must of been my bad :cyclops:

Can anyone help me?
I can't for the life of me get Magisk to install on my Nova 3i. Every time i install it with TRWP, the install runs fine, then when i reboot the device, it says "Magisk not installed"??? I've tried updating, it doesn't work. Ive tried to download the official firware, but the extractor tool doesnt work with Nova 3i. Anyone help me???
Thanks

Question We need unbrick tool for Redmagic 6/6 pro

Hello everyone, I want to ask if there is any developer who can help us please, we need unbrick tool for Redmagic 6 and 6 pro ASAP because the RM support team doesn't answer our complaints or emails. Please help us

M5tha said:
Hello everyone, I want to ask if there is any developer who can help us please, we need unbrick tool for Redmagic 6 and 6 pro ASAP because the RM support team doesn't answer our complaints or emails. Please help us
Click to expand...
Click to collapse
i've been waiting for my paperweight turn into a phone for a month now, i don't think it will be here any soon....

Nocturne Seigneur said:
i've been waiting for my paperweight turn into a phone for a month now, i don't think it will be here any soon....
Click to expand...
Click to collapse
It’s like Cinderella turning into a pumpkin after midnight. Our devices went from being phones to paperweights overnight.
Someone get our fairy god mothers up in here to bipity bopity this crap back into a working state

Out of curiosity may I ask how did it get to this state? Also I was able to get myself out thru a combination of reflashing boot.img (i was on 4.12), unlocking and relocking bootloader, and factory resetting via recovery mode. Not in that order and each multiple times. Somehow it worked out. Possibly worth a try if you are just waiting anyways with not too much to lose?
I found that a locked bootloader is good at telling whether you didn't quite flash an img right. It kept telling me that things are corrupt and whatnot, and all of a sudden it booted.

So I'm pretty close to getting a working TWRP for this device. I have extracted a basic TWRP.img file and merged it with the boot image for the Red Magic 6. When I flashed it, the logo shows up but nothing happens.
When I have time this weekend, I'll mess around with it some more.
That way we can unbrick it with twrp and not have to worry about waiting for an unbrick tool.

Nocturne Seigneur said:
i've been waiting for my paperweight turn into a phone for a month now, i don't think it will be here any soon....
Click to expand...
Click to collapse
I didn't unlock my bootloader, so I can't do anything to unbric this **** device

M5tha said:
I didn't unlock my bootloader, so I can't do anything to unbric this **** device
Click to expand...
Click to collapse
I’m in the same boat but Nubia is having me send my phone back to them to check out.

Guys the unbrick tool is already in this forum: https://forum.xda-developers.com/t/unbrick-tool-edl-flash-switch-from-cn-to-eu.4284797/
Note if you are rooted before going to EDL mode (9008) you should backup EFS via QFIL QCOM tool as a few people lost their IMEIs - I think it's in EFS Explorer the tool is free just Google it. Then do an EFS backup and save where you can't lose it. Here's a guide just ignore the Lenovo part, but you must go into diag mode Qualcomm 901D which is (try dial code *#7678# first it worked on the Red Magic 5 series, probably puts you in diag mode still) otherwise: adb shell; su; setprop sys.usb.config diag,adb before QFIL will see it: https://forums.easy-firmware.com/showthread.php/29143-How-To-Restore-Backup-QCN-EFS-on-Qualcomm-devices-(Giuide)
You can also back up the partition if you are rooted via adb shell. From memory, enable dev options (click build # under system until it shows up), patch your boot.img with Magisk Manager (should be in the ROM zip file you downloaded, copy to phone), flash back to the phone with fastboot (it will be in Downloads/magisk_patched_xyz.img "xyz" changes names just depends on Magisk) command is just after reboot to fastboot: fastboot flash boot magisk_patched_xyz.img; reboot and you should be rooted. Then from ADB do an ADB shell (it will ask to trust the device connected) adb shell (on PC), su (will ask for root access, grant it), $ dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img and copy that to your PC. That's your persist partition in case it gets messed up you should be able to: $dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist that assumes you copied persist.img back to your /sdcard/ in internal memory.
If I messed up a step feel free to correct it, this is all from memory no PC in front of me on vacation...

mslezak said:
Guys the unbrick tool is already in this forum: https://forum.xda-developers.com/t/unbrick-tool-edl-flash-switch-from-cn-to-eu.4284797/
Note if you are rooted before going to EDL mode (9008) you should backup EFS via QFIL QCOM tool as a few people lost their IMEIs - I think it's in EFS Explorer the tool is free just Google it. Then do an EFS backup and save where you can't lose it. Here's a guide just ignore the Lenovo part, but you must go into diag mode Qualcomm 901D which is (try dial code *#7678# first it worked on the Red Magic 5 series, probably puts you in diag mode still) otherwise: adb shell; su; setprop sys.usb.config diag,adb before QFIL will see it: https://forums.easy-firmware.com/showthread.php/29143-How-To-Restore-Backup-QCN-EFS-on-Qualcomm-devices-(Giuide)
You can also back up the partition if you are rooted via adb shell. From memory, enable dev options (click build # under system until it shows up), patch your boot.img with Magisk Manager (should be in the ROM zip file you downloaded, copy to phone), flash back to the phone with fastboot (it will be in Downloads/magisk_patched_xyz.img "xyz" changes names just depends on Magisk) command is just after reboot to fastboot: fastboot flash boot magisk_patched_xyz.img; reboot and you should be rooted. Then from ADB do an ADB shell (it will ask to trust the device connected) adb shell (on PC), su (will ask for root access, grant it), $ dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img and copy that to your PC. That's your persist partition in case it gets messed up you should be able to: $dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist that assumes you copied persist.img back to your /sdcard/ in internal memory.
If I messed up a step feel free to correct it, this is all from memory no PC in front of me on vacation...
Click to expand...
Click to collapse
I locked the bootlooder the screen is black, the only way to connect to the device is on a PC "COM",
I tried this link but and the next steps but it doesn't work, I don't know what to do with the phone and still it doesn't work,
I think I need the firmware RED MAGIC 6 "NX669J_NON EU Common".
PLEASE HELP ME
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.

Good evening I found a guy who unlocked the phone for me at 150 dollars.
the phone quickly repaired without any problems so the problem is solved.

Marofyxx said:
I locked the bootlooder the screen is black, the only way to connect to the device is on a PC "COM",
I tried this link but and the next steps but it doesn't work, I don't know what to do with the phone and still it doesn't work,
I think I need the firmware RED MAGIC 6 "NX669J_NON EU Common".
PLEASE HELP ME
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
Click to expand...
Click to collapse
i tried running it and now the phone is on but no display . who can help me ?
my device is :
Model: NX669J-P
Red magic OS :V4.5
Build number : NX669J_CNCommon_V7.14
Adroid version :11
Hardware version : NX669J_V1AM
I will pay for the software for you if I have to . Hope your help!

Hello,
I can give you the email of the person who repaired my phone but it's expensive 150dollar

manhdoan1601 said:
i tried running it and now the phone is on but no display . who can help me ?
my device is :
Model: NX669J-P
Red magic OS :V4.5
Build number : NX669J_CNCommon_V7.14
Adroid version :11
Hardware version : NX669J_V1AM
I will pay for the software for you if I have to . Hope your help!
Click to expand...
Click to collapse
Hello,
I can give you the email of the person who repaired my phone but it's expensive 150dollar

guide

Marofyxx said:
Hello,
I can give you the email of the person who repaired my phone but it's expensive 150dollar
Click to expand...
Click to collapse
i can pay it 150 usd . give me email

Ok

hey guys..
can u pls share qcn or especially xqcn for NX669J..?

How To Guide June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]

Pixel 6 Pro [Raven]​
Updated May 13, 2023
Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes)
Someone reported it to Google (added a comment about 34.0.1 to the existing 34.0.0 report).
Spoiler
b0uNz said:
tried to flash the latest build of AncientOS with it, did not work. Back to r33.0.3 and it worked fine
Click to expand...
Click to collapse
Aphex13 said:
platform-tools_r34.0.1-windows is not functioning properly. Back to 33.0.3 we go...
Click to expand...
Click to collapse
budmannxx said:
Add me to the list of users that had a problem with platform-tools 34.0.1. I got into a bootloop after running flash-all.bat. Downgraded to 33.0.3, reran the new (old) flash-all.bat, and was all good.
Using 34.0.1, the phone never even got to the fastbootd part of the process
Click to expand...
Click to collapse
May 10, 2023 binary update of 34.0.1:
Homeboy76 said:
Update
I tested SDK Platform-tools r. 34.0.1 it is not fixed. There are still problems with fastbootd. Use SDK Platform-tools r. 33.0.3
Click to expand...
Click to collapse
Namelesswonder said:
Anyone that updated their platform tools and needs to downgrade can use these links.
Windows
https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip
Mac
https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip
Linux
https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google Pixel Update
Android Security Bulletins | Android Open Source Project
source.android.com
Regarding Developer Support Android 12 images, see @Lughnasadh's post here.
I am not linking directly to the Developer Support Android 12 images because I don't want them to be confused with Stable Android 12, and since the Developer Support images won't receive any OTAs...ever. They likely also will never be manually updated on the Developer Support images site, so they will forever be stuck with the security patch level they're currently on, which will become further out of date every month. You can Google search Developer Support Android images if you want to find them.
TL;DR regarding the PSA. If you update one slot to Android 13, you can fastboot reboot bootloader after and then fastboot --set-active=other to change slots in order to flash Android 13 to the new slot, but IF you have Android 13 on one slot and still have Android 12 (including Android 12 bootloader) on the other slot and you try to fully boot into Android 12, you will be permanently bricked and have to seek repair from Google. No one has yet found a way to repair this on our own. I will update if there is any progress. At least a small handful, and probably more, people have done this already.
At a minimum, do this first: fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img (change the name of the bootloader file to the one for your device), then you *should* be much safer than without doing that first. Also note that the bootloader is NOT the same as boot.img (kernel). The bootloader image file has "bootloader" in the filename.
IF you have already bricked your phone and the screen is blank - there is likely nothing we can do to help. You should seek to get a repair from Google, possibly under warranty.
You CANNOT go back to Android 12 Stable. It *seems* as if you can, but Android 12 will not work 100% correctly after updating to the Android 13 bootloader.
My tiny, early, very mini-review of Android 13 is here.
Note that this is mainly for the officially listed "Unlocked" Pixel 6 Pro, available directly from the Google Store. All of this will also apply to any other (carrier-specific) variant of the Pixel 6 Pro which you can achieve an unlocked bootloader on. This includes T-Mobile and AT&T variants. It's likely Verizon variants will never be able to unlock their bootloader, or if so it will require paying the right person to do so.
Feel free to ask about general questions, but for anything that's specific to your variant, you should use one of the other already existing threads. You'll find Verizon, AT&T, and T-Mobile-related threads in those respective search results.
Click to expand...
Click to collapse
Here there be dragons. I am not responsible for anything at all.
Spoiler: Warnings / FYI
Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device.​
Click to expand...
Click to collapse
Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, your local bank's app, or even the ability to install some apps like NetFlix. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12​
Click to expand...
Click to collapse
If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it.​
Click to expand...
Click to collapse
There are no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. You will also continue to receive updates (if you've merely unlocked the bootloader, you can take updates as normal) unlike Samsung, Sony, et cetera, which have permanent major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to manually update each month, and to keep root/re-root.​
Click to expand...
Click to collapse
All posts about Google Pay or banking will be reported to be deleted. Please keep this thread on-topic. There are at least one or two other How To Guide threads in this section in which folks discuss how to get around banking app restrictions when you're rooted or just have an unlocked bootloader. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
Click to expand...
Click to collapse
If users persist in discussing banking apps in this thread, I will have this thread locked and only update this first post when there is new and updated information regarding the subjects of the title of the thread: Unlocking the Pixel 6 Pro bootloader, rooting, and TWRP. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
Click to expand...
Click to collapse
Honorable mention to @Jawomo's aodNotify - Notification Light / LED for Pixel 6 Pro! (XDA link) / Notification light / LED for Pixel - aodNotify (Play Store link), which in my opinion restores useful functionality missing in most phones these days. It also solves some subjective issues some folks have with AOD (Always On Display), and/or solves/works around the problem where AOD is required for the optical fingerprint reader to work without the screen being on.​
Click to expand...
Click to collapse
Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
Official Google Pixel Update and Software Repair (reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Lughnasadh said:
OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.
Click to expand...
Click to collapse
ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
You'll need this if you're going to unlock the bootloader on your Pixel 6 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?
You can alternately use the tools from the SDK Manager, but most of us will want to stick to the basic tools-only without the complications of the full development manager.
For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you "adb reboot-bootloader", to be able to use ADB and Fastboot.
Thanks to @96carboard for posting the details of unlocking the bootloader, be sure to thank him in his post. Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device. Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, or your local bank's app. If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it. My experience on my Pixel 1 was that there were no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. All of this should still be the case. You will also continue to receive updates. Unlike Samsung, Sony, et cetera, which have major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to keep root/re-root.:
The unlock process works like this:
1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on (you can put a SIM card if you want, you just don't have to).
2) When it starts harassing you to join Google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Repeatedly tap it until it says you're a developer.
4) Back --> Network --> WiFi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize on the phone when requested.
Using the Platform Tools previously mentioned in command line/terminal:
6) #
Code:
adb reboot-bootloader
7) #
Code:
fastboot flashing unlock
Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.
Official Instructions for Locking/Unlocking the Bootloader
Click to expand...
Click to collapse
roirraW edor ehT said:
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
Click to expand...
Click to collapse
Alekos said:
I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).
Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.
Fastboot/ADB Driver Interface - Official Download Link:
When flashing a full image or unlocking your bootloader, the fastboot interface is being used.
First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.
Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.
Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
Official Download Page
"Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"
It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).
Click to expand...
Click to collapse
Rooting-related​
@Az Biker's thread [How To Guide] [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root.​
OR
@V0latyle's thread [How To Guide] Root Pixel 6 Pro with Magisk
Click to expand...
Click to collapse
No longer applies - Things that make rooting more complicated on Android 12
@V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.
Click to expand...
Click to collapse
A list of the other important guides - be sure to thank the respective OPs
For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.
Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub. The most recent Magisk Stable is what's recommended these days.
@sean222's thread Restore WiFi and Cellular Data in Quick Settings (Root Required)
@rickysidhu_'s thread HBM (High Brightness Mode)
@gururoop's thread Probable method to upgrade every month, without wiping data and retaining root
@rickysidhu_'s thread Limit Charge
@Typhus_' thread [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
@siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ - a mod that compliments @Typhus_' mod above, and may eventually completely replace it.
@TotallyAnxious' thread [MOD] Collection of "Anxious" Modules for Pixel 6/Pro Series
Every single one of @foobar66's posts.
TWRP (not made for the Pixel 6 Pro yet - will update when it has)
I would guess that this should be the appropriate URL for official TWRP custom recovery for the Pixel 6 Pro, but who knows when/if that will actually be made available, and it may become available unofficially in these forum sections before being made official. I'll adjust this URL as needed. https://twrp.me/google/googlepixel6pro.html.
Click to expand...
Click to collapse
Custom kernels for stock ROM(s)
@Freak07's Kirisakura-Kernel for the Pixel 6 Pro (and possibly the Pixel 6)
@DespairFactor's Despair Kernel (I believe also for both the P6P and P6)
@tbalden's CleanSlate Kernel
@acuicultor's Radioactive Kernel
Click to expand...
Click to collapse
Factory Images (requires an unlocked bootloader)
It's also handy to have to the full official firmware available, whether it's to recovery from accidents or for actual development. Note the official link to the general Factory Images for Nexus and Pixel Devices page. The following link goes directly to the Pixel 6 Pro (Raven) section: Pixel 6 Pro Factory Images. I prefer to actually bookmark a link to the device listed immediately below the device I want the firmware for, because Google dumbly (in my opinion) puts the latest firmware at the bottom of the list for each particular device, and that ends up making you scroll a lot after a year or two of monthly updates.
Note: You can still get the December 2021 Factory Images and OTA from this thread, if you need them for any reason: Alternate links to December - all full factory images and OTAs available
Click to expand...
Click to collapse
Full OTA Images (doesn't require an unlocked bootloader)
Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.
Regarding P6P 5G model numbers and capabilities - post #3 below.
List of all Pixel monthly security bulletins and Play System Updates - post #4 below.
How I root and update (which is identical whether rooting the first time or updating):
Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
Extracted the new boot.img
Copied new boot.img to the phone
Patched the new boot.img with Magisk Stable
Renamed Magisk'd boot.img so I know what version of firmware it's for
Copied the Magisk'd boot.img back to the computer
Disabled all my Magisk Modules
Removed the "-w " from the flash-all.bat
Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
Open a Command Prompt, navigated to S:\platform-tools
adb reboot bootloader
flash-all.bat
Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
adb reboot bootloader
fastboot flash boot kernel.img (renamed Magisk'd boot.img)
fastboot reboot
Unlock, check everything's working
Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
Reboot, unlock, made sure everything's working
Back to modding!
Click to expand...
Click to collapse
I may append these first four posts with further useful information or links as needed.
Click to expand...
Click to collapse

Disabling Verity and Verification isn't required except for use with some custom kernels, but just rooting those custom kernels with the latest Magisk Stable v24.1 or higher should make them not require disabled Verity and Verification anymore.
A reminder that disabling Verity and Verification, at least if you've never disabled them before, will cause you to need to factory reset the device otherwise there will be corruption.
prokiller1199 said:
if you didnt disable before then it is enabled since the beginning. Disabling requires a full wipe.
It will show this image if you try to disable.
You can also verify it using adb shell with:
adb shell
su
avbctl get-verity
avbctl get-verification
{
"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"
}
Click to expand...
Click to collapse
The usefulness of having Verity and Verification enabled (now that it's not needed for root but IS still required for some custom kernels):
jwoegerbauer said:
1. DM-Verity ( VB 1.0 ) verifies /system and /vendor - it was introduced with Android 4.4, modified with Android 7
2. Android Verified Boot ( VB 2.0 aka AVB ) additionally verifies /boot - it was introduced with Android 8, works on Project Treble enabled devices
Both are running a hash on the memory blocks mentioned of your device to ensure the integrity of your software and help prevent rootkits and the like.
If you disable VB 1.0 and/or VB 2.0 your Android device becomes vulnerable to malware of any type: IMO only those do it who do not care about the built-in protection.
Click to expand...
Click to collapse
V0latyle said:
Yes - this is covered on Android Source.
The basics:
Android Verified Boot ensures that the boot code is legitimate, by using a boot image "signature" compared to a signature stored in the key registry.
Dm-verity is a method by which the code on the block devices is hashed; this hash is then compared to a reference hash to determine its authenticity before the image is loaded, thereby preventing rootkits from declaring themselves legitimate.
Vbmeta verification is a method of storing those reference hashes to which the generated hashes are compared. This can be and often is used for any critical partition, such as /boot and /system.
These aren't new concepts and indeed have been integral to Android for some time. What is new is how the Android 12 AVB headers were handled.
We still don't know exactly where in the process the problem occurred when trying to run custom boot images with Android 12. I suspect that the issue wasn't custom software itself - after all, you could still flash a custom ROM and run it without issues - but rather, trying to use a modified boot image with otherwise stock Android 12 system. Don't take my word for it, though, because I don't know for sure.
Click to expand...
Click to collapse
Freak07 said:
It has nothing to do with the kernel itself. The anykernel.zip uses magiskboot to "repack" the kernel during the flashing kernel.
Click to expand...
Click to collapse

Regarding P6P 5G model numbers and capabilities:
There are three hardware versions:
G8VOU (AU, US); also listed as G8V0U - zero instead of "oh" on some sites, Google shows the former, G8VOU) - has mmWave 5G support
GF5KQ (JP) - has mmWave 5G support
GLUOG (CA, DE, FR, GB, IE, TW) - no mmWave 5G support
For instance, my factory unlocked direct from Google in the United States Pixel 6 Pro 512 GB is a G8VOU. As far as I know, all other variations in each individual phone are controlled by software (which firmware is loaded) and over the internet (which IMEIs are Carrier Unlocked or not, and OEM Unlockable or not).
Check carriers, their 5G networks & their 5G roaming support for Pixel phones. Make sure and choose your country from the drop-down to see the list of carriers beneath.
There's also the section above that Learn which Pixel phones can work with which kinds of 5G.

My personal advice for how to get your device back up and running like you had it previously after a factory reset:
I use Nova Launcher Prime, so I do backups anytime I change my home screen or app drawer/tabs setup, so widgets and app icons and other Nova-specific configurations are easier to restore.
Go to Android Settings and use Settings' search box for Backup. Make sure that your Google account is set up to backup your apps (and app data for the apps that developers have configured to use Google's Backup API). Make sure things are backed up. Note, this doesn't backup the apps themselves, only the list of apps, so only applies to apps installed from the Play Store. As I said in parentheses, developers have to choose to integrate Google's Backup API into their app, and those apps only will get their app data backed up into Google's cloud.
If you're rooted also, then you could use something like Swift Backup to backup to the cloud. I do so, although I still restore as much as possible through Google's backup, and I only restore through Swift on a case-by-case basis, as needed when I discover an app that's tough to set back up doesn't have it's data restored by Google.
If you've used Google Photos to backup your photos to Google's cloud, then hit the button in Google Photos to free up space. This will automatically and only delete your local copies of photos and videos that it's already backed up.
Once that ^ is done, look at your internal storage with your favorite File Manger and see if there's anything left that you want to back up manually, since a factory reset will wipe everything. Copy them to your computer or a flash drive.
When you're just starting the out of the box setup after the reset, when it asks you if you want to use a cable to restore things from an old phone, choose No, and that will lead you to Google's cloud backup where you can choose to restore everything, or you can select what you want to restore.
I think you can figure out the rest.

Reserved.

Reserved.

Reserved.

Reserved.

If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.

dj24 said:
If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.
Click to expand...
Click to collapse
This one's kinda long for what it is, and this is for the Pixel 1, but it should be similar for the Pixel 6/Pro. I won't add it to the first post just yet in case there are differences, and I don't want to recommend something I can't actually try on the 6 Pro (since I won't get mine for likely another two days). Unlocking the Bootloader of the Pixel and Pixel XL
Good luck!

roirraW edor ehT said:
This one's kinda long for what it is, and this is for the Pixel 1, but it should be similar for the Pixel 6/Pro. I won't add it to the first post just yet in case there are differences, and I don't want to recommend something I can't actually try on the 6 Pro (since I won't get mine for likely another two days). Unlocking the Bootloader of the Pixel and Pixel XL
Good luck!
Click to expand...
Click to collapse
This is great. I won't be getting mine for a while as well so please come back and update this thread.

dj24 said:
If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.
Click to expand...
Click to collapse
Generally YouTube video guides for software related things aren't particularly helpful, as they can often get outdated very quickly; especially in the early days of a device as they can't be updated when new things are found out.
It would probably be best to carefully read through guides

@sidhaarthm reports here (be sure to thank him on his original post):
Bootloader successfully unlocked. I will just run everything stock for now - this is just so I don't have to wipe the device later after I have completed full setup and transferred all my data.
View attachment 5441915
Click to expand...
Click to collapse

dj24 said:
This is great. I won't be getting mine for a while as well so please come back and update this thread.
Click to expand...
Click to collapse
FYI, I'm reminded by several members in these forums that unlocking the bootloader (the first step before being able to root your Carrier-Unlocked Pixel 6 Pro) wipes the device - so does re-locking it. So I highly recommend unlocking it as the first step when you get the phone, otherwise, you'll have to back up anything that doesn't normally get backed up, and go through the initial setup process again. Not a big deal for some, but would likely not be optimal for a new user.
Instructions for Locking/Unlocking the Bootloader (note that unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device).
Click to expand...
Click to collapse

roirraW edor ehT said:
FYI, I'm reminded by several members in these forums that unlocking the bootloader (the first step before being able to root your Carrier-Unlocked Pixel 6 Pro) wipes the device - so does re-locking it. So I highly recommend unlocking it as the first step when you get the phone
Click to expand...
Click to collapse
This! It's the first thing you should do out of the box if you plan on rooting later.

@V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.

That's great news about Unlocking the bootloader! I'll be doing that first thing to be ready for the future...

Does this mean to say there is no OEM unlocking switch in the developer options screen?

biTToe said:
Does this mean to say there is no OEM unlocking switch in the developer options screen?
Click to expand...
Click to collapse
There is, its there and you need to flip it.

The unlock process works like this;
1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Tap it until it says you're a developer.
4) Back --> Network --> Wifi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
6) # adb reboot-bootloader
7) # fastboot flashing unlock
Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.