I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.
cmorin543 said:
I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.
Click to expand...
Click to collapse
Hello,
I wonder ? do you have pixel 3 phone?
I see that you have the bootloader of the crossheath for the google pixel 3 XL installed.
bootloader-crosshatch-b1c1-0.1-5191736.img
Maybe you should download the google pixel 3 OTA or Factory.img.
That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.
cmorin543 said:
That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.
Click to expand...
Click to collapse
Succes, and let me know if you succeeded flashing.
9.0.0 (PQ2A.190405.003, Apr 2019) Link c12f40f0b189eb2daa80d029917bc9a8841da89cfcafa21b8f61b0d9f90826e7
Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.
I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.
cmorin543 said:
Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.
Click to expand...
Click to collapse
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!
wangdaning said:
I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.
Click to expand...
Click to collapse
I should've mentioned that I did do the format of userdata at one point and it didn't make a difference.
sakerhetz said:
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!
Click to expand...
Click to collapse
I tried using the flash_all.bat with no joy and I also tried using twrp (when I was actually able to boot into it) to sideload the OTA zip still with no joy.
I think I'm just going to contact Google and see what they can do -- the phone is technically still under warranty and I am still able to re-lock the bootloader... I appreciate the help.
Maybe try:
1) fastboot erase userdata
2) flash-all.bat
If no good:
1) fastboot erase userdata
2) fastboot format userdata
3) flash-all.bat
Everything will be gone, but already is from what you have said.
if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.
SacredDeviL666 said:
if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.
Click to expand...
Click to collapse
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
I will double check that. Thanks!
cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
just to confirm.
a) you booted to bootloader using power + volume down key and then use volume down key to change it to bootloader and press power again (this reboots the bootloader)
b) while you are inside the ADB folder use shift + right click while you are inside the adb folder and then select the option -- open command window here.
c) considering that you have already connected your pixel to pc via usb type the command " fastboot devices " in the command prompt window to ensure that your device is detected.
d) once it has detected the device/s proceed to unzip the april factory image from https://dl.google.com/dl/android/aosp/blueline-pq2a.190405.003-factory-c12f40f0.zip in the same folder as ADB
e) Double click on flash.all bat file and let us know the result.
I am sure you might have followed above steps but just to make sure if everything is covered. as the above should actually fix all partition errors.
pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
You are a genius -- apparently I did have the newest version of ADB in my downloads folder, but I was so used to using a specific directory with platform-tools for my old phone, I didn't realize it was an old version -- tried it with the newest version of ADB and it worked like a charm... too bad I already contacted google and they're sending me a new phone.. :-\
Thanks again for all your help guys.
Related
Is this the most up to date instructions? https://www.xda-developers.com/flash-monthly-security-update-google-pixel/
Pixel noob alert! I have basically the same question. I've done a bunch of reading and it seems like I can:
1) Use flash-all on the factory image after removing "-w"
2) ADB sideload the OTA zip file
3) TWRP install the OTA zip file
I'm not clear which, if any, is really "best" and in each case whether I'll need to reboot TWRP, reinstall TWRP and reinstall Magisk?
Thanks for any help on this!
Oof, I'm in the same boat. I messed installing TWRP and had to flash the factory images over the weekend, so I'm a little gun shy to flash this until I know exactly what to do.
On my Pixel 2 I've been doing the below -- I do not install TWRP but I do have a custom kernel and magisk:
1) flash stock boot img from previous month to remove Magisk and custom kernel (I *assume* that removing magisk via magisk manager would also accomplish this if magisk was installed before custom kernel - but I have never bothered doing this)
2) sideloading OTA (via stock recovery)
3) installing magisk and custom kernel
There are cases where Google says on their factory image page that you must take the OTA (rather than flashing to a new image) - that fact is enough reason to me to sideload the OTA rather than flashing the entire new month's image
ktdt00 said:
Pixel noob alert! I have basically the same question. I've done a bunch of reading and it seems like I can:
1) Use flash-all on the factory image after removing "-w"
2) ADB sideload the OTA zip file
3) TWRP install the OTA zip file
I'm not clear which, if any, is really "best" and in each case whether I'll need to reboot TWRP, reinstall TWRP and reinstall Magisk?
Thanks for any help on this!
Click to expand...
Click to collapse
1 or 2. Not 3. Either way you will have to re root and install TWRP if you want.
Both are equally good.
Sideloading through TWRP did not work for me at all with this phone so I had to download the Nov factory firmware, delete the -w on the flash-all.bat file. Then flashed this through fastboot, rebooted to make sure I was on the Nov update. After that, booted back to bootloader and reflashed TWRP and Maigisk, now all is fine.
Archangel said:
Sideloading through TWRP did not work for me at all with this phone so I had to download the Nov factory firmware, delete the -w on the flash-all.bat file. Then flashed this through fastboot, rebooted to make sure I was on the Nov update. After that, booted back to bootloader and reflashed TWRP and Maigisk, now all is fine.
Click to expand...
Click to collapse
I've tried to flash-all the Nov. factory image like 4 times now, and every time I check the build number and it's still the Oct version. Can someone please help me figure out what I'm doing wrong? I've extracted and copied all the .img files into the adb directory. This is super long but here is the cmd readout I get after flash-all:
PS - what is the -w thing about? I don't see it in the names of any downloaded files.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8489 KB)...
OKAY [ 0.289s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5004167
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.642s]
finished. total time: 0.936s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
target reported max download size of 268435456 bytes
sending 'radio_a' (71148 KB)...
OKAY [ 1.659s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.463s]
finished. total time: 2.122s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.070s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.226s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2157 MB) to disk... took 9.974s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 1.930s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (444 MB) to disk... took 2.022s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5004167
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 897X0687T
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.361s
Press any key to exit...
I had this happen to me and the variable not found error is due to your platform tools being out of date. I updated mine,,, unfortunately I cant remember where,,or I would give that you to,,,if you do a google search on updated platform tools/xda it will come up and just take the most recent one you see. Once you swap out the platform tools folders you should be good to go. Once I did mine the flash completed and I am on Nov update.
Oh and the -w is a part of a line of code that you will find in the flash-all.bat file once you have extracted the Nov system image. Look for that flash-all.bat file then right click on it and open it up with Note+. Find the line at the bottom that has a -w in it and delete it out. Once that is done go to the top and hit save just dont exit out or it will not work. Once you hit save then you can hit the flash-all.bat and it will flash the Nov entire system up without erasing your current data. Hope this helps.
Troy The Great said:
I've tried to flash-all the Nov. factory image like 4 times now, and every time I check the build number and it's still the Oct version. Can someone please help me figure out what I'm doing wrong? I've extracted and copied all the .img files into the adb directory. This is super long but here is the cmd readout I get after flash-all:
PS - what is the -w thing about? I don't see it in the names of any downloaded files.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8489 KB)...
OKAY [ 0.289s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5004167
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.642s]
finished. total time: 0.936s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
target reported max download size of 268435456 bytes
sending 'radio_a' (71148 KB)...
OKAY [ 1.659s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.463s]
finished. total time: 2.122s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.070s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.226s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2157 MB) to disk... took 9.974s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 1.930s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (444 MB) to disk... took 2.022s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5004167
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 897X0687T
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.361s
Press any key to exit...
Click to expand...
Click to collapse
Archangel said:
Sideloading through TWRP did not work for me at all with this phone so I had to download the Nov factory firmware, delete the -w on the flash-all.bat file. Then flashed this through fastboot, rebooted to make sure I was on the Nov update. After that, booted back to bootloader and reflashed TWRP and Maigisk, now all is fine.
Click to expand...
Click to collapse
Archangel said:
I had this happen to me and the variable not found error is due to your platform tools being out of date. I updated mine,,, unfortunately I cant remember where,,or I would give that you to,,,if you do a google search on updated platform tools/xda it will come up and just take the most recent one you see. Once you swap out the platform tools folders you should be good to go. Once I did mine the flash completed and I am on Nov update.
Oh and the -w is a part of a line of code that you will find in the flash-all.bat file once you have extracted the Nov system image. Look for that flash-all.bat file then right click on it and open it up with Note+. Find the line at the bottom that has a -w in it and delete it out. Once that is done go to the top and hit save just dont exit out or it will not work. Once you hit save then you can hit the flash-all.bat and it will flash the Nov entire system up without erasing your current data. Hope this helps.
Click to expand...
Click to collapse
You are a genius, the updated platform tools worked; all rooted and good to go. Thank you so much for your help
Why does the XDA guide not talk about re-rooting?
Followed XDAs instructions on unlocked bootloader, rooted with Magisk and now getting the "device is corrupt" message. Ugh.
I'm now 100% back to stock. Took forever. How the heck do I do this right next time? Working on restoring my data.
Update your platform tools often.
so is there a working step by step somewhere now?
Updated tools
Archangel said:
I had this happen to me and the variable not found error is due to your platform tools being out of date. I updated mine,,, unfortunately I cant remember where,,or I would give that you to,,,if you do a google search on updated platform tools/xda it will come up and just take the most recent one you see. Once you swap out the platform tools folders you should be good to go. Once I did mine the flash completed and I am on Nov update.
Oh and the -w is a part of a line of code that you will find in the flash-all.bat file once you have extracted the Nov system image. Look for that flash-all.bat file then right click on it and open it up with Note+. Find the line at the bottom that has a -w in it and delete it out. Once that is done go to the top and hit save just dont exit out or it will not work. Once you hit save then you can hit the flash-all.bat and it will flash the Nov entire system up without erasing your current data. Hope this helps.
Click to expand...
Click to collapse
Glad I found your post. I bricked my new 3XL I received today and was unable to get the factory image installed. Getting the new tools resolved the problem. I bricked when I used Magisk 17.1. After I got it going again, I used 17.3. Now she runs great.
km8j said:
I'm now 100% back to stock. Took forever. How the heck do I do this right next time? Working on restoring my data.
Click to expand...
Click to collapse
Anyone?
km8j said:
Anyone?
Click to expand...
Click to collapse
Look at post 6
https://forum.xda-developers.com/showthread.php?p=78083312
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
Look at post 6
https://forum.xda-developers.com/showthread.php?p=78083312
Click to expand...
Click to collapse
#1 is basically what I did already
km8j said:
#1 is basically what I did already
Click to expand...
Click to collapse
I have sideloaded the Nov OTA zip in stock recovery and not lost data. Pixel 3, unlocked bootloader, unrooted.
Soft Brick recovery help
So my Pixel 3 is soft bricked and I can't seem to rescue it this time. I am bootloader unlocked and rooted on the stock rom. I was trying to update through fastboot to the April update and the flash all batch file wasn't working, I kept getting the following error
"target reported max download size of 268435456 bytes
sending 'bootloader' (8493 KB)...
OKAY [ 0.261s]
writing 'bootloader'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.213s]
finished. total time: 0.475s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 268435456 bytes
sending 'radio' (71132 KB)...
OKAY [ 1.742s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.407s]
finished. total time: 2.151s
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.049s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1999310544 bytes
error: update package missing system.img
Press any key to exit..."
I tried updating all my ADB and SDK tools. Formatting slot a and b and boot a and b then ran the batch file again and same error. Tried flashing each image file individually and the same error. I'm stuck in Fastboot. Any help would be greatly appreciated!
Try redownloading the .img and check CRC to make sure it's good, shouldn't be missing stuff
Sorry to resurrect a dead thread, but did you ever figure out how to fix your issue?
I've got the same problem over here.
Kandern97 said:
Sorry to resurrect a dead thread, but did you ever figure out how to fix your issue?
I've got the same problem over here.
Click to expand...
Click to collapse
Are you using the latest SDK platform tools, fastboot?
Hi!
I just finished sideloading the latest image for Pixel 3 (9.0.0 (PQ3A.190505.002, May 2019)
I did everything correct by following all the steps:
- unlocked bootloader
- executed flash_all.bat
- locked bootloader
At the end, after I rebooted the phone, I got into the system and checked the version.. it's still PD1A from september 2018!
Everything is wiped out as a result of unlocking the bootloader so something did work.. but the system isn't PQ3A.
Here is the flash_all.bat log:
Code:
E:\android\blueline-pq3a.190505.002>flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.288s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5343672
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.220s]
finished. total time: 0.510s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.684s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.420s]
finished. total time: 2.114s
rebooting into bootloader...
OKAY [ 0.067s]
finished. total time: 0.067s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.223s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.021s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2196 MB) to disk... took 10.381s
archive does not contain 'system.sig'
extracting system_other.img (421 MB) to disk... took 1.999s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 2.062s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5343672
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8ATX0Z2PL
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.363s
Press any key to exit...
Can you help me understand what I did wrong?
change active slots
Use this command:
fastboot getvar current-slot
This will return the active slot ( either a or b)
then use this command:
fastboot set_active (enter a or b here)
If the first command gives you a enter b and vice versa into the command above, then reflash.
Hi!
Thank you for your suggestion! Before I try it, I want to understand what I did wrong.
First, I realised I was using the 27.0.0-4455170 version of ADB so the first thing I did was to update it to 28.0.3-5475833.
Ok, so from what I understand, there are two boot slots, a and b; a being the one in which the stock image came and b the one which I flashed yesterday.
Because I had an outdated fastboot version, the flashing was successful but the slot wasn't automatically changed (this explains the "remote: variable not found" error at the end of my log).
So the system still used slot a to boot and, of course, I returned to the same stock image the phone came with. Am I correct?
So now, in order to use the second image, I simply need to do "fastboot set_active b" and reboot my phone so it uses that slot instead.
This is where I don't understand why you wrote "[...] into the command above, then reflash", Is that a typo and you actually meant "then reboot"? why should I reflash if slot b is already flashed?
Also, if I were to repeat the flashing sequence with the new adb tool, then I think I don't need to set slot b active manually as this will be done automatically now.
SOLVED
Hi
I tried to flash the original image for my blueline. The flash-all script flashes the bootloader and radio ok but it fails to flash the last file
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8493 KB)...
OKAY [ 0.295s]
writing 'bootloader'...
(bootloader) Flashing Pack version b1c1-0.1-5578427
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.509s]
finished. total time: 0.804s
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.049s
target reported max download size of 268435456 bytes
sending 'radio' (71132 KB)...
OKAY [ 1.694s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.416s]
finished. total time: 2.112s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
error: failed to load 'image-blueline-pq3a.190705.003.zip': Not enough space
Press any key to exit...
Flashing the files individually restult with: ERROR: cannot load ".\system.img" etc.
I'm on the latest platform tools for windows.
I was able to manually flash Pixel device - but Pixel 3 gives me issues. I had TWRP prior to that and Magisk running. Any suggestions appreciated
Edit:
After running flash-all with -s flag instead of -w I noticed that the sequence stops after modem_a and the device reboots into Error reason: error booting boot.img
That space error almost always means you have the wrong version of the toolkit.
TonikJDK said:
That space error almost always means you have the wrong version of the toolkit.
Click to expand...
Click to collapse
That's what I thought of at first but I'm on r29.0.1 from this link.
solved
I don't know how or why but looks like my ADB installation has been corrupted. As soon as I tried a new PC everything worked the 1st time.
It seems my slot A is dead. No matter what I try I cannot boot to it.
I've tried flash.android.com to flash back to stock, even tried going back to Pie, and back to Q, but still Slot A is dead.
With stock Pie I flashed TWRP and tried flashing custom ROM to both slots, but slot A always fails.
Tried sideloading factory OTA and LineageOS, but it keeps failing.
Tried ./flash-all.sh using a few different ROMs, stock and CalyxOS, but it always fails with the following error.
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8537 KB)...
OKAY [ 0.340s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.2-6374987
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.279s]
finished. total time: 0.619s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
target reported max download size of 268435456 bytes
sending 'radio_a' (71436 KB)...
OKAY [ 2.050s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00107-200409-B-6382632
(bootloader) Flashing partition modem_a
OKAY [ 0.418s]
finished. total time: 2.467s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
extracting android-info.txt (0 MB)...
extracting boot.img (64 MB)...
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (787 MB)...
archive does not contain 'system.sig'
extracting system_other.img (152 MB)...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (440 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6374987
Baseband Version.....: g845-00107-200409-B-6382632
Serial Number........: 96KX220PE
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
When slot A is active and I run fastboot flash boot boot.img for installing LineageOS, it will not boot to recovery, but if I set slot B active and do that then recovery works fine.
Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?
sliding_billy said:
Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?
Click to expand...
Click to collapse
Can you explain how to do that?
What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh
Is there a way to run that file from somewhere other than where it is located?
The Lepricon said:
Can you explain how to do that?
What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh
Is there a way to run that file from somewhere other than where it is located?
Click to expand...
Click to collapse
Extract the .zip directly into your platform tools folder and then with that folder open right click and open terminal from the folder. That is easier than changing your terminal path and should result in the ./ running directly from that place. Again, be sure you are running the current platform tools.
Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?
Vanschtezla said:
Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?
Click to expand...
Click to collapse
Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.
sliding_billy said:
Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.
Click to expand...
Click to collapse
I see. Thanks for clarifying that.
I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.
@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.
The Lepricon said:
I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.
@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.
Click to expand...
Click to collapse
One other thing... Have you tried a factory reset from recovery?
sliding_billy said:
One other thing... Have you tried a factory reset from recovery?
Click to expand...
Click to collapse
I believe I have. I'll try that tonight
Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot
So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.
Does anyone know why I am getting the error when running flash-all.sh?
The Lepricon said:
Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot
So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.
Does anyone know why I am getting the error when running flash-all.sh?
Click to expand...
Click to collapse
I still haven't seen that you are running the current planform tools, so that is my first suggestion. My second one is to sideload the OTA twice (including full boot after of course) so that it will install on both slots and swap. I suspect that you will then have it truly back to normal and can then do a flash-all including the -w to completely wipe.
I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.
Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.
Thank you for all your help, sliding_billy
The Lepricon said:
I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.
Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.
Thank you for all your help, sliding_billy
Click to expand...
Click to collapse
Great news, and you are quite welcome.