Related
The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e
i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues
What would we need to provide for you to make one for v1.0.0B06?
I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse
tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.
Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
I would suggest flashing the no verity boot just to avoid the headache
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse
tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.
JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here
MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?
Stock Android 7.0 (Nougat) for the Moto X Pure 2015 XT1575 US NPH25.200-22
TWRP Recovery Image (Includes /boot and /system only)
**Factory reset after restore is advised.**
https://drive.google.com/drive/folders/0B2lKWOIH0bTqc29NbVNWWWhsYVE?usp=sharing
**Not tested coming straight from stock 6.0 MPH24.49-18-16.**
I did an incremental OTA upgrade from stock 6.0 MPH24.49-18-8.
Use at your own risk. If you have TWRP installed your warranty is void anyway. I'm not responsible for bricking your device.
worked great for me 18-16 thanks really appropriate the work
Hi
and thx for sharing.
I have unlocked booloader and rooted, can I just flash this one with twrp?
thx in advance
the-light said:
Hi
and thx for sharing.
I have unlocked booloader and rooted, can I just flash this one with twrp?
thx in advance
Click to expand...
Click to collapse
Yes. Root is nonconsequential. You really just need twrp.
Can i just flash it over TruPureX Android 6?
(I guess i can, just want to be sure)
Where can I find Android 7 modem to flash separately?
Will it work with Android 6 modem?
newHere:) said:
Can i just flash it over TruPureX Android 6?
(I guess i can, just want to be sure)
Where can I find Android 7 modem to flash separately?
Will it work with Android 6 modem?
Click to expand...
Click to collapse
No Nougat modem is available until the flashable (non OTA) full stock 7.0 rom is made available from Motorola. This is not likely to happen. No issues have been mentioned running this update on a 6.0 modem. Not sure what the advantages are honestly. I never had problems with bt, wifi, or calls with the 6.0 modem firmware.
Create a backup beforehand and you can always go back to it.
hi i noob, i speak spanish.
I have moto x pure clark xt1575, android 6 no root, i install twrp an unlock bootloader.
I try to install this "ota" room, but fail. i restore back up and now the phone follow work
mphs24.49-18-16.
Need help how instal android 7 official, or only way custom room "lineage 14"
Thanks.
Can I flash this over Lineage OS 14.1 after a full wipe?
acoupleofdroids said:
worked great for me 18-16 thanks really appropriate the work
Click to expand...
Click to collapse
Hi talk about u experience
Greetings, it counts as you did, I have android 6.0 mphs24.49-18-16 and I can not update. Phone with bootloader unlocked and with twrp, no root
I get "invalid ZIP file format" using TWRP 3.1.1-0 on an XT1575. Was running lineageOS 14.1 but I wiped system and data before trying to install the zip. On my laptop I can open the ZIP fine and extract the files, but that doesn't help.
bussemac said:
I get "invalid ZIP file format" using TWRP 3.1.1-0 on an XT1575. Was running lineageOS 14.1 but I wiped system and data before trying to install the zip. On my laptop I can open the ZIP fine and extract the files, but that doesn't help.
Click to expand...
Click to collapse
See this thread :
https://forum.xda-developers.com/moto-x-style/general/guide-xt1575-update-to-nph25-200-22-t3680477
The OP will need to comment - he may be coming from a rooted stock ; at least according the the thread noted above - if you have installed a custom ROM ; there are other steps besides just trying to flash this
I have NOT tried the OP's method or the referenced thread - so I cannot really speak from experience ; just pointing out other resources that have additional information -
Will this work with XT1572? Just confirming.
This is not a traditional TWRP zip file. It is a backup file. You need to unzip it and put it in the backup directory. You then restore backup, choose the nph25-200-22. . . directory, and away you go!
stevejohnson42 said:
See this thread :
https://forum.xda-developers.com/moto-x-style/general/guide-xt1575-update-to-nph25-200-22-t3680477
The OP will need to comment - he may be coming from a rooted stock ; at least according the the thread noted above - if you have installed a custom ROM ; there are other steps besides just trying to flash this
I have NOT tried the OP's method or the referenced thread - so I cannot really speak from experience ; just pointing out other resources that have additional information -
Click to expand...
Click to collapse
kelru2000 said:
This is not a traditional TWRP zip file. It is a backup file. You need to unzip it and put it in the backup directory. You then restore backup, choose the nph25-200-22. . . directory, and away you go!
Click to expand...
Click to collapse
Ah, sure, OK, that makes sense, just wish that had been explained somewhere. I'll give that a shot tonight, thanks!
bussemac said:
Ah, sure, OK, that makes sense, just wish that had been explained somewhere. I'll give that a shot tonight, thanks!
Click to expand...
Click to collapse
Success? Some people have reported bootloops due to a firmware problem. I'd like to know how it went.
ptn107 said:
Success? Some people have reported bootloops due to a firmware problem. I'd like to know how it went.
Click to expand...
Click to collapse
Well it worked, sort of. It booted to stock but it wasn't stable and the play store kept crashing, I tried all the usual stuff for that, clear services & play store data, uninstall updates, finally tried a factory reset and now I'm stuck in TWRP bootloop, even if I reinstall this image.
So very much YMMV.
bussemac said:
Well it worked, sort of. It booted to stock but it wasn't stable and the play store kept crashing, I tried all the usual stuff for that, clear services & play store data, uninstall updates, finally tried a factory reset and now I'm stuck in TWRP bootloop, even if I reinstall this image.
So very much YMMV.
Click to expand...
Click to collapse
Thankfully the 7.0 stock firmware is available now. I wiped and clean flashed it and it works perfectly.
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
the link is dead
someone can help, sharing a new link? thank you
Hello,
I recently unlocked the bootloader and installed TWRP as custom recovery, but I'm now in need to return full-stock:
could anyone please tell me (or link me - I searched but I didn't found anything about it) a full procedure to restore the phone status?
I need a stock ROM, I guess, but then what? Flash it in TWRP? Does it also include stock recovery or is it a separate file instead?
Thank you very much!
shakathesaint said:
Hello,
I recently unlocked the bootloader and installed TWRP as custom recovery, but I'm now in need to return full-stock:
could anyone please tell me (or link me - I searched but I didn't found anything about it) a full procedure to restore the phone status?
I need a stock ROM, I guess, but then what? Flash it in TWRP? Does it also include stock recovery or is it a separate file instead?
Thank you very much!
Click to expand...
Click to collapse
so you do know that relocking the bootloader will cause a factory reset and all data will be wiped from device.
First, all you need to do is download a full rom update and flash in system local update. that will put stock software and stock recovery back.
second, Reboot phone to bootloader mode. Then you just type in cmd "fastboot oem lock"
MrSteelX said:
so you do know that relocking the bootloader will cause a factory reset and all data will be wiped from device.
First, all you need to do is download a full rom update and flash in system local update. that will put stock software and stock recovery back.
second, Reboot phone to bootloader mode. Then you just type in cmd "fastboot oem lock"
Click to expand...
Click to collapse
Thanks for your fast answer!
So is it better to flash stock ROM through local update than through TWRP? Or it's the same procedure both ways?
Thanks again!
They both will work.
Use the msmdownloadtool it's easiest, safest and fastest way.
Lownita said:
Use the msmdownloadtool it's easiest, safest and fastest way.
Click to expand...
Click to collapse
File name : 6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12
Hi, i have downloaded many times file above, why the said .rar file can not be extracted?
What is content the .rar file above?
Download Source : https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
DancingFate said:
File name : 6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12
Hi, i have downloaded many times file above, why the said .rar file can not be extracted?
What is content the .rar file above?
Download Source : https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Click to expand...
Click to collapse
This is for 6t. Is OP at 6t or 6?
Latest and greatest https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
These tools will return your phone to 100% stock.
I've use them multiple times.
I recommend using these qualcomm drivers.
https://drive.google.com/file/d/1k1cXnVaz5d2IRLqxFE9AiY8GFMmx3CDG/view?usp=sharing
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Dont work on daisy (android one)?:crying:
heyimvitor2 said:
Dont work on daisy (android one)?:crying:
Click to expand...
Click to collapse
They´re for Daisy, stock rom is Android One.
Are these just a repack of the fastboot ROMs available from xiaomi?
They are already listed here. And are .tar.gz rather than .zip
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
How to use it? Flash via twrp?
fastboot with miflash
a1291762 said:
Are these just a repack of the fastboot ROMs available from xiaomi?
They are already listed here. And are .tar.gz rather than .zip
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Fastboot rom is the whole rom including system, userdata, and more as you know to be flashed through fastboot directly or using a tool like MiFlash but these are not a repack but a flashable zip the way that all the update process to switch to other rom can be done while in TWRP.
Cause all my previous devices were running Miui they had available firmwares and never need to flash all the rom as a base for custom roms and since I bought this device I missed this feature.
Here you have a reference what I´m talking about https://xiaomifirmwareupdater.com
prodang2509 said:
How to use it? Flash via twrp?
Click to expand...
Click to collapse
Yes, as any flashable zip, recommendable as first step (as a base) after to make the wipes and before the other required steps.
dochdoc said:
fastboot with miflash
Click to expand...
Click to collapse
Nope, zips can´t be flashed through fastboot.
https://docs.google.com/spreadsheets/d/1Uy6qouIV0WbVouK4X5PhmUz2quxfLguHDqSf6LYDBO8/edit#gid=0
here you have all flashable stock trough miflash/fastboot
SubwayChamp said:
these are a flashable zip the way that all the update process to switch to other rom can be done while in TWRP.
Click to expand...
Click to collapse
I'm used to the fastboot ROMs but these may prove useful... Is there a process for converting a fastboot ROM into a twrp-flashable ROM?
a1291762 said:
I'm used to the fastboot ROMs but these may prove useful... Is there a process for converting a fastboot ROM into a twrp-flashable ROM?
Click to expand...
Click to collapse
If you refer to the whole rom yes, it does. Other Xiaomi devices have a fastboot (tar) and also a recovery (zip) but TWRP must be adapted to work with.
Thank you for this, it is really helpful.
Last night I played with offains TWRP 3.3.1-0 and restored a firmware backup, but it only got deleted and restoring failed.
Then I flashed your 10.3.0 file and all is good. You also put a custom dark splash.img in it, which I really like (was too lazy to create my own). :good:
Firmware 10.0.15
SubwayChamp said:
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Click to expand...
Click to collapse
Do you have also the newest firmware 10.0.15? I have a bug with screen rotation (not longer works after a few hours), i hope firmware 10.0.15 is the solution because because I read that a screen rotation error is known.
counti said:
Do you have also the newest firmware 10.0.15? I have a bug with screen rotation (not longer works after a few hours), i hope firmware 10.0.15 is the solution because because I read that a screen rotation error is known.
Click to expand...
Click to collapse
Firmware is based on major updates i.e. on fastboot global images (full rom) when all partitions are modified but is not included in OTA updates (incremental rom) when mostly only system and vendor (sometimes also kernel) receive modifications but all the other partitions remain untouched.
To better understanding the three next OTA updates (v10.0.14.0, v10.0.15.0 and v10.0.16.0) are using as base v10.0.13.0 firmware.
Just appear the next full rom I will upload it but hopefully it is 10.
Great Job !
SubwayChamp said:
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Click to expand...
Click to collapse
Hello Dear SubwayChamp,
It Will Be Very Helpful For US. Thank You Once Again...
Thanks for updating this to 10.0.13.
I wanted to create my own file and have some questions about the file emmc_appsboot.mbn
1. The updater script flashes the above file as an img file. Is it ok to just rename the mbn file or is a program like HxD Hex Editor needed?
2. In your 10.0.13 version there is only the mbn file but not the img file, is that ok? In your 10.0.3 file there is only the img file and in 10.0.9 there are both, so I'm a little confused.
I am seeing a few custom Android 10 roms out there, with the Android 9 base firmware, is not better wait for the android 10 base firmware? and the source code for the kernel.
Pat750 said:
Thanks for updating this to 10.0.13.
I wanted to create my own file and have some questions about the file emmc_appsboot.mbn
1. The updater script flashes the above file as an img file. Is it ok to just rename the mbn file or is a program like HxD Hex Editor needed?
2. In your 10.0.13 version there is only the mbn file but not the img file, is that ok? In your 10.0.3 file there is only the img file and in 10.0.9 there are both, so I'm a little confused.
Click to expand...
Click to collapse
Hi, I switched to other devices since I uploaded these files, anyway thanks for notice that, there was an error on the typo in versions 9, 12 and 13.
Xiaomi fastboot ROMs are mirrored on a lot of sites and I don´t remember now from where I downloaded it and I duplicated from inside the version 10.0.9, it wasn´t right, now all the files were re-uploaded and corrected.
As per mbn files can´t be simply renamed as image, you can look inside and change some values with a HEX editor but is not a good idea to make this without a solid knowledge so it may get corrupted and flashing a corrupted bootloader can seriously brick your device anyway don´t worry about so no need to change nothing, TWRP will place the images in the right places/partitions as they´re originally inside the fastboot ROMs.
SubwayChamp said:
Hi, I switched to other devices since I uploaded these files, anyway thanks for notice that, there was an error on the typo in versions 9, 12 and 13.
Xiaomi fastboot ROMs are mirrored on a lot of sites and I don´t remember now from where I downloaded it and I duplicated from inside the version 10.0.9, it wasn´t right, now all the files were re-uploaded and corrected.
As per mbn files can´t be simply renamed as image, you can look inside and change some values with a HEX editor but is not a good idea to make this without a solid knowledge so it may get corrupted and flashing a corrupted bootloader can seriously brick your device anyway don´t worry about so no need to change nothing, TWRP will place the images in the right places/partitions as they´re originally inside the fastboot ROMs.
Click to expand...
Click to collapse
Thank you. I see the changes.
Good luck with your new device. You did some good things here and helped people a lot.
Dear members plz suggest me a best solution for this problem plz
I have a pixel 2 (walleye) and few days ago i am unlocked my bootloader and i used sum custom os like linage os on my device this yesterday I have changed my mind and i flashed a stock factory images
But i do a mistake is i am flashed a Android 8.0 factory images that is walleyes first release frimware or factory images after i am flashed my device flashing process is susessful and it is booted normally and work fine but when I am now trying to flash latest version factory images that's besed on Android 11 it is showing me sum errors on flashing time what i do now
Theracerlucky said:
Dear members plz suggest me a best solution for this problem plz
I have a pixel 2 (walleye) and few days ago i am unlocked my bootloader and i used sum custom os like linage os on my device this yesterday I have changed my mind and i flashed a stock factory images
But i do a mistake is i am flashed a Android 8.0 factory images that is walleyes first release frimware or factory images after i am flashed my device flashing process is susessful and it is booted normally and work fine but when I am now trying to flash latest version factory images that's besed on Android 11 it is showing me sum errors on flashing time what i do now
Click to expand...
Click to collapse
The error is telling you exactly what you need to do - you need to update bootloader to the required version. If you are attempting to flash the factory firmware, the required bootloader and baseband files should be included in the zip file.
V0latyle said:
The error is telling you exactly what you need to do - you need to update bootloader to the required version. If you are attempting to flash the factory firmware, the required bootloader and baseband files should be included in the zip file.
Click to expand...
Click to collapse
I don't understand properly can you brother tell me with more details plz i tried already to flash sum upper versions bootloader factory images but showing this errors continue
Theracerlucky said:
I don't understand properly can you brother tell me with more details plz i tried already to flash sum upper versions bootloader factory images but showing this errors continue
Click to expand...
Click to collapse
The screenshot you posted describes the problem. When you flash a factory image, it first checks the device bootloader and baseband versions to make sure they are up to date. If they are out of date, you get the error as shown:
Device bootloader version is 'mw8998-002.0059.00'
Update requires 'mw8998-002.0076.00'
You need to update the bootloader and possibly the baseband version.
The absolute easiest way to flash the factory firmware is with the Android Flash Tool. Leave your device connected to your computer, and go to this link. Allow ADB keys access when requested. Before you flash, make sure you click the pencil icon to choose options, as the tool selects Wipe Device and Lock Bootloader by default.
If you are still trying to flash your device manually, make sure your Platform Tools are up to date.
V0latyle said:
The screenshot you posted describes the problem. When you flash a factory image, it first checks the device bootloader and baseband versions to make sure they are up to date. If they are out of date, you get the error as shown:
Device bootloader version is 'mw8998-002.0059.00'
Update requires 'mw8998-002.0076.00'
You need to update the bootloader and possibly the baseband version.
The absolute easiest way to flash the factory firmware is with the Android Flash Tool. Leave your device connected to your computer, and go to this link. Allow ADB keys access when requested. Before you flash, make sure you click the pencil icon to choose options, as the tool selects Wipe Device and Lock Bootloader by default.
If you are still trying to flash your device manually, make sure your Platform Tools are up to date.
Click to expand...
Click to collapse
But bro when I trying to flash with Android flash tool showing this errors
Theracerlucky said:
But bro when I trying to flash with Android flash tool showing this errors
Click to expand...
Click to collapse
I haven't seen that error before. Your bootloader is unlocked, right?
Theracerlucky said:
But bro when I trying to flash with Android flash tool showing this errors
Click to expand...
Click to collapse
"FAILED (remote: Command Flash Error)" -- When flashing bootloader
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader: sending 'bootloader_a' (38728 KB)... OKAY [ 2.095s] writing 'bootloader_a'...
forum.xda-developers.com
V0latyle said:
I haven't seen that error before. Your bootloader is unlocked, right?
Click to expand...
Click to collapse
Yes properly unlocked bro
Theracerlucky said:
"FAILED (remote: Command Flash Error)" -- When flashing bootloader
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader: sending 'bootloader_a' (38728 KB)... OKAY [ 2.095s] writing 'bootloader_a'...
forum.xda-developers.com
Yes properly unlocked bro
Click to expand...
Click to collapse
Bro can you please read this post for me i think it's the same like my issues but i don't understand this things properly what i do
Theracerlucky said:
Bro can you please read this post for me i think it's the same like my issues but i don't understand this things properly what i do
Click to expand...
Click to collapse
I don't say this to be rude, but if you don't know what you're doing, nor understand the basic concepts at play here, you shouldn't be tinkering with your phone.
It looks like the user who posted that thread was able to fix his issue by sideloading the OTA. Do you have a custom recovery such as TWRP installed, or is everything stock?
I can provide instructions on how to sideload the OTA later today, but I must emphasize how important it is for you to understand what you are doing, because doing something wrong could result in bricking your device.
Lastly, please don't call me "bro".
V0latyle said:
I don't say this to be rude, but if you don't know what you're doing, nor understand the basic concepts at play here, you shouldn't be tinkering with your phone.
It looks like the user who posted that thread was able to fix his issue by sideloading the OTA. Do you have a custom recovery such as TWRP installed, or is everything stock?
I can provide instructions on how to sideload the OTA later today, but I must emphasize how important it is for you to understand what you are doing, because doing something wrong could result in bricking your device.
Lastly, please don't call me "bro".
Click to expand...
Click to collapse
Ok sir i don't installed any custom recovery now my devices all things is stock
Alright. Here's how to sideload the OTA.
Connect your device to your PC.
Download Pixel 2 December 2017 OTA. You can also try the December 2020 OTA. Do not unzip or extract these files, you will use them as-is.
In bootloader mode, use the Volume + and - buttons to select Recovery Mode, then press the Power button.
You will arrive at a screen with a green Android and "No command". Hold down the Power button and click the Volume Up button.
You will now be in the recovery menu. Use the Volume buttons to select Apply update from ADB, then press the Power button.
On your PC, open a command window in Platform Tools. Use this command: adb sideload, insert a space, then drag and drop the OTA file you just downloaded into the command window.
Press Enter. The sideload process will begin. Once it finishes, you will be taken back to Recovery Mode. Select Reboot now.
Your device should boot into Android. At this point you should be able to reboot to bootloader and use the Android Flash Tool to flash your desired update.
V0latyle said:
Alright. Here's how to sideload the OTA.
Connect your device to your PC.
Download Pixel 2 December 2017 OTA. You can also try the December 2020 OTA. Do not unzip or extract these files, you will use them as-is.
In bootloader mode, use the Volume + and - buttons to select Recovery Mode, then press the Power button.
You will arrive at a screen with a green Android and "No command". Hold down the Power button and click the Volume Up button.
You will now be in the recovery menu. Use the Volume buttons to select Apply update from ADB, then press the Power button.
On your PC, open a command window in Platform Tools. Use this command: adb sideload, insert a space, then drag and drop the OTA file you just downloaded into the command window.
Press Enter. The sideload process will begin. Once it finishes, you will be taken back to Recovery Mode. Select Reboot now.
Your device should boot into Android. At this point you should be able to reboot to bootloader and use the Android Flash Tool to flash your desired update.
Click to expand...
Click to collapse
Sir i know this process but my tension is this process work properly or i brick my device
Theracerlucky said:
Sir i know this process but my tension is this process work properly or i brick my device
Click to expand...
Click to collapse
Sideloading the OTA is actually the safest way to update, and the least likely of bricking your device.
As long as you're able to access bootloader, your device isn't truly bricked.
I understand your consternation, especially as it appears you're fairly inexperienced regarding this. Simply follow my instructions and you'll be fine. I'm trying to make this as easy and foolproof as possible for you.
V0latyle said:
Sideloading the OTA is actually the safest way to update, and the least likely of bricking your device.
As long as you're able to access bootloader, your device isn't truly bricked.
I understand your consternation, especially as it appears you're fairly inexperienced regarding this. Simply follow my instructions and you'll be fine. I'm trying to make this as easy and foolproof as possible for you.
Click to expand...
Click to collapse
Sir can I download this ota file for sideload or other versions
Theracerlucky said:
Sir can I download this ota file for sideload or other versions
Click to expand...
Click to collapse
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Sir you busy now ??
When you free sir reply me i have one more last question answer me plz after that i try to sideload the ota
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
I see a video on YouTube ithink that is the same issues
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
Whe
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you
Click to expand...
Click to collapse
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
When I comented this Youtuber brothers he told me to sideload the latest ota file he created the video on 4 year ago but the latest ota is now Android 11 what can I do sir plz help i am confused he doesn't reply me after this comment reply