Database Info

cannot flash Bootloader on unlocked Pixel 2

I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?

lazarus2297 said:
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
Click to expand...
Click to collapse
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help

Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.

razrlover said:
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Click to expand...
Click to collapse
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
foosion said:
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
Click to expand...
Click to collapse
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..

lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought

phonefreedom said:
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
Click to expand...
Click to collapse
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..

lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
lazarus2297 said:
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
Click to expand...
Click to collapse
+Natahranta had shared the following with me and I hope it helps in your case...
"Download factory image from Google, unpack it, insidebis another zip, there is boot.img file
Flash it to both slots A and B. It must be the same version/update your phone was on.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
If you're not sure which exactly stock rom build your phone is on, use the flash_all.bat to flash the whole image on your phone, to be sure you have no mismatch between system and boot. Just remove "-w" from the bat file so it doesn't erase your user data"

So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.

lazarus2297 said:
I have relocked the BL then booted into the OS
Click to expand...
Click to collapse
I don't have any suggestions for your issue. But don't relock it, ever. You are playing with fire, if it goes bad and it's locked you are done.

lazarus2297 said:
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
Click to expand...
Click to collapse
I had this problem and created a thread about it a month ago: https://forum.xda-developers.com/pixel-2/help/failed-remote-command-flash-error-t3701929. A couple other people in that thread are now also reporting the problem.
No one seemed to know what the " FAILED (remote: Command Flash Error)" means. I never figured it out.
At the time of the November update, however, I was able to sideload OTA images with adb without problem. I assume that the OTA method also updates the bootloader, like the Dev Preview did for you. I couldn't tell with the November update, though, because it had the same version of the bootloader in it as the one that shipped with the phone.
So I'm wondering if simply sideloading the current December OTA image with adb would accomplish the same thing you did, without having to lock the bootloader, unlock it again, and go through the pain of wiping the device. I wonder if there was just something weird about the original version of the bootloader. Weirdness like this was discussed early on with the Pixel 2 in this XDA article: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ If I'm right, then once one sideloads the December OTA image and gets a new bootloader, there may not be an issue flashing bootloaders with fastboot in the future. I assume that the Dev Preview also used the OTA method to update the device.
In other words, I'm wondering if the step of unlocking and relocking the bootloader was not necessary. You just had to do it to get the Developer Preview (right?).
Just guessing here. I haven't had time yet to try this.

Okay, I tried my idea above and I was correct. Simplying sideloading the December OTA image updates the bootloader. After that the problem is solved. I can successfully flash the bootloader .img file directly (from the factory image zip) using fastboot. So I assume going forward there should not be any problems flashing factory images, instead of sideloading OTA images.
This solution also avoids having to lock and unlock the bootloader and wipe the whole device in the process.

cb474 said:
Simplying sideloading the December OTA image updates the bootloader.
Click to expand...
Click to collapse
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
-----------
Nevermind. I figured out that recovery is part of boot now. I flashed the factory boot and flashing OTA now.

snovvman said:
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
Click to expand...
Click to collapse
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.

cb474 said:
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
Click to expand...
Click to collapse
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.

snovvman said:
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
Click to expand...
Click to collapse
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.

cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.

cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php

kendong2 said:
https://forum.xda-developers.com/showpost.php
Click to expand...
Click to collapse
That link leads to nothing.
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
snovvman said:
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
Click to expand...
Click to collapse
Yeah, I saw that. I'm just hoping with what was learned from the original Pixel and given that supposedly most phones will eventually use the A/B partition scheme that maybe TWRP will advance further on the Pixel 2. I really miss nandroid backups. I miss LineageOS too. Everything was so much simpler on my old Nexus 4. And I wasn't constantly feeling like I was going to brick my device every time I tried to do something.

cb474 said:
That link leads to nothing.
Click to expand...
Click to collapse
Sorry, did that on the phone. Was supposed to go here: https://forum.xda-developers.com/showpost.php?p=74704694&postcount=155
TWRP 3.2.0.0 final release (as I understand it) has been announced a few days ago. Don't know why the thread title still says beta.

This is freaking weird. Anyway, followed post #11 to sideload DEC OTA zip in stock recovery, and now finally I have a bootloader that is 0066 on both slot a and b. Thanked @cb474 !

Unrooting Mi A1 [Android Oreo ] completely

complete unrooting procedure for Mi A1 [Android Oreo]
1) remove all magisk modules
I mean untick all magisk modules and click on delete icon beside them
After this reboot your device
2) then open magisk manager and uninstall using completely uninstall option
3) ‎then power off your device
4) ‎go to fastboot mode
‎ ( by pressing vol- + power buttons simultaneously)
5) ‎then unlock OEM using command
fastboot oem unlock
6) then check for current slot by using below command
fastboot getvar current-slot
7) then we should flash stock boot image
Using this command
fastboot flash boot_a boot.img
( If a is current slot )
Or
fastboot flash boot_b boot.img
( if current slot is b )
‎
‎Boot image file : https://drive.google.com/file/d/1EsuVTv5zIrfhDH7VG6uSyTXUWPS7Dvfl/view?usp=drivesdk
8) then lock your OEM using command
‎fastboot oem lock
9) then reboot using command
fastboot reboot
Congratulations your device is unrooted successfully !!
Suggested vedios for mi A1 users
Iam maintaing my channel for mi A1 related vedios and other technical stuff
Do subscribe for latest updates
Rooting using magisk :
Complete gcam setup :

#reserved

Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".

Thank you very much!!!! Was looking for this in a pretty long time!!!

Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".

nicolasmart said:
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
Click to expand...
Click to collapse
This one works for me https://forum.xda-developers.com/showpost.php?p=75027522&postcount=63
Currently I'm rooted, but I fully booted right after flashing it without any mods and ROM started fine.
It will show some sparse warning during flashing, but it will complete the process OK.

Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.

nicolasmart said:
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
Click to expand...
Click to collapse
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..

_mysiak_ said:
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
Click to expand...
Click to collapse
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.

nicolasmart said:
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
Click to expand...
Click to collapse
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.

_mysiak_ said:
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
Click to expand...
Click to collapse
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:

nicolasmart said:
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
Click to expand...
Click to collapse
You saved me too.
presented error in the "no command" and did not accept the January update

Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again

_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?

rkview37 said:
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
Click to expand...
Click to collapse
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.

_mysiak_ said:
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
Click to expand...
Click to collapse
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota

rkview37 said:
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
Click to expand...
Click to collapse
For OTA update, just reflash the latest stock ROM (keep data), apply OTA and root with Magisk again.

camerlengo said:
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
Click to expand...
Click to collapse
Ok bro

_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess

AlwaysWin said:
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
Click to expand...
Click to collapse
http://ru.miui.com/thread-1308-1-1.html
This website is in Russian but download from this site
Rom is Oreo Jan official rom flash it using mi flash tool

Cannot use fastboot

Hey all,
I am unlocked, rooted, etc. I have latest platform tools. i am trying to reflash a modem img using fastboot on windows 10 64 but am given "FAILED (remote: 'Not allowed to flash (modem_b)')"
Can someone point me in the right direction?

Xdevillived666 said:
Hey all,
I am unlocked, rooted, etc. I have latest platform tools. i am trying to reflash a modem img using fastboot on windows 10 64 but am given "FAILED (remote: 'Not allowed to flash (modem_b)')"
Can someone point me in the right direction?
Click to expand...
Click to collapse
Is there a "modem.img" that you extracted from the factory image?

Badger50 said:
Is there a "modem.img" that you extracted from the factory image?
Click to expand...
Click to collapse
Yes. I've tried opening command window as admin, too. Seems to return this error noattwr what:-/

Xdevillived666 said:
Yes. I've tried opening command window as admin, too. Seems to return this error noattwr what:-/
Click to expand...
Click to collapse
Are you trying to use a different radio/baseband from a previous month? I've actually never seen anyone wanting to flash a modem.img for whatever reason. So now I'm curious.

Badger50 said:
Are you trying to use a different radio/baseband from a previous month? I've actually never seen anyone wanting to flash a modem.img for whatever reason. So now I'm curious.
Click to expand...
Click to collapse
Nope. Long story short I'm trying to use qpst and pdc tool. Getting a qmi error and read on a German thread that sometimes reflashing modem will fix it. Problem is that I can't flash individual images aside from radio or bootloader with fastboot -_-

Are your platform tools up to date?

jsauder2 said:
Are your platform tools up to date?
Click to expand...
Click to collapse
Yeah. Is this normal for a pixel 3 to be so locked down? I know my pixel one wasn't

Xdevillived666 said:
Yeah. Is this normal for a pixel 3 to be so locked down? I know my pixel one wasn't
Click to expand...
Click to collapse
If it's a Verizon model, you can't unlock the bootloader. If it's from Google, you should be fine. I've not tried flashing a modem. If you can flash the factory images, just use the flash all script and remove the w. That will flash everything, including the modem, but will not wipe your data.

jsauder2 said:
If it's a Verizon model, you can't unlock the bootloader. If it's from Google, you should be fine. I've not tried flashing a modem. If you can flash the factory images, just use the flash all script and remove the w. That will flash everything, including the modem, but will not wipe your data.
Click to expand...
Click to collapse
I can use the script but opening it in notepad ++ , the flash all bat doesn't show anything about modem. I've tried everything from just fastboot flash modem modem.img to
Flash modem slot a, etc. Keeps giving remote error flash modem not allowed . I really think Google just locked this phone down that much more. Ridiculous.

The factory image does flash the modem. It doesn't say so in the bat or sh files, but you'll also notice that it doesn't mention the boot, system, or vendor files either (along with many other things), even though those are most certainly flashed during an update. That's because those are all inside the image zip that is referenced in the last line of the bat or sh (where you remove the -w). It flashes everything inside of that, including the modem.
If a screwed up modem is your problem, flashing the factory image will fix it. If that doesn't fix it, then the modem is not your issue.

Xdevillived666 said:
I can use the script but opening it in notepad ++ , the flash all bat doesn't show anything about modem. I've tried everything from just fastboot flash modem modem.img to
Flash modem slot a, etc. Keeps giving remote error flash modem not allowed . I really think Google just locked this phone down that much more. Ridiculous.
Click to expand...
Click to collapse
I don't know if this will work. I also don't know what the fastboot update command does under the hood. But the flash-all batch file does flash the modem image using the fastboot update command. What if you created a zip file with your modem image in it and then tried to flash it with the update command, or possibly replace the modem.img in the zip in the factory image with your image?
Sent from my [device_name] using XDA-Developers Legacy app

Pixel 3 Twrp will NOT boot no matter what

Hello, today i've successfully rooted my Pixel 3 with magisk and everything seems to be working fine except, i cant install TWRP.
i get the following upon doing fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 2.169s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
i've tried mulitple USB A to USB C cables, and even usb-c to usb-c because my laptop has that port. Someone Please help

AmberKat said:
Hello, today i've successfully rooted my Pixel 3 with magisk and everything seems to be working fine except, i cant install TWRP.
i get the following upon doing fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 2.169s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
i've tried mulitple USB A to USB C cables, and even usb-c to usb-c because my laptop has that port. Someone Please help
Click to expand...
Click to collapse
If you're on Android 10, twrp doesn't work. You really don't need it now anyway.

jd1639 said:
If you're on Android 10, twrp doesn't work. You really don't need it now anyway.
Click to expand...
Click to collapse
So downgrading back to Pie will solve the issue?

AmberKat said:
So downgrading back to Pie will solve the issue?
Click to expand...
Click to collapse
If you're adamant about having twrp, yes.

Xdevillived666 said:
If you're adamant about having twrp, yes.
Click to expand...
Click to collapse
I have the same issue, how can i flash a custom kernel and magisk without twrp in Android 10 please?

luizffgarcia said:
I have the same issue, how can i flash a custom kernel and magisk without twrp in Android 10 please?
Click to expand...
Click to collapse
For a custom kernel, you will need to use a kernel manager (EX kernel manager or FK kernel manager). Both are a small amount of money that is of course well worth it to support the devs. As for Magisk, you need to install the Magisk Manager canary APK and then patch boot to root.

sliding_billy said:
For a custom kernel, you will need to use a kernel manager (EX kernel manager or FK kernel manager). Both are a small amount of money that is of course well worth it to support the devs. As for Magisk, you need to install the Magisk Manager canary APK and then patch boot to root.
Click to expand...
Click to collapse
Thanks, i already have EX manager, and i have just rooted with canary. Cheer

luizffgarcia said:
Thanks, i already have EX manager, and i have just rooted with canary. Cheer
Click to expand...
Click to collapse
Easy peasy!

jd1639 said:
If you're on Android 10, twrp doesn't work. You really don't need it now anyway.
Click to expand...
Click to collapse
Why is TWRP not needed in Android 10? I have the same issue as the OP with fastboot boot hanging at sending boot.img, but a different reason for wanting TWRP to boot, namely to make a nandroid backup. I do not want to flash twrp, just boot as I have done for years pre OS10. I have no interest in backing up on Google servers, just wish to do a nandroid. Is there some other way to do this in OS10 without root?
Thanks, John

John Markley said:
Why is TWRP not needed in Android 10? I have the same issue as the OP with fastboot boot hanging at sending boot.img, but a different reason for wanting TWRP to boot, namely to make a nandroid backup. I do not want to flash twrp, just boot as I have done for years pre OS10. I have no interest in backing up on Google servers, just wish to do a nandroid. Is there some other way to do this in OS10 without root?
Thanks, John
Click to expand...
Click to collapse
Android 10's file structure is different so you won't be able to boot or flash twrp. Teamwin may figure out how to get twrp to work on it someday but for now it doesn't. So no nandriod, you'll need to find another way to backup if that's what you're looking to do.

jd1639 said:
Android 10's file structure is different so you won't be able to boot or flash twrp. Teamwin may figure out how to get twrp to work on it someday but for now it doesn't. So no nandriod, you'll need to find another way to backup if that's what you're looking to do.
Click to expand...
Click to collapse
Thank you. I'll just do adb backups then, unless Teamwin solves it. Until now I've always done both adb and nandroid.

I am currently on Android 9 and going to upgrade to the latest 10.
Is there anything chance for me to do a full image backup of the phone in advance before upgrading.
In case that the Android 10 doesn't fit me very well, I can roll back to Android 9 without losing any files.
Appreciate your comments and thank you in advance for the assistance.
jd1639 said:
Android 10's file structure is different so you won't be able to boot or flash twrp. Teamwin may figure out how to get twrp to work on it someday but for now it doesn't. So no nandriod, you'll need to find another way to backup if that's what you're looking to do.
Click to expand...
Click to collapse

Android 11 preview

https://www.xda-developers.com/essential-phone-android-11-developer-preview/
It's not quite over...

Nice!

garywojdan81 said:
https://www.xda-developers.com/essential-phone-android-11-developer-preview/
It's not quite over...
Click to expand...
Click to collapse
very nice!

It's my understanding that the Essential was built to basically meet exact specs of what an Android phone should be. Is it possible to continue to get monthly security updates direct from google, even though Essential as a company won't be around?? Or is the firmware ALWAYS customized to the model?

NuAngel said:
It's my understanding that the Essential was built to basically meet exact specs of what an Android phone should be. Is it possible to continue to get monthly security updates direct from google, even though Essential as a company won't be around?? Or is the firmware ALWAYS customized to the model?
Click to expand...
Click to collapse
I'm no developer, but I don't think it's that simple.

NuAngel said:
It's my understanding that the Essential was built to basically meet exact specs of what an Android phone should be. Is it possible to continue to get monthly security updates direct from google, even though Essential as a company won't be around?? Or is the firmware ALWAYS customized to the model?
Click to expand...
Click to collapse
There fact that there's still customizations and changes that have to be made even to the Pixel GSI to even boot on mata says the firmware has to be customized even though the specs themselves match

They just upload a new file, is a vendor for developers.

android 11 working realy good on essential phone i will upload complete package to flash BOOTLOADER UNLOCK NEEDED

Is WiFi and mobile data working?
Sent from my PH-1 using Tapatalk

on my site wifi is not working with the latest vendor image. i also miss some features like full screen navigation and some other features like fingerprint gestures.

I am interested.
veisen said:
android 11 working realy good on essential phone i will upload complete package to flash BOOTLOADER UNLOCK NEEDED
Click to expand...
Click to collapse
Like how good? WiFi and data and BT all working?
I have "OEM unlocking" on under developer options, what else do I need to do to lock and load?

freshlysqueezed said:
Is WiFi and mobile data working?
Click to expand...
Click to collapse
@mrmrkmail
on reddit they are saying data works but not wifi
edit: some other things not working either
edit: wifi fixed

IronRoo said:
@mrmrkmail
on reddit they are saying data works but not wifi
edit: some other things not working either
Click to expand...
Click to collapse
Looks like we need an updated boot.img to get WiFi working. Anyone create a user debug build and have the boot.img they can share with us?
https://github.com/EssentialOpenSource/device_essential_mata/blob/master/README.md
Sent from my PH-1 using Tapatalk

thanks for your responses.
the issue with the older kernel in the boot images (february) i have read already on reddit . i am also hoping that someone is able to provide us a boot image with a newer kernel that will work.
edit: on reddit there is a guide how to create a boot image: https://www.reddit.com/r/essential/comments/fbnmpg/comment/fj7yma5?utm_source=share&utm_medium=web2x
there is also a direct link to download a packed boot image.

The reddit thread links the GSI system image, the vendor image, and a custom boot image to get the PH-1 flashed successfully. The trick is that TWRP isn't going to install, so probably not Magisk either.
I checked the Wifi, Mobile Data, and voicecalls working. Did not check BT.
If anyone knows how to get Magisk working with this, please post instructions.

daverup said:
The reddit thread links the GSI system image, the vendor image, and a custom boot image to get the PH-1 flashed successfully. The trick is that TWRP isn't going to install, so probably not Magisk either.
I checked the Wifi, Mobile Data, and voicecalls working. Did not check BT.
If anyone knows how to get Magisk working with this, please post instructions.
Click to expand...
Click to collapse
I haven't tried the Preview yet, but if I were going to flash Magisk, I'd copy the boot image to my phone, open Magisk Manager, tap Install and choose Patch Boot Image. Then select the boot image. It'll make a new, patched boot image in addition to preserving the original. Then flash the patched boot image via Fastboot.

gk1984 said:
I haven't tried the Preview yet, but if I were going to flash Magisk, I'd copy the boot image to my phone, open Magisk Manager, tap Install and choose Patch Boot Image. Then select the boot image. It'll make a new, patched boot image in addition to preserving the original. Then flash the patched boot image via Fastboot.
Click to expand...
Click to collapse
I did run magisk manager with the boot image copied to the phone, but I didn't get an install option. Is there a specific location for the image?

Open Magisk Manager. Top should indicate if you have Magisk installed, update available, etc. To the right of that is an install button. Then it'll ask how to install.
The boot image will be wherever you saved it to on the phone, the patched boot image might default to the same directory, but mine usually goes to the downloads folder once patched.
https://images.app.goo.gl/NWF4h47zQQiyJNYGA
That link should show the install button and the option to patch a boot image. But it's not necessarily the proper steps.

gk1984 said:
Open Magisk Manager. Top should indicate if you have Magisk installed, update available, etc. To the right of that is an install button. Then it'll ask how to install.
The boot image will be wherever you saved it to on the phone, the patched boot image might default to the same directory, but mine usually goes to the downloads folder once patched.
https://images.app.goo.gl/NWF4h47zQQiyJNYGA
That link should show the install button and the option to patch a boot image. But it's not necessarily the proper steps.
Click to expand...
Click to collapse
Thanks for the help.
I got a little further. I must have failed to install Magisk Manager properly the first time,
This install worked and I was able to patch the boot image. I then attempted to flash it using fastboot, and got a failure.
FAILED (remote: 'unknown command')
fastboot: error: command failed
The boot image was modded by someone on reddit, maybe there is something in there causing problems.

daverup said:
Thanks for the help.
I got a little further. I must have failed to install Magisk Manager properly the first time,
This install worked and I was able to patch the boot image. I then attempted to flash it using fastboot, and got a failure.
FAILED (remote: 'unknown command')
fastboot: error: command failed
The boot image was modded by someone on reddit, maybe there is something in there causing problems.
Click to expand...
Click to collapse
You copied the patched boot image back to your PC? Did you use the following command?
fastboot flash boot_a magisk_patched.img
Replacing boot_a for the slot you're on?
It's also very possible that Magisk isn't compatible with Android 11, which is more likely the case than something about whoever built the boot image.
The errors tell me you typed something wrong. Maybe wrong command or the patched boot couldn't be found.