Question Unbrick Oneplus 9 that boots to Qualcomm crash dump mode? - OnePlus 9

Recently i was trying to flash Stag OS when i accidentally flashed the wrong img to the system partition. now I can only boot into fastboot and the Qualcomm Crash Dump Mode. Is there a way out of this? I tried unpacking my payload.bin and flashing each img individually but it took me back to the same error.

I have had this happen to two separate oneplus 9's. My recommendation would be to start trying to run MSM tools from the forums here (both for your correct device and then for other 9 variants, i had the most success using the India 9+ version then running the correct version once the phone was booting again)

I did that and it worked! I was having issues getting into msm mode but then I realized I wasn't supposed to hold the power button. Thanks!

Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img

LinhBT said:
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
It's not dangerous to use the MSM tool that's made for your device. Manual fastboot flashing is more likely to cause problems due to human error than the MSM is. The MSM is done quicker too.

Hi,
I'll try to follow your tutorial, I have an LE2113 and I only cna boot into Qualcomm Crash Dump Mode, sometimes into bootloader mode.
I tried to follow the tutorials to root the phone, but I didn't do it until my OnePlus6, and the tutorials looks more complicated than in the past, in my opinion, it missed a lot of step for the beginners.
I'll try to find a way to make my phone alive again.

EtherealRemnant said:
It's not dangerous to use the MSM tool that's made for your device. Manual fastboot flashing is more likely to cause problems due to human error than the MSM is. The MSM is done quicker too.
Click to expand...
Click to collapse
I always trust myself more than any other tools But yeah, for some, the tools would be more confort

LinhBT said:
I always trust myself more than any other tools But yeah, for some, the tools would be more confort
Click to expand...
Click to collapse
Yeah I have never had an issue with manual flashing either but all the reports of people bricking and having to use MSM tell me that it's pretty common with OnePlus devices. I saw so many of those reports that I made sure MSM Tool was working before I even unlocked my bootloader lol.

EtherealRemnant said:
Yeah I have never had an issue with manual flashing either but all the reports of people bricking and having to use MSM tell me that it's pretty common with OnePlus devices. I saw so many of those reports that I made sure MSM Tool was working before I even unlocked my bootloader lol.
Click to expand...
Click to collapse
True bro. I used to try in vain lots of MSM build just to find one which can actually works and unbrick my 8T, but if not sahara error, then would be param or else. At last, fastboot saved my ass ))

LinhBT said:
True bro. I used to try in vain lots of MSM build just to find one which can actually works and unbrick my 8T, but if not sahara error, then would be param or else. At last, fastboot saved my ass ))
Click to expand...
Click to collapse
I was kind of surprised at how straightforward it was. I booted up Windows 11, installed the drivers, put the USB cord for my Pixel 3 XL in the USB-C port, put phone in EDL with the key combo, ran MSM. Zero issues either time I have tried it. I was absolutely prepared to have to fight with it.

EtherealRemnant said:
I was kind of surprised at how straightforward it was. I booted up Windows 11, installed the drivers, put the USB cord for my Pixel 3 XL in the USB-C port, put phone in EDL with the key combo, ran MSM. Zero issues either time I have tried it. I was absolutely prepared to have to fight with it.
Click to expand...
Click to collapse
Yeah, after I figured out what happened, then the rest are just like what u said. Turns out that my 8T was having CyberPunk param ( I did tried to convert ) therefore, MSM doesn't recognized it since MSM is specific for each model ))

LinhBT said:
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I'll try your method, MSM don't work, even on test mode on Windows10. Last chance operation :/ but when I fastboot flash abl abl.img, I have the actual message:
fastboot: error: cannot load 'abl.img': No such file or directory
Click to expand...
Click to collapse

BroenGuiraldson said:
I'll try your method, MSM don't work, even on test mode on Windows10. Last chance operation :/ but when I fastboot flash abl abl.img, I have the actual message:
Click to expand...
Click to collapse
Normally, it's abl.elf bro, depends on the Firm u r using to flash

I'm trying to flash the "OnePlus9Oxygen_22.E.47_OTA_1470_all_2203102118_ad7f1.zip" for my LE2113 version.
I extracted all the img files. How can I know if it's abl.elf instead of abl ? What about the other image flash ?
I tried with the aop and it returns the same error.
In parallel, still trying to detect my phone on MSM :/

LinhBT said:
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
Are you sure this is right? I don't see boot.img in that list.

Z-Blade said:
Are you sure this is right? I don't see boot.img in that list.
Click to expand...
Click to collapse
boot.img dtbo.img ( and sometimes stock recovery.img )you will have to flash before execute this commands, since we will need to boot into fastbootD which only available in wherether boot.img or recovery.img

Related

[SOLVED] Unable to install factory image. "Not enough space"

I have a bootloader unlocked Google Pixel. On my computer I have Fastboot and ADB
I wanted to flash the Android 8.0 factory images from here:
https://developers.google.com/android/images#sailfish
I downloaded and extracted the zip, booted into download mode, and ran the flash-all.bat
When I do that it goes for a short while then terminates with the following:
error: failed to load 'image-sailfish-opr6.170623.012.zip': Not enough space
I have gone into TWRP and wiped everything as well as formatted but it hasn't let me run the factory image due to space.
What can I do?
EDIT: My problem was solved by mannunikhil:
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
Tate Adams said:
I have a bootloader unlocked Google Pixel. On my computer I have Fastboot and ADB
I wanted to flash the Android 8.0 factory images from here:
https://developers.google.com/android/images#sailfish
I downloaded and extracted the zip, booted into download mode, and ran the flash-all.bat
When I do that it goes for a short while then terminates with the following:
error: failed to load 'image-sailfish-opr6.170623.012.zip': Not enough space
I have gone into TWRP and wiped everything as well as formatted but it hasn't let me run the factory image due to space.
What can I do?
Click to expand...
Click to collapse
there are couple of things that I can think of as of now,
1 ) Take backup of internal storage and run flash-all.bat as original (do not remove -w from the batch file),
2) Update Android SDK / Google USB Drivers with latest version and flash it again.
Sadly updating those didn't help. Everytime I try to install factory image it says it cannot allocate about 4 time the amount it says my max is. Any way to clear data from TWRP? I was quick to clear data so I have no backup to go back to. I'll take anyone's suggestions but I've lost hope.
Tate Adams said:
Sadly updating those didn't help. Everytime I try to install factory image it says it cannot allocate about 4 time the amount it says my max is. Any way to clear data from TWRP? I was quick to clear data so I have no backup to go back to. I'll take anyone's suggestions but I've lost hope.
Click to expand...
Click to collapse
suggest you to check the disk space where your windows temp directory set to.
during flashing it needs to unzip image-sailfish-opr6.170623.012.zip to temp folder
Tate Adams said:
Sadly updating those didn't help. Everytime I try to install factory image it says it cannot allocate about 4 time the amount it says my max is. Any way to clear data from TWRP? I was quick to clear data so I have no backup to go back to. I'll take anyone's suggestions but I've lost hope.
Click to expand...
Click to collapse
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
Thank you mannunikhil! I wish I could extend a hug and a hand shake to you. Fixed it for me! Also thank you lonelytibetj even though I was unable to get that to work, I appreciate the reply. Love you all.
Tate Adams said:
Thank you mannunikhil! I wish I could extend a hug and a hand shake to you. Fixed it for me! Also thank you lonelytibetj even though I was unable to get that to work, I appreciate the reply. Love you all.
Click to expand...
Click to collapse
Glad it worked out for you. Cheers ?
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
That's works. Thanks man ?
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
when i flash aboot.img it shows target reported max downloaded size of 53670912 bytes error: cannot load aboot.img:ni error how can i solve it
updating google pixel
when i use adb it says:
archive does not contain boot.sig
archive does not contain recovery.img
package missing system.img
Dont know what to do im out of date just like my phone thanks ...
phoe zay said:
when i flash aboot.img it shows target reported max downloaded size of 53670912 bytes error: cannot load aboot.img:ni error how can i solve it
Click to expand...
Click to collapse
By at this stage I assume you have already enabled OEM unlocking and bootloader is unlocked. Now, 1st I would like you to use USB 2.0 port on your computer to follow the entire procedure and not USB 3.0 port.
If this doesnt help, update your adb drivers and re-download the image file and try.
thisnish87 said:
when i use adb it says:
archive does not contain boot.sig
archive does not contain recovery.img
package missing system.img
Dont know what to do im out of date just like my phone thanks ...
Click to expand...
Click to collapse
You need to extract all the files from all the zips in one location and then follow the procedure.
Hi. I am in a similar boat, but for android 9.0 Pie. Would you be able to post instructions for manually flashing stock on my Pixel 3XL? I would really appreciate it if you knew and wouldn't mind sharing. Thanks!
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
sahilmp3 said:
Hi. I am in a similar boat, but for android 9.0 Pie. Would you be able to post instructions for manually flashing stock on my Pixel 3XL? I would really appreciate it if you knew and wouldn't mind sharing. Thanks!
Click to expand...
Click to collapse
Follow the instructions here:
https://developers.google.com/android/images
TYSM!!!!!!! luv u
mannunikhil said:
Try these step by step, this is manual flashing
Since you have already run flash-all.bat, bootloader and radio img had been already flash or you can flash them again if feel so.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Extract the zip "image-sailfish-opr6.170623.012.zip " to adb/fastboot location
Then to fix slot_b:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
Then erase/format system_b..
Fastboot erase system_b
And erase/format userdata ...
Fastboot erase userdata
Then proceed to fix slot_a
fastboot flash aboot aboot.img
fastboot flash apdp apdp.img
fastboot flash boot boot.img
fastboot flash bootlocker bootlocker.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash hosd hosd.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Finally, "fastboot reboot".
Click to expand...
Click to collapse
How would I remove the fastboot reboot at the end if I run the flash-all.sh. Tried using vim to just remove it, but I don't see that command. Where is it being executed? In the "image-sailfish-opr6.170623.012.zip"? If so where in the zip
Thank you
Hi guys
I have pixel 1 and I was on android 10
I had some problems so I decided to downgrade
I downloaded Android 7.1 recovery sailfish
Extracted the zip file
And flashall.bat
Bootloader and radio were ok
But when it comes to zip file
It gives me a massage
That zip file is too big and dosent goes
Then boots to Google logo and loop
I tried another sailfish recovery and another
The same problem
I the way by extracting zip file and flash every single img file
Every thing goes okey
But when I reboot it loops again
In fastboot mode it shows that bootloader sector is _b
Is that correct and what is the difference between sector a and sector b

Android Pie image and how to flash stock Android 9

These are image files that are extracted from the payload of the android P OTA: https://drive.google.com/open?id=1gLRvB3A7uxbt5xgh9ntKiLfspzi1wcuK
Warning: You will erase all of your data
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
Run the code and then factory reset in recovery, and you will have android P.
Will you looae all data?
HoangP05 said:
These are image files that are extracted from the payload of the android P OTA: https://drive.google.com/open?id=1gLRvB3A7uxbt5xgh9ntKiLfspzi1wcuK
Warning: You will erase all of your data
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
Run the code and then factory reset in recovery, and you will have android P.
Click to expand...
Click to collapse
:good::good::good:
Thank you very much :good::good::good::good:
Oh my God thanks, easy, speed, nice, you are a the best
Thanks!
I created my XDA user (after 4 years using this forum) just to thank you. Feel special
Are these images from untouched Pie 10.0.1.0?
aryacebe said:
Are these images from untouched Pie 10.0.1.0?
Click to expand...
Click to collapse
Yes it is, but you can update directly to pie now I believe, and i saw people saying that the later version is better. You can still follow my instruction if you want!
HoangP05 said:
Yes it is, but you can update directly to pie now I believe, and i saw people saying that the later version is better. You can still follow my instruction if you want!
Click to expand...
Click to collapse
Not because I don't need the new version, but I need system.img and boot.img from my current android version (10.0.1.0), it is because my ota couldn't be installed, I think my system or boot is tampered when I rooted my phone :crying:
Wanna ask, is it safe if I only flash only boot and system? My A2 Lite already on 10.0.1.0 Pie
Only do:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
Will this take you back to stock, I have rooted Oreo and would like to go back to stock, are there any risks using this method, e.g. boot loop, etc... will it relock the boot.
I'm getting a Bootloop with this methode.
Question: By flashing this would my device be eligible to receive the stock OTA Android One release of Android 10 once it's released?
Thanks
ConsistentCarl said:
Question: By flashing this would my device be eligible to receive the stock OTA Android One release of Android 10 once it's released?
Click to expand...
Click to collapse
In theory the images here are stock, extracted from a full OTA (or Recovery) package.
Stock images won't hurt future OTAs (as long as they match the "current version" you're running)

oneplus 6 stuck at fastboot

So its just stuck in fastboot mode ive tried fastboot flash boot_a,boot_b and nothing happens its just stuck in fastboot.
That's the best custom kernel I've seen so far. But it is missing information and the GitHub source code
I take it using the volume keys and power keys to select start or recovery do not work? If that's the case, use the MSM Recovery Tool found here and revert back to stock
can you boot twrp? if not, than try to flash ALL partitions manually with fastbootcommands
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
of course U need the -stock-fastboot-rom which u have

Stuck on animation initial boot after 11.1.6.6 OS via OTA

Hi all, just received and updated the 11.1.6.6 via OTA... but after reboot I'm locked on the two white dots around the one red icons, and the phone doesn't start anymore.. so it's NOT a bootloop, but just blocked situation..
I'm rooted... what can I do to exit from this situation as well?
Just tried with VOL UP + POWER combo, but this casue only a power off, or a new reboot, but the situation doesn't change and the screen still stuck on the dots animation..
EDIT:
Had to resolve with a full wipe factory reset, no other way.
There was another way. You could've downloaded the latest update package onto your PC, used PayloadDumper to extract the payload.bin file found inside the zip file, extracted Android's 'Platform tools' into the output folder of the payload dump and then ran these commands without wiping while your phone is connected in fastboot:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
You'd lose root but your phone would be updated to the latest OS and your data would hold.
You can then follow the root guide to patch the boot.img extracted from the payload file and let magisk do its thing.

Question Flashed into TWRP = Qualcomm Crashdump Mode

I accidentally flashed twrp-3.7.0_11-0-lemonadep.img onto my OP9 and is not met by Qualcomm Crashdump Mode constantly when trying to boot. wanted to boot it temporarily, but did this instead.
I tried temparirely booting after but it did not work sadly.
I read that I have to boot into Oxygen again, but I am pretty stuck on what's to do next, since I booting into fastbootd with no luck, which led me to not be able boot Oxygen.
Do any of you guys have any idea of what I can do to get out of this state and booted into LineageOS.
dimitrysulah6211 said:
I accidentally flashed twrp-3.7.0_11-0-lemonadep.img onto my OP9 and is not met by Qualcomm Crashdump Mode constantly when trying to boot. wanted to boot it temporarily, but did this instead.
I tried temparirely booting after but it did not work sadly.
I read that I have to boot into Oxygen again, but I am pretty stuck on what's to do next, since I booting into fastbootd with no luck, which led me to not be able boot Oxygen.
Do any of you guys have any idea of what I can do to get out of this state and booted into LineageOS.
Click to expand...
Click to collapse
reflash to stock and try again
I am doing this:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And already came to the part where I need to enter fastbootd, but when I turn off OP9 it boots into fastboot and if I do the command "fastboot reboot fastboot", it says this:
C:\Users\%Username%>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
This is the error codewhen flashing:
fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (2132 KB)...
OKAY [ 0.047s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions.
dimitrysulah6211 said:
I am doing this:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And already came to the part where I need to enter fastbootd, but when I turn off OP9 it boots into fastboot and if I do the command "fastboot reboot fastboot", it says this:
C:\Users\%Username%>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
This is the error codewhen flashing:
fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (2132 KB)...
OKAY [ 0.047s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions.
Click to expand...
Click to collapse
use these commands
fastboot reboot bootloader
after flash press space drag and drop the img file and wait for it to flash
fastboot flash
dimitrysulah6211 said:
I am doing this:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And already came to the part where I need to enter fastbootd, but when I turn off OP9 it boots into fastboot and if I do the command "fastboot reboot fastboot", it says this:
C:\Users\%Username%>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
This is the error codewhen flashing:
fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (2132 KB)...
OKAY [ 0.047s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions.
Click to expand...
Click to collapse
Never mind
bloxycola said:
use these commands
fastboot reboot bootloader
after flash press space drag and drop the img file and wait for it to flash
fastboot flash
Click to expand...
Click to collapse
try this
download the fastboot folder and driver from here ---> https://highonandroid.com/fastboot-zip-android-usb-drivers/
extract the fastboot folder
drag and drop the .imgs onto the fastboot folder then where the directory is (if your on windows) press on it and type in cmd the command promt will apear now connect your phone and turn it on and type
fastboot reboot bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot reboot bootloader
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot reboot
if fastboot reboot bootloader not allowing you to flash try fastboot reboot fastboot
bloxycola said:
try this
download the fastboot folder and driver from here ---> https://highonandroid.com/fastboot-zip-android-usb-drivers/
extract the fastboot folder
drag and drop the .imgs onto the fastboot folder then where the directory is (if your on windows) press on it and type in cmd the command promt will apear now connect your phone and turn it on and type
fastboot reboot bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot reboot bootloader
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot reboot
if fastboot reboot bootloader not allowing you to flash try fastboot reboot fastboot
Click to expand...
Click to collapse
I fixed it by downloading the MSM tool and flashing it into stock OxygenOS, with no issues whatsoever.
I will now try again, but this time boot it into TWRP temporarily and then flash it after.
dimitrysulah6211 said:
I fixed it by downloading the MSM tool and flashing it into stock OxygenOS, with no issues whatsoever.
I will now try again, but this time boot it into TWRP temporarily and then flash it after.
Click to expand...
Click to collapse
Yes
dimitrysulah6211 said:
I fixed it by downloading the MSM tool and flashing it into stock OxygenOS, with no issues whatsoever.
I will now try again, but this time boot it into TWRP temporarily and then flash it after.
Click to expand...
Click to collapse
Your trying to flash LineageOS right?
bloxycola said:
Your trying to flash LineageOS right?
Click to expand...
Click to collapse
Boot intro TWRP flash LineageOS then flash TWRP and try to se eif it boots
I believe that the right procedure is to update all the way up to OOS 13 F.20 firmware, then flash the Lineage Rec and from there flash LOS

Categories

Resources