Develop Bugs

[Q] How to sim-unlock?

I have been following this guide over here http://forum.xda-developers.com/showthread.php?t=2221039 and did this :
1. Unlocked bootloader from htcdev
Questions :
Where should I copy the rom in step 2 ? What folders are from the SD card?
When I go in bootloader recovery an image of phone with ! wrapped in triangle is shown?
Is there any other simple free way to sim unlock my HTC Desire HD?

1) download the rom on your PC when download plug your phone into USB then select mount to copy files. Then drag & drop the from to the root of the sdcard ( not in any folders.
2) sounds like you don't have a custom recovery installed.
Also just to point out the cmd line for fast boot should be: fastboot flash recovery recovery1.img
Sent from my Desire HD using xda app-developers app

BlackLynx said:
I have been following this guide over here http://forum.xda-developers.com/showthread.php?t=2221039 and did this :
1. Unlocked bootloader from htcdev
Questions :
Where should I copy the rom in step 2 ? What folders are from the SD card?
When I go in bootloader recovery an image of phone with ! wrapped in triangle is shown?
Is there any other simple free way to sim unlock my HTC Desire HD?
Click to expand...
Click to collapse
What is your HBOOT Version?

thekool said:
What is your HBOOT Version?
Click to expand...
Click to collapse
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011, 14:28:19
When I go in recovery it first displays the HTC on white logo, then phone with symbol similar to active sync symbol, and then the phone with the exclamation mark in triangle, it cannot be turned off, i have to remove battery and then restart.

If you follow the linked guide in this thread, it also will remove the carrier lock. I followed the guide with a Telus-locked phone and, after completing, the phone is sim unlocked.

audit13 said:
If you follow the linked guide in this thread, it also will remove the carrier lock. I followed the guide with a Telus-locked phone and, after completing, the phone is sim unlocked.
Click to expand...
Click to collapse
Did you install custom recovery before? Were you able to go to recovery in bootloader?

BlackLynx said:
Did you install custom recovery before? Were you able to go to recovery in bootloader?
Click to expand...
Click to collapse
you need to put the rom zip on your card, when you open the card on your computer, just paste it in as you open it in your file explorer or whatever.Then fastboot flash recovery recovery1.img, wipe data/factory reset, flash the zip from install zip from sdcard option, go upwards so you reach the bottom faster, and select your zip.Flash it, reboot, then continue with the guide.

BlackLynx said:
Did you install custom recovery before? Were you able to go to recovery in bootloader?
Click to expand...
Click to collapse
The guide did all three for me. I rooted, unlocked the bootloader, and it installed 4ext.
If you just want to sum-unlock the phone and nothing else, you could just buy a cheap unlock code.

Steam. said:
you need to put the rom zip on your card, when you open the card on your computer, just paste it in as you open it in your file explorer or whatever.Then fastboot flash recovery recovery1.img, wipe data/factory reset, flash the zip from install zip from sdcard option, go upwards so you reach the bottom faster, and select your zip.Flash it, reboot, then continue with the guide.
Click to expand...
Click to collapse
When I boot in bootloader or fastboot or whatever- should I leave the phone connection with the PC - on mounted as disk drive? or change it back to charge only?

BlackLynx said:
When I boot in bootloader or fastboot or whatever- should I leave the phone connection with the PC - on mounted as disk drive? or change it back to charge only?
Click to expand...
Click to collapse
Disconnect when rebooting to bootloader, then pick fastboot, then connect the USB cable.

Steam. said:
Disconnect when rebooting to bootloader, then pick fastboot, then connect the USB cable.
Click to expand...
Click to collapse
Ok, I am in fastboot usb.. ill "fastboot recovery1.img" and then go in recovery.

I checked if i have root access... with "adb shell" then "su" then i went back with "exit" "exit"
Now the next command gives me error
{
"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"
}

BlackLynx said:
I checked if i have root access... with "adb shell" then "su" then i went back with "exit" "exit"
Now the next command gives me error
Click to expand...
Click to collapse
You were not granted root access. That is why it says read only
Sent from my GT-N7100 using xda app-developers app

Rooted, did everything correct, got s-off and bootloader is unlocked, but sim card still not detected.

BlackLynx said:
Rooted, did everything correct, got s-off and bootloader is unlocked, but sim card still not detected.
Click to expand...
Click to collapse
Before going through the guide, were you prompted to enter a network unlock code with your sim on the phone? If not, is it possible the phone was already carrier unlocked?
If you were prompted for a network unlock code before completing the steps in the guide and you are no longer being prompted for a network unlock code, sounds to me like your phone is now unlocked.

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | Smartwatch 3

Link To Main Thread
{
"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"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.

Reserved
Reserved.

i try but the program doesn't unlock the bootloader. The smartphone go in fastboot mode but nothing happen

fer2503 said:
i try but the program doesn't unlock the bootloader. The smartphone go in fastboot mode but nothing happen
Click to expand...
Click to collapse
Once it's in fastboot, try doing the Unlock Bootloader command again. Sometimes the program gets stuck when the phone reboots then tries to do a command.

WinDroid Universal Android Toolkit v2.3 Now Out!
I'm happy to announce that the WinDroid Universal Android Toolkit v2.3 update is now out! It includes a bunch of new features, fixes and supported devices, so check it out and let me know what you think! :fingers-crossed:
You can download it here.

fastboot boot
This is not working for me. Bootloader unlocked but I cannot go into the TWRP recovery.
Later I followed this thread: it both mentioned reason and solution as below.
If you boot into system without booting twrp once, the system overwrittes twrp with the stock recovery. If this happens to you, then boot into fastboot and boot twrp without flashing it with "fastboot boot <NAMEOFTHE.IMG>". Afterwards boot into bootloader from the recovery's reboot menu and flash twrp again
Click to expand...
Click to collapse
I successfully rooted the watch.

WinDroid Universal Android Toolkit v2.5 Now Out!
I'm happy to announce that the WinDroid Universal Android Toolkit v2.5 update is now out! As always, let me know what you think and report any bugs you encounter! :highfive:
You can download it here.

not loading
win 7 64bit, it is not loading and crashing..
problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: AMVTCOVYVOYG4CJW4BOZUOCFK2NAVXGX
Problem Signature 02: 2.5.0.0
Problem Signature 03: 55ff894d
Problem Signature 04: PresentationCore
Problem Signature 05: 4.0.0.0
Problem Signature 06: 4ba2361f
Problem Signature 07: 13ce
Problem Signature 08: 7
Problem Signature 09: System.IO.FileLoadException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: ba19
Additional Information 2: ba19cb920b085645c3e4b12657df4b92
Additional Information 3: 770c
Additional Information 4: 770ce0b63d515dfb5051b12f5c3687e7

WinDroid Toolkit v3.0 Is Now Out!
WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!
You can out more specific changes in the changelog here.
You can download the new update here.
All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!

How can i root my sw3?

chikrron said:
How can i root my sw3?
Click to expand...
Click to collapse
it fails to unlock bootloader for me

daveyp187 said:
it fails to unlock bootloader for me
Click to expand...
Click to collapse
Me too

don't think this is working

daveyp187 said:
it fails to unlock bootloader for me
Click to expand...
Click to collapse
chikrron said:
Me too
Click to expand...
Click to collapse
MacSeoin said:
don't think this is working
Click to expand...
Click to collapse
Just go through this process..
Plug the SWR50 into the computer (be sure ADB Debugging is turned on), and type this in CMD:
Code:
adb reboot bootloader
The watch will reboot into Fastboot mode.
Then type this (yes, twice):
Code:
fastboot oem unlock
fastboot oem unlock
fastboot reboot
Now your bootloader is unlocked.

Ok, been playing around, seems my issue was windows 10 fastboot drivers. Android SDK and device manager sorted this, I didn't need to unlock the bootloader in the end, I just fastboot then hotboot recovery and push SuperSU and then flash it from recovery. Now rooted

crunchybutternut said:
Just go through this process..
Plug the SWR50 into the computer (be sure ADB Debugging is turned on), and type this in CMD:
Code:
adb reboot bootloader
The watch will reboot into Fastboot mode.
Then type this (yes, twice):
Code:
fastboot oem unlock
fastboot oem unlock
fastboot reboot
Now your bootloader is unlocked.
Click to expand...
Click to collapse
Tried this but always says <waiting for device>

You need to update your driver. Fastboot, stock recovery, twrp, and the running system all have slightly different drivers. Most packages include all the drivers, but some do not. It is notoriously annoying to get all the pieces to work right on Win 10.
Sent from my SM-T810 using Tapatalk

hi, i've got the last android wear update,and i'm trying to root the smartwatch with the windroid toolkit...but when i try to unlock the bootloader or flashing twrp recovey,the watch reboot in fastboot mode,and it gets stucked in it,doin' nothing...when i try to root the device,it goes in recovery mode,but there isn't any file to install,as suggested from the step to step guide of the windows program. i'm running windows 10..any suggestion on how to fix the problem..?

Unable to unlock?
I tried to unlock my sw3, but nothing changed after it says "Your bootloader is now unlocked"...

For those trying to use this app to unlock and root you SW3 please just have a look at
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
and
http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3353580
Full instructions are at the beginning of the thread..

Can't unlock bootloader on N5X

Hello guys I try 10 times unlock my N5X bootloader and nothing happened after everything. I am using NRT method. I have developer options enabled and oem unlock turned on. Phone is going to bootloader mode I tap on screen when I choose if I want to unlock and after all procedure device has wiped data because I have to set my language etc. etc. but when I want to root it in bootloader mode system show BOOTLOADER: locked. I posted screen. What am I doing wrong. Thx for helping!
{
"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"
}

Blacknighter said:
Hello guys I try 10 times unlock my N5X bootloader and nothing happened after everything. I am using NRT method. I have developer options enabled and oem unlock turned on. Phone is going to bootloader mode I tap on screen when I choose if I want to unlock and after all procedure device has wiped data because I have to set my language etc. etc. but when I want to root it in bootloader mode system show BOOTLOADER: locked. I posted screen. What am I doing wrong. Thx for helping!
Click to expand...
Click to collapse
Did you flash twrp?
I reccomend you start from scratch using this guide:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Doing it all manually gives you a way better understanding of what you are doing than using a toolkit.

Bro I can't unlock bootloader, so how can I install TWRP? What is this secure boot: enabled , what does NO RPMB mean?

Blacknighter said:
Bro I can't unlock bootloader, so how can I install TWRP? What is this secure boot: enabled , what does NO RPMB mean?
Click to expand...
Click to collapse
Just trying to help. Chill a bit please. The second part of your story isn't all that clear.
Let's take a few steps back. Do you have fastboot access working?

Yes, when I connect phone to PC in fastboot pc see my phone.

Blacknighter said:
Yes, when I connect phone to PC in fastboot pc see my phone.
Click to expand...
Click to collapse
And you tried the manual steps in Heisenbergs guide?
Mainly:
Fastbbot devices (check serial)
Fastboot OEM unlock
Fastboot reboot
If that doesn't work there's probably something wrong in your initial setup.

When I wrote command fastboot devices I don't saw serial ... so problem is here. What to do?

Blacknighter said:
When I wrote command fastboot devices I don't saw serial ... so problem is here. What to do?
Click to expand...
Click to collapse
My guess is not all required software is installed correctly.
As I said start from scratch using the guide I mentioned.

On third PC I get the sam result - when I fastboot oem unlock, I will see the lock state change to unlock, but then when I execute fastboot reboot-bootloader, the lock state after reboot will show locked.

Blacknighter said:
On third PC I get the sam result - when I fastboot oem unlock, I will see the lock state change to unlock, but then when I execute fastboot reboot-bootloader, the lock state after reboot will show locked.
Click to expand...
Click to collapse
What if you flash TWRP before executing "fastboot reboot-bootloader". Does it work?

C:\SDK\platform-tools>fastboot devices
0140998a5ec096e4 fastboot
C:\SDK\platform-tools>fastboot oem unlock
...
OKAY [ 3.972s]
finished. total time: 3.972s
C:\SDK\platform-tools>fastboot flash recovery twrp_bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16325 KB)...
OKAY [ 0.590s]
writing 'recovery'...
OKAY [ 0.100s]
finished. total time: 0.700s
C:\SDK\platform-tools>
After rebooting, information appeared that file may be corruption, but when I go to recovery it still showing state LOCKED. Now after rebooting system Logo Google appeared and nothing happened (Bootloop?) Now I can't do anything

Why after rebooting everything goes back and device state is LOCKED? I have motherboard replaced by warranty service. What to do?

USB drivers are (re-)installed?
You never relocked bootloader at any point in the proces?

OK I flash *.img files manually one by one and I installed system. But main problem isn't solved.
After fastboot command oem unlock in bootloader mode it showing bootloader unlocked but after rebooting STATE is showing LOCK.
Any ideas? What **** is restore back system unlock to lock?

ok I found a simillar thread
http://forum.xda-developers.com/google-nexus-5/help/fastboot-oem-unlock-goes-to-lock-reboot-t2903581
So it can't be repaired... great warranty service replace my damaged motherboard for another not good working motherboard where I can't unlock bootloader to even flash nexus factory images hehehehehe OMG...

It's not fastboot oem unlock anymore.. The command is fastboot flashing unlock
Sent from my Nexus 5X using Tapatalk

graffixnyc said:
It's not fastboot oem unlock anymore.. The command is fastboot flashing unlock
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Since when is this implemented?

Even I wrote command fastboot flashing unlock, after reboot bootloader I get the same result - state: locked :/ and I have to again set everything from the beginning because command wipes my device... Thx for trying to helping me but I think that nothing can solve this problem.

Blacknighter said:
Even I wrote command fastboot flashing unlock, after reboot bootloader I get the same result - state: locked :/ and I have to again set everything from the beginning because command wipes my device... Thx for trying to helping me but I think that nothing can solve this problem.
Click to expand...
Click to collapse
Which version of the SDK and Platform Tools do you have installed?
Sent from my Nexus 5X using Tapatalk

I have installed latest sdk tools version. What does this have to do with it? I have all drivers installed. Any fastboot commands work ok, even flashing manually img files also work. System after rebooting bootloader do not save the unlock state settings :/

MI 9 SE Brick After Locking the Bootloader (Global rom installed on Chinese phone)

Hi everyone!
I bought a MI 9 SE for my dad, it was a Chinese version with an unlocked bootloader and global rom installed.
After trying to use Google Pay, I figured it needs a locked bootloader. So I locked it using "fastboot oem lock".
After that, the phone is bricked
I didn't have an account bound to it, so can't use the official unlock.
Can access fastboot and recovery.
Tried flashing using recovery, sideloading.
It refuses to install a chinese rom, only a global one can be installed.
Obviously, I get the "This MIUI version can't be installed on this device".
I know there's the EDL path, but that requires an authorized account
Is there any other way around this?
Is there a way to force install a chinese rom over the global rom?
I would really appreciate any help or advice. I've spent a few days reading the forums, tried a lot of utilities but with zero luck.

Did you try the original chinese ROM, the first release? The same with global?

elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
I have tried the last few MIUI versions, but didn't try the original release versions. That's a good point! Will try today, and get back with the results :good:

If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from https://drive.google.com/open?id=1-Np8xHPfVlJwUJLURntIklmkCyVqU5jH and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.

Flounderist said:
If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.
Click to expand...
Click to collapse
{
"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"
}
It didn't work, says 'Flashing is not allowed in Lock State'

elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
The same error both times, seems it refuses to install older versions of MIUI

savandriy said:
The same error both times, seems it refuses to install older versions of MIUI
Click to expand...
Click to collapse
Oh, you don't use miflash tools?

savandriy said:
It didn't work, says 'Flashing is not allowed in Lock State'
Click to expand...
Click to collapse
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily

Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box

Flounderist said:
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
What the hell, I have a family? What's this about?

Grus said:
What the hell, I have a family? What's this about?
Click to expand...
Click to collapse
Hahaha sorry mate. It's the link of a telegram group and it matched with your nickname.
Grus is the device name for Mi 9 SE :laugh:

That's so incredibly strange. Guess I'll have to check that phone out.

Flounderist said:
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
Sadly, it just hangs forever on the "Sending 'userdata' (4400 KB)" part ...

pikouchou said:
Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box
Click to expand...
Click to collapse
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?

savandriy said:
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?
Click to expand...
Click to collapse
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.

https://mirom.ezbox.idv.tw/en/phone/grus/roms-cn-stable/
Try the first chinese version (10.2.3).

Flounderist said:
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.
Click to expand...
Click to collapse
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then

Try global too. I would try all Chinese and global versions, just to be sure. Because, you know, edl isn't free.

savandriy said:
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then
Click to expand...
Click to collapse
If you get device mismatch error you should:
- check if your device is actually a Mi9 SE
- check if you downloaded a fastboot ROM for Mi 9SE
- check if you are using the latest MIUI driver and MiFlash.
Probably your device had a fake-MIUI ROM installed with some messed device fingerprint, hence MiFlash does not recognize it as Grus.
If you are 100% sure your device is a Mi 9SE, and you downloaded the correct ROM (I would recommend latest China Stable), you can try editing the flash-all.bat file.
Here is a tutorial (you probably will need to translate it): https://www.miui.it/forum/index.php...lazione-delle-rom-fastboot-con-miflash.15301/
Good luck!

You can flash him only with testpoint and auth account

Question Android 13 and unlocked bootloader

Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
Click to expand...
Click to collapse
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?

Ralendil said:
Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?
Click to expand...
Click to collapse
You don't need to do all of that to upgrade to android 13. You can read how to upgrade to android 13 here: https://forum.xda-developers.com/t/...-6-pro-bootloader-central-repository.4352027/
as well as here: https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root-update.4361847/
it is a long thread with a lot of information, so I'll just give you an adlibbed version of how to upgrade
I read that you have removed root. You can re-root after upgrading. Make sure your bootloader is unlocked first.
First make sure you have the latest sdk platform tools version here: https://developer.android.com/studio/releases/platform-tools
Download the android 13 factory image here: https://developers.google.com/android/images
Extract the platform tools and the factory image, and make sure the flash-all.bat file is in the same location as adb.exe and fastboot.exe
If you want to keep your data, do this. If you don't want to lose your data and don't mind wiping your phone, skip this step and just run flash-all.bat in fastboot.
Edit the flash-all.bat file and remove the -w flag from the
Code:
fastboot update -w image-raven-tp1a.220624.021.zip
command. So it'll just be
Code:
fastboot update image-raven-tp1a.220624.021.zip
Save it, edit again just to double check that -w flag is gone. If it is, reboot your phone back into fastboot and run flash-all.bat.
It'll upgrade and do everything for you. You're on Android 13 now and your data is still intact.
Once your phone is booted, you can patch the boot image from the factory image you downloaded with Magisk and flash it in fastboot again by doing fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img. Then you will have root.
If you want to go back to complete factory with a locked bootloader, run Android Flash Tool from Google here: https://flash.android.com/welcome?continue=/back-to-public
Make sure "Wipe Device", "Lock Bootloader", and "Force Flash All Partitions" are checked.

You could always try the 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). It's possible you could also take advantage of it's new option to flash only the 13 bootloader to both slots, and then will update the current slot to 13 completely.
Lughnasadh said:
FYI: Even though Android Flash Tool does not flash the whole image to both slots, they have added an option to flash the A13 bootloader to the inactive slot. This may be the easiest option to use when updating to A13 from A12.
Just to be clear, when updating to A13 from A12 a prompt will show up asking whether you want to also flash the bootloader to the inactive slot as well. It doesn't show up in the regular tick boxes.
{
"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
FYI, you most definitely didn't need to re-lock the bootloader. Also, a pro tip for rooters. Once you unlock a device's bootloader, never ever re-lock it except in very rare circumstances. This didn't count as rare before you consult us.

I would have loved that it would be a solution.
It would allow me only to install android 12... and locking the bootloader make me affraid… I think I will never be able to unlock it cause I can’t use bootloader (see under)
For now, I try to make bootloader drivers working.
Every time I reboot to bootloader, the phone is not recognized by the computer and no adb/fastboot command can be used. So, I cannot use the flash-all.bat script.
Also, now when I use adb reboot fastboot the fastboot screen appears, then bootloader is loaded immediately...
I can’t believe I will spend several hours to be able to install that… I am stuck.
I tried to uninstall several drivers and reinstall drivers, but no changes... or yes a change. Now it is worst, Pixel 6 pro isn’t listed in device manager, and adb bootloader driver has disapear replaced by an adb driver line. Anyways, bootloader driver was never activated.
Edit: I should add that the update through the phone doesn’t work.
Don’t know why... the interface for google android flash tool changed... and now I was able to choose the version and I could flash the two slot with a13 bootloader.
Thanks for the idea...
Even if… I would love to understand why I did not succeed to install it...
Final edit: Android 13 has been successfully installed
Now, time to root it