Develop Bugs

[HOW-TO] Root the Shield TV

First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
teletype said:
I just managed to get TWRP running on the new Shield console, and installed SuperSU successfully. Two caveats: the display is upside down, and the USB host ports don't work. I had to plugin a mouse via an OTG cable in order to interact with it. ETA: That's only an issue when booted to TWRP. Everything's working fine in the stock ROM after rooting.
Procedure:
- enable developer tools / USB debugging
- adb push supersu.zip /sdcard
- adb reboot bootloader
- fastboot oem unlock
- fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img
- unplug USB cable, connect mouse via USB, install SuperSU
TWRP boot image is attached. Off to explore...
EDIT: by request, some more detailed instructions:
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Go to Settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download and extract recovery.zip from this thread.
Head to the SuperSU forum and download the latest version.
Open a command prompt and navigate to the directory where you downloaded everything. (Google this for your OS if you don't know how).
With the Shield still booted, run "adb push supersu.zip /sdcard" (change supersu.zip to appropriate file name). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
If that worked fine, run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done (this was the case on my Xperia Z3 Compact). I will say that Grid streaming still works fine after doing this.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is visible.
Run "fastboot oem unlock" and follow the prompts on the screen. Your bootloader is now unlocked.
Now, boot the TWRP image with: "fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting.
You should now see a TWRP recovery menu (upside down for now).
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse

does this have to be done with an otg cable

You can use the supplied micro USB cable to do the adb portion. You shouldn't ever need otg with this device since it also has 2 full sized USB ports.
Sent from my nexus 9 using XDA Free mobile app

Instructions got updated
Hi,
I have updated the instructions to ones that more closely aligned with my experience of doing this. The initial instructions were good for me - but some were in slightly the wrong order or not quite clear enough to be immediately intuitive. I've tried to fix that Hope it helps.
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Exit settings, then go back in to settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities on to your PC if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download the latest Super user zip file from the super user thread here.
Download and extract the recovery file from here. (it needs to be a .img not a .zip)
run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is listed when you do so.
Run "fastboot oem unlock" and follow the prompts on the Shield's screen. You use the power button on the shield device itself to navigate the menu, and long press to select an option. Once you have confirmed, this can take along time to unlock (hour and a half for me on the Pro version). Your bootloader is now unlocked.
"Fastboot reboot" to reboot to AndroidTV.
run "adb push supersu.zip /sdcard/" (change supersu.zip to appropriate file name that you downloaded earlier). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
Now, boot the TWRP image with: "fastboot boot RECOVERYFILENAME.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting. (change the name of the file in the instructions to the name of your recovery file that you downloaded).
After a short while you should now see a TWRP recovery menu.
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse

Anyone tried kingroot?

Sean09 said:
Anyone tried kingroot?
Click to expand...
Click to collapse
We have a factory supported way to unlock and root. No real point in trying to exploit the system. If you are rooted, you should have a custom recovery anyway, which means you need to unlock the bootloader anyway in case you need to fix something.

Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks

Gig11gs said:
Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks
Click to expand...
Click to collapse
You can download the 1.4 firmware and flash it manually. There's a discussion on it a few pages back :good:

Will I be able to get OTA updates if I root ?

rahulkadukar said:
Will I be able to get OTA updates if I root ?
Click to expand...
Click to collapse
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.

Can I still root it this way if I already updated to 1.4 as I'm still fully stock and took the OTA

Im asking the same, im on the latest as of 2015 10 19, can i root using this method ?

baileyjr said:
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.
Click to expand...
Click to collapse
You're guided imagery? I read without understanding very much

Can anyone confirm this rooting method works for new firmware 2.1?

garz said:
Can anyone confirm this rooting method works for new firmware 2.1?
Click to expand...
Click to collapse
I struggled to get root with this write up, and I am not a rookie. There were a few key steps missing, for example, you actually have to flash twrp, you can't just boot from twrp as suggested, if you are on 1.4 and up. Also, you have to let the unit reboot after you do the OEM unlock before flashing twrp. I didn't and mine just froze after flashing the recovery img. I found this write up http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
That one in the shield zone forum was so much more complete. And yes, it worked just fine with the 2.1 update. I did it yesterday with no problems. It will wipe out your data, and it will take a long time after you do the fastboot oem unlock, especially if you have the PRO version. But root is working with no problems.

RyanInBinary said:
First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
Click to expand...
Click to collapse
Do you want to build pre-root shiled TV firmware by nvidia open source？ and have experience？

Rooting.
KingRoot dose not work on this device.

Good guide thanks.

OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?

bearkilla said:
OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?
Click to expand...
Click to collapse
Try
Adb push supersu.zip /sdcard/
Inviato dal mio SHIELD Tablet utilizzando Tapatalk

Help I bricked my Oneplus 3

Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))

have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.

bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)

Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs

bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?

Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.

simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"

Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?

ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol

bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?

gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs

Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something

simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))

Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.

simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?

Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..

jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...

simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english

Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.

can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!

[GUIDE] Relock bootloader (Should work in all versions)

Guide updated!!!!!
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Download the "Lock Script" here, according to your android version and PC's OS.
For example: if your PC uses Windows as OS, and your phone is in android 10, download the "Lock-10q_windows.bat" file.
Or if you have a Linux distro on your PC and android 9 on your phone, download "Lock-9pie_linux.sh" file.
Place the file inside the platform-tools folder, where the ROM was extracted too.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM and re-locking bootloader
Just double click on the Lock.bat/.sh file and it will reflash stock ROM and lock bootloader. Now all you have to do is wait till it finishes. This should take a few minutes to be done.
The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.

Very nice, it's really working! Thanks!

Works on xt1955-4 thanks very much, will the warranty still apply?

piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Will tell you if warranty is voided.
Sent from my ali using XDA Labs

piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
Yes, should work fine. Afaik, once you unlock your bootloader, your warranty is avoid, theoretically. But I guess you can send it to service center (if it's needed) with no problems. They don't always check if you have unlocked your bootloader or not.

Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!

Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?

DarkAngelNoctis said:
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
Click to expand...
Click to collapse
If the device is in fastboot mode only fastboot commands will work
Code:
fastboot getvar all
edit:grammer
Sent from my ali using XDA Labs

sd_shadow said:
If the device is in fastboot mode only fastboot commands work like
Click to expand...
Click to collapse
Ok. Thanks!

LuisLFSS said:
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Click to expand...
Click to collapse
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks

darko454 said:
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
Click to expand...
Click to collapse
Yes, it's safe. Now we have blankflash so it's safe

LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
ok thanks!

LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.

hawkdown77 said:
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
Click to expand...
Click to collapse
Yes, join in my group: t.me/motog7brasil

LuisF201707 said:
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM
If you're already in stock ROM with no modules and stuff installed on it, just skip this and jump to the next step. If you're not, then stay here.
Open CMD (command prompt) in the same folder you had extracted firmware and android platform tools.
Shift+right click and then "Open command window here" or just type CMD in the folder path bar at the top in windows explorer. Run this commands all at once in CMD:
Once it is done, DON'T power on your phone, just leave it as it is and let's go to the last step.
Step 4 - Relocking Bootoader
In cmd, run this commands all at once
Done! The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Click to expand...
Click to collapse
There is an bat file out to relsash stock rom with out trying all that stuff in manually

Help
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch

JPalomo1997 said:
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
Click to expand...
Click to collapse
Which android version? There's april security patch for android 9 and 10...

roadkill42 said:
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Click to expand...
Click to collapse
I know... I'll update the thread soon

chrisbchrisb85 said:
For step 4 relocking the bootloader what does "run these commands all at once" mean??? As soon as I lock the bootloader I can no longer flash anything else, therefore still stuck with a boot screen warning
Click to expand...
Click to collapse
"run these commands all at once" = copy all the commands and execute them in cmd...
And which android version did you install? because the commands to flash android 10 are different than android 9 ones

Guide updated!!!!!
I removed those annoying commands and put a link to download Scripts that already do everything automatically. Now the guide is simpler and easier

Question Update to January HELP

I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much

I just updated from Dec/rooted to Jan/rooted by running Flash-all -nowipe while having my phone in Fastboot mode. I then patched the boot.img. Went very smoothly.

clipdawg05 said:
I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much
Click to expand...
Click to collapse
Here ya go. Let's try to keep all rooting questions in this forum. It will make it easier to get an answer and the OP has put in a lot of work to keep this up to date. Otherwise we have 'update to January help' which says nothing. Give it a try and there are a lot of people there willing to help you.
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com

bobby janow said:
Here ya go. Let's try to keep all rooting questions in this forum. It will make it easier to get an answer and the OP has put in a lot of work to keep this up to date. Otherwise we have 'update to January help' which says nothing. Give it a try and there are a lot of people there willing to help you.
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Click to expand...
Click to collapse
ok thank you

clipdawg05 said:
I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much
Click to expand...
Click to collapse
I'd recommend using this method from the linked Thread above
Don't forget to get the boot.img from the new Firmware (extract factory image, find it) and patch that with Magisk, then transfer it back to your PC ADB folder and use that as "master root").

Morgrain said:
I'd recommend using this method from the linked Thread above
View attachment 5509367
Don't forget to get the boot.img from the new Firmware (extract factory image, find it) and patch that with Magisk, then transfer it back to your PC ADB folder and use that as "master root").
Click to expand...
Click to collapse
This is the boot img from when I rooted the phone the first time, or do I have to patch the boot from this new January update

clipdawg05 said:
This is the boot img from when I rooted the phone the first time, or do I have to patch the boot from this new January update
Click to expand...
Click to collapse
Patch the new January boot image and use that instead of the old one.
Also when you do step 4, (after the system boots normally and you see the update bar slowly rising until the OS comes), unlock the phone and look into notifications, it will say something like "finishing updates", only when that finishes you reboot into bootloader.

This happened as soon as i pressed enter. What to do now

What I did (p6p, november update, rooted, bootloader unlocked):
1. Downloaded latest Jan factory image https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip, extracted boot.img and put it aside for step 6.
2. Disabled all magisk modules (not necessary, just in case).
3. Went to flash.android.com via Edge, agreed to all prompts on the page and phone screen.
4. UNCHECKED all checkboxes. There were 3 of them, something like Wipe All, Lock Bootlocker, Flash All Partitions).
5. Follow all prompts - "Reselect your device" etc.
6. Successfully rebooted, put boot.img file into phone's memory, run Magisk app and patched boot file.
7. Moved the patched file "magisk_patched-23016_IVwVbT.img" (your file name may be different) back to my pc and run via cmd "fastboot flash boot <location of your patched boot img file>".
8. Rebooted and re-enabled all magisk modules.
With the January update I experience no issues and honestly no changes that I could notice. At least I'm happy there is nothing worse

clipdawg05 said:
This happened as soon as i pressed enter. What to do now
Click to expand...
Click to collapse
If you reboot and come back to the same screen I'm afraid your only option is to wipe data/factory reset.

asdor said:
If you reboot and come back to the same screen I'm afraid your only option is to wipe data/factory reset.
Click to expand...
Click to collapse
ok i will reset. i tried adb devices and it says unauthorized

I think there is something wrong with my phone. When i try a normal update it fails. When i try the android flash tool it tells me my phone is already in use and sideloading does not work.
Finally got past the phone already in use by restarting, only to have another failure flashing

clipdawg05 said:
This happened as soon as i pressed enter. What to do now
Click to expand...
Click to collapse
What does that even mean? What're you doing when you hit enter to get that screen? I'm assuming you're issuing a fastboot command but you need to provide more details.
clipdawg05 said:
ok i will reset. i tried adb devices and it says unauthorized
Click to expand...
Click to collapse
You need to enable developer options on your phone if you haven't already. Go into settings > about phone > click on build number until it says "you're a developer" at the bottom. Then, go into settings > system > developer options and enable USB debugging. Try running adb devices again and clock on "allow" prompt on your phone when it pops up.
clipdawg05 said:
I think there is something wrong with my phone. When i try a normal update it fails. When i try the android flash tool it tells me my phone is already in use and sideloading does not work.
Finally got past the phone already in use by restarting, only to have another failure flashing
Click to expand...
Click to collapse
It says phone is in use because you need to issue a "adb kill-server" command and then try the flash tool again.
I had the same OTA issue yesterday. You can try using the flash tool again once you issue the "adb kill-server" command, but if it doesn't work try applying the update via sideload.
Download the OTA image from here - https://dl.google.com/dl/android/aosp/raven-ota-sq1d.220105.007-3a7aafbf.zip
You will also need the stock image so you can extract the boot img. Get it from here - https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip
Once you do that, follow these steps.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image:
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
You can find full instructions in this thread:
https://forum.xda-developers.com/t/guide-root-pixel-6-pro-raven-with-magisk.4356231

RetroTech07 said:
What does that even mean? What're you doing when you hit enter to get that screen? I'm assuming you're issuing a fastboot command but you need to provide more details.
You need to enable developer options on your phone if you haven't already. Go into settings > about phone > click on build number until it says "you're a developer" at the bottom. Then, go into settings > system > developer options and enable USB debugging. Try running adb devices again and clock on "allow" prompt on your phone when it pops up.
It says phone is in use because you need to issue a "adb kill-server" command and then try the flash tool again.
I had the same OTA issue yesterday. You can try using the flash tool again once you issue the "adb kill-server" command, but if it doesn't work try applying the update via sideload.
Download the OTA image from here - https://dl.google.com/dl/android/aosp/raven-ota-sq1d.220105.007-3a7aafbf.zip
You will also need the stock image so you can extract the boot img. Get it from here - https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip
Once you do that, follow these steps.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image:
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
You can find full instructions in this thread:
https://forum.xda-developers.com/t/guide-root-pixel-6-pro-raven-with-magisk.4356231/[/CODE]
[/LIST]
Click to expand...
Click to collapse
The first picture of a failure was when I was trying to sideload the update.
Thanks for your response but i finally got it done on Android flash tool with the wipe enabled

OnePlus 7T boot error after Android F.15 update

Hello, I downloaded and installed android beta update https://gauss-componentotacostmanua...22/08/03/b5192ec34f094ad9bb76e5554cd69f89.zip from https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-open-beta-2/amp/ and since then the device is just booting in loops and not going ahead. I get the boot reason error as attached. The boot logo has also changed.
My device did not had developer module enabled nor had I backed up any data from my mobile before installing the update.
I desperately want to recover data from my phone before formatting it. Please assist. Thanks a lot.

kiranlalge said:
Hello, I downloaded and installed android beta update https://gauss-componentotacostmanua...22/08/03/b5192ec34f094ad9bb76e5554cd69f89.zip from https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-open-beta-2/amp/ and since then the device is just booting in loops and not going ahead. I get the boot reason error as attached. The boot logo has also changed.
My device did not had developer module enabled nor had I backed up any data from my mobile before installing the update.
I desperately want to recover data from my phone before formatting it. Please assist. Thanks a lot.
Click to expand...
Click to collapse
Try to reboot into recovery, then normal reboot.

Did that already. No luck :-(

kiranlalge said:
Did that already. No luck :-(
Click to expand...
Click to collapse
Data must be formatted to boot

HueyT said:
Data must be formatted to boot
Click to expand...
Click to collapse
Sorry I cannot afford to format the device as I'm desperate to recover the data.

Take phone to repair shop to download data via adb commands using laptop
Also try switching slots in fastboot mode: "fastboot set_active other" and then "fastboot reboot"

HueyT said:
Take phone to repair shop to download data via adb commands using laptop
Click to expand...
Click to collapse
I have ADB utilities on my laptop. I connect my device to my laptop via USB cable and then do "adb devices" on the command prompt. It shows no devices. Perhaps this happens because my device was not rooted? Is there any other way I can access files on my device using adb?
HueyT said:
Also try switching slots in fastboot mode: "fastboot set_active other" and then "fastboot reboot"
Click to expand...
Click to collapse
Please can you elaborate a little more on this? Where to switch slots? Can we connect over WhatsApp or a ZOOM call please?

kiranlalge said:
Please can you elaborate a little more on this? Where to switch slots? Can we connect over WhatsApp or a ZOOM call please?
Click to expand...
Click to collapse
Enable USB debugging in developer options
Spoiler

HueyT said:
Enable USB debugging in developer options
Click to expand...
Click to collapse
The device needs to be booted successfully to enable USB debugging. Booting is the fundamental problem. How can I enable USB debugging without booting the device?
The device needs to be booted successfully to see this screen. Booting is the fundamental problem. How can I enable USB debugging without booting the device?

Phone needs to be off. Try holding down vol. Down button, power button til it reboots into bootloader mode while plugged into usb-c to USB-a cable to laptop. Then type "fastboot devices" on laptop while changed into adb subdirectory with "command C:/ prompt"

HueyT said:
Phone needs to be off. Try holding down vol. Down button, power button til it reboots into bootloader mode while plugged into usb-c to USB-a cable to laptop. Then type "fastboot devices" on laptop while changed into adb subdirectory with "command C:/ prompt"
Click to expand...
Click to collapse
I appreciate you trying to help me promptly. Thank you.
I tried doing what you advised. The command did not show anything. Photos attached.

You need to unlock bootloader by using Superboy msmtool, but will lose all data
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
You shouldn't mess with oos12 with locked bootloader as it can lose data
You could try to manually flash each file using fastboot (fastboot devices must show a number so install correct OnePlus and adb drivers for windows 10) --use payload dumper to extract all files from payload.bin from Indian op7t rollback zip below. Just don't do "fastboot -w" as that will format your data
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip

HueyT said:
You could try to manually flash each file using fastboot (fastboot devices must show a number so install correct OnePlus and adb drivers for windows 10) --use payload dumper to extract all files from payload.bin from Indian op7t rollback zip below. Just don't do "fastboot -w" as that will format your data
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip
Click to expand...
Click to collapse
Thank you. I have just started downloading this file (2.6 GB) on my laptop. Yes I am very keen to save my data before formatting. Please can you guide on the next steps to do after the download completes?
I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
kiranlalge said:
Thank you. I have just started downloading this file (2.6 GB) on my laptop. Yes I am very keen to save my data before formatting. Please can you guide on the next steps to do after the download completes?
I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
Click to expand...
Click to collapse
Right OK so I have downloaded the ZIP package and have also managed to extract the payload.bin file. See file contents in the attached image.
Please can you guide on the next steps hereafter? I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
kiranlalge said:
Right OK so I have downloaded the ZIP package and have also managed to extract the payload.bin file. See file contents in the attached image.
Please can you guide on the next steps hereafter? I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
Click to expand...
Click to collapse
I think this is getting closer. I managed to install drivers as in the attached. Please take a look. 3 out of 4 have yellow triangles not sure if that means any issue. The 4th one appears only when I connect the device to laptop via a cable.

Only works on win10/11

HueyT said:
Only works on win10/11
Click to expand...
Click to collapse
OK. I still tried on Windows 7 and I got the attached. If I manage to change the slot from a to b using "https://www.droidwin.com/fix-failed-remote-slot-change-is-not-allowed-in-lock-state/", then will I loose any data? Again, I'm very keen to retrieve my data.

kiranlalge said:
OK. I still tried on Windows 7 and I got the attached. If I manage to change the slot from a to b using "https://www.droidwin.com/fix-failed-remote-slot-change-is-not-allowed-in-lock-state/", then will I loose any data? Again, I'm very keen to retrieve my data.
Click to expand...
Click to collapse
Yes, unlocking BL will wipe data

HueyT said:
Yes, unlocking BL will wipe data
Click to expand...
Click to collapse
Thats sad :-( I'm looking for a solution to retain all my data in a situation where my device is just booting in loops (not reaching the home screen), developer option is disabled and USB debugging is also disabled. Please help.

kiranlalge said:
Thats sad :-( I'm looking for a solution to retain all my data in a situation where my device is just booting in loops (not reaching the home screen), developer option is disabled and USB debugging is also disabled. Please help.
Click to expand...
Click to collapse
All you can do is keep repeating reboot to recovery, normal reboot, reboot to bootloader, reboot to recovery, normal reboot, while praying and hoping that your phone boots up.

kiranlalge said:
Thats sad :-( I'm looking for a solution to retain all my data in a situation where my device is just booting in loops (not reaching the home screen), developer option is disabled and USB debugging is also disabled. Please help.
Click to expand...
Click to collapse
Does "fastboot devices" give you numbers and letters?

HueyT said:
Does "fastboot devices" give you numbers and letters?
Click to expand...
Click to collapse
Yes. It printed the serial no. of my device.