Develop Bugs

Phone won't boot after update

I received a msg to perform an ota now the phone won't boot

justdrew said:
I received a msg to perform an ota now the phone won't boot
Click to expand...
Click to collapse
Was your phone rooted?
If it was and you didn't unroot 1st that is why it won't boot...

I restored with fastboot system IMG

justdrew said:
I restored with fastboot system IMG
Click to expand...
Click to collapse
Cool, just remember before updating you need to unroot...

More details on fastboot system IMG?
justdrew said:
I restored with fastboot system IMG
Click to expand...
Click to collapse
I'm currently stuck also, could you get me started with using "fastboot system IMG" please?

bubblegoose said:
I'm currently stuck also, could you get me started with using "fastboot system IMG" please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3079590
Flash the system image in that thread. Boot, open supersu, unroot, reboot. Search for update through settings and apply.

Where do you put the IMG file? on the external SD card?? I'm in the same situation. I unrooted the phone first before i updated. Now it bootloops, and I cant go into recovery.

justdrew said:
I received a msg to perform an ota now the phone won't boot
Click to expand...
Click to collapse
Have a look here:
http://forum.xda-developers.com/zenfone2/general/firmware-update-2-18-40-12-release-date-t3127193

OK I was able to get into recovery via this link http://www.asus.com/support/FAQ/1006346
Do I then do the factory reset wipe/data option ? Im currently doing this.. but its just sitting there at "Wiping data formatting/data..." Not sure if this will progress or just stay there?

boot in recovery, do factory reset wipe/data then wipe cache and just wait, otherwise try erase cache via fastboot

katsikoskulo said:
boot in recovery, do factory reset wipe/data then wipe cache and just wait, otherwise try erase cache via fastboot
Click to expand...
Click to collapse
i did erase the cache first though.. I'm still waiting haha.. Hope this works.

downshift00 said:
i did erase the cache first though.. I'm still waiting haha.. Hope this works.
Click to expand...
Click to collapse
if eveything fails, download and flash the latest full firmware from the asus site
have a look here: http://www.asus-zenfone.com/2015/04/how-to-flash-asus-zenfone-2.html
has instructions step by step

OK it wiped it, then i went to reboot after it was done.. but its just sitting at the main screen now with the cursor circling.. I guess I have to try the method you listed above, damn.

first give it sometime, it takes some time the 1st reboot.
Patience bro i feel you

Well its not working. So if I use this info http://www.asus-zenfone.com/2015/04/how-to-flash-asus-zenfone-2.html
What is the file that I use with ADB to send to the phone? Which firmware, or whatever file do I use?
katsikoskulo said:
first give it sometime, it takes some time the 1st reboot.
Patience bro i feel you
Click to expand...
Click to collapse

its the latest firmware from here:
http://www.asus.com/Phones/ZenFone_2_ZE550ML/HelpDesk_Download/
or
http://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
example: for ZE550ML is the UL-Z008-WW-2.17.40.6-user.zip so you type: "adb sideload UL-Z008-WW-2.17.40.6-user.zip"

OK i did that.. it finished and I cleared cache and rebooted and I'm just waiting on main screen again.... I don't have to flash a recovery IMG file right? I can just sideload that zip file correct?

I'm right there with you on the formatting /data

downshift00 said:
OK i did that.. it finished and I cleared cache and rebooted and I'm just waiting on main screen again.... I don't have to flash a recovery IMG file right? I can just sideload that zip file correct?
Click to expand...
Click to collapse
boot in recovery, update from adb , then adb sideload (name of the firmware).zip

This is what I did. It is still on the boot screen with the circle cursor... It's not working apparently.
katsikoskulo said:
boot in recovery, update from adb , then adb sideload (name of the firmware).zip
Click to expand...
Click to collapse

Nexus 5x in google logo. Cannot flash factory image

I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.

eNVy said:
I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.
Click to expand...
Click to collapse
post a screenshot from cmd here to see the error you get from fastboot...

kopfik said:
post a screenshot from cmd here to see the error you get from fastboot...
Click to expand...
Click to collapse
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.

eNVy said:
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.
Click to expand...
Click to collapse
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)

kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Shouldn't you be using the latest twrp 2.8.7.2? Ive had issues flashing roms without using the latest version. You could also have issues with older versions of twrp and encryption. Id suggest wiping data from twrp and then flashing the factory image from bootloader.
Sent from my Nexus 5X using Tapatalk

Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp

I think to be able to really do anything you need to get into bootloader and have fastboot recognize the device. Make sure the files from 6.01 are all correct and you're flashing in the right order. Follow the guide item #8 http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 If you can get the system.img and vendor.img flashed and then lock the bootloader it will wipe everything to factory, internal storage included. If you do that you must have stock recovery.img flashed as well. If downloading system.img hangs reboot and try it again.

kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Sorry, I was using v.2.8.7.2.

mnehring said:
Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp
Click to expand...
Click to collapse
I got it to work. I just had to change the USB port.
Why don't you try a different USB port or a different cable. Or even try on a different computer.

How to OTA update your ROOTED Nexus 5X

**When i will get all of the information needed,i will edit this thread and make it as simple for reaching the objective for everyone,as possible.**
Recently i got an OTA update for my nexus 5x device,a security patch form june 2017.
I`ve rooted it with this tutorial: https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
My question is: In order to install that OTA i need to follow "11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" section from Heisenberg`s tutorial or this "9. How To Update To A New Build Of The Stock ROM" section of the same tutorial?.On the "9. update the build of a stock rom" it says no data will be wiped yet this statement of google offical site still concerns me : "Warning: Installing this factory image will erase all data from the device. While it may be possible to restore certain data backed up to your Google Account, apps and their associated data will be uninstalled. Before proceeding, please ensure that data you would like to retain is backed up to your Google Account."
So what`s the safest way to OTA update your rooted device?Please provide some explanations.

ionut15 said:
**When i will get all of the information needed,i will edit this thread and make it as simple for reaching the objective for everyone,as possible.**
Recently i got an OTA update for my nexus 5x device,a security patch form june 2017.
I`ve rooted it with this tutorial: https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
My question is: In order to install that OTA i need to follow "11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" section from Heisenberg`s tutorial or this "9. How To Update To A New Build Of The Stock ROM" section of the same tutorial?.On the "9. update the build of a stock rom" it says no data will be wiped yet this statement of google offical site still concerns me : "Warning: Installing this factory image will erase all data from the device. While it may be possible to restore certain data backed up to your Google Account, apps and their associated data will be uninstalled. Before proceeding, please ensure that data you would like to retain is backed up to your Google Account."
So what`s the safest way to OTA update your rooted device?Please provide some explanations.
Click to expand...
Click to collapse
It is very simple actually. Here's a quick lesson for you to try out. Download any factory image then examine the flash-all.sh script inside the zip. Find the line command that begins with "-w." This command will cause the entire phone to be wiped when the script is executed, as Google highlights.
You can edit and remove the entire -w line to leave your internal storage intact. However, TWRP will be replaced because this script installs each partition including the stock recovery.
I don't believe my guide could be any clearer. Manually entering the commands for each partition, as my guide states, does not wipe the device. With fastboot, the primary ways to wipe the device are: executing the flashall script for a factory image, flash the userdata.img, issue fastboot format userdata, or lock/unlock the bootloader.
Follow my guide to update
Sent from my Nexus 5X using Tapatalk

@SlimSnoopOS thank you,very clear response

ionut15 said:
@SlimSnoopOS thank you,very clear response
Click to expand...
Click to collapse
Also, make sure to flash root and any other mods BEFORE booting up once you update.
My pleasure! That's why this great place exists and I'm always happy to pass on information that I've learned.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Also, make sure to flash root and any other mods BEFORE booting up once you update.
My pleasure! That's why this great place exists and I'm always happy to pass on information that I've learned.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Can i ask what are the cons of not doing so? I would flash the factory img that will lead to replacing custom recovery with the stock one and cancelling my root.After flashing it,i asumme that my phone will boot up,so i need to power it off again and proceed to install recovery and root again via adb.How can i install them before the phone will be booting up?
Sent from my Nexus 5X using Tapatalk

I always followed this guide here: http://elementalx.org/how-to-install-android-monthly-security-updates/
Here's the quick summary:
Download the newest factory update for your device
Extract all files
Update system boot vendor bootloader radio
Flash whatever root and/or kernel you want.
Wipe cache/dalik
Reboot
Worked like a charm, and only took me ~10 or so minutes once I knew what I was doing.

crazyates said:
I always followed this guide here: http://elementalx.org/how-to-install-android-monthly-security-updates/
Here's the quick summary:
Download the newest factory update for your device
Extract all files
Update system boot vendor bootloader radio
Flash whatever root and/or kernel you want.
Wipe cache/dalik
Reboot
Worked like a charm, and only took me ~10 or so minutes once I knew what I was doing.
Click to expand...
Click to collapse
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?

ionut15 said:
Can i ask what are the cons of not doing so? I would flash the factory img that will lead to replacing custom recovery with the stock one and cancelling my root.After flashing it,i asumme that my phone will boot up,so i need to power it off again and proceed to install recovery and root again via adb.How can i install them before the phone will be booting up?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It is just a time saving step. If you manually install each partition excluding recovery.img, you can still boot directly into TWRP from bootloader to flash root and now TWRP will persist. This is more relevant on Nougat and newer, this didn't happen on Marshmallow.
Installing a OTA/factory image will always override every partition including TWRP recovery. But if you manually install each image except recovery, upon booting into the phone the stock recovery will replace TWRP. To get root now you will need to: boot into bootloader, flash TWRP, then boot into TWRP to flash your mods afterwards. Make sense?
ionut15 said:
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
Click to expand...
Click to collapse
Please do not erase cache. Skip this step when using Nougat and newer. I have to update this part of the guide.
Sent from my Nexus 5X using Tapatalk

ionut15 said:
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
Click to expand...
Click to collapse
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).

crazyates said:
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
Click to expand...
Click to collapse
Thank you,managed to update the security patch and works just fine.
Sent from my Nexus 5X using Tapatalk

crazyates said:
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
Click to expand...
Click to collapse
Thank you again for your time and devotion.You cleared off all of my doubts.Furthermore i hope someone who's in my situation could find this topic helpful.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
It is just a time saving step. If you manually install each partition excluding recovery.img, you can still boot directly into TWRP from bootloader to flash root and now TWRP will persist. This is more relevant on Nougat and newer, this didn't happen on Marshmallow.
Installing a OTA/factory image will always override every partition including TWRP recovery. But if you manually install each image except recovery, upon booting into the phone the stock recovery will replace TWRP. To get root now you will need to: boot into bootloader, flash TWRP, then boot into TWRP to flash your mods afterwards. Make sense?
Please do not erase cache. Skip this step when using Nougat and newer. I have to update this part of the guide.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you again for your time and devotion.You cleared off all of my doubts.Furthermore i hope someone who's in my situation could find this topic helpful.
Sent from my Nexus 5X using Tapatalk

If you want install OTA updates while your device is rooted, use Flashfire.

AFK269 said:
If you want install OTA updates while your device is rooted, use Flashfire.
Click to expand...
Click to collapse
its a straight-forward method,unfortunately my system partition was changed and flashfire can't flash ota.
Sent from my Nexus 5X using Tapatalk

ionut15 said:
its a straight-forward method,unfortunately my system partition was changed and flashfire can't flash ota.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Then flash factory images with adb fastboot commands

Can't downgrade from Android 8.1.

I installed the 8.1 dp on my pixel 2 xl and I have decided to go back to android 8.0. I signed out of the beta and the OTA showed up as it was supposed to, from there I tried to install the downgrading OTA but it came up with a generic error (update was not able to be installed) from there I decided to try flashing the factory image and this error came up
writing 'bootb'...
FAILED (remote: No such partition.)
and when I rebooted it booted fine but was still on android 8.1. I also tried manually flashing the system partition as I noticed the script made no mention of flashing system, it came up with the error
sending sparse 'systemb' 1/4 (524284 KB)...
OKAY [ 16.552s]
writing 'systemb' 1/4...
FAILED (remote: No such partition.)
and once again after a reboot it went back to android 8.1. Any help is appreciated, thanks.

Download and flash the entire Factory image from Google's factory image page. That should work. However, this will wipe your phone.

I did flash the factory image which is what resulted in the partition error.

If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.

Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.

Moostafa29 said:
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Click to expand...
Click to collapse
I already tried downgrading through the OTA, it came up with a generic error.
clnzx2 said:
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Click to expand...
Click to collapse
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.

I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).

I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,

TheSt33v said:
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
Click to expand...
Click to collapse
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
TheDonXR said:
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
Click to expand...
Click to collapse
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.

Afriendlytrashcan said:
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Click to expand...
Click to collapse
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.

Afriendlytrashcan said:
I already tried downgrading through the OTA, it came up with a generic error.
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
Click to expand...
Click to collapse
That is your problem. Update to latest tools and it will work. :good:

TheSt33v said:
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Click to expand...
Click to collapse
clnzx2 said:
That is your problem. Update to latest tools and it will work. :good:
Click to expand...
Click to collapse
Sounds good! I'll try it a bit later, my fingers have never been more crossed.

It worked! After updating fastboot the flash-all zip worked perfectly. Thanks everyone for your help!

Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock

TimeTurn said:
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
Click to expand...
Click to collapse
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???

Badger50 said:
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Click to expand...
Click to collapse
He said he was tired...

galaxys said:
He said he was tired...
Click to expand...
Click to collapse
Well shucks! ???

so actualy there is option to go back in versions?
that's nice!

I7210I said:
so actualy there is option to go back in versions?
that's nice!
Click to expand...
Click to collapse
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 ?

Badger50 said:
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 [emoji50]
Click to expand...
Click to collapse
so it's not quite works now?
in nexus it was worked right away
Sent from my Pixel 2 XL using Tapatalk

Need help manually flashing factory image

Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices

motcher41 said:
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
Click to expand...
Click to collapse
How did you get to DP3? Did you enroll in the beta program?

Badger50 said:
How did you get to DP3? Did you enroll in the beta program?
Click to expand...
Click to collapse
yes and weirdly using a factory image on my Mi A1 gave no error

motcher41 said:
yes
Click to expand...
Click to collapse
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:

Badger50 said:
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Click to expand...
Click to collapse
i would but i am currently soft bricked. have access to bootloader only

even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc

motcher41 said:
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
Click to expand...
Click to collapse
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.

but are they all the same target as the .img name

Badger50 said:
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
Click to expand...
Click to collapse
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too

motcher41 said:
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
Click to expand...
Click to collapse
Hey, as long as it worked your good. Welcome :good:
Yeah my format userdata may have been off. I was going by memory from my 6p. P2XL might be different. Sorry.