Develop Bugs

Bricked? target reported max download size of 536870912 bytes

[Solved]Dear friends,
I tried to upgrade my Nexus 5x via factory image files and adb commands. FYI I have done it before on my Nexus 4 so I thought it would be straightforward.
Downloaded the image files and did as the routine procedure is. However when I was flashing individual files, it was system.img turn to be flashed, I got this error "target reported max download size of 536870912 bytes"
and it won't flash system.img file.
The phone can go into bootloader, but fails to start up or whatever.
Any solution is much appreciated. :crying:
[emoji736] Solution:
Use flashall.bat which comes with the stock recovery and give it a good deal of time to parse system.img and transfer it to the phone.

You have to wait longer.

sure thet you have flashed img files one by one? i've had the same problem flashing factory image by flashall.bat...flashing img file one by one, no prob.
but if you have this problem with manual flash, try to flash twrp and install a rom zip by twrp

hamedunix said:
Dear friends,
I tried to upgrade my Nexus 5x via factory image files and adb commands. FYI I have done it before on my Nexus 4 so I thought it would be straightforward.
Downloaded the image files and did as the routine procedure is. However when I was flashing individual files, it was system.img turn to be flashed, I got this error "target reported max download size of 536870912 bytes"
and it won't flash system.img file.
The phone can go into bootloader, but fails to start up or whatever.
Any solution is much appreciated. :crying:
Click to expand...
Click to collapse
It isn't an error I think.
it's because the filesize of system.img is too big for flashed in one go, so system.img need to be parsed (in Nougat, it become 5 parts) and send one by one to phone (the fastboot command will handle this, so no need to manual parsing).
I had this problem, I just canceled the command and tried again, and success.
if it still not working, try clear cache and reset from recovery (twrp is recommended)
as long as your phone can boot to bootloader and detected by fastboot, I think your phone is far from bricked.

ikyeye said:
It isn't an error I think.
it's because the filesize of system.img is too big for flashed in one go, so system.img need to be parsed (in Nougat, it become 5 parts) and send one by one to phone (the fastboot command will handle this, so no need to manual parsing).
I had this problem, I just canceled the command and tried again, and success.
if it still not working, try clear cache and reset from recovery (twrp is recommended)
as long as your phone can boot to bootloader and detected by fastboot, I think your phone is far from bricked.
Click to expand...
Click to collapse
I am on stock recovery.
I managed to solve the problem by using "flash all" command instead of flashing each file separately.
Thanks for the reply though.

There might have been a problem with the version of fastboot I was using since it was unable to parse the package automatically and I had to use flashall.bat and give it a good deal of time to be parsed, transfered and written.

hamedunix said:
There might have been a problem with the version of fastboot I was using since it was unable to parse the package automatically and I had to use flashall.bat and give it a good deal of time to be parsed, transfered and written.
Click to expand...
Click to collapse
Glad that you figured it out. Make sure to update your fastboot of course. For me, flashing system.img took quite awhile longer than I recall it taking on Marshmallow but it did eventually flash for me.
Sent from my Nexus 5X using Tapatalk

It's confirmed, need updating fastboot to latest version to get it work.

Wuzimu said:
You have to wait longer.
Click to expand...
Click to collapse
Thanks. I figured it out accidentally by leaving the phone connected for a while and saw it booted up and all done with flashing.
Sent from my Nexus 5X using Tapatalk

Tried updating to O - think I'm screwed. Help please

So - I usually apply / sideload OTA updates to upgrade my Pixel XL (Google Store, Unlocked, rooted) and they usually go just fine. But for the O upgrade, I decided it would be a good idea to do a full clean flash for the major upgrade. I downloaded the full factory image, extracted, edited the "flash-all.bat" to remove the "-w" and executed. Everything seemed to be going fine. I saw the script flash the bootloader, then the radio successfully. However, when it attempted to flash the update image, it failed with a "too many links" error. I attempted to execute that last line in the flash-all.bat manually....
fastboot update image-marlin-opr6.170623.012.zip and receive:
target didn't report max-download-size
archive does not contain "'boot.sig'
archive does not contain 'recovery.img'
error cannot load system.img from flash
Am I bricked? Any suggestions? Right now my phone is sitting on the bootloader and I have fastboot connection (it seems)...fastboot devices yields the expected return...BUT if I issue fastboot reboot-bootloader
it fails....
I don't want to try a reboot and risk not being able to get back to the bootloader...any ideas?
Thanks!

sb1893 said:
So - I usually apply / sideload OTA updates to upgrade my Pixel XL (Google Store, Unlocked, rooted) and they usually go just fine. But for the O upgrade, I decided it would be a good idea to do a full clean flash for the major upgrade. I downloaded the full factory image, extracted, edited the "flash-all.bat" to remove the "-w" and executed. Everything seemed to be going fine. I saw the script flash the bootloader, then the radio successfully. However, when it attempted to flash the update image, it failed with a "too many links" error. I attempted to execute that last line in the flash-all.bat manually....
fastboot update image-marlin-opr6.170623.012.zip and receive:
target didn't report max-download-size
archive does not contain "'boot.sig'
archive does not contain 'recovery.img'
error cannot load system.img from flash
Am I bricked? Any suggestions? Right now my phone is sitting on the bootloader and I have fastboot connection (it seems)...fastboot devices yields the expected return...BUT if I issue fastboot reboot-bootloader
it fails....
I don't want to try a reboot and risk not being able to get back to the bootloader...any ideas?
Thanks!
Click to expand...
Click to collapse
Do you have the most current adb fastboot tools?
reminds of the error i had with the old tools and nougat.

parakleet said:
Do you have the most current adb fastboot tools?
reminds of the error i had with the old tools and nougat.
Click to expand...
Click to collapse
I believe so....same tools I used to perform the August security update on Nougat...fastboot is dates 12/19/2016.
Fastboot --version returns: fastboot version 0e9850346394-android

sb1893 said:
I believe so....same tools I used to perform the August security update on Nougat...fastboot is dates 12/19/2016.
Fastboot --version returns: fastboot version 0e9850346394-android
Click to expand...
Click to collapse
So - there are more current versions...I'm downloading now...but I'm afraid that by using the older versions, I may have messed up the update. What is my best method to recover at this point?

sb1893 said:
So - there are more current versions...I'm downloading now...but I'm afraid that by using the older versions, I may have messed up the update. What is my best method to recover at this point?
Click to expand...
Click to collapse
for me once i had the newer version i just ran the update and that was that.
at worst you might be hosed from a recovery standpoint.
most likely your user data is still there and you could do a fresh install with -w to avoid wiping user data.
you are definitely not bricked
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
this is a superb guide for accomplishing the task

parakleet said:
for me once i had the newer version i just ran the update and that was that.
at worst you might be hosed from a recovery standpoint.
most likely your user data is still there and you could do a fresh install with -w to avoid wiping user data.
you are definitely not bricked
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
this is a superb guide for accomplishing the task
Click to expand...
Click to collapse
Thank you so much! Once I installed the latest ADB/Fastboot tools, I was able to rerun the flash-all.bat (without the -w) and it seems to have completed succesfully. Rebooting now - hopefully it completes. I'm sitting on the white screen / G with some sort of progress meter cycling below the G...not sure I've seen that before - but might be new to "O"....
---and the reboot just completed...Looks like I am an Android o now. Really appreciated your quick assistance. Total lifesaver.

sb1893 said:
Thank you so much! Once I installed the latest ADB/Fastboot tools, I was able to rerun the flash-all.bat (without the -w) and it seems to have completed succesfully. Rebooting now - hopefully it completes. I'm sitting on the white screen / G with some sort of progress meter cycling below the G...not sure I've seen that before - but might be new to "O"....
---and the reboot just completed...Looks like I am an Android o now. Really appreciated your quick assistance. Total lifesaver.
Click to expand...
Click to collapse
Experience builds on experience.
enjoy

I had the same "too many links" problem today as I was flashing the factory image using flash-all.bat.
I was on 7.1.2, rooted, TWRP recovery.
After getting the same problem multiple times, I changed to a different USB port on my laptop, and it worked.
Don't know why though, but no complaints.
Just adding my experience to the mix.
My next step to try would have been to update to the latest ADB/fastboot tools.

Mine wouldn't flash the image because I was getting the to many bytes error. I can flash every part of the package except the system.IMG after hours I rebooted and was on 8.0. I was on the Tmo build but the wrong baseband. I tried to flash the whole package again this morning and received the same error. My tools are updated. Anyone have any ideas? My device is fine, I just want to fix it for future flashing
Sent from my Pixel XL using Tapatalk

Unlocked Google Pixel XL BOOTLOOP. Redid the latest factory image. Still nothing.

So my google pixel has been boot looping the past couple days now.
I've read that many others have had this issue, but none of that has helped. First I tired factory resetting it using the recovery mod, then I reloaded the latest factory image using my computer.
Honestly I don't know what else to try.
The cycle is usually as followers. Warning screen - logo screen - repeat.
After a few times i got the EX4 file screen but then it just repeats some more.
It is unlocked but that's it, never got around to doing anything else with it.
If anyone can help me it'd be greatly appreciated, really don't wanna have to buy a new phone ya know.

Leo226 said:
So my google pixel has been boot looping the past couple days now.
I've read that many others have had this issue, but none of that has helped. First I tired factory resetting it using the recovery mod, then I reloaded the latest factory image using my computer.
Honestly I don't know what else to try.
The cycle is usually as followers. Warning screen - logo screen - repeat.
After a few times i got the EX4 file screen but then it just repeats some more.
It is unlocked but that's it, never got around to doing anything else with it.
If anyone can help me it'd be greatly appreciated, really don't wanna have to buy a new phone ya know.
Click to expand...
Click to collapse
Go here:
[Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2018 Security Patch
Do #4 then #8.

Homeboy76 said:
Go here:
[Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2018 Security Patch
Do #4 then #8.
Click to expand...
Click to collapse
For #4, Flash all command doesn't work. But I can manually run the batch file, That's how I've tried doing doing it before.
The one I've been using is "marlin-ppr1.180610.010-factory-3b90270c.zip" I assumed it was the most recent one although "marlin-ppr1.180610.009-factory-90a4fa8b.zip." seems like it is just as recent.
Am I supposed to use some how both?
For #8 Simply doesn't work, just says Error: Cannot load 'twrp.img'.
Any actual detailed guides on this stuff? Because honestly it's just a confusing mess, seems like I'm doing it right. But clearly I'm not.

Leo226 said:
For #4, Flash all command doesn't work. But I can manually run the batch file, That's how I've tried doing doing it before.
The one I've been using is "marlin-ppr1.180610.010-factory-3b90270c.zip" I assumed it was the most recent one although "marlin-ppr1.180610.009-factory-90a4fa8b.zip." seems like it is just as recent.
Am I supposed to use some how both?
For #8 Simply doesn't work, just says Error: Cannot load 'twrp.img'.
Any actual detailed guides on this stuff? Because honestly it's just a confusing mess, seems like I'm doing it right. But clearly I'm not.
Click to expand...
Click to collapse
Well first your bootloader is definitely unlocked correct? I assume it is because you did say you saw the warning screen but I like to err on the side of caution. Second, you're saying that when you plug the phone into the PC that it is recognized and you are able to run commands via fastboot right? If you can run commands, but certain commands aren't working properly, I would say that it is your version of the platform tools and that you need to make sure you have the latest version. Platform tools is the folder that usually houses ADB and fastboot along with the other files necessary. These are updated occasionally and I know for a fact that outdated versions do cause issues sometimes. The next step if you can run commands would be to try a different USB port on the PC. Some ports are different when comparing the back and front and top ports. If none of that seems to do anything I would say lastly to try a different USB to USB C plug. I'm only listing all of these things because I've had to go through all of these issues myself at one point or another, but I do hope it's something simple.
I didn't mention this but obviously the files that you're flashing with fast boot have to be in the same folder as fastboot, I don't know your level of knowledge and expertise so I don't mean to sound condescending I just wanted to make sure I added that.

Leo226 said:
For #4, Flash all command doesn't work. But I can manually run the batch file, That's how I've tried doing doing it before.
The one I've been using is "marlin-ppr1.180610.010-factory-3b90270c.zip" I assumed it was the most recent one although "marlin-ppr1.180610.009-factory-90a4fa8b.zip." seems like it is just as recent.
Am I supposed to use some how both?
For #8 Simply doesn't work, just says Error: Cannot load 'twrp.img'.
Any actual detailed guides on this stuff? Because honestly it's just a confusing mess, seems like I'm doing it right. But clearly I'm not.
Click to expand...
Click to collapse
@Leo226;77325519
Verify bootloader unlocked: Turn phone off > Press Power and Volume Down keys (At the same time) until phone vibrates and you see 'Start'
The bottom line should read: ' device is Unlocked'
You missed a step.
Start over and take your time.
Use this factory image: marlin-ppr1.180610.009-factory-3b90270c.zip
Unless your Carrier/provider is Telus then use this one: marlin-ppr1.180610.010-factory-3b90270c.zip (Telus)
Do #4 - Install Factory Image 'keep' data
4C. Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Then do #8.
The #8 error is because you either didn't copy the twrp file to the directory/folder with fastboot in it or you typed the command incorrect.
This is a detailed Guide

Homeboy76 said:
@Leo226;77325519
Verify bootloader unlocked: Turn phone off > Press Power and Volume Down keys (At the same time) until phone vibrates and you see 'Start'
The bottom line should read: ' device is Unlocked'
You missed a step.
Start over and take your time.
Use this factory image: marlin-ppr1.180610.009-factory-3b90270c.zip
Unless your Carrier/provider is Telus then use this one: marlin-ppr1.180610.010-factory-3b90270c.zip (Telus)
Do #4 - Install Factory Image 'keep' data
4C. Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Then do #8.
The #8 error is because you either didn't copy the twrp file to the directory/folder with fastboot in it or you typed the command incorrect.
This is a detailed Guide
Click to expand...
Click to collapse
Sigh well everything is up to date most recent. Switched usb drives to see if it makes a difference.
Was not aware I needed to use the "09" factory image, been trying the "10".
So just flashed that, still in bootloop obviously, don't know if installing twrp would even do anything because as I said the command won't work..
It just says "cannot load 'twrp.img' . No such file exist"
The file is there, right in the platform tools folder with fastboot, adb and everything else. So not sure why it's acting like it's not.
Are their other files I need for it?

Check the properties of twrp.img and make sure it is named correctly.
Sent from my Pixel XL using Tapatalk

Leo226 said:
Sigh well everything is up to date most recent. Switched usb drives to see if it makes a difference.
Was not aware I needed to use the "09" factory image, been trying the "10".
So just flashed that, still in bootloop obviously, don't know if installing twrp would even do anything because as I said the command won't work..
It just says "cannot load 'twrp.img' . No such file exist"
The file is there, right in the platform tools folder with fastboot, adb and everything else. So not sure why it's acting like it's not.
Are their other files I need for it?
Click to expand...
Click to collapse
So, I'm going to 'assume' after updating everything and extracting the factory image to the folder with fastboot in it. You were able to use the flash-all.bat command. Yes?
Open Windows Explorer and make sure it is set to show the extension. The default is to not show the extension. Then look in the folder with the twrp file you renamed twrp.img. Does it look like this, twrp.img.img? If yes remove the last .img.
"Are their other files I need for it?" No.

Homeboy76 said:
So, I'm going to 'assume' after updating everything and extracting the factory image to the folder with fastboot in it. You were able to use the flash-all.bat command. Yes?
Open Windows Explorer and make sure it is set to show the extension. The default is to not show the extension. Then look in the folder with the twrp file you renamed twrp.img. Does it look like this, twrp.img.img? If yes remove the last .img.
"Are their other files I need for it?" No.
Click to expand...
Click to collapse
Correct, was able to flash by double clicking the batch file.
As for the twrp, yes already had made sure that the name was correct since I have had that issue with other things before.
"fastboot boot twrp.img" still does not work. I have even tried redownloading everything, placing them in it's own folder together, on and on. Nothing.
At this point I'm not even sure if installing twrp will even do anything though.
For my boot loop problem I thought just flashing the latest factory image would fix it. Clearly I was wrong.

Leo226 said:
Correct, was able to flash by double clicking the batch file.
As for the twrp, yes already had made sure that the name was correct since I have had that issue with other things before.
"fastboot boot twrp.img" still does not work. I have even tried redownloading everything, placing them in it's own folder together, on and on. Nothing.
At this point I'm not even sure if installing twrp will even do anything though.
For my boot loop problem I thought just flashing the latest factory image would fix it. Clearly I was wrong.
Click to expand...
Click to collapse
hi leo,
Have you fixed the bootloop issue yet? If yes, how?
My Pixel XL is now having same bootloop issue as yours, but my phone takes all fastboot cmds, and it just keep bootlooping.
If you just get trouble to touch the file twrp.img, I have some tips for you here:
1. I read that you are using Windows environment, so first right click the file "twrp.img", and make sure at bottom of the pop-up proprieties window, the file is not "locked", if you see it's locked, you can check the unlock box to unlock it. This is usually happen to downloaded files put in windows system partition;
2. I read that you double-click the flash-all.bat file to executive the command, please right-click on the file, and select "Run as Administrator", this way will make sure windows security policy won't prevent you from running all the cmds you intended.
3. If above 2 items you checked and not solve the twrp.img access issue, just try to download a new copy from internet again, and put in another partition folder, and repeat the above two steps. Or even try another PC/Mac.
Thanks,
Lei

unbrick Nokia 3.2

Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!

After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!

page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.

HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!

page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.

Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?

Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.

Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.

page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!

@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now

Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader

I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!

Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?

Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.

Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them

hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much

thanks so much i was able to put my phone back to life. i had almost given up.

smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.

damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.

December update not rootable?

Hi Y'all,
I just dirty flashed the December update, and then attempted to patch boot.img with magisk and flash that with fastboot, same as I've always been doing on Android 10 without fail. However, this time, it starts to boot, I get ADB, it bootloops twice, then goes back to fastboot with an error saying something to the effect of "no available slots"
I re-patched and it came out with the same md5sum of b1d09aa00e3376f3d4ceba4e97b99eae
I was able to get an adb logcat on both attempted boots, they're too large for any paste service so I threw them on a VPC I have
http://irc.killingkittens.net/logcat1.txt
http://irc.killingkittens.net/logcat2.txt
Magisk Canary, manager version 7.4.1-72edbfc4 (260)
Magisk 20.2-72edbfc4 (20108)
Happy to provide any other info that would help.

Worked fine for me.

I update ota by magisk method and work fine.
http://www.mediafire.com/view/k1r6pzneqwcrp4d/Screenshot_20191203-112633.png/file

phoe zay said:
I update ota by magisk method and work fine.
http://www.mediafire.com/view/k1r6pzneqwcrp4d/Screenshot_20191203-112633.png/file
Click to expand...
Click to collapse
I see that you're on older versions of both Magisk and Manager than I am. Which update channel are you on?

OK, root worked on my wife's P3. Canary 7.4.1-72edbfc4 (260) Manager an 20.2.72-edbfcr (20108) Magisk after flashing patched. Both show up to date. Install was a hyrbrid of flash-all and OTA. Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product, but if you then switch to recovery while still on and then ADB sideload the OTA all is fine. 29.0.5 platform tools of course.

Works as normal for me.
I always sideload ota and then patch the boot.img from the full download

sliding_billy said:
OK, root worked on my wife's P3. Canary 7.4.1-72edbfc4 (260) Manager an 20.2.72-edbfcr (20108) Magisk after flashing patched. Both show up to date. Install was a hyrbrid of flash-all and OTA. Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product, but if you then switch to recovery while still on and then ADB sideload the OTA all is fine. 29.0.5 platform tools of course.
Click to expand...
Click to collapse
Are you saying that if I update by having the phone in fastboot mode and running flash-all with -w removed than the phone update fails or gets wiped?
I had that experience last month where my phone was wiped even with -w removed! I would like to avoid getting wiped this time!

swieder711 said:
Are you saying that if I update by having the phone in fastboot mode and running flash-all with -w removed than the phone update fails or gets wiped?
I had that experience last month where my phone was wiped even with -w removed! I would like to avoid getting wiped this time!
Click to expand...
Click to collapse
Thankfully, no. I can't speak for any possible error when doing a flash-all (without -w), but the one that fails with the "sending product FAILED (Write to device failed (Invalid argument))" just shows a press any failure in command prompt and press any key to continue. The phone remains in fastbootd where you can use the volume keys and power to select recovery he use the keys again to select "sideload OTA from ADB" and while it is waiting use the "adb sideload [OTA path/filename].zip" command in commander and it acts as if you used the sideload in the first place changing slots, not erasing any data/settings/apps. I am not 100% sure yet, but I tend to think that the script is now acting differently if used without the -w but started without flashing stock .boot to both slots to unroot and remove any non-stock kernel. I have been doing it that way for 3+ years now on a Pixal, Piixel XL, Pixel 3 and Pixel 3 XL without issue until last month. I wanted to try it one more time this month after messing with my path and such, but I guess I will have to wait until January to try again. The 3 XL is on Havoc, so I can't test that one. My proposed instructions before doing it are 1)disable all modules, 2)reboot to system, 3)go to BL, 4)Flash previous stock .boot to both slots, 5)boot to system, 6)go to BL, 7)flash-all (without -w), 8)cross your fingers.

Can someone give me the md5 of the patched boot.img from this release? Or, upload a working patched file?
The specific error I got was "no valid slot to boot"
I tried flashing each slot manually, same error. I see that happened a year ago and it related to magisk versions: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712/page2

I always update via flash-all with -w option removed.
Did the same this time and no issues.
Not sure how to attach the patched boot as it is too large.
Here is the patched md5:
02536812e6b2e09e4707f98d65e7918f magisk_patched.img

I have the same problem with the same version of Magisk as you and the -w flag in flash-all didn't make a difference.

nomisunrider said:
I always update via flash-all with -w option removed.
Did the same this time and no issues.
Not sure how to attach the patched boot as it is too large.
Here is the patched md5:
02536812e6b2e09e4707f98d65e7918f magisk_patched.img
Click to expand...
Click to collapse
Completely different md5 as me when I try either magisk canary or stable! Can you please upload it to something like https://mega.co.nz/ and generate a share link?

DOMF said:
Completely different md5 as me when I try either magisk canary or stable! Can you please upload it to something like https://mega.co.nz/ and generate a share link?
Click to expand...
Click to collapse
Well, crap, I was able to get the same md5sum by flashing Canary-non-debug, but I still get the crash back to the bootloader with the error "no valid slot to boot"
Anyone have any suggestions before I try a full wipe?

I'm rooted in December but my network connectivity took a serious downgrade with it.

I'm having the same problem on Pixel 3, it just can't boot after patching the boot.img :\

sliding_billy said:
Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product,...
Click to expand...
Click to collapse
I found the reason:
Bad cable -> Solution: try another cable,
bad USB port -> Solution: try another port or computer,
or old SDK version -> download and update.
Definitely one of these.
Anyway, I also have the problem with bootloop after patch.

Worked just fine here flashing full image (-w) and then applying the patched boot.img from Magisk (20108). Not sure what is going on, but make sure you are on the latest binaries 29.0.5 (October 2019)

v12xke said:
Worked just fine here flashing full image (-w) and then applying the patched boot.img from Magisk (20108). Not sure what is going on, but make sure you are on the latest binaries 29.0.5 (October 2019)
Click to expand...
Click to collapse
Ugh I don't wanna wipe, especially without having taken a TiBu backup first (I know, bad me, it's just worked every time flawlessly so far!)
I'm on 29.0.5.1
Code:
~ fastboot --version
fastboot version 29.0.5-1
Installed as /usr/bin/fastboot
but now that you mention it, I've run into an issue with Arch's implementation of android-tools in the past. Will try from my mac tomorrow.

DOMF said:
Ugh I don't wanna wipe, especially without having taken a TiBu backup first (I know, bad me, it's just worked every time flawlessly so far!) I'm on 29.0.5.1
Click to expand...
Click to collapse
You wouldn't need to wipe... just fastboot flash the original (stock) boot.img and then get it sorted once back into System. Best of luck :good:

v12xke said:
You wouldn't need to wipe... just fastboot flash the original (stock) boot.img and then get it sorted once back into System. Best of luck :good:
Click to expand...
Click to collapse
When I got into the bootloop after applying the Magisk modified boot.img, flashing stock boot.img didn't fix it for me. I had to flash-all again to get it to boot.
I have the latest Canary Magisk Manager 7.4.1-72edbfc4(260) installed, but I also tried the stable channel and still had the same problem. I noticed that my phone faile SafetyNet over ctsProfile: false. Could my problems be related to not un-hiding Magisk? And thinking back, I may not have rebooted after disabling my modules before I started flashing.