Stock ROM slot wiped - Motorola Droid Bionic

As the title says the stock slot was wiped on this Bionic. I have tried using BionicRestorer to fxz to 5.5.893 and 5.9.901 and it encountered a couple of errors. I'm not sure exactly what the mean though. The phone boots to the Moto logo, then the screen goes blank and the soft keys stay lit. Nothing else happens and I have to pull the battery. I tried booting into recovery mode but after selecting recovery I get the android laying on his back with a triangle/exclamation point above him.
I'm not sure what else I can do with this and would greatly appreciate some help. I do have a charger so I'm not worried about the battery getting low. I'm using Linux but do have access to Windows as well.
Here is the command line output from the BionicRestorer script:
Code:
Here we go, I don't stop on errors, once it starts there is no stopping
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm allow-mbmloader-flashing-mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.023s]
writing 'mbm'... OKAY [ 0.453s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbmloader mbmloader.bin
sending 'mbmloader' (40 KB)... OKAY [ 0.009s]
writing 'mbmloader'... OKAY [ 0.289s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.024s]
writing 'mbm'... OKAY [ 0.451s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdt.bin cdt.bin
sending 'cdt.bin' (16 KB)... OKAY [ 0.007s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase cache
erasing 'cache'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase userdata
erasing 'userdata'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash lbl lbl
sending 'lbl' (16 KB)... OKAY [ 0.007s]
writing 'lbl'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash logo.bin logo.bin
sending 'logo.bin' (854 KB)... OKAY [ 0.061s]
writing 'logo.bin'... OKAY [ 0.267s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash ebr ebr
sending 'ebr' (16 KB)... OKAY [ 0.008s]
writing 'ebr'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbr mbr
sending 'mbr' (16 KB)... OKAY [ 0.007s]
writing 'mbr'... OKAY [ 0.397s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash devtree device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.041s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash system system.img
sending 'system' (262144 KB)... OKAY [ 16.514s]
writing 'system'... OKAY [ 21.258s]
sending 'system' (229120 KB)... OKAY [ 14.442s]
writing 'system'... OKAY [ 18.771s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.533s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash recovery recovery.img
sending 'recovery' (9216 KB)... OKAY [ 0.600s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdrom cdrom
sending 'cdrom' (12032 KB)... OKAY [ 0.771s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash preinstall preinstall.img
sending 'preinstall' (262144 KB)... OKAY [ 16.499s]
writing 'preinstall'... OKAY [ 22.208s]
sending 'preinstall' (49152 KB)... OKAY [ 3.106s]
writing 'preinstall'... OKAY [ 3.931s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash webtop grfs.img
sending 'webtop' (262144 KB)... OKAY [ 16.516s]
writing 'webtop'... OKAY [ 23.794s]
sending 'webtop' (262144 KB)... OKAY [ 16.515s]
writing 'webtop'... OKAY [ 23.305s]
sending 'webtop' (262144 KB)... OKAY [ 16.507s]
writing 'webtop'... OKAY [ 21.253s]
sending 'webtop' (262144 KB)... OKAY [ 16.521s]
writing 'webtop'... OKAY [ 22.130s]
sending 'webtop' (262144 KB)... OKAY [ 16.514s]
writing 'webtop'... OKAY [ 22.110s]
sending 'webtop' (54016 KB)... OKAY [ 3.408s]
writing 'webtop'... OKAY [ 5.240s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash radio radio.img
sending 'radio' (21768 KB)... OKAY [ 1.377s]
writing 'radio'... OKAY [ 3.805s]
I think I've tried flashing the wrong file in a mad case of Idon'tknowwhati'mdoingsoIshouldhaveleftittheheckalone. So I'm going to try flashing http://sbf.droid-developers.org/download.php?device=12&file=162 with RSD Lite as suggested in some other posts I've read today.

Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd

Ryan11271 said:
Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd
Click to expand...
Click to collapse
That's what I plan on doing. I can still get to recovery and ap fastboot mode. I'm going to d/l rsd now.

The biggest thing is that you cannot flash back to an earlier version than what had been installed. You can only flash the same version or newer.

How about this, I ordered a droid bionic, I'll root and put on safestrap, Once I do all that good stuff I'll make you a stock rom backup and send you the zip. I'll pm you when I get it

Probably doesn't have safestrap installed anymore, so a backup from safestrap wouldn't help.

Ohhh, I didn't think of that XD

Yeah I borked safestrap too but thanks for the offer though. I'm about to reboot into windows and try to rsd what I believe to be the correct version.

Related

[Q] Question about using HoM and stock

I'm moving this from another forum, to post in the correct place.
From Me
Hello all, I really appreciate all the work that Samurai HL has put into HoB/HoM. I used it in the past, and still I'm very grateful.
I have installed SafeStrap 3.5 on my Bionic, and I've successfully installed CM10 on the Slot 1. However, what I seem to have done is also installed CM10 in the Factory slot. When I boot using that slot, it just sits there and does not do anything. I've tried several times to install the stock roms, but all I get are Error Flashing Zip messages.
My question is about whether HoM will solve my problem or not. Am I able to flash the stock slot with HoM or do I remove SS and try flashing the slot another way? I've searched and searched, but I haven't seen an issue quite like this.
Thanks for all your help.
From SamuriHL
Yes, you can use the House of Moto with the xt875 support file and the latest FXZ to restore stock. Use the KEEP DATA option. You will have to reinstall root and SS recovery once that's done. (No need to uninstall SS).
Click to expand...
Click to collapse
SamuriHL, I did exactly what you said, but now SS doesn't come up and the phone still sits after the M logo goes away.
Then you've managed to corrupt the data partition. That sucks. The only fix is to FDR.
SamuriHL said:
Then you've managed to corrupt the data partition. That sucks. The only fix is to FDR.
Click to expand...
Click to collapse
Is that the full option?
Sure you can do it that way. Or you can boot into recovery and do it from there. Just understand what it means....your phone will be reset completely and you'll have to reinstall everything.
SamuriHL said:
Sure you can do it that way. Or you can boot into recovery and do it from there. Just understand what it means....your phone will be reset completely and you'll have to reinstall everything.
Click to expand...
Click to collapse
I did both methods, and same issue. Do I need to try another FXZ version? I have all 4 from the sbf site.
Um, it can't be "same issue" if it flashed properly and you did in fact do an FDR. That's not possible. So I'm guessing your flash didn't work. And no, you can't just pick a different FXZ. The phone is security locked and you'll brick it trying to downgrade it. How did you flash the FXZ? fastboot or rsd? I need to see the log of the flash.
SamuriHL said:
Um, it can't be "same issue" if it flashed properly and you did in fact do an FDR. That's not possible. So I'm guessing your flash didn't work. And no, you can't just pick a different FXZ. The phone is security locked and you'll brick it trying to downgrade it. How did you flash the FXZ? fastboot or rsd? I need to see the log of the flash.
Click to expand...
Click to collapse
Fastboot, and here's the log.
Please ensure your phone is:
o] Charged
o] Connected to USB using your OEM cable
o] USB drivers are installed
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
Ready to flash...
Press any key to continue . . .
Flashing: FULL_xt875.bat
rebooting into bootloader... OKAY [ 0.006s]
sending 'mbm' (256 KB)... OKAY [ 0.029s]
writing 'mbm'... OKAY [ 0.480s]
rebooting into bootloader... OKAY [ 0.293s]
sending 'mbmloader' (41 KB)... OKAY [ 0.011s]
writing 'mbmloader'... OKAY [ 0.288s]
sending 'mbm' (256 KB)... OKAY [ 0.314s]
writing 'mbm'... OKAY [ 0.477s]
rebooting into bootloader... OKAY [ 0.293s]
sending 'cdt.bin' (16 KB)... OKAY [ 0.008s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
rebooting into bootloader... OKAY [ 0.293s]
erasing 'cache'... OKAY [ 0.012s]
erasing 'userdata'... OKAY [ 0.012s]
error: cannot load 'lbl'
sending 'logo.bin' (854 KB)... OKAY [ 0.065s]
writing 'logo.bin'... OKAY [ 0.281s]
sending 'ebr' (16 KB)... OKAY [ 0.294s]
writing 'ebr'... OKAY [ 0.444s]
sending 'mbr' (16 KB)... OKAY [ 0.294s]
writing 'mbr'... OKAY [ 0.401s]
sending 'devtree' (512 KB)... OKAY [ 0.336s]
writing 'devtree'... OKAY [ 0.447s]
sending 'system' (262144 KB)... OKAY [ 18.319s]
writing 'system'... OKAY [ 21.761s]
sending 'system' (229120 KB)... OKAY [ 16.152s]
writing 'system'... OKAY [ 19.797s]
sending 'boot' (8192 KB)... OKAY [ 0.625s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
sending 'recovery' (9216 KB)... OKAY [ 0.949s]
writing 'recovery'... OKAY [ 1.524s]
sending 'cdrom' (12032 KB)... OKAY [ 1.167s]
writing 'cdrom'... OKAY [ 2.052s]
sending 'preinstall' (262144 KB)... OKAY [ 18.260s]
writing 'preinstall'... OKAY [ 22.709s]
sending 'preinstall' (49152 KB)... OKAY [ 3.410s]
writing 'preinstall'... OKAY [ 4.335s]
sending 'webtop' (262144 KB)... OKAY [ 18.449s]
writing 'webtop'... OKAY [ 22.590s]
sending 'webtop' (262144 KB)... OKAY [ 18.218s]
writing 'webtop'... OKAY [ 22.377s]
sending 'webtop' (262144 KB)... OKAY [ 18.481s]
writing 'webtop'... OKAY [ 21.559s]
sending 'webtop' (262144 KB)... OKAY [ 18.192s]
writing 'webtop'... OKAY [ 22.479s]
sending 'webtop' (262144 KB)... OKAY [ 18.124s]
writing 'webtop'... OKAY [ 21.669s]
sending 'webtop' (54016 KB)... OKAY [ 3.768s]
writing 'webtop'... OKAY [ 4.137s]
sending 'radio' (21896 KB)... OKAY [ 1.445s]
writing 'radio'... OKAY [ 2.697s]
rebooting...
Press any key to continue . . .
UMMMMM, you didn't notice the flash failures in there? Yea, that's bad. What is the filename of the FXZ you're flashing? Cause this isn't a good thing. When I said flashing the wrong FXZ can brick the phone I wasn't speaking hypothetically.
SamuriHL said:
UMMMMM, you didn't notice the flash failures in there? Yea, that's bad. What is the filename of the FXZ you're flashing? Cause this isn't a good thing. When I said flashing the wrong FXZ can brick the phone I wasn't speaking hypothetically.
Click to expand...
Click to collapse
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip is what I used. I see the flash failures, but have no idea what that means or why they show up. I did a few searches and didn't find anything specific.
Akivaran said:
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip is what I used. I see the flash failures, but have no idea what that means or why they show up. I did a few searches and didn't find anything specific.
Click to expand...
Click to collapse
Oh man. It means you flashed the WRONG file. And have now bricked the thing which is why it won't boot.
cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip
That is what you need to flash with. Show me the log when flashing this.
SamuriHL said:
Oh man. It means you flashed the WRONG file. And have now bricked the thing which is why it won't boot.
cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip
That is what you need to flash with. Show me the log when flashing this.
Click to expand...
Click to collapse
Will do.
OMG IT BOOTED. I about lost my crap when I heard the noise. Thank you so much for being patient with me.
What I don't understand is why I was pointed to the other files. What are those for?
They're old versions which can't be used anymore. Delete the old FXZ's so you don't run into this problem again. The sucky part is that it bricked because of the wrong FXZ so had you used the proper one in the beginning, you wouldn't have lost the data partition. Ah well.

[Q]-USB 2.0 don't work to flash system.img

C:\Program Files (x86)\Minimal ADB and Fastboot\NX629J_Z69_EN_WPJ0O_V209>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system'...
OKAY [ 0.016s]
sending sparse 'system' 1/5 (768623 KB)...
OKAY [ 26.609s]
writing 'system' 1/5...
OKAY [ 0.010s]
sending sparse 'system' 2/5 (753639 KB)...
OKAY [ 31.166s]
writing 'system' 2/5...
OKAY [ 0.010s]
sending sparse 'system' 3/5 (776366 KB)...
OKAY [ 32.717s]
writing 'system' 3/5...
OKAY [ 0.008s]
sending sparse 'system' 4/5 (786429 KB)...
OKAY [ 32.807s]
writing 'system' 4/5...
OKAY [ 0.004s]
sending sparse 'system' 5/5 (138400 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 136.141s
Click to expand...
Click to collapse
i try use usb port 3.0, nothing, i try use usb port 2.0, nothing, i try another cable, nothing....

android 12 fastboot FAILED (remote: Partition system not found)

I get my pixel 4 xl oem unlocked(auto reset after the unlock) and try to flash Android 12 beta image of below link
https://dl.google.com/developers/android/sc/images/factory/coral-spp1.210122.022-factory-0b84a8a1.zip
but durning run flash-all.sh, it failed in writing system, any idea how to deal with this?
checking product...
OKAY [ 0.070s]
checking version-bootloader...
OKAY [ 0.070s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot_b' (65536 KB)...
OKAY [ 2.810s]
writing 'boot_b'...
OKAY [ 0.221s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.459s]
writing 'dtbo_b'...
OKAY [ 0.093s]
sending sparse 'system' 1/4 (262140 KB)...
OKAY [ 10.958s]
writing 'system' 1/4...
FAILED (remote: Partition system not found)
finished. total time: 15.109s
finnally I find the issue:
the fastboot on my test machine(ubuntu20.04) need sudo fastboot to run ,and with sudo , it uses the android studio old fastboot bin. after force replace the fastboot bin to newest , the flash is good
but any idea the fastboot flash need a sudo?

Question Help with Redmi Note 10 5G: Bricked, but has access to Fastboot

Hi Everyone,
I tried to change the image of my Note 10 (Global to Europe), but I was getting this "Flash Preloader Error" midway through the update. My bootloader is unlocked, no TWRP. Any help is greatly appreciated. Thanks!
I got stuck in a fastboot loop at one point but managed to restore MIUI with XiaomiADBFastbootTools.jar from https://szaki.github.io/XiaomiADBFastbootTools/ (if that isn't already how you were installing the new image), extracting the MIUI .tgz to a folder, and going through Flasher -> Image -> Select ROM Folder -> Clean Install -> Flash ROM
skm_1 said:
I got stuck in a fastboot loop at one point but managed to restore MIUI with XiaomiADBFastbootTools.jar from https://szaki.github.io/XiaomiADBFastbootTools/ (if that isn't already how you were installing the new image), extracting the MIUI .tgz to a folder, and going through Flasher -> Image -> Select ROM Folder -> Clean Install -> Flash ROM
Click to expand...
Click to collapse
Thanks, will try this! BTW, will there be an issue, if the device is MTK? Been reading there is a difference in approaches when dealing with MTK devices.
Xtrobe13 said:
BTW, will there be an issue, if the device is MTK? Been reading there is a difference in approaches when dealing with MTK devices.
Click to expand...
Click to collapse
Couldn't say for sure. CPU-Z says my phone has ARM Cortex-A55 and ARM Cortex-A76
Xtrobe13 said:
Thanks, will try this! BTW, will there be an issue, if the device is MTK? Been reading there is a difference in approaches when dealing with MTK devices.
Click to expand...
Click to collapse
i have flashed global miui on my phone that have stock europe without problem
wetito said:
i have flashed global miui on my phone that have stock europe without problem
Click to expand...
Click to collapse
Thanks for the verification.
So, I managed to install it using the tool successfully, but when I rebooted, I end up with the "dm-verity corrupt" error. I tried this approach, but it didn't work: https://forum.xda-developers.com/t/root-gained.4290689/. Now, I end up with the device going into the logo, then going back to fastboot.
Am I missing something?
I also had the dm-verity error at one point and IIRC I fixed it with the steps from "fastboot --disable-verity" onwards on the first post in https://forum.xda-developers.com/t/...s-on-redmi-note-10-5g-poco-m3-pro-5g.4346983/, using the vbmeta.img attached further down on the same page
skm_1 said:
I also had the dm-verity error at one point and IIRC I fixed it with the steps from "fastboot --disable-verity" onwards on the first post in https://forum.xda-developers.com/t/...s-on-redmi-note-10-5g-poco-m3-pro-5g.4346983/, using the vbmeta.img attached further down on the same page
Click to expand...
Click to collapse
I see. I actually tried that, but no dice. What happens now is that my phone ends up stuck in the redmi boot logo and doesn't go anywhere (I think I ended up all night, and nothing happened). Wishing there was a way to check what the reall error is actually.
are you shure you flash the eea firmware? dm verity error appen when you flash china firmware on global or eea firmware. global and eea firmwares all fully compatibles. i'm 100% because i switched between these more than one time. now i'm on 12.5.2 global, but my original stock was eea branded. have you unlocked the bootloader? you have to do
wetito said:
are you shure you flash the eea firmware? dm verity error appen when you flash china firmware on global or eea firmware. global and eea firmwares all fully compatibles. i'm 100% because i switched between these more than one time. now i'm on 12.5.2 global, but my original stock was eea branded. have you unlocked the bootloader? you have to do
Click to expand...
Click to collapse
Yes, I made sure I didn't use the China firmware. I already tried the Global, EEA, and Indonesia firmwares, but nothing worked. The bootloader is unlocked as well.
This is what I get with the update:
C:\Users\RAD\XiaomiADBFastbootTools>fastboot erase boot ||
Erasing 'boot_a' OKAY [ 2.237s]
Finished. Total time: 2.239s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot erase metadata ||
Erasing 'metadata' OKAY [ 1.146s]
Finished. Total time: 1.148s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash preloader F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\preloader_camellia.bin ||
Sending 'preloader_a' (376 KB) OKAY [ 0.026s]
Writing 'preloader_a' OKAY [ 0.004s]
Finished. Total time: 0.032s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash logo F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\logo.bin ||
Sending 'logo' (2174 KB) OKAY [ 0.075s]
Writing 'logo' OKAY [ 0.009s]
Finished. Total time: 0.086s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash tee_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\tee.img ||
Sending 'tee_a' (2525 KB) OKAY [ 0.086s]
Writing 'tee_a' OKAY [ 0.011s]
Finished. Total time: 0.099s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash tee_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\tee.img ||
Sending 'tee_b' (2525 KB) OKAY [ 0.084s]
Writing 'tee_b' OKAY [ 0.011s]
Finished. Total time: 0.096s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash scp_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\scp.img ||
Sending 'scp_a' (1185 KB) OKAY [ 0.048s]
Writing 'scp_a' OKAY [ 0.006s]
Finished. Total time: 0.057s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash scp_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\scp.img ||
Sending 'scp_b' (1185 KB) OKAY [ 0.049s]
Writing 'scp_b' OKAY [ 0.007s]
Finished. Total time: 0.061s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash sspm_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\sspm.img ||
Sending 'sspm_a' (646 KB) OKAY [ 0.033s]
Writing 'sspm_a' OKAY [ 0.005s]
Finished. Total time: 0.040s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash sspm_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\sspm.img ||
Sending 'sspm_b' (646 KB) OKAY [ 0.033s]
Writing 'sspm_b' OKAY [ 0.005s]
Finished. Total time: 0.040s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash lk_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\lk.img ||
Sending 'lk_a' (1558 KB) OKAY [ 0.059s]
Writing 'lk_a' OKAY [ 0.009s]
Finished. Total time: 0.070s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash lk_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\lk.img ||
Sending 'lk_b' (1558 KB) OKAY [ 0.059s]
Writing 'lk_b' OKAY [ 0.008s]
Finished. Total time: 0.070s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash super F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\super.img ||
Sending sparse 'super' 1/43 (131066 KB) OKAY [ 3.664s]
Writing 'super' OKAY [ 1.196s]
Sending sparse 'super' 2/43 (130868 KB) OKAY [ 3.626s]
Writing 'super' OKAY [ 0.759s]
Sending sparse 'super' 3/43 (130892 KB) OKAY [ 3.621s]
Writing 'super' OKAY [ 0.749s]
Sending sparse 'super' 4/43 (130905 KB) OKAY [ 3.809s]
Writing 'super' OKAY [ 0.781s]
Sending sparse 'super' 5/43 (130781 KB) OKAY [ 3.675s]
Writing 'super' OKAY [ 0.950s]
Sending sparse 'super' 6/43 (130267 KB) OKAY [ 3.787s]
Writing 'super' OKAY [ 1.516s]
Sending sparse 'super' 7/43 (130821 KB) OKAY [ 3.710s]
Writing 'super' OKAY [ 0.921s]
Sending sparse 'super' 8/43 (131020 KB) OKAY [ 3.627s]
Writing 'super' OKAY [ 0.539s]
Sending sparse 'super' 9/43 (130706 KB) OKAY [ 3.641s]
Writing 'super' OKAY [ 1.177s]
Sending sparse 'super' 10/43 (130797 KB) OKAY [ 3.656s]
Writing 'super' OKAY [ 0.892s]
Sending sparse 'super' 11/43 (127149 KB) OKAY [ 3.662s]
Writing 'super' OKAY [ 3.634s]
Sending sparse 'super' 12/43 (125865 KB) OKAY [ 3.629s]
Writing 'super' OKAY [ 1.066s]
Sending sparse 'super' 13/43 (120136 KB) OKAY [ 3.304s]
Writing 'super' OKAY [ 0.677s]
Sending sparse 'super' 14/43 (122952 KB) OKAY [ 3.405s]
Writing 'super' OKAY [ 0.593s]
Sending sparse 'super' 15/43 (126212 KB) OKAY [ 3.527s]
Writing 'super' OKAY [ 0.570s]
Sending sparse 'super' 16/43 (128752 KB) OKAY [ 3.610s]
Writing 'super' OKAY [ 0.623s]
Sending sparse 'super' 17/43 (131052 KB) OKAY [ 3.618s]
Writing 'super' OKAY [ 0.515s]
Sending sparse 'super' 18/43 (131040 KB) OKAY [ 3.639s]
Writing 'super' OKAY [ 0.535s]
Sending sparse 'super' 19/43 (130505 KB) OKAY [ 3.604s]
Writing 'super' OKAY [ 0.814s]
Sending sparse 'super' 20/43 (131032 KB) OKAY [ 3.622s]
Writing 'super' OKAY [ 0.560s]
Sending sparse 'super' 21/43 (130905 KB) OKAY [ 3.659s]
Writing 'super' OKAY [ 0.839s]
Sending sparse 'super' 22/43 (130988 KB) OKAY [ 3.622s]
Writing 'super' OKAY [ 0.618s]
Sending sparse 'super' 23/43 (130968 KB) OKAY [ 3.623s]
Writing 'super' OKAY [ 0.562s]
Sending sparse 'super' 24/43 (130645 KB) OKAY [ 3.737s]
Writing 'super' OKAY [ 1.090s]
Sending sparse 'super' 25/43 (125864 KB) OKAY [ 3.779s]
Writing 'super' OKAY [ 10.468s]
Sending sparse 'super' 26/43 (131056 KB) OKAY [ 3.629s]
Writing 'super' OKAY [ 0.488s]
Sending sparse 'super' 27/43 (130848 KB) OKAY [ 3.625s]
Writing 'super' OKAY [ 0.712s]
Sending sparse 'super' 28/43 (130828 KB) OKAY [ 3.627s]
Writing 'super' OKAY [ 0.549s]
Sending sparse 'super' 29/43 (130776 KB) OKAY [ 3.622s]
Writing 'super' OKAY [ 0.675s]
Sending sparse 'super' 30/43 (131056 KB) OKAY [ 3.637s]
Writing 'super' OKAY [ 0.553s]
Sending sparse 'super' 31/43 (130689 KB) OKAY [ 3.639s]
Writing 'super' OKAY [ 0.896s]
Sending sparse 'super' 32/43 (130992 KB) OKAY [ 3.635s]
Writing 'super' OKAY [ 0.643s]
Sending sparse 'super' 33/43 (130199 KB) OKAY [ 3.646s]
Writing 'super' OKAY [ 1.807s]
Sending sparse 'super' 34/43 (130408 KB) OKAY [ 3.681s]
Writing 'super' OKAY [ 1.739s]
Sending sparse 'super' 35/43 (130916 KB) OKAY [ 3.650s]
Writing 'super' OKAY [ 0.693s]
Sending sparse 'super' 36/43 (130384 KB) OKAY [ 3.659s]
Writing 'super' OKAY [ 1.816s]
Sending sparse 'super' 37/43 (131069 KB) OKAY [ 3.681s]
Writing 'super' OKAY [ 2.166s]
Sending sparse 'super' 38/43 (128772 KB) OKAY [ 3.572s]
Writing 'super' OKAY [ 0.592s]
Sending sparse 'super' 39/43 (119316 KB) OKAY [ 3.322s]
Writing 'super' OKAY [ 0.556s]
Sending sparse 'super' 40/43 (115328 KB) OKAY [ 3.203s]
Writing 'super' OKAY [ 0.546s]
Sending sparse 'super' 41/43 (131068 KB) OKAY [ 3.635s]
Writing 'super' OKAY [ 0.581s]
Sending sparse 'super' 42/43 (131068 KB) OKAY [ 3.633s]
Writing 'super' OKAY [ 0.572s]
Sending sparse 'super' 43/43 (17568 KB) OKAY [ 0.498s]
Writing 'super' OKAY [ 0.100s]
Finished. Total time: 201.198s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash boot_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\boot.img ||
Sending 'boot_a' (65536 KB) OKAY [ 1.819s]
Writing 'boot_a' OKAY [ 0.217s]
Finished. Total time: 2.593s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash boot_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\boot.img ||
Sending 'boot_b' (65536 KB) OKAY [ 1.816s]
Writing 'boot_b' OKAY [ 0.218s]
Finished. Total time: 2.591s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash dtbo_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\dtbo.img ||
Sending 'dtbo_a' (147 KB) OKAY [ 0.018s]
Writing 'dtbo_a' OKAY [ 0.003s]
Finished. Total time: 0.023s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash dtbo_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\dtbo.img ||
Sending 'dtbo_b' (147 KB) OKAY [ 0.019s]
Writing 'dtbo_b' OKAY [ 0.002s]
Finished. Total time: 0.023s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash rescue F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\rescue.img ||
Sending 'rescue' (40 KB) OKAY [ 0.015s]
Writing 'rescue' OKAY [ 0.022s]
Finished. Total time: 0.040s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash vbmeta_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\vbmeta.img ||
Sending 'vbmeta_a' (4 KB) OKAY [ 0.014s]
Writing 'vbmeta_a' OKAY [ 0.001s]
Finished. Total time: 0.017s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash vbmeta_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\vbmeta.img ||
Sending 'vbmeta_b' (4 KB) OKAY [ 0.015s]
Writing 'vbmeta_b' OKAY [ 0.001s]
Finished. Total time: 0.017s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash spmfw_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\spmfw.img ||
Sending 'spmfw_a' (14 KB) OKAY [ 0.015s]
Writing 'spmfw_a' OKAY [ 0.001s]
Finished. Total time: 0.017s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash spmfw_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\spmfw.img ||
Sending 'spmfw_b' (14 KB) OKAY [ 0.015s]
Writing 'spmfw_b' OKAY [ 0.001s]
Finished. Total time: 0.017s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash pi_img_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\pi_img.img ||
Sending 'pi_img_a' (5 KB) OKAY [ 0.015s]
Writing 'pi_img_a' OKAY [ 0.001s]
Finished. Total time: 0.017s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash pi_img_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\pi_img.img ||
Sending 'pi_img_b' (5 KB) OKAY [ 0.014s]
Writing 'pi_img_b' OKAY [ 0.001s]
Finished. Total time: 0.018s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash dpm_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\dpm.img ||
Sending 'dpm_a' (143 KB) OKAY [ 0.018s]
Writing 'dpm_a' OKAY [ 0.003s]
Finished. Total time: 0.023s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash dpm_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\dpm.img ||
Sending 'dpm_b' (143 KB) OKAY [ 0.018s]
Writing 'dpm_b' OKAY [ 0.003s]
Finished. Total time: 0.023s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash mcupm_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\mcupm.img ||
Sending 'mcupm_a' (433 KB) OKAY [ 0.026s]
Writing 'mcupm_a' OKAY [ 0.005s]
Finished. Total time: 0.033s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash mcupm_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\mcupm.img ||
Sending 'mcupm_b' (433 KB) OKAY [ 0.026s]
Writing 'mcupm_b' OKAY [ 0.005s]
Finished. Total time: 0.032s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash gz_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\gz.img ||
Sending 'gz_a' (1977 KB) OKAY [ 0.068s]
Writing 'gz_a' OKAY [ 0.020s]
Finished. Total time: 0.089s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash gz_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\gz.img ||
Sending 'gz_b' (1977 KB) OKAY [ 0.069s]
Writing 'gz_b' OKAY [ 0.010s]
Finished. Total time: 0.081s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash md1img_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\md1img.img ||
Sending 'md1img_a' (60680 KB) OKAY [ 1.671s]
Writing 'md1img_a' OKAY [ 0.247s]
Finished. Total time: 1.920s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash md1img_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\md1img.img ||
Sending 'md1img_b' (60680 KB) OKAY [ 1.665s]
Writing 'md1img_b' OKAY [ 0.204s]
Finished. Total time: 1.870s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash vbmeta_system_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\vbmeta_system.img ||
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.015s]
Writing 'vbmeta_system_a' OKAY [ 0.001s]
Finished. Total time: 0.018s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash vbmeta_vendor_a F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\vbmeta_vendor.img ||
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.015s]
Writing 'vbmeta_vendor_a' OKAY [ 0.001s]
Finished. Total time: 0.018s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash vbmeta_system_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\vbmeta_system.img ||
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.014s]
Writing 'vbmeta_system_b' OKAY [ 0.001s]
Finished. Total time: 0.017s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash vbmeta_vendor_b F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\vbmeta_vendor.img ||
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.014s]
Writing 'vbmeta_vendor_b' OKAY [ 0.001s]
Finished. Total time: 0.018s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash cust F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\cust.img ||
Sending sparse 'cust' 1/6 (129672 KB) OKAY [ 3.584s]
Writing 'cust' OKAY [ 0.492s]
Sending sparse 'cust' 2/6 (129012 KB) OKAY [ 3.574s]
Writing 'cust' OKAY [ 0.451s]
Sending sparse 'cust' 3/6 (129028 KB) OKAY [ 3.581s]
Writing 'cust' OKAY [ 0.478s]
Sending sparse 'cust' 4/6 (129016 KB) OKAY [ 3.583s]
Writing 'cust' OKAY [ 0.521s]
Sending sparse 'cust' 5/6 (131068 KB) OKAY [ 3.638s]
Writing 'cust' OKAY [ 0.460s]
Sending sparse 'cust' 6/6 (103536 KB) OKAY [ 2.878s]
Writing 'cust' OKAY [ 0.407s]
Finished. Total time: 23.652s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot flash userdata F:\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5\camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global\\images\userdata.img ||
Sending sparse 'userdata' 1/14 (131068 KB) OKAY [ 3.613s]
Writing 'userdata' OKAY [ 0.660s]
Sending sparse 'userdata' 2/14 (131068 KB) OKAY [ 3.630s]
Writing 'userdata' OKAY [ 0.492s]
Sending sparse 'userdata' 3/14 (131068 KB) OKAY [ 3.651s]
Writing 'userdata' OKAY [ 0.485s]
Sending sparse 'userdata' 4/14 (131068 KB) OKAY [ 3.635s]
Writing 'userdata' OKAY [ 0.498s]
Sending sparse 'userdata' 5/14 (131068 KB) OKAY [ 3.629s]
Writing 'userdata' OKAY [ 0.460s]
Sending sparse 'userdata' 6/14 (131068 KB) OKAY [ 3.639s]
Writing 'userdata' OKAY [ 0.496s]
Sending sparse 'userdata' 7/14 (131068 KB) OKAY [ 3.628s]
Writing 'userdata' OKAY [ 0.527s]
Sending sparse 'userdata' 8/14 (131068 KB) OKAY [ 3.639s]
Writing 'userdata' OKAY [ 0.458s]
Sending sparse 'userdata' 9/14 (131068 KB) OKAY [ 3.623s]
Writing 'userdata' OKAY [ 0.487s]
Sending sparse 'userdata' 10/14 (131068 KB) OKAY [ 3.635s]
Writing 'userdata' OKAY [ 0.498s]
Sending sparse 'userdata' 11/14 (131068 KB) OKAY [ 3.629s]
Writing 'userdata' OKAY [ 0.461s]
Sending sparse 'userdata' 12/14 (131068 KB) OKAY [ 3.661s]
Writing 'userdata' OKAY [ 0.491s]
Sending sparse 'userdata' 13/14 (131068 KB) OKAY [ 3.629s]
Writing 'userdata' OKAY [ 0.527s]
Sending sparse 'userdata' 14/14 (58496 KB) OKAY [ 1.626s]
Writing 'userdata' OKAY [ 0.213s]
Finished. Total time: 55.625s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot set_active a ||
Setting current slot to 'a' OKAY [ 0.001s]
Finished. Total time: 0.001s
C:\Users\RAD\XiaomiADBFastbootTools>fastboot reboot ||
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Done!
No matter what version I use, I still end up with a 'dm-verity corrupt' error. If I try to replace it with a blank vbmeta.img, I end up going to fastboot. Not sure what to do anymore, to be honest.
the error at the end of flashing is normal, but in my case when i boot phone all work fine
wetito said:
the error at the end of flashing is normal, but in my case when i boot phone all work fine
Click to expand...
Click to collapse
The weird part is that when I use the XiaomiTool V2, and goes to fastboot, it can't identify my phone codename. It's as if the firmware never existed.
use miflash, not xiaomi tool
Did you definitely use "fastboot reboot fastboot" before carrying out these steps? The phone should display "FASTBOOTD" in yellow (I think), not "FASTBOOT" in blue
skm_1 said:
Did you definitely use "fastboot reboot fastboot" before carrying out these steps? The phone should display "FASTBOOTD" in yellow (I think), not "FASTBOOT" in blue
Click to expand...
Click to collapse
Sorry, it just saw FASTBOOT. I just saw this instruction now. It tried it, but it wouldn't go to fastbootd. It simply showed the list of commands for fastboot.
wetito said:
use miflash, not xiaomi tool
Click to expand...
Click to collapse
I tried using the latest MiFlash (2021.2.26.0), now, I'm getting this error
"error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done"
Any thoughts on this?
Ah, did you install the fastbootd drivers? I think there's a video showing how to do it in Windows on the same page with the fastboot commands. (I used the Android platform tools on Linux.)
Xtrobe13 said:
I tried using the latest MiFlash (2021.2.26.0), now, I'm getting this error
"error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done"
Any thoughts on this?
Click to expand...
Click to collapse
lock?!? what option have u selected? i hope flash all, not flash and lock. or u made a damage
wetito said:
lock?!? what option have u selected? i hope flash all, not flash and lock. or u made a damage
Click to expand...
Click to collapse
I used the Clean All Settings. I got this image (camellian_id_global_images_V12.0.4.0.RKSIDXM_20210813.0000.00_11.0_global_e8b6b36cdd), and it now seems to work! The DM-Verity error can now be loaded with a blank one, and my phone now boots as normally.

[SHARE] SailfishOS 4.4.0.64 for Pro¹ X

We will flash the ubuntu touch boot image which is required temporarily. And the currently latest sfos build for the QX1050.
1. Download ubuntu touch build from here and extract the boot.img
Ubuntu for Pro¹ X build job 2830649718 artifact.zip
2. Download SailfishOS 4.4.0.64 build from here and extract the userdata.simg
SailfishOS for Pro¹ X job 2807435728 artifact.zip
3. Flash using fastboot
Code:
fastboot flash boot_a boot.img
fastboot flash userdata userdata.simg
4. Reboot using fastboot reboot or fastboot continue
Thanks for moving mods! Did not realize its more appropriate here in the guides section than in the development section.
fastboot flash userdata userdata.img
fastboot flash userdata userdata.simg Typo
Nope, the sailfish userdata is in sparse format. So its .simg correctly.
Thats why you will not have the infamous "Invalid sparse file format at header magic" message from fastboot when flashing that .simg. Since fastboot expects sparse images, but *****es about raw images like the ubuntu boot.img above.
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
bobnot said:
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
Click to expand...
Click to collapse
what version of the android platform tools are you using? I'm on r33.0.2 and "fastboot flash userdata userdata.simg" works just fine for me
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
eltmosen said:
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
Click to expand...
Click to collapse
Neither SFOS or UT will boot
I also updated to latest fastboot from googles source. Still same issue as previously stated.

Categories

Resources