[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS - OnePlus Nord N10 5G Guides, News, & Discussion

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord and OP8T here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N10.
Albeit it has not been tested, you should hopefully be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
Please note that crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. For reference EU devices project ID is 20889 while international devices project ID is 20886. This has been found with @Elidone unit, which hasn't been able to crossflash EU software on his international device (see second screenshot attached). I therefore assume that same happens when trying to flash international software on EU units.
BE86AA tools (international firmware):
ANDROID 10:
OOS 10.5.7
OOS 10.5.8
OOS 10.5.9
OOS 10.5.11
Mirror for first and last MSMs: https://onepluscommunityserver.com/
BE89BA tools (european firmware):
ANDROID 10:
OOS 10.5.7
OOS 10.5.8
OOS 10.5.9
OOS 10.5.10
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@Elidone for testing 10.5.7 AA version on his device and for the screenshots
OnePlus for the device and OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Reserved

Good!
I planned to get US version once it's released

Hello kind sir. I just tested out the wonderful software you provide, and may I say, it works flawlessly!
Have a great Christmas!

I really wish this was available before I spent well over two weeks waiting for their support to use this exact tool on my bricked N10. At least I have their tools now. Thanks for the release, and hopefully no one else has to go through the support for this kind of stuff again.

@Some_Random_Username
Hi. Do you have a new version 10.5.9.BE86AA?

Alexey71 said:
@Some_Random_Username
Hi. Do you have a new version 10.5.9.BE86AA?
Click to expand...
Click to collapse
Hi, no, most likely because 10.5.9 got released too recently (today is first time I'm hearing of that build).
I however have 10.5.8 which I aim to release in next days.

@Some_Random_Username
Tell me how to unpack billie8_14_O.01_201121.ops?
I need stock xxx.img

Alexey71 said:
@Some_Random_Username
Tell me how to unpack billie8_14_O.01_201121.ops?
I need stock xxx.img
Click to expand...
Click to collapse
You can't, however you can find OOS 10.5.7 BE86AA stock boot.img at https://forum.xda-developers.com/t/root-n10-using-magisk.4197369/ (in the zip file boot_10.5.7.BE86AA.zip )

Added OOS 10.5.8 MSMs
For those unfamilliar, you don't need latest version to unbrick your device, it's just a convenience to restore to a newer build.

Mod edit - translated by https://www.deepl.com/translator:
Which region does the version of the appliance belong to? Firmware 10.5.9. BE86AA. Model BE2029. Global or Eu? And where can i download full firmware images for this phone model?
*******************************
К какому региону относится версию аппарата? Прошивка 10.5.9. BE86AA. Модель BE2029. Глобал или Eu? И где можно скачать полные образы прошивки для этой модели телефона?

serg7500 said:
Mod edit - translated by https://www.deepl.com/translator:
Which region does the version of the appliance belong to? Firmware 10.5.9. BE86AA. Model BE2029. Global or Eu? And where can i download full firmware images for this phone model?
*******************************
К какому региону относится версию аппарата? Прошивка 10.5.9. BE86AA. Модель BE2029. Глобал или Eu? И где можно скачать полные образы прошивки для этой модели телефона?
Click to expand...
Click to collapse
Please use the English language! [Пожалуйста, используйте английский язык!]
XDA Forum Rules (excerpt):
...
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
...
Click to expand...
Click to collapse

serg7500 said:
Mod edit - translated by https://www.deepl.com/translator:
Which region does the version of the appliance belong to? Firmware 10.5.9. BE86AA. Model BE2029. Global or Eu? And where can i download full firmware images for this phone model?
*******************************
К какому региону относится версию аппарата? Прошивка 10.5.9. BE86AA. Модель BE2029. Глобал или Eu? И где можно скачать полные образы прошивки для этой модели телефона?
Click to expand...
Click to collapse
BE86AA software is global software.
Unfortunately OnePlus hasn't released full zip for it on its support website yet.

Some_Random_Username said:
BE86AA software is global software.
Unfortunately OnePlus hasn't released full zip for it on its support website yet.
Click to expand...
Click to collapse
Mod edit - translated by https://www.deepl.com/translator and quotation repaired:
Would you kindly provide a link to this website?
********************************
А будьде добры дать ссылку на этот веб-сайт

serg7500 said:
[QUOTE = "Some_Random_Username, сообщение: 84311381, участник: 8234677"]
Программное обеспечение BE86AA - это глобальное программное обеспечение.
К сожалению, OnePlus еще не выпустил полный zip для него на своем веб-сайте поддержки.
[/ QUOTE]
А будьде добры дать ссылку на этот веб-сайт
Click to expand...
Click to collapse
Please, english only
OnePlus Support Softwareupgrade - OnePlus (United States)
support softwareupgrade
www.oneplus.com

Thanks, it worked like a charm.

Some_Random_Username said:
BE86AA software is global software.
Unfortunately OnePlus hasn't released full zip for it on its support website yet.
Click to expand...
Click to collapse
It may be worth asking support about it. They seemed to release the UK zip the day after I asked about it to them.

Thanks for posting this. You saved my a$$.
Just got a BE86AA 2 days ago and I rooted it per the instructions posted here.
It worked perfectly rooted for over 24 hours, then refused to boot, just hung at the message about the bootloader being unlocked.
I tried reflashing the patched boot image--no help, then tried wiping anything I could from recovery--no help.
I then flashed the unpatched boot image--still no luck, then I re-locked the bootloader--still not booting.
At that point I downloaded the unbrick tool and I was able to restore to stock successfully !!!
Thank you so much for posting this here !!
FYI: Just before the failure to boot I installed a couple of Magisk apps, the first Magisk apps that I installed.
It's nice to know that I have a solution to restore my phone no matter what happens to it.

Any way to do it in Linux ? i mean script to do all, i know about
extracting zip to fastboot all like
Code:
[email protected] ~/Downloads/extract_android_ota_payload-master $ python extract_android_ota_payload.py OnePlusN10Oxygen_14.E.09_OTA_009_all_2101021731_9c32820c43e443f1.zip 1/
Extracting 'payload.bin' from OTA file...
Extracting 'abl.img'
Extracting 'boot.img'
Extracting 'dtbo.img'
Extracting 'odm.img'
Extracting 'product.img'
Extracting 'recovery.img'
Extracting 'system.img'
Extracting 'vbmeta.img'
Extracting 'vbmeta_system.img'
Extracting 'vendor.img'
Extracting 'aop.img'
Extracting 'bluetooth.img'
Extracting 'devcfg.img'
Extracting 'dsp.img'
Extracting 'featenabler.img'
Extracting 'hyp.img'
Extracting 'imagefv.img'
Extracting 'keymaster.img'
Extracting 'modem.img'
Extracting 'qupfw.img'
Extracting 'storsec.img'
Extracting 'tz.img'
Extracting 'uefisecapp.img'
Extracting 'xbl_config.img'
Extracting 'xbl.img'
Extracting 'oem_stanvbk.img'
(n):cry:[email protected] ~/Downloads/extract_android_ota_payload-master $ cd 1
abl.img dtbo.img odm.img storsec.img vendor.img
aop.img featenabler.img oem_stanvbk.img system.img xbl_config.img
bluetooth.img hyp.img payload.bin tz.img xbl.img
boot.img imagefv.img product.img uefisecapp.img
devcfg.img keymaster.img qupfw.img vbmeta.img
dsp.img modem.img recovery.img vbmeta_system.img
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash boot boot.img
< waiting for any device >
Sending 'boot_b' (98304 KB) OKAY [ 2.314s]
Writing 'boot_b' OKAY [ 1.953s]
Finished. Total time: 4.279s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (782003 KB) OKAY [ 18.506s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.822s]
Finished. Total time: 0.828s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot erase cache
Erasing 'cache' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot -w
Erasing 'userdata' OKAY [ 0.801s]
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.318s]
Writing 'boot_b' OKAY [ 1.885s]
Finished. Total time: 4.217s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.195s]
Writing 'dtbo' OKAY [ 0.188s]
Finished. Total time: 0.391s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash modem modem.img
Sending 'modem_b' (152332 KB) OKAY [ 3.607s]
Writing 'modem_b' OKAY [ 2.974s]
Finished. Total time: 6.590s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 2.412s]
Writing 'recovery' OKAY [ 2.023s]
Finished. Total time: 4.455s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 9.477s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash abl abl.img
Sending 'abl_b' (1996 KB) OKAY [ 0.057s]
Writing 'abl_b' OKAY [ 0.028s]
Finished. Total time: 0.093s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash aop aop.img
Sending 'aop_b' (176 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.020s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash bluetooth bluetooth.img
Sending 'bluetooth_b' (220 KB) OKAY [ 0.007s]
Writing 'bluetooth_b' OKAY [ 0.008s]
Finished. Total time: 0.021s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash devcfg devcfg.img
Sending 'devcfg_b' (44 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.005s]
Finished. Total time: 0.014s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash dsp dsp.img
Sending 'dsp_b' (65536 KB) OKAY [ 1.618s]
Writing 'dsp_b' OKAY [ 0.531s]
Finished. Total time: 2.153s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash featenabler featenabler.img
Sending 'featenabler_b' (88 KB) OKAY [ 0.003s]
Writing 'featenabler_b' OKAY [ 0.006s]
Finished. Total time: 0.014s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash hyp hyp.img
Sending 'hyp_b' (396 KB) OKAY [ 0.011s]
Writing 'hyp_b' OKAY [ 0.010s]
Finished. Total time: 0.025s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash imagefv imagefv.img
Sending 'imagefv_b' (524 KB) OKAY [ 0.017s]
Writing 'imagefv_b' OKAY [ 0.012s]
Finished. Total time: 0.036s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash keymaster keymaster.img
Sending 'keymaster_b' (232 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.008s]
Finished. Total time: 0.022s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash logo logo.img
fastboot: error: cannot load 'logo.img': No such file or directory
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash oem_stanvbk oem_stanvbk.img
Sending 'oem_stanvbk' (2920 KB) OKAY [ 0.078s]
Writing 'oem_stanvbk' OKAY [ 0.038s]
Finished. Total time: 0.123s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash odm odm.img
Resizing 'odm_b' OKAY [ 0.004s]
Sending 'odm_b' (968 KB) OKAY [ 0.027s]
Writing 'odm_b' OKAY [ 0.293s]
Finished. Total time: 0.331s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash qupfw qupfw.img
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.005s]
Finished. Total time: 0.012s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash storsec storsec.img
Sending 'storsec_b' (20 KB) OKAY [ 0.001s]
Writing 'storsec_b' OKAY [ 0.005s]
Finished. Total time: 0.013s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash tz tz.img
Sending 'tz_b' (2960 KB) OKAY [ 0.076s]
Writing 'tz_b' OKAY [ 0.038s]
Finished. Total time: 0.120s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash uefisecapp uefisecapp.img
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.018s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash xbl xbl.img
Sending 'xbl_b' (3296 KB) OKAY [ 0.083s]
Writing 'xbl_b' OKAY [ 1.794s]
Finished. Total time: 1.884s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash xbl_config xbl_config.img
Sending 'xbl_config_b' (96 KB) OKAY [ 0.003s]
Writing 'xbl_config_b' OKAY [ 0.029s]
Finished. Total time: 0.040s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash system system.img
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/4 (523001 KB) OKAY [ 12.780s]
Writing 'system_b' OKAY [ 3.391s]
Sending sparse 'system_b' 2/4 (520279 KB) OKAY [ 12.756s]
Writing 'system_b' OKAY [ 3.428s]
Sending sparse 'system_b' 3/4 (523321 KB) OKAY [ 12.786s]
Writing 'system_b' OKAY [ 3.450s]
Sending sparse 'system_b' 4/4 (450188 KB) OKAY [ 11.003s]
Writing 'system_b' OKAY [ 3.045s]
Finished. Total time: 62.944s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash vendor vendor.img
Invalid sparse file format at header magic
Resizing 'vendor_b' OKAY [ 0.003s]
Sending sparse 'vendor_b' 1/3 (523167 KB) OKAY [ 12.819s]
Writing 'vendor_b' OKAY [ 3.502s]
Sending sparse 'vendor_b' 2/3 (510001 KB) OKAY [ 12.478s]
Writing 'vendor_b' OKAY [ 3.398s]
Sending sparse 'vendor_b' 3/3 (291316 KB) OKAY [ 7.133s]
Writing 'vendor_b' OKAY [ 2.147s]
Finished. Total time: 41.657s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash product product.img
Invalid sparse file format at header magic
Resizing 'product_b' OKAY [ 0.003s]
Sending sparse 'product_b' 1/4 (522958 KB) OKAY [ 12.807s]
Writing 'product_b' OKAY [ 3.412s]
Sending sparse 'product_b' 2/4 (523010 KB) OKAY [ 12.818s]
Writing 'product_b' OKAY [ 3.418s]
Sending sparse 'product_b' 3/4 (520218 KB) OKAY [ 12.759s]
Writing 'product_b' OKAY [ 3.440s]
Sending sparse 'product_b' 4/4 (235736 KB) OKAY [ 5.795s]
Writing 'product_b' OKAY [ 1.825s]
Finished. Total time: 56.543s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.051s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $

powergo said:
Any way to do it in Linux ? i mean script to do all, i know about
extracting zip to fastboot all like
Code:
[email protected] ~/Downloads/extract_android_ota_payload-master $ python extract_android_ota_payload.py OnePlusN10Oxygen_14.E.09_OTA_009_all_2101021731_9c32820c43e443f1.zip 1/
Extracting 'payload.bin' from OTA file...
Extracting 'abl.img'
Extracting 'boot.img'
Extracting 'dtbo.img'
Extracting 'odm.img'
Extracting 'product.img'
Extracting 'recovery.img'
Extracting 'system.img'
Extracting 'vbmeta.img'
Extracting 'vbmeta_system.img'
Extracting 'vendor.img'
Extracting 'aop.img'
Extracting 'bluetooth.img'
Extracting 'devcfg.img'
Extracting 'dsp.img'
Extracting 'featenabler.img'
Extracting 'hyp.img'
Extracting 'imagefv.img'
Extracting 'keymaster.img'
Extracting 'modem.img'
Extracting 'qupfw.img'
Extracting 'storsec.img'
Extracting 'tz.img'
Extracting 'uefisecapp.img'
Extracting 'xbl_config.img'
Extracting 'xbl.img'
Extracting 'oem_stanvbk.img'
(n):cry:[email protected] ~/Downloads/extract_android_ota_payload-master $ cd 1
abl.img dtbo.img odm.img storsec.img vendor.img
aop.img featenabler.img oem_stanvbk.img system.img xbl_config.img
bluetooth.img hyp.img payload.bin tz.img xbl.img
boot.img imagefv.img product.img uefisecapp.img
devcfg.img keymaster.img qupfw.img vbmeta.img
dsp.img modem.img recovery.img vbmeta_system.img
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash boot boot.img
< waiting for any device >
Sending 'boot_b' (98304 KB) OKAY [ 2.314s]
Writing 'boot_b' OKAY [ 1.953s]
Finished. Total time: 4.279s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (782003 KB) OKAY [ 18.506s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.822s]
Finished. Total time: 0.828s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot erase cache
Erasing 'cache' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot -w
Erasing 'userdata' OKAY [ 0.801s]
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.318s]
Writing 'boot_b' OKAY [ 1.885s]
Finished. Total time: 4.217s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.195s]
Writing 'dtbo' OKAY [ 0.188s]
Finished. Total time: 0.391s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash modem modem.img
Sending 'modem_b' (152332 KB) OKAY [ 3.607s]
Writing 'modem_b' OKAY [ 2.974s]
Finished. Total time: 6.590s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 2.412s]
Writing 'recovery' OKAY [ 2.023s]
Finished. Total time: 4.455s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 9.477s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash abl abl.img
Sending 'abl_b' (1996 KB) OKAY [ 0.057s]
Writing 'abl_b' OKAY [ 0.028s]
Finished. Total time: 0.093s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash aop aop.img
Sending 'aop_b' (176 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.020s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash bluetooth bluetooth.img
Sending 'bluetooth_b' (220 KB) OKAY [ 0.007s]
Writing 'bluetooth_b' OKAY [ 0.008s]
Finished. Total time: 0.021s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash devcfg devcfg.img
Sending 'devcfg_b' (44 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.005s]
Finished. Total time: 0.014s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash dsp dsp.img
Sending 'dsp_b' (65536 KB) OKAY [ 1.618s]
Writing 'dsp_b' OKAY [ 0.531s]
Finished. Total time: 2.153s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash featenabler featenabler.img
Sending 'featenabler_b' (88 KB) OKAY [ 0.003s]
Writing 'featenabler_b' OKAY [ 0.006s]
Finished. Total time: 0.014s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash hyp hyp.img
Sending 'hyp_b' (396 KB) OKAY [ 0.011s]
Writing 'hyp_b' OKAY [ 0.010s]
Finished. Total time: 0.025s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash imagefv imagefv.img
Sending 'imagefv_b' (524 KB) OKAY [ 0.017s]
Writing 'imagefv_b' OKAY [ 0.012s]
Finished. Total time: 0.036s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash keymaster keymaster.img
Sending 'keymaster_b' (232 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.008s]
Finished. Total time: 0.022s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash logo logo.img
fastboot: error: cannot load 'logo.img': No such file or directory
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash oem_stanvbk oem_stanvbk.img
Sending 'oem_stanvbk' (2920 KB) OKAY [ 0.078s]
Writing 'oem_stanvbk' OKAY [ 0.038s]
Finished. Total time: 0.123s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash odm odm.img
Resizing 'odm_b' OKAY [ 0.004s]
Sending 'odm_b' (968 KB) OKAY [ 0.027s]
Writing 'odm_b' OKAY [ 0.293s]
Finished. Total time: 0.331s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash qupfw qupfw.img
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.005s]
Finished. Total time: 0.012s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash storsec storsec.img
Sending 'storsec_b' (20 KB) OKAY [ 0.001s]
Writing 'storsec_b' OKAY [ 0.005s]
Finished. Total time: 0.013s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash tz tz.img
Sending 'tz_b' (2960 KB) OKAY [ 0.076s]
Writing 'tz_b' OKAY [ 0.038s]
Finished. Total time: 0.120s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash uefisecapp uefisecapp.img
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.018s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash xbl xbl.img
Sending 'xbl_b' (3296 KB) OKAY [ 0.083s]
Writing 'xbl_b' OKAY [ 1.794s]
Finished. Total time: 1.884s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash xbl_config xbl_config.img
Sending 'xbl_config_b' (96 KB) OKAY [ 0.003s]
Writing 'xbl_config_b' OKAY [ 0.029s]
Finished. Total time: 0.040s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash system system.img
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/4 (523001 KB) OKAY [ 12.780s]
Writing 'system_b' OKAY [ 3.391s]
Sending sparse 'system_b' 2/4 (520279 KB) OKAY [ 12.756s]
Writing 'system_b' OKAY [ 3.428s]
Sending sparse 'system_b' 3/4 (523321 KB) OKAY [ 12.786s]
Writing 'system_b' OKAY [ 3.450s]
Sending sparse 'system_b' 4/4 (450188 KB) OKAY [ 11.003s]
Writing 'system_b' OKAY [ 3.045s]
Finished. Total time: 62.944s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash vendor vendor.img
Invalid sparse file format at header magic
Resizing 'vendor_b' OKAY [ 0.003s]
Sending sparse 'vendor_b' 1/3 (523167 KB) OKAY [ 12.819s]
Writing 'vendor_b' OKAY [ 3.502s]
Sending sparse 'vendor_b' 2/3 (510001 KB) OKAY [ 12.478s]
Writing 'vendor_b' OKAY [ 3.398s]
Sending sparse 'vendor_b' 3/3 (291316 KB) OKAY [ 7.133s]
Writing 'vendor_b' OKAY [ 2.147s]
Finished. Total time: 41.657s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash product product.img
Invalid sparse file format at header magic
Resizing 'product_b' OKAY [ 0.003s]
Sending sparse 'product_b' 1/4 (522958 KB) OKAY [ 12.807s]
Writing 'product_b' OKAY [ 3.412s]
Sending sparse 'product_b' 2/4 (523010 KB) OKAY [ 12.818s]
Writing 'product_b' OKAY [ 3.418s]
Sending sparse 'product_b' 3/4 (520218 KB) OKAY [ 12.759s]
Writing 'product_b' OKAY [ 3.440s]
Sending sparse 'product_b' 4/4 (235736 KB) OKAY [ 5.795s]
Writing 'product_b' OKAY [ 1.825s]
Finished. Total time: 56.543s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.051s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $
Click to expand...
Click to collapse
No, as said in OP this tool is Windows only.
It is not a GUI for fastboot, it uses Qualcomm EDL mode to flash your device like at factory.

Related

Update 7.1.1 Rooted XL to 7.1.2 Without Losing Data?

Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
tryfont said:
Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
Click to expand...
Click to collapse
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the​ instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
SOLVED
TonikJDK said:
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the​ instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I'm on a mac, not sure how to do the last step with running the .bat file
Edit: went into the bat file and ran the equivalent commands in terminal
(fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-marlin-n2g47e.zip)
Here is the terminal messages I got
Last login: Mon Apr 3 18:00:13 on ttys000
Tryfons-MBP:~ tryfon$ cd /Users/tryfon/Desktop/platform-tools
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.811s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.163s]
finished. total time: 4.974s
Tryfons-MBPlatform-tools tryfon$ fastboot reboot-bootloader
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
Tryfons-MBPlatform-tools tryfon$ fastboot flash radio radio-marlin-8996-012901-1702171013.img
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash radio radio-marlin-8996-012901-1702171013.img
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.444s]
writing 'radio_b'...
OKAY [ 0.704s]
finished. total time: 2.148s
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
Tryfons-MBPlatform-tools tryfon$ ./fastboot update image-marlin-n2g47e.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: 8996-012001-1702151126
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT72A0200395
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_b' (25997 KB)...
OKAY [ 0.701s]
writing 'boot_b'...
OKAY [ 0.260s]
erasing 'system_b'...
OKAY [ 0.457s]
sending sparse 'system_b' 1/4 (514854 KB)...
OKAY [ 14.106s]
writing 'system_b' 1/4...
OKAY [ 6.005s]
sending sparse 'system_b' 2/4 (524140 KB)...
OKAY [ 14.606s]
writing 'system_b' 2/4...
OKAY [ 4.937s]
sending sparse 'system_b' 3/4 (512784 KB)...
OKAY [ 14.072s]
writing 'system_b' 3/4...
OKAY [ 6.243s]
sending sparse 'system_b' 4/4 (32756 KB)...
OKAY [ 0.905s]
writing 'system_b' 4/4...
OKAY [ 0.297s]
erasing 'system_a'...
OKAY [ 0.411s]
sending sparse 'system_a' 1/4 (520579 KB)...
OKAY [ 13.904s]
writing 'system_a' 1/4...
OKAY [ 3.787s]
sending sparse 'system_a' 2/4 (521193 KB)...
OKAY [ 13.721s]
writing 'system_a' 2/4...
OKAY [ 4.103s]
sending sparse 'system_a' 3/4 (510216 KB)...
OKAY [ 14.206s]
writing 'system_a' 3/4...
OKAY [ 3.788s]
sending sparse 'system_a' 4/4 (128745 KB)...
OKAY [ 3.513s]
writing 'system_a' 4/4...
OKAY [ 1.049s]
erasing 'vendor_b'...
OKAY [ 0.154s]
sending 'vendor_b' (242238 KB)...
OKAY [ 6.003s]
writing 'vendor_b'...
OKAY [ 3.653s]
Setting current slot to 'b'...
OKAY [ 0.087s]
rebooting...
finished. total time: 131.364s
Tryfons-MBPlatform-tools tryfon$
Everything turned out fine!!!

FAILED (remote: 'Chunk data size exceeds partition size') when flashing system.img

Hi, guys.
I couldn't install update 10.0.3.0 after restoring boot.img from Magisk.
So, I flash boot.img in fastboot but still cannot.
And then I found out maybe because Substratum modified system.img
Then I tried to flash 10.0.2.0 system.img using this command:
Code:
fastboot flash system_a system_10.0.2.0.img
and this error shown:
Code:
Sending sparse 'system_a' 1/3 (462332 KB) OKAY [ 10.736s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Chunk data size exceeds partition size')
Finished. Total time: 30.924s
I also tried these 2 commands get from this solution:
Code:
fastboot flash -S 256M system_a system_10.0.2.0.img
fastboot flash -S 128M system_a system_10.0.2.0.img
but same error.
Any help is appreciated.
current-slot:
Code:
D:\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
Sorry guys, problem solved.
I don't know what happened, my phone suddenly stuck in bootloop?
no animation just black screen, increase brightness to 100 then drop to 0 then increase to 100 and cycle.
then I boot into fastboot and try flash again
Code:
D:\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.012s
D:\platform-tools>fastboot flash boot_a boot_10.0.2.0.img
Sending 'boot_a' (27219 KB) OKAY [ 0.633s]
Writing 'boot_a' OKAY [ 0.339s]
Finished. Total time: 0.996s
D:\platform-tools>fastboot flash system_a system_10.0.2.0.img
Sending sparse 'system_a' 1/4 (522236 KB) OKAY [ 17.728s]
Writing sparse 'system_a' 1/4 OKAY [ 5.516s]
Sending sparse 'system_a' 2/4 (522236 KB) OKAY [ 17.947s]
Writing sparse 'system_a' 2/4 OKAY [ 5.576s]
Sending sparse 'system_a' 3/4 (522236 KB) OKAY [ 17.854s]
Writing sparse 'system_a' 3/4 OKAY [ 5.629s]
Sending sparse 'system_a' 4/4 (447916 KB) OKAY [ 15.042s]
Writing sparse 'system_a' 4/4 OKAY [ 4.804s]
Finished. Total time: 148.451s
D:\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.012s
now the system.img split into 522.236 MB instead of 462.332 MB and got 4 parts instead of 3?
wtf is happening!
Anyway, the updated is installed successfully.

Bwaaahhhhhahhaha soft brick

Trying to flash to updated to android 10... Used deuces scrips, used factory script, used 10 different ota image files, several different programs like winzip/winrar etc.... Keep getting stuck wtih your device is corrupt... Any suggestions? Lemme know anything you need to know cause right now i'm f'd
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?n
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' OKAY [ 0.016s]
Finished. Total time: 0.021s
Sending 'bootloader_a' (36356 KB) OKAY [ 0.836s]
Writing 'bootloader_a' OKAY [ 0.293s]
Finished. Total time: 1.416s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
Sending 'radio_a' (60372 KB) OKAY [ 1.583s]
Writing 'radio_a' OKAY [ 0.817s]
Finished. Total time: 3.026s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.003s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' OKAY [ 0.016s]
Finished. Total time: 0.022s
Sending 'bootloader_b' (36356 KB) OKAY [ 0.936s]
Writing 'bootloader_b' OKAY [ 0.266s]
Finished. Total time: 1.778s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
Sending 'radio_b' (60372 KB) OKAY [ 1.303s]
Writing 'radio_b' OKAY [ 0.828s]
Finished. Total time: 2.221s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.003s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' OKAY [ 0.016s]
Finished. Total time: 0.020s
Sending 'abl_a' (540 KB) OKAY [ 0.012s]
Writing 'abl_a' OKAY [ 0.009s]
Finished. Total time: 0.037s
Sending 'aes_a' (48 KB) OKAY [ 0.002s]
Writing 'aes_a' OKAY [ 0.004s]
Finished. Total time: 0.017s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_a' (40960 KB) OKAY [ 0.884s]
Writing 'boot_a' OKAY [ 0.377s]
Finished. Total time: 1.326s
Sending 'cmnlib_a' (224 KB) OKAY [ 0.005s]
Writing 'cmnlib_a' OKAY [ 0.022s]
Finished. Total time: 0.041s
Sending 'cmnlib64_a' (296 KB) OKAY [ 0.007s]
Writing 'cmnlib64_a' OKAY [ 0.024s]
Finished. Total time: 0.044s
Sending 'devcfg_a' (60 KB) OKAY [ 0.002s]
Writing 'devcfg_a' OKAY [ 0.015s]
Finished. Total time: 0.031s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.178s]
Writing 'dtbo_a' OKAY [ 0.284s]
Finished. Total time: 0.484s
Sending 'hyp_a' (264 KB) OKAY [ 0.006s]
Writing 'hyp_a' OKAY [ 0.017s]
Finished. Total time: 0.036s
Sending 'keymaster_a' (312 KB) OKAY [ 0.007s]
Writing 'keymaster_a' OKAY [ 0.006s]
Finished. Total time: 0.028s
Sending 'laf_a' (29800 KB) OKAY [ 0.681s]
Writing 'laf_a' OKAY [ 0.130s]
Finished. Total time: 0.874s
Sending 'modem_a' (60364 KB) OKAY [ 1.383s]
Writing 'modem_a' OKAY [ 1.303s]
Finished. Total time: 2.790s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_a' (52 KB) OKAY [ 0.001s]
Writing 'pmic_a' OKAY [ 0.004s]
Finished. Total time: 0.019s
Sending 'rpm_a' (232 KB) OKAY [ 0.005s]
Writing 'rpm_a' OKAY [ 0.006s]
Finished. Total time: 0.026s
Sending 'tz_a' (1868 KB) OKAY [ 0.041s]
Writing 'tz_a' OKAY [ 0.013s]
Finished. Total time: 0.070s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.018s
Sending 'vendor_a' (360032 KB) OKAY [ 8.197s]
Writing 'vendor_a' OKAY [ 1.520s]
Finished. Total time: 9.923s
Sending 'xbl_a' (2624 KB) OKAY [ 0.058s]
Writing 'xbl_a' OKAY [ 0.020s]
Finished. Total time: 0.094s
Flashing System A
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 11.730s]
Writing 'system_a' OKAY [ 2.231s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 11.741s]
Writing 'system_a' OKAY [ 2.222s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 11.837s]
Writing 'system_a' OKAY [ 2.215s]
Sending sparse 'system_a' 4/5 (521180 KB) OKAY [ 11.666s]
Writing 'system_a' OKAY [ 2.204s]
Sending sparse 'system_a' 5/5 (186148 KB) OKAY [ 4.158s]
Writing 'system_a' OKAY [ 0.783s]
Finished. Total time: 66.619s
Flashing System B
Sending 'system_b' (329560 KB) OKAY [ 7.172s]
Writing 'system_b' OKAY [ 1.396s]
Finished. Total time: 8.774s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' OKAY [ 0.012s]
Finished. Total time: 0.018s
Sending 'abl_b' (540 KB) OKAY [ 0.012s]
Writing 'abl_b' OKAY [ 0.009s]
Finished. Total time: 0.034s
Sending 'aes_b' (48 KB) OKAY [ 0.001s]
Writing 'aes_b' OKAY [ 0.003s]
Finished. Total time: 0.014s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_b' (40960 KB) OKAY [ 0.898s]
Writing 'boot_b' OKAY [ 0.975s]
Finished. Total time: 4.287s
Sending 'cmnlib_b' (224 KB) OKAY [ 0.005s]
Writing 'cmnlib_b' OKAY [ 0.011s]
Finished. Total time: 0.028s
Sending 'cmnlib64_b' (296 KB) OKAY [ 0.006s]
Writing 'cmnlib64_b' OKAY [ 0.037s]
Finished. Total time: 0.059s
Sending 'devcfg_b' (60 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.009s]
Finished. Total time: 0.021s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.188s]
Writing 'dtbo_b' OKAY [ 0.317s]
Finished. Total time: 1.015s
Sending 'hyp_b' (264 KB) OKAY [ 0.006s]
Writing 'hyp_b' OKAY [ 0.013s]
Finished. Total time: 0.030s
Sending 'keymaster_b' (312 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.029s]
Finished. Total time: 0.051s
Sending 'laf_b' (29800 KB) OKAY [ 0.662s]
Writing 'laf_b' OKAY [ 0.186s]
Finished. Total time: 3.118s
Sending 'modem_b' (60364 KB) OKAY [ 1.325s]
Writing 'modem_b' OKAY [ 0.812s]
Finished. Total time: 5.371s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_b' (52 KB) OKAY [ 0.002s]
Writing 'pmic_b' OKAY [ 0.004s]
Finished. Total time: 0.015s
Sending 'rpm_b' (232 KB) OKAY [ 0.005s]
Writing 'rpm_b' OKAY [ 0.007s]
Finished. Total time: 0.024s
Sending 'tz_b' (1868 KB) OKAY [ 0.041s]
Writing 'tz_b' OKAY [ 0.014s]
Finished. Total time: 0.082s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
Finished. Total time: 0.013s
Sending 'vendor_b' (360032 KB) OKAY [ 8.128s]
Writing 'vendor_b' OKAY [ 1.541s]
Finished. Total time: 11.953s
Sending 'xbl_b' (2624 KB) OKAY [ 0.062s]
Writing 'xbl_b' OKAY [ 0.050s]
Finished. Total time: 0.163s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' OKAY [ 0.013s]
Finished. Total time: 0.022s
Format Userdata[Y/N]?
What's the problem?
Download stock firmware from Google. Then run
flash-all.sh on Mac
flash-all.bat on Windows.
krabban said:
What's the problem?
Download stock firmware from Google. Then run
flash-all.sh on Mac
flash-all.bat on Windows.
Click to expand...
Click to collapse
I did... Download factory images from google... Did flash-all.bat as well as deuces, both give me the same result
Zooandbio4me said:
I did... Download factory images from google... Did flash-all.bat as well as deuces, both give me the same result
Click to expand...
Click to collapse
Tried format data ?
You'll need to select "Y" when the prompt to format userdata comes up. Formatting the internal storage is I believe the only way to resolve the device corruption issue. A much easier way to go than by using a script is to simply download a factory image (NOT AN OTA), unzip it and run the flash-all command. Deuces should only be used as a weapon of last resort.
I had issues using win zip. 7zipper works though.
In case you were unaware, do not unzip the folder inside. Flash all looks for that zip file and extracts it automatically.
Larzzzz82 said:
I had issues using win zip. 7zipper works though.
In case you were unaware, do not unzip the folder inside. Flash all looks for that zip file and extracts it automatically.
Click to expand...
Click to collapse
WinZip has had problems for some time now, so I mostly use WinRAR, although I have 7-Zip on my PortableApps flash drive.
Strephon Alkhalikoi said:
WinZip has had problems for some time now, so I mostly use WinRAR, although I have 7-Zip on my PortableApps flash drive.
Click to expand...
Click to collapse
This is my ammo too!! Never fails...
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
This is my ammo too!! Never fails...
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Yeah I only used 7zip as a means to rule out potential problems
Fastboot boot twrp
Format data and flash/adbsideload the OTA and TWRP installer zip in twrp. I use a type c thumbdrive, mount it in twrp and flash **** from there

Image signed with bad key trying to flash stock firmware (boot.img, recovery.img)

I'm trying to relock the bootloader on my Moto G5s coming back after a hardbrick. I have the BC.12 (2018-06-26) bootloader and I've tried a dozen different firmwares. All have the same problem when flashing boot and recovery images.
Code:
D:\www.stockrom.net_MONTANA_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory_NO_ERASE_CFC.xml>fastboot flash boot boot.img
Sending 'boot' (16384 KB) OKAY [ 0.519s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.380s]
Finished. Total time: 0.907s
D:\www.stockrom.net_MONTANA_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory_NO_ERASE_CFC.xml>fastboot flash recovery recovery.img
Sending 'recovery' (16484 KB) OKAY [ 0.522s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.411s]
Finished. Total time: 0.944s
All of the other images flash fine, and the phone does boot, but it won't let me relock the bootloader due to the images not being signed. Is there any way of fixing this or am I doomed and stuck with an unlocked phone?
Same Problem here, anyone a idea to fix?
okay, i finally found a solution after 2 days of fighting haha
so, here's what you need to do:
download the latest firmware (link)
then flash it with the usual method but without flashing partition and bootloader images
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot fb_mode clear
and then do:
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash boot boot.img
fastboot oem lock
this worked for me on xt1794
THX A LOT!!! This really helped!
It didn't work. What else can I do?
Code:
E:\moto\fb>fastboot oem fb_mode_set
...
OKAY [ 0.004s]
finished. total time: 0.004s
E:\moto\fb>fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2195 KB)...
OKAY [ 0.071s]
writing 'logo'...
OKAY [ 0.106s]
finished. total time: 0.180s
E:\moto\fb>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.382s]
finished. total time: 0.901s
E:\moto\fb>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.522s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.413s]
finished. total time: 0.938s
E:\moto\fb>fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (67978 KB)...
OKAY [ 2.141s]
writing 'modem'...
OKAY [ 1.078s]
finished. total time: 3.222s
E:\moto\fb>fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (3560 KB)...
OKAY [ 0.114s]
writing 'fsg'...
OKAY [ 0.125s]
finished. total time: 0.241s
E:\moto\fb>fastboot flash dsp adspso.bin
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.518s]
writing 'dsp'...
OKAY [ 0.283s]
finished. total time: 0.802s
E:\moto\fb>fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (135426 KB)...
OKAY [ 4.263s]
writing 'oem'...
OKAY [ 1.828s]
finished. total time: 6.093s
E:\moto\fb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (256294 KB)...
OKAY [ 8.065s]
writing 'system'...
OKAY [ 4.087s]
finished. total time: 15.253s
E:\moto\fb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256762 KB)...
OKAY [ 8.633s]
writing 'system'...
OKAY [ 3.316s]
finished. total time: 11.953s
E:\moto\fb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (255764 KB)...
OKAY [ 8.597s]
writing 'system'...
OKAY [ 3.545s]
finished. total time: 12.145s
E:\moto\fb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (260630 KB)...
OKAY [ 8.759s]
writing 'system'...
OKAY [ 3.389s]
finished. total time: 12.150s
E:\moto\fb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (257521 KB)...
OKAY [ 8.661s]
writing 'system'...
OKAY [ 3.360s]
finished. total time: 12.023s
E:\moto\fb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (245941 KB)...
OKAY [ 8.264s]
writing 'system'...
OKAY [ 3.176s]
finished. total time: 11.442s
E:\moto\fb>fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (258569 KB)...
OKAY [ 8.685s]
writing 'system'...
OKAY [ 3.244s]
finished. total time: 11.931s
E:\moto\fb>fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (251493 KB)...
OKAY [ 8.456s]
writing 'system'...
OKAY [ 3.680s]
finished. total time: 12.139s
E:\moto\fb>fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (257933 KB)...
OKAY [ 8.666s]
writing 'system'...
OKAY [ 3.741s]
finished. total time: 12.408s
E:\moto\fb>fastboot flash system system.img_sparsechunk.9
target reported max download size of 535822336 bytes
sending 'system' (214096 KB)...
OKAY [ 7.202s]
writing 'system'...
OKAY [ 2.700s]
finished. total time: 9.905s
E:\moto\fb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.021s
E:\moto\fb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.248s]
finished. total time: 0.250s
E:\moto\fb>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.002s]
finished. total time: 0.004s
E:\moto\fb>fastboot fb_mode clear
fastboot: usage: unknown command fb_mode
E:\moto\fb>fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.006s]
finished. total time: 0.006s
E:\moto\fb>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.007s]
finished. total time: 0.008s
E:\moto\fb>fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (135426 KB)...
OKAY [ 4.263s]
writing 'oem'...
OKAY [ 1.814s]
finished. total time: 6.079s
E:\moto\fb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (256294 KB)...
OKAY [ 8.066s]
writing 'system'...
OKAY [ 4.092s]
finished. total time: 12.161s
E:\moto\fb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256762 KB)...
OKAY [ 8.078s]
writing 'system'...
OKAY [ 3.292s]
finished. total time: 11.372s
E:\moto\fb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (255764 KB)...
OKAY [ 8.046s]
writing 'system'...
OKAY [ 3.500s]
finished. total time: 11.547s
E:\moto\fb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (260630 KB)...
OKAY [ 8.199s]
writing 'system'...
OKAY [ 3.394s]
finished. total time: 11.595s
E:\moto\fb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (257521 KB)...
OKAY [ 8.103s]
writing 'system'...
OKAY [ 3.348s]
finished. total time: 11.451s
E:\moto\fb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (245941 KB)...
OKAY [ 7.738s]
writing 'system'...
OKAY [ 3.185s]
finished. total time: 10.924s
E:\moto\fb>fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (258569 KB)...
OKAY [ 8.135s]
writing 'system'...
OKAY [ 3.250s]
finished. total time: 11.387s
E:\moto\fb>fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (251493 KB)...
OKAY [ 7.914s]
writing 'system'...
OKAY [ 3.677s]
finished. total time: 11.592s
E:\moto\fb>fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (257933 KB)...
OKAY [ 8.115s]
writing 'system'...
OKAY [ 3.724s]
finished. total time: 11.842s
E:\moto\fb>fastboot flash system system.img_sparsechunk.9
target reported max download size of 535822336 bytes
sending 'system' (214096 KB)...
OKAY [ 6.737s]
writing 'system'...
OKAY [ 2.693s]
finished. total time: 9.432s
E:\moto\fb>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.517s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.374s]
finished. total time: 0.893s
E:\moto\fb>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.005s

Fastboot can't flash boot with any img

I was using phh-treble gsi before and I always has been unable to flash anything to boot partition. Today I am trying to flash the factory image, and it also failed at flashing boot. But now because it also flashed to other parition, my phone cannot boot anymore. Tried the official oreo and pie image, both the same thing. Also tried flashing lineage recovery, also failed.
The error message is either
Code:
FAILED (Write to device failed (Invalid argument))
or
Code:
FAILED (Status read failed (Too many links))
.
I tried using different platform tools, including the ones provided by lineage tutorial, and this one [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows. Same thing. I also tried using Linux and using other cables and using USB2.0 and 3.0 ports. Nothing helps so far.
Full log flashing the official android pie firmware
Code:
D:\cheryl-pie>flash_all.bat
D:\cheryl-pie>set fastboot_cmd=fastboot
D:\cheryl-pie>fastboot flash partition:0 gpt_both0.bin
< waiting for any device >
Sending 'partition:0' (44 KB) OKAY [ 0.002s]
Writing 'partition:0' OKAY [ 0.085s]
Finished. Total time: 0.098s
D:\cheryl-pie>fastboot flash partition:1 gpt_both1.bin
Sending 'partition:1' (44 KB) OKAY [ 0.001s]
Writing 'partition:1' OKAY [ 0.100s]
Finished. Total time: 0.121s
D:\cheryl-pie>fastboot flash partition:2 gpt_both2.bin
Sending 'partition:2' (44 KB) OKAY [ 0.001s]
Writing 'partition:2' OKAY [ 0.096s]
Finished. Total time: 0.113s
D:\cheryl-pie>fastboot flash partition:3 gpt_both3.bin
Sending 'partition:3' (44 KB) OKAY [ 0.002s]
Writing 'partition:3' OKAY [ 0.088s]
Finished. Total time: 0.107s
D:\cheryl-pie>fastboot flash partition:4 gpt_both4.bin
Sending 'partition:4' (44 KB) OKAY [ 0.001s]
Writing 'partition:4' OKAY [ 0.100s]
Finished. Total time: 0.125s
D:\cheryl-pie>fastboot flash partition:5 gpt_both5.bin
Sending 'partition:5' (44 KB) OKAY [ 0.002s]
Writing 'partition:5' OKAY [ 0.170s]
Finished. Total time: 0.188s
D:\cheryl-pie>fastboot flash xbl_a xbl.img
Sending 'xbl_a' (2629 KB) OKAY [ 0.074s]
Writing 'xbl_a' OKAY [ 0.015s]
Finished. Total time: 0.104s
D:\cheryl-pie>fastboot flash xbl_b xbl.img
Sending 'xbl_b' (2629 KB) OKAY [ 0.066s]
Writing 'xbl_b' OKAY [ 0.036s]
Finished. Total time: 0.112s
D:\cheryl-pie>fastboot flash tz_a tz.img
Sending 'tz_a' (1868 KB) OKAY [ 0.054s]
Writing 'tz_a' OKAY [ 0.017s]
Finished. Total time: 0.086s
D:\cheryl-pie>fastboot flash tz_b tz.img
Sending 'tz_b' (1868 KB) OKAY [ 0.047s]
Writing 'tz_b' OKAY [ 0.017s]
Finished. Total time: 0.073s
D:\cheryl-pie>fastboot flash rpm_a rpm.img
Sending 'rpm_a' (228 KB) OKAY [ 0.008s]
Writing 'rpm_a' OKAY [ 0.003s]
Finished. Total time: 0.028s
D:\cheryl-pie>fastboot flash rpm_b rpm.img
Sending 'rpm_b' (228 KB) OKAY [ 0.006s]
Writing 'rpm_b' OKAY [ 0.004s]
Finished. Total time: 0.018s
D:\cheryl-pie>fastboot flash hyp_a hyp.img
Sending 'hyp_a' (264 KB) OKAY [ 0.008s]
Writing 'hyp_a' OKAY [ 0.003s]
Finished. Total time: 0.027s
D:\cheryl-pie>fastboot flash hyp_b hyp.img
Sending 'hyp_b' (264 KB) OKAY [ 0.007s]
Writing 'hyp_b' OKAY [ 0.005s]
Finished. Total time: 0.021s
D:\cheryl-pie>fastboot flash pmic_a pmic.img
fastboot: error: cannot load 'pmic.img': No such file or directory
D:\cheryl-pie>fastboot flash pmic_b pmic.img
fastboot: error: cannot load 'pmic.img': No such file or directory
D:\cheryl-pie>fastboot flash keymaster_a keymaster.img
Sending 'keymaster_a' (373 KB) OKAY [ 0.011s]
Writing 'keymaster_a' OKAY [ 0.006s]
Finished. Total time: 0.034s
D:\cheryl-pie>fastboot flash keymaster_b keymaster.img
Sending 'keymaster_b' (373 KB) OKAY [ 0.009s]
Writing 'keymaster_b' OKAY [ 0.003s]
Finished. Total time: 0.021s
D:\cheryl-pie>fastboot flash cmnlib_a cmnlib.img
Sending 'cmnlib_a' (221 KB) OKAY [ 0.007s]
Writing 'cmnlib_a' OKAY [ 0.005s]
Finished. Total time: 0.028s
D:\cheryl-pie>fastboot flash cmnlib_b cmnlib.img
Sending 'cmnlib_b' (221 KB) OKAY [ 0.006s]
Writing 'cmnlib_b' OKAY [ 0.002s]
Finished. Total time: 0.017s
D:\cheryl-pie>fastboot flash cmnlib64_a cmnlib64.img
Sending 'cmnlib64_a' (292 KB) OKAY [ 0.009s]
Writing 'cmnlib64_a' OKAY [ 0.005s]
Finished. Total time: 0.031s
D:\cheryl-pie>fastboot flash cmnlib64_b cmnlib64.img
Sending 'cmnlib64_b' (292 KB) OKAY [ 0.008s]
Writing 'cmnlib64_b' OKAY [ 0.003s]
Finished. Total time: 0.020s
D:\cheryl-pie>fastboot flash devcfg_a devcfg.img
Sending 'devcfg_a' (56 KB) OKAY [ 0.002s]
Writing 'devcfg_a' OKAY [ 0.002s]
Finished. Total time: 0.020s
D:\cheryl-pie>fastboot flash devcfg_b devcfg.img
Sending 'devcfg_b' (56 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.001s]
Finished. Total time: 0.012s
D:\cheryl-pie>fastboot flash abl_a abl.img
Sending 'abl_a' (204 KB) OKAY [ 0.007s]
Writing 'abl_a' OKAY [ 0.004s]
Finished. Total time: 0.028s
D:\cheryl-pie>fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.003s
D:\cheryl-pie>timeout /t 10
Waiting for 0 seconds, press a key to continue ...
D:\cheryl-pie>fastboot flash abl_b abl.img
< waiting for any device >
Sending 'abl_b' (204 KB) OKAY [ 0.006s]
Writing 'abl_b' OKAY [ 0.003s]
Finished. Total time: 0.018s
D:\cheryl-pie>fastboot erase ddr
Erasing 'ddr' OKAY [ 0.114s]
Finished. Total time: 0.118s
D:\cheryl-pie>fastboot flash persist persist.img
Sending 'persist' (32768 KB) OKAY [ 0.870s]
Writing 'persist' OKAY [ 0.598s]
Finished. Total time: 1.488s
D:\cheryl-pie>fastboot flash modem_a modem.img
Sending 'modem_a' (105572 KB) OKAY [ 2.857s]
Writing 'modem_a' OKAY [ 0.944s]
Finished. Total time: 3.820s
D:\cheryl-pie>fastboot flash modem_b modem.img
Sending 'modem_b' (105572 KB) OKAY [ 2.658s]
Writing 'modem_b' OKAY [ 0.948s]
Finished. Total time: 3.612s
D:\cheryl-pie>fastboot flash dsp_a dsp.img
Sending 'dsp_a' (16384 KB) OKAY [ 0.464s]
Writing 'dsp_a' OKAY [ 0.164s]
Finished. Total time: 0.645s
D:\cheryl-pie>fastboot flash dsp_b dsp.img
Sending 'dsp_b' (16384 KB) OKAY [ 0.430s]
Writing 'dsp_b' OKAY [ 0.149s]
Finished. Total time: 0.586s
D:\cheryl-pie>fastboot flash boot_a boot.img
Sending 'boot_a' (25797 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
D:\cheryl-pie>fastboot flash boot_b boot.img
< waiting for any device >
i cant even get my razer phone to recognize in fastboot (it shows adb devices when powered on normally) but never when in bootloader mode fastboot.
you should use the command
fastboot flash:raw boot_a boot.img
fastboot flash:raw boot_b boot.img

Categories

Resources