Database Info

stuck on boot logo help

I have a Razr HD (my dad's) he took the newest update last week and now he is stuck at the boot logo.(I have told him to not do it) ADB screen is telling me it is unlocked at stats code 3, (I think a dev edition, he bought it used) now I can't get it to take a recovery to flash stock 4.4.2. I tried this script here (http://forum.xda-developers.com/showthread.php?t=2474393) but it wouldn't restore it to stock and let me use the phone.
Any ideas from the android gurus.

Latheman said:
I have a Razr HD (my dad's) he took the newest update last week and now he is stuck at the boot logo.(I have told him to not do it) ADB screen is telling me it is unlocked at stats code 3, (I think a dev edition, he bought it used) now I can't get it to take a recovery to flash stock 4.4.2. I tried this script here (http://forum.xda-developers.com/showthread.php?t=2474393) but it wouldn't restore it to stock and let me use the phone.
Any ideas from the android gurus.
Click to expand...
Click to collapse
is this a 926 or 925
if 926
use rsd lite and this guide form @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083 i would recommend the full script since you are already unlocked and it was a used phone
if 925
same procedure but with the correct sbf from http://sbf.droid-developers.org/

I did this earlier. Same problem

Latheman said:
I did this earlier. Same problem
Click to expand...
Click to collapse
try this utility. it is a special version to fix certain issues that cant be fixed with fastboot and rsd.
watch the dialog and let me know if any operations fail, or copy and paste the output here for me to see.
i may have to update it for you if a couple specific things fail.

windows or linux?

Latheman said:
windows or linux?
Click to expand...
Click to collapse
windows only
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Latheman said:
windows or linux?
Click to expand...
Click to collapse
flash in fastboot same as the rest.

OK thanks. give me 10 minuets

this phone has the 9/9/14 update that won't be a problem right? just making sure

Latheman said:
this phone has the 9/9/14 update that won't be a problem right? just making sure
Click to expand...
Click to collapse
it wont be a problem, but some parts will fail. im downloading the files now to compare the parts i would like to see work.
either way, try that for now and let me know how it goes. there should be no added danger, the trust zone and partition files are what could fail, neither can be downgraded, so i dont see it making things worse if it doesnt work.

the phone says update gpt-main partition failed then the terminal end is FAILED (remote failure)

here is the output on the computer, sorry it is so long
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] Be VERY aware! This WILL wipe your userdata, including contacts, apps, etc.
[*] I am not responsible if this wipes your internal sdcard, and you should
[*] backup anything worth it to you to your external sdcard and computer before
[*] you choose to continue. You can exit now with the X button on this window.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] This script will also wipe your data (did i mention this will wipe your data
?).
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.156s
sending 'sbl1' (101 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.187s
sending 'sbl2' (126 KB)...
OKAY [ 0.031s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.172s
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.370s
sending 'rpm' (140 KB)...
OKAY [ 0.029s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.315s
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.200s
sending 'aboot' (256 KB)...
OKAY [ 0.039s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.346s
sending 'modem' (30720 KB)...
OKAY [ 2.299s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.464s
sending 'fsg' (165 KB)...
OKAY [ 0.032s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.187s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.083s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
sending 'logo' (854 KB)...
OKAY [ 0.083s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.238s
sending 'boot' (10240 KB)...
OKAY [ 0.781s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.929s
sending 'recovery' (10240 KB)...
OKAY [ 0.805s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.969s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
sending 'system' (30720 KB)...
OKAY [ 2.357s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 2.447s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.188s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.009s
Hit ENTER to return.

Latheman said:
here is the output on the computer, sorry it is so long
Click to expand...
Click to collapse
dammm
my file is almost done, let me compare a couple md5's from the old update and ill get right back to ya with what it looks like.
---------- Post added at 06:35 PM ---------- Previous post was at 06:24 PM ----------
@Latheman
ok, they changed the partition table again, not saying the phone is fixable, but this is the best chance i could have wanted to fix it.
its going to take me 1/2 hour to fix the script, and an hour (barring issue) to upload it.
ill send it over as soon as its done, if not tonight, then tomorrow.

Thank-you

Latheman said:
Thank-you
Click to expand...
Click to collapse
test flash on my updated phone, only tz failed because i removed it, but will be in your version as you already took it.
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.015s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.859s]
finished. total time: 0.874s
sending 'sbl1' (101 KB)...
OKAY [ 0.019s]
writing 'sbl1'...
OKAY [ 0.648s]
finished. total time: 0.668s
sending 'sbl2' (127 KB)...
OKAY [ 0.183s]
writing 'sbl2'...
OKAY [ 1.033s]
finished. total time: 1.216s
sending 'sbl3' (512 KB)...
OKAY [ 0.052s]
writing 'sbl3'...
OKAY [ 1.113s]
finished. total time: 1.165s
sending 'rpm' (140 KB)...
OKAY [ 0.023s]
writing 'rpm'...
OKAY [ 0.473s]
finished. total time: 0.496s
error: cannot load 'tz.mbn'
sending 'aboot' (256 KB)...
OKAY [ 0.193s]
writing 'aboot'...
OKAY [ 1.594s]
finished. total time: 1.788s
sending 'modem' (30720 KB)...
OKAY [ 2.320s]
writing 'modem'...
OKAY [ 2.680s]
sending 'modem' (19212 KB)...
OKAY [ 3.845s]
writing 'modem'...
OKAY [ 1.095s]
finished. total time: 9.944s
sending 'fsg' (165 KB)...
OKAY [ 0.027s]
writing 'fsg'...
OKAY [ 0.855s]
finished. total time: 0.882s
erasing 'modemst1'...
OKAY [ 1.698s]
finished. total time: 1.699s
erasing 'modemst2'...
OKAY [ 1.232s]
finished. total time: 1.232s
sending 'logo' (854 KB)...
OKAY [ 0.076s]
writing 'logo'...
OKAY [ 1.955s]
finished. total time: 2.032s
sending 'boot' (10240 KB)...
OKAY [ 0.784s]
writing 'boot'...
OKAY [ 5.946s]
finished. total time: 6.730s
sending 'recovery' (10240 KB)...
OKAY [ 0.781s]
writing 'recovery'...
OKAY [ 4.749s]
finished. total time: 5.530s
sending 'system' (30720 KB)...
OKAY [ 2.324s]
writing 'system'...
OKAY [ 2.254s]
sending 'system' (30720 KB)...
OKAY [ 5.467s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.717s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.697s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.707s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.223s]
writing 'system'...
OKAY [ 0.015s]
sending 'system' (30720 KB)...
OKAY [ 4.727s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.707s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.712s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.983s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.718s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.729s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.646s]
writing 'system'...
OKAY [ 0.023s]
sending 'system' (30720 KB)...
OKAY [ 5.097s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 5.140s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.697s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.662s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.712s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.067s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.677s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.682s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.696s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 5.232s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.717s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.636s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.703s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.750s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.715s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.701s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.703s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 5.604s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.694s]
writing 'system'...
OKAY [ 0.018s]
sending 'system' (30720 KB)...
OKAY [ 4.708s]
writing 'system'...
OKAY [ 0.018s]
sending 'system' (30720 KB)...
OKAY [ 4.710s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.034s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.686s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (21722 KB)...
OKAY [ 4.040s]
writing 'system'...
OKAY [ 1.323s]
finished. total time: 285.670s
erasing 'tombstones'...
OKAY [ 2.049s]
finished. total time: 2.049s
erasing 'cache'...
OKAY [ 2.632s]
finished. total time: 2.632s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.005s
Hit ENTER to return.

so what should I do? remove a file from the folder you sent me?

Latheman said:
so what should I do? remove a file from the folder you sent me?
Click to expand...
Click to collapse
no, i was just showing you the new version is built, tested, working and uploading now.
so, when i post it later for you to try, this is pretty much a last resort script. if it doesn't work for you, the phone is likely gone.
---------- Post added at 07:42 PM ---------- Previous post was at 07:05 PM ----------
Latheman said:
so what should I do? remove a file from the folder you sent me?
Click to expand...
Click to collapse
ok she is done
http://www.mediafire.com/download/5mmd0jv84c51rvt/DROID_RAZR_HD_Utility_1.4gpt-2a_KK.rar
edit: just changed the download link to another version containing the tz file i forgot to replace, for whoever might need it in the future.

Thanks I'll try it soon.

Latheman said:
Thanks I'll try it soon.
Click to expand...
Click to collapse
i forgot to drop the tz file back in before i uploaded it, its no big deal and shouldnt matter, but you should drop this into the directory in the rare event it becomes needed.
https://www.dropbox.com/s/f27cfsjyewlnlu4/tz.mbn?dl=0

I tried it, and no soap, I think this one is a loss . (first one of every phone I have worked on). the BL is still unlocked so if anybody ever comes up with something in the future, or I can put something together I might be able to restore it.

Did you try to flash stock with rsd 6.1.5 and editing xml file, say removing tz line

Encountering an error when flashing a sending 'system' (844889 KB)... FAILED (remote

Code:
C:\Users\metroPCS01\Desktop\adb>fastboot flash modem NON-HLOS.bin
sending 'modem' (56369 KB)... OKAY
writing 'modem'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (295 KB)... OKAY
writing 'sbl1'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash dbi sdi.mbn
sending 'dbi' (11 KB)... OKAY
writing 'dbi'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
sending 'aboot' (376 KB)... OKAY
writing 'aboot'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash rpm rpm.mbn
sending 'rpm' (185 KB)... OKAY
writing 'rpm'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash tz tz.mbn
sending 'tz' (283 KB)... OKAY
writing 'tz'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash LOGO logo.bin
sending 'LOGO' (9591 KB)... OKAY
writing 'LOGO'... OKAY
C:\Users\metroPCS01\Desktop\adb>
C:\Users\metroPCS01\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bi
sending 'oppostanvbk' (10240 KB)... OKAY
writing 'oppostanvbk'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash boot boot.img
sending 'boot' (5956 KB)... OKAY
writing 'boot'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash cache cache.img
sending 'cache' (10432 KB)... OKAY
writing 'cache'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash recovery recovery.img
sending 'recovery' (7854 KB)... OKAY
writing 'recovery'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash system system.img
sending 'system' (844889 KB)... [B]FAILED (remote: data too large)[/B]
I am trying to flash m-11.0-XNPH05Q-bacon-signed-fastboot.zip but I keep encountering this error. Now I am stuck on the android logo. Any help would be really appreciated. Thanks

You need to update your adb/fastboot, how did you install it? If you didn't install it with the Android SDK you need to uninstall it and then install it with the Android SDK.
Transmitted via Bacon

Same problem!
hi i got the same problem! seacrhing topics, trying but nothing work:
sending 'modem' (56369 KB)...
OKAY [ 3.610s]
writing 'modem'...
OKAY [ 1.026s]
finished. total time: 4.637s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'sbl1' (295 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.011s]
finished. total time: 0.029s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
OKAY [ 0.006s]
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'aboot' (376 KB)...
OKAY [ 0.023s]
writing 'aboot'...
OKAY [ 0.024s]
finished. total time: 0.047s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'rpm' (185 KB)...
OKAY [ 0.011s]
writing 'rpm'...
OKAY [ 0.008s]
finished. total time: 0.019s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'tz' (283 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.030s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'LOGO' (9591 KB)...
OKAY [ 0.557s]
writing 'LOGO'...
OKAY [ 0.190s]
finished. total time: 0.747s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.669s]
writing 'oppostanvbk'...
OKAY [ 0.207s]
finished. total time: 0.876s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 15ee5ede
--------------------------------------------
checking product...
OKAY [ 0.002s]
sending 'boot' (5956 KB)...
OKAY [ 0.346s]
writing 'boot'...
OKAY [ 0.114s]
sending 'recovery' (7854 KB)...
OKAY [ 0.484s]
writing 'recovery'...
OKAY [ 0.156s]
sending 'system' (844889 KB)...
FAILED (remote: data too large)
finished. total time: 1.168s
install android-sdk from site working onlinux mint 17.1 javajdk7 what i can do

fastboot error no such file

im getting this error when im flashing an image
{
"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"
}

MehmetCanWT said:
im getting this error when im flashing an image
View attachment 5694307
Click to expand...
Click to collapse
Newer devices have two modes for fastboot commands.
bootloader (fastboot).
fastboot (fastboot_d, fastbootd, or some other variation of the name).​
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
Example from OnePlus 7T.
Bootloader (fastboot).
Code:
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786356 KB) OKAY [ 32.517s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (786288 KB) OKAY [ 32.146s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Fastboot (fastboot_d).
Code:
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.004s]
Sending sparse 'system_ext_b' 1/6 (262112 KB) OKAY [ 11.085s]
Writing 'system_ext_b' OKAY [ 1.698s]
Sending sparse 'system_ext_b' 2/6 (262128 KB) OKAY [ 11.182s]
Writing 'system_ext_b' OKAY [ 1.708s]
Sending sparse 'system_ext_b' 3/6 (262116 KB) OKAY [ 10.854s]
Writing 'system_ext_b' OKAY [ 1.676s]
Sending sparse 'system_ext_b' 4/6 (262128 KB) OKAY [ 10.923s]
Writing 'system_ext_b' OKAY [ 1.677s]
Sending sparse 'system_ext_b' 5/6 (230160 KB) OKAY [ 9.749s]
Writing 'system_ext_b' OKAY [ 1.481s]
Sending sparse 'system_ext_b' 6/6 (158200 KB) OKAY [ 6.649s]
Writing 'system_ext_b' OKAY [ 1.071s]
Finished. Total time: 69.990s
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/6 (262108 KB) OKAY [ 10.725s]
Writing 'system_b' OKAY [ 1.684s]
Sending sparse 'system_b' 2/6 (262120 KB) OKAY [ 10.835s]
Writing 'system_b' OKAY [ 1.675s]
Sending sparse 'system_b' 3/6 (262060 KB) OKAY [ 10.865s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 4/6 (262128 KB) OKAY [ 11.052s]
Writing 'system_b' OKAY [ 1.668s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 11.024s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 6/6 (32956 KB) OKAY [ 1.360s]
Writing 'system_b' OKAY [ 0.320s]
Finished. Total time: 64.798s
What device do you have?
If it is a Legion Phone Duel 2, then you more than likely need to flash using fastboot_d mode.
Hope it helps more than confuse.
Cheers.

ipdev said:
Newer devices have two modes for fastboot commands.
bootloader (fastboot).​fastboot (fastboot_d, fastbootd, or some other variation of the name).​
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
Example from OnePlus 7T.
Bootloader (fastboot).
Code:
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786356 KB) OKAY [ 32.517s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (786288 KB) OKAY [ 32.146s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Fastboot (fastboot_d).
Code:
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.004s]
Sending sparse 'system_ext_b' 1/6 (262112 KB) OKAY [ 11.085s]
Writing 'system_ext_b' OKAY [ 1.698s]
Sending sparse 'system_ext_b' 2/6 (262128 KB) OKAY [ 11.182s]
Writing 'system_ext_b' OKAY [ 1.708s]
Sending sparse 'system_ext_b' 3/6 (262116 KB) OKAY [ 10.854s]
Writing 'system_ext_b' OKAY [ 1.676s]
Sending sparse 'system_ext_b' 4/6 (262128 KB) OKAY [ 10.923s]
Writing 'system_ext_b' OKAY [ 1.677s]
Sending sparse 'system_ext_b' 5/6 (230160 KB) OKAY [ 9.749s]
Writing 'system_ext_b' OKAY [ 1.481s]
Sending sparse 'system_ext_b' 6/6 (158200 KB) OKAY [ 6.649s]
Writing 'system_ext_b' OKAY [ 1.071s]
Finished. Total time: 69.990s
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/6 (262108 KB) OKAY [ 10.725s]
Writing 'system_b' OKAY [ 1.684s]
Sending sparse 'system_b' 2/6 (262120 KB) OKAY [ 10.835s]
Writing 'system_b' OKAY [ 1.675s]
Sending sparse 'system_b' 3/6 (262060 KB) OKAY [ 10.865s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 4/6 (262128 KB) OKAY [ 11.052s]
Writing 'system_b' OKAY [ 1.668s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 11.024s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 6/6 (32956 KB) OKAY [ 1.360s]
Writing 'system_b' OKAY [ 0.320s]
Finished. Total time: 64.798s
What device do you have?
If it is a Legion Phone Duel 2, then you more than likely need to flash using fastboot_d mode.
Hope it helps more than confuse.
Cheers.
Click to expand...
Click to collapse
i have fastbootd and bootloader
my phone is trident a24

im flashing image on fastbootd

If you still get the error in fastbootd, then..
- Try a different usb cable or port.
- Make sure to use a USB-2 port on the computer.
Known issues using a USB-3 or USB-C port for flashing devices.​
- Incompatible version of fastboot.
- Incompatible image file format or corrupted image file.
Newer versions of fastboot should detect the active slot.
Some older devices (and older fastboot), you have to call the slot you want to flash.
fastboot flash flash system_a legion.img
fastboot system_b legion.img
--
I looked up the trident a24, nice looking phone.
Released with Android 10 (?), it should be a slot device.
I could not find out if it was a normal A/B device or one of the odd few A-Olny slot devices.
You can find the current (active) slot.
fastboot getvar current-slot
You can set the active slot.
fastboot set_active a
fastboot set_active b
Cheers.
PS.
When I updated my main computer, I only have USB-C ports on new computer.
I use a cheap USB-C hub that includes a USB-2 port and do all my flashing using it.

i just waited a night and problem solved thanks to all

need help Oneplus 8 IN2017 rom Flash successfull but not booting. crashdump mode

It is not booting just crash dump mode is showing.
Cmd commands:
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.125s]
F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 210903704 (102980 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1147] Writing root inode (hot node), 1c000 0 200 at offset 0x00114688
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c601, 0001c602
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114689
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c603, 0001c604
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114690
[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001c600
Info: Overprovision ratio = 0.620%
Info: Overprovision segments = 645 (GC reserved = 330)
[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.014s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.002s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.885s
Sending 'boot_a' (98304 KB) OKAY [ 3.574s]
Writing 'boot_a' OKAY [ 0.370s]
Finished. Total time: 5.594s
Sending 'dtbo' (8192 KB) OKAY [ 0.302s]
Writing 'dtbo' OKAY [ 0.031s]
Finished. Total time: 0.537s
Sending 'modem_a' (234332 KB) OKAY [ 8.446s]
Writing 'modem_a' OKAY [ 0.827s]
Finished. Total time: 10.818s
Sending 'recovery' (102400 KB) OKAY [ 3.722s]
Writing 'recovery' OKAY [ 0.365s]
Finished. Total time: 5.689s
Sending 'vbmeta' (8 KB) OKAY [ 0.012s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.067s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.005s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.068s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 11.197s
Sending 'abl_a' (1996 KB) OKAY [ 0.074s]
Writing 'abl_a' OKAY [ 0.020s]
Finished. Total time: 0.349s
Sending 'aop_a' (200 KB) OKAY [ 0.010s]
Writing 'aop_a' OKAY [ 0.009s]
Finished. Total time: 0.145s
Sending 'bluetooth_a' (652 KB) OKAY [ 0.024s]
Writing 'bluetooth_a' OKAY [ 0.012s]
Finished. Total time: 0.214s
Sending 'cmnlib_a' (384 KB) OKAY [ 0.013s]
Writing 'cmnlib_a' OKAY [ 0.010s]
Finished. Total time: 0.117s
Sending 'cmnlib64_a' (500 KB) OKAY [ 0.018s]
Writing 'cmnlib64_a' OKAY [ 0.011s]
Finished. Total time: 0.122s
Sending 'devcfg_a' (52 KB) OKAY [ 0.003s]
Writing 'devcfg_a' OKAY [ 0.008s]
Finished. Total time: 0.061s
Sending 'dsp_a' (65536 KB) OKAY [ 2.428s]
Writing 'dsp_a' OKAY [ 0.476s]
Finished. Total time: 3.674s
Sending 'featenabler_a' (88 KB) OKAY [ 0.004s]
Writing 'featenabler_a' OKAY [ 0.008s]
Finished. Total time: 0.085s
Sending 'hyp_a' (436 KB) OKAY [ 0.018s]
Writing 'hyp_a' OKAY [ 0.011s]
Finished. Total time: 0.139s
Sending 'imagefv_a' (20 KB) OKAY [ 0.002s]
Writing 'imagefv_a' OKAY [ 0.007s]
Finished. Total time: 0.072s
Sending 'keymaster_a' (252 KB) OKAY [ 0.009s]
Writing 'keymaster_a' OKAY [ 0.009s]
Finished. Total time: 0.088s
Sending 'logo_a' (7780 KB) OKAY [ 0.293s]
Writing 'logo_a' OKAY [ 0.058s]
Finished. Total time: 0.522s
Sending 'mdm_oem_stanvbk' (3776 KB) OKAY [ 0.149s]
Writing 'mdm_oem_stanvbk' OKAY [ 0.032s]
Finished. Total time: 0.347s
Sending 'multiimgoem_a' (16 KB) OKAY [ 0.002s]
Writing 'multiimgoem_a' OKAY [ 0.008s]
Finished. Total time: 0.074s
Resizing 'odm_a' OKAY [ 0.005s]
Sending 'odm_a' (42716 KB) OKAY [ 1.604s]
Writing 'odm_a' OKAY [ 0.310s]
Finished. Total time: 2.531s
fastboot: error: cannot load 'opproduct.img': No such file or directory
Sending 'qupfw_a' (56 KB) OKAY [ 0.003s]
Writing 'qupfw_a' OKAY [ 0.008s]
Finished. Total time: 0.070s
Sending 'spunvm' (348 KB) OKAY [ 0.013s]
Writing 'spunvm' OKAY [ 0.010s]
Finished. Total time: 0.115s
Sending 'storsec_a' (20 KB) OKAY [ 0.002s]
Writing 'storsec_a' OKAY [ 0.008s]
Finished. Total time: 0.063s
Sending 'tz_a' (3096 KB) OKAY [ 0.119s]
Writing 'tz_a' OKAY [ 0.027s]
Finished. Total time: 0.288s
Sending 'uefisecapp_a' (124 KB) OKAY [ 0.006s]
Writing 'uefisecapp_a' OKAY [ 0.009s]
Finished. Total time: 0.092s
Sending 'xbl_a' (3404 KB) OKAY [ 0.129s]
Writing 'xbl_a' OKAY [ 0.062s]
Finished. Total time: 0.316s
Sending 'xbl_config_a' (96 KB) OKAY [ 0.004s]
Writing 'xbl_config_a' OKAY [ 0.012s]
Finished. Total time: 0.097s
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.006s]
Sending sparse 'system_a' 1/6 (262108 KB) OKAY [ 10.385s]
Writing 'system_a' OKAY [ 1.491s]
Sending sparse 'system_a' 2/6 (262112 KB) OKAY [ 10.225s]
Writing 'system_a' OKAY [ 1.486s]
Sending sparse 'system_a' 3/6 (262080 KB) OKAY [ 10.399s]
Writing 'system_a' OKAY [ 1.500s]
Sending sparse 'system_a' 4/6 (262128 KB) OKAY [ 10.478s]
Writing 'system_a' OKAY [ 1.483s]
Sending sparse 'system_a' 5/6 (262128 KB) OKAY [ 10.452s]
Writing 'system_a' OKAY [ 1.505s]
Sending sparse 'system_a' 6/6 (193388 KB) OKAY [ 7.722s]
Writing 'system_a' OKAY [ 1.150s]
Finished. Total time: 116.782s
Invalid sparse file format at header magic
Resizing 'vendor_a' OKAY [ 0.006s]
Sending sparse 'vendor_a' 1/6 (262116 KB) OKAY [ 10.247s]
Writing 'vendor_a' OKAY [ 1.491s]
Sending sparse 'vendor_a' 2/6 (262032 KB) OKAY [ 10.419s]
Writing 'vendor_a' OKAY [ 1.483s]
Sending sparse 'vendor_a' 3/6 (262100 KB) OKAY [ 10.353s]
Writing 'vendor_a' OKAY [ 1.483s]
Sending sparse 'vendor_a' 4/6 (262112 KB) OKAY [ 10.403s]
Writing 'vendor_a' OKAY [ 1.479s]
Sending sparse 'vendor_a' 5/6 (262128 KB) OKAY [ 10.445s]
Writing 'vendor_a' OKAY [ 1.475s]
Sending sparse 'vendor_a' 6/6 (202836 KB) OKAY [ 8.104s]
Writing 'vendor_a' OKAY [ 1.210s]
Finished. Total time: 101.877s
Invalid sparse file format at header magic
Resizing 'product_a' OKAY [ 0.006s]
Sending sparse 'product_a' 1/5 (262116 KB) OKAY [ 10.417s]
Writing 'product_a' OKAY [ 1.491s]
Sending sparse 'product_a' 2/5 (262116 KB) OKAY [ 10.449s]
Writing 'product_a' OKAY [ 1.482s]
Sending sparse 'product_a' 3/5 (262128 KB) OKAY [ 10.516s]
Writing 'product_a' OKAY [ 1.482s]
Sending sparse 'product_a' 4/5 (262128 KB) OKAY [ 10.524s]
Writing 'product_a' OKAY [ 1.500s]
Sending sparse 'product_a' 5/5 (102700 KB) OKAY [ 4.086s]
Writing 'product_a' OKAY [ 0.652s]
Finished. Total time: 77.536s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.014s
Press any key to continue . . .

Question Error when trying to enable 32 bit apps

Hows it going guys,
im following this guide:
How to Install and Run 32-Bit Apps on Pixel 7 Pro
In this comprehensive tutorial, we will show you the detailed steps to install and run 32-bit apps on your Google Pixel 7/Pro.
www.droidwin.com
I am on the step where you flash the image.zip file you drag out of the stock ota image file and rename. I did this and then followed the next step, I run into this problem when I am executing the commands.
C:\Users\Gogop\Desktop\platform-tools>fastboot --skip-reboot -w update image.zip
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9288096
Baseband Version.....: g5300g-220923-221028-B-9229469
Serial Number........: 28101FDH300AX6
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.117s]
extracting boot.img (64 MB) to disk... took 0.145s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.088s]
Writing 'boot_b' OKAY [ 0.161s]
extracting init_boot.img (8 MB) to disk... took 0.016s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.257s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.036s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.515s]
Writing 'dtbo_b' OKAY [ 0.039s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.002s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.032s]
Writing 'pvmfw_b' OKAY [ 0.005s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_b' OKAY [ 0.004s]
extracting vendor_boot.img (64 MB) to disk... took 0.143s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.069s]
Writing 'vendor_boot_b' OKAY [ 0.162s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.110s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 2.066s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.155s]
extracting super_empty.img (0 MB) to disk... took 0.000s
extracting product.img (2778 MB) to disk... took 7.526s
extracting system.img (841 MB) to disk... took 2.387s
extracting system_dlkm.img (0 MB) to disk... took 0.000s
extracting system_ext.img (356 MB) to disk... took 1.017s
extracting system_other.img (24 MB) to disk... took 0.079s
extracting vendor.img (636 MB) to disk... took 1.678s
extracting vendor_dlkm.img (40 MB) to disk... took 0.081s
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed
I have tried to just continue past this and not do anything else about it and then flash the patched init_boot but after successfully doing this I am still unable to install 32 bit apps. Please help.

androidoverapple1 said:
Hows it going guys,
im following this guide:
How to Install and Run 32-Bit Apps on Pixel 7 Pro
In this comprehensive tutorial, we will show you the detailed steps to install and run 32-bit apps on your Google Pixel 7/Pro.
www.droidwin.com
I am on the step where you flash the image.zip file you drag out of the stock ota image file and rename. I did this and then followed the next step, I run into this problem when I am executing the commands.
C:\Users\Gogop\Desktop\platform-tools>fastboot --skip-reboot -w update image.zip
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9288096
Baseband Version.....: g5300g-220923-221028-B-9229469
Serial Number........: 28101FDH300AX6
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.117s]
extracting boot.img (64 MB) to disk... took 0.145s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.088s]
Writing 'boot_b' OKAY [ 0.161s]
extracting init_boot.img (8 MB) to disk... took 0.016s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.257s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.036s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.515s]
Writing 'dtbo_b' OKAY [ 0.039s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.002s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.032s]
Writing 'pvmfw_b' OKAY [ 0.005s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_b' OKAY [ 0.004s]
extracting vendor_boot.img (64 MB) to disk... took 0.143s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.069s]
Writing 'vendor_boot_b' OKAY [ 0.162s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.110s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 2.066s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.155s]
extracting super_empty.img (0 MB) to disk... took 0.000s
extracting product.img (2778 MB) to disk... took 7.526s
extracting system.img (841 MB) to disk... took 2.387s
extracting system_dlkm.img (0 MB) to disk... took 0.000s
extracting system_ext.img (356 MB) to disk... took 1.017s
extracting system_other.img (24 MB) to disk... took 0.079s
extracting vendor.img (636 MB) to disk... took 1.678s
extracting vendor_dlkm.img (40 MB) to disk... took 0.081s
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed
I have tried to just continue past this and not do anything else about it and then flash the patched init_boot but after successfully doing this I am still unable to install 32 bit apps. Please help.
Click to expand...
Click to collapse
1. Try using this guide.
2. Use Platform Tools v33.0.3 instead of v34.0.0 because the latter seems to skip fastbootd. This bug will cause the error you got.

Lughnasadh said:
1. Try using this guide.
2. Use Platform Tools v33.0.3 instead of v34.0.0 because the latter seems to skip fastbootd. This bug will cause the error you got.
Click to expand...
Click to collapse
I went with the reccomendation and im still not gaining access.
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9288096
Baseband Version.....: g5300g-220923-221028-B-9229469
Serial Number........: 28101FDH300AX6
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.114s]
extracting boot.img (64 MB) to disk... took 0.165s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.068s]
Writing 'boot_b' OKAY [ 0.145s]
extracting init_boot.img (8 MB) to disk... took 0.024s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.260s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.519s]
Writing 'dtbo_b' OKAY [ 0.039s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.002s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.033s]
Writing 'pvmfw_b' OKAY [ 0.005s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.003s]
extracting vendor_boot.img (64 MB) to disk... took 0.178s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.063s]
Writing 'vendor_boot_b' OKAY [ 0.151s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.127s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 2.068s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.154s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (5 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 1.037s]
Resizing 'product_b' OKAY [ 0.006s]
Resizing 'system_b' OKAY [ 0.005s]
Resizing 'system_dlkm_b' OKAY [ 0.003s]
Resizing 'system_ext_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_dlkm_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2778 MB) to disk... took 11.696s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.010s]
Sending sparse 'product_b' 1/11 (262112 KB) OKAY [ 8.436s]
Writing 'product_b' OKAY [ 0.370s]
Sending sparse 'product_b' 2/11 (262124 KB) OKAY [ 8.416s]
Writing 'product_b' OKAY [ 0.364s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 8.473s]
Writing 'product_b' OKAY [ 0.376s]
Sending sparse 'product_b' 4/11 (262120 KB) OKAY [ 8.442s]
Writing 'product_b' OKAY [ 0.407s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 8.456s]
Writing 'product_b' OKAY [ 0.368s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 8.503s]
Writing 'product_b' OKAY [ 0.411s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 8.540s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 8/11 (262124 KB) OKAY [ 8.509s]
Writing 'product_b' OKAY [ 0.409s]
Sending sparse 'product_b' 9/11 (262128 KB) OKAY [ 8.491s]
Writing 'product_b' OKAY [ 0.388s]
Sending sparse 'product_b' 10/11 (262116 KB) OKAY [ 8.565s]
Writing 'product_b' OKAY [ 0.395s]
Sending sparse 'product_b' 11/11 (215056 KB) OKAY [ 7.057s]
Writing 'product_b' OKAY [ 0.337s]
extracting system.img (841 MB) to disk... took 2.719s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.012s]
Sending sparse 'system_b' 1/4 (262116 KB) OKAY [ 8.561s]
Writing 'system_b' OKAY [ 0.383s]
Sending sparse 'system_b' 2/4 (262120 KB) OKAY [ 8.560s]
Writing 'system_b' OKAY [ 0.375s]
Sending sparse 'system_b' 3/4 (262140 KB) OKAY [ 8.576s]
Writing 'system_b' OKAY [ 0.377s]
Sending sparse 'system_b' 4/4 (71952 KB) OKAY [ 2.345s]
Writing 'system_b' OKAY [ 0.146s]
extracting system_dlkm.img (0 MB) to disk... took 0.001s
archive does not contain 'system_dlkm.sig'
Resizing 'system_dlkm_b' OKAY [ 0.006s]
Sending 'system_dlkm_b' (340 KB) OKAY [ 0.013s]
Writing 'system_dlkm_b' OKAY [ 0.040s]
extracting system_ext.img (356 MB) to disk... took 1.097s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_b' OKAY [ 0.009s]
Sending sparse 'system_ext_b' 1/2 (262136 KB) OKAY [ 8.552s]
Writing 'system_ext_b' OKAY [ 0.397s]
Sending sparse 'system_ext_b' 2/2 (101724 KB) OKAY [ 3.335s]
Writing 'system_ext_b' OKAY [ 0.189s]
extracting system_other.img (24 MB) to disk... took 0.089s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.008s]
Sending 'system_a' (25220 KB) OKAY [ 0.832s]
Writing 'system_a' OKAY [ 0.096s]
extracting vendor.img (636 MB) to disk... took 2.468s
archive does not contain 'vendor.sig'
Resizing 'vendor_b' OKAY [ 0.013s]
Sending sparse 'vendor_b' 1/3 (262120 KB) OKAY [ 8.551s]
Writing 'vendor_b' OKAY [ 0.434s]
Sending sparse 'vendor_b' 2/3 (262140 KB) OKAY [ 8.498s]
Writing 'vendor_b' OKAY [ 0.409s]
Sending sparse 'vendor_b' 3/3 (124972 KB) OKAY [ 4.073s]
Writing 'vendor_b' OKAY [ 0.202s]
extracting vendor_dlkm.img (40 MB) to disk... took 0.094s
archive does not contain 'vendor_dlkm.sig'
Resizing 'vendor_dlkm_b' OKAY [ 0.010s]
Sending 'vendor_dlkm_b' (41116 KB) OKAY [ 1.332s]
Writing 'vendor_dlkm_b' OKAY [ 0.088s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 2.059s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.019s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 226.485s
C:\Users\Gogop\Desktop\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.003s
C:\Users\Gogop\Desktop\platform-tools>fastboot devices
28101FDH300AX6 fastboot
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot C:\Users\Gogop\Desktop\magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.262s]
Writing 'init_boot_b' OKAY [ 0.055s]
Finished. Total time: 0.346s
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.260s]
Writing 'init_boot_b' OKAY [ 0.073s]
Finished. Total time: 0.336s
C:\Users\Gogop\Desktop\platform-tools>fastboot flash C:\Users\Gogop\Desktop\magisk_patched_boot.img
unknown partition 'C:\Users\Gogop\Desktop\magisk_patched_boot.img'
fastboot: error: cannot determine image filename for 'C:\Users\Gogop\Desktop\magisk_patched_boot.img'
C:\Users\Gogop\Desktop\platform-tools>fastboot devices
28101FDH300AX6 fastboot
C:\Users\Gogop\Desktop\platform-tools>fastboot flash
fastboot: usage: expected argument
C:\Users\Gogop\Desktop\platform-tools>fastboot flash C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img
unknown partition 'C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img'
fastboot: error: cannot determine image filename for 'C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img'
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.271s]
Writing 'init_boot_b' OKAY [ 0.074s]
Finished. Total time: 0.347s
i tried changing how i flashed the init boot but it seems like its not patching the magisk delta patch. There were failures in there as well. Any ideas?

androidoverapple1 said:
I went with the reccomendation and im still not gaining access.
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9288096
Baseband Version.....: g5300g-220923-221028-B-9229469
Serial Number........: 28101FDH300AX6
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.114s]
extracting boot.img (64 MB) to disk... took 0.165s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.068s]
Writing 'boot_b' OKAY [ 0.145s]
extracting init_boot.img (8 MB) to disk... took 0.024s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.260s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.519s]
Writing 'dtbo_b' OKAY [ 0.039s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.002s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.033s]
Writing 'pvmfw_b' OKAY [ 0.005s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.003s]
extracting vendor_boot.img (64 MB) to disk... took 0.178s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.063s]
Writing 'vendor_boot_b' OKAY [ 0.151s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.127s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 2.068s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.154s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (5 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 1.037s]
Resizing 'product_b' OKAY [ 0.006s]
Resizing 'system_b' OKAY [ 0.005s]
Resizing 'system_dlkm_b' OKAY [ 0.003s]
Resizing 'system_ext_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_dlkm_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2778 MB) to disk... took 11.696s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.010s]
Sending sparse 'product_b' 1/11 (262112 KB) OKAY [ 8.436s]
Writing 'product_b' OKAY [ 0.370s]
Sending sparse 'product_b' 2/11 (262124 KB) OKAY [ 8.416s]
Writing 'product_b' OKAY [ 0.364s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 8.473s]
Writing 'product_b' OKAY [ 0.376s]
Sending sparse 'product_b' 4/11 (262120 KB) OKAY [ 8.442s]
Writing 'product_b' OKAY [ 0.407s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 8.456s]
Writing 'product_b' OKAY [ 0.368s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 8.503s]
Writing 'product_b' OKAY [ 0.411s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 8.540s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 8/11 (262124 KB) OKAY [ 8.509s]
Writing 'product_b' OKAY [ 0.409s]
Sending sparse 'product_b' 9/11 (262128 KB) OKAY [ 8.491s]
Writing 'product_b' OKAY [ 0.388s]
Sending sparse 'product_b' 10/11 (262116 KB) OKAY [ 8.565s]
Writing 'product_b' OKAY [ 0.395s]
Sending sparse 'product_b' 11/11 (215056 KB) OKAY [ 7.057s]
Writing 'product_b' OKAY [ 0.337s]
extracting system.img (841 MB) to disk... took 2.719s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.012s]
Sending sparse 'system_b' 1/4 (262116 KB) OKAY [ 8.561s]
Writing 'system_b' OKAY [ 0.383s]
Sending sparse 'system_b' 2/4 (262120 KB) OKAY [ 8.560s]
Writing 'system_b' OKAY [ 0.375s]
Sending sparse 'system_b' 3/4 (262140 KB) OKAY [ 8.576s]
Writing 'system_b' OKAY [ 0.377s]
Sending sparse 'system_b' 4/4 (71952 KB) OKAY [ 2.345s]
Writing 'system_b' OKAY [ 0.146s]
extracting system_dlkm.img (0 MB) to disk... took 0.001s
archive does not contain 'system_dlkm.sig'
Resizing 'system_dlkm_b' OKAY [ 0.006s]
Sending 'system_dlkm_b' (340 KB) OKAY [ 0.013s]
Writing 'system_dlkm_b' OKAY [ 0.040s]
extracting system_ext.img (356 MB) to disk... took 1.097s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_b' OKAY [ 0.009s]
Sending sparse 'system_ext_b' 1/2 (262136 KB) OKAY [ 8.552s]
Writing 'system_ext_b' OKAY [ 0.397s]
Sending sparse 'system_ext_b' 2/2 (101724 KB) OKAY [ 3.335s]
Writing 'system_ext_b' OKAY [ 0.189s]
extracting system_other.img (24 MB) to disk... took 0.089s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.008s]
Sending 'system_a' (25220 KB) OKAY [ 0.832s]
Writing 'system_a' OKAY [ 0.096s]
extracting vendor.img (636 MB) to disk... took 2.468s
archive does not contain 'vendor.sig'
Resizing 'vendor_b' OKAY [ 0.013s]
Sending sparse 'vendor_b' 1/3 (262120 KB) OKAY [ 8.551s]
Writing 'vendor_b' OKAY [ 0.434s]
Sending sparse 'vendor_b' 2/3 (262140 KB) OKAY [ 8.498s]
Writing 'vendor_b' OKAY [ 0.409s]
Sending sparse 'vendor_b' 3/3 (124972 KB) OKAY [ 4.073s]
Writing 'vendor_b' OKAY [ 0.202s]
extracting vendor_dlkm.img (40 MB) to disk... took 0.094s
archive does not contain 'vendor_dlkm.sig'
Resizing 'vendor_dlkm_b' OKAY [ 0.010s]
Sending 'vendor_dlkm_b' (41116 KB) OKAY [ 1.332s]
Writing 'vendor_dlkm_b' OKAY [ 0.088s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 2.059s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.019s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 226.485s
C:\Users\Gogop\Desktop\platform-tools>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.003s
C:\Users\Gogop\Desktop\platform-tools>fastboot devices
28101FDH300AX6 fastboot
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot C:\Users\Gogop\Desktop\magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.262s]
Writing 'init_boot_b' OKAY [ 0.055s]
Finished. Total time: 0.346s
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.260s]
Writing 'init_boot_b' OKAY [ 0.073s]
Finished. Total time: 0.336s
C:\Users\Gogop\Desktop\platform-tools>fastboot flash C:\Users\Gogop\Desktop\magisk_patched_boot.img
unknown partition 'C:\Users\Gogop\Desktop\magisk_patched_boot.img'
fastboot: error: cannot determine image filename for 'C:\Users\Gogop\Desktop\magisk_patched_boot.img'
C:\Users\Gogop\Desktop\platform-tools>fastboot devices
28101FDH300AX6 fastboot
C:\Users\Gogop\Desktop\platform-tools>fastboot flash
fastboot: usage: expected argument
C:\Users\Gogop\Desktop\platform-tools>fastboot flash C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img
unknown partition 'C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img'
fastboot: error: cannot determine image filename for 'C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img'
C:\Users\Gogop\Desktop\platform-tools>fastboot flash init_boot C:\Users\Gogop\Desktop\platform-tools\magisk_patched_boot.img
Sending 'init_boot_b' (8192 KB) OKAY [ 0.271s]
Writing 'init_boot_b' OKAY [ 0.074s]
Finished. Total time: 0.347s
i tried changing how i flashed the init boot but it seems like its not patching the magisk delta patch. There were failures in there as well. Any ideas?
Click to expand...
Click to collapse
If you are trying to flash a patched init_boot.img, the command is:
Code:
fastboot flash init_boot <name of patched init_boot.img>