Database Info

fastboot failed:image update error

Hi all,
My friends HTC One SV has got itself stuck on the boot screen. Also I cannot enter recovery mode (Selecting "recovery" just vibrates, shows the android skaters, and then goes back to hboot).
After booting into hboot and then fastboot usb, I'm trying to flash a new recovery image or a new boot.img. Unfortunately I get this output:
Code:
>fastboot.exe devices
HT31KTP01681 fastboot
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxx
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
>fastboot flash recovery TWRP-2.7.0.1-k2_ul-k2u.img
sending 'recovery' (8452 KB)...
OKAY [ 1.203s]
writing 'recovery'...
[B]FAILED (remote: image update error)[/B]
finished. total time: 2.513s
>fastboot flash boot images\422_k2ul_stock_kernel\boot.img
sending 'boot' (6160 KB)...
OKAY [ 0.911s]
writing 'boot'...
[B]FAILED (remote: image update error)[/B]
finished. total time: 2.224s
Anyone else seen this and know if its fixable?
Info at the top of hboot:
Code:
TAMPERED
UNLOCKED
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
OS-
eMMC-boot 1024MB
Nov 7 2013 15:32:31.0

@captainbadger
First: removed the serial number also from you fastboot devices result, please.
Then, have you tried another recovery build too? This one should also work on your hboot.
About the hboot: you can't update your hboot when the device is S-On.
What you can try, (if you can't flash recovery) is to flash again the whole firmware package. But as far as i know you must lock the bootloader for that and i don't know if you can flash the same firmware on the already same installed firmware.
But you have not much options for a S-on device, which don't has a working custom recovery.
A small F.A.Q. to understand things. Not written for k2ul but most likely similar.

Yep I tried another recovery just to be certain. No luck.

Then you should maybe really lock the device and try to flash the firmware.zip.
And maybe then you have more luck with recovery.

OK.
I need to reflash firmware.zip.
To do that I need to relock the bootloader.
To do that I need S-Off.
To do that I need to install and run firewater
To do that I need to get a working adb shell connection.
That doesn't work. The only working connection I have is fastboot. I assume that adb requires the OS to be up and running. This isn't the case.

You can relock your bootloader with fastboot cmd:
Code:
fastboot oem lock
Then you should be able to flash a signed (by HTC) firmware.zip, also when you are S-on.
The firmware.zip you need, you can get here: http://d-h.st/uwh
How to flash, you'll find in the linked FAQ in post #2.

old.splatterhand said:
You can relock your bootloader with fastboot cmd:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Nah doesn't work:
Code:
C:\adt\sdk\platform-tools>fastboot oem lock
...
(bootloader) SD: write failed in CMD25.
(bootloader) [PG_ERROR] htc_pg_part_update(982):
(bootloader) sd_write_sector failed
(bootloader) [PG_ERROR] htc_pg_part_traverse(930):
(bootloader) fn return error
(bootloader) Lock successfully...
(bootloader) mipi_dsi_panel_off
(bootloader) **** This command mode dma test is failed ****
(bootloader) pm8038_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
FAILED (status read failed (Too many links))
finished. total time: 2.283s
C:\adt\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.228s]
finished. total time: 1.228s
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.140s

Ok, but then i'm sorry, i don't have a idea, whats wrong with your device.

Yeah seems like a hardware issue. It has a cracked screen so maybe that's what caused it. Thanks for the advice anyway.

Pop quiz folks! Has any of you experienced problems with installing a Splash screen using HBoot 2.21? I can't even find which partition it is currently stored on an I checked all 38 of them. Any ideas from you guys?
Sent from my C525c using Tapatalk
---------- Post added at 09:43 PM ---------- Previous post was at 09:29 PM ----------
Disregard..... It's been so long for me that I actually forgot it had to be placed at the root of the external sdcard haha. Oops!
Sent from my C525c using Tapatalk

HTC One Mini, boot loop, recovery wont work - help

Hi, first post here and its a plea for help, most probably the same way quite a few people find their way onto here!
My wife has a HTC one mini and it will power on and go straight to the "Fastboot" screen, it does this constantly. if you select restart it ends up in exactly the same place, same with the power button.
The phone had been unlocked with TWRP recovery about 6 months ago. it was flashed with a stock ROM
This has happened before a couple of times but after a couple of restart attempts it fired up normally and went into normal operation, after a little research we started to believe that it had a sticking volume down button, but now no amount of squeezing and resetting will get it to power up this time
If i select to go into recovery the screen goes blank for a split second and comes right back onto the "Fastboot" screen.
When I connect the phone to a computer the phone goes into "Fastboot USB" and the computer beeps to say something has been connected, HTC sync fires up but says no phone is connected.
With the phone plugged into the computer I can use fastboot to see it is connected but adb does not see it:
Code:
C:\adb>fastboot devices
SH3ACWA****** fastboot
C:\adb>adb devices
List of devices attached
C:\adb>
I have tried to reflash the recovery, I have tried CWM TWRP and the Stock recovery but all do this:
Code:
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 800227328 bytes
sending 'recovery' (8572 KB)...
OKAY [ 1.065s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.218s
C:\adb
I have used the command "fastboot oem boot" and this makes the phone show a white screen with the scateboarding androinds in the centre and gives:
Code:
C:\adb>fastboot oem boot
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) [DISPLAY_ERR] read sp1 partition fail!!!
(bootloader) [ERR] Cmd17 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) CMD17: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) [ERR] Cmd17 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) CMD17: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.407s]
finished. total time: 0.409s
C:\adb>
In case this is of any help:
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3ACWA*****
(bootloader) imei: 355866056******
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-871d213f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.230s
I have also tried to fastboot flash a new ROM onto the phone (one that will not wipe the SDcard and all data), this also fails:
Code:
C:\adb>fastboot flash rom mini.zip
target reported max download size of 800227328 bytes
sending 'rom' (36992 KB)...
OKAY [ 2.731s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 8.164s
The rom was from the thread http://forum.xda-developers.com/showthread.php?t=2659109 - I have renamed the zip out of lazyness so there is less to type in CMD prompt!
I have loaded up a FUU and this seems to work, it will recognise and bring up the software number of the phone and bring up the option to update it - I haven't gone through with this as it will wipe all of the SDcard data and this against what I am trying to achieve.
I would like to get access to the phone to extract the data, whether that be by mounting it and getting the data via comuter or getting it working via another method. We have a new Mini 2 as an upgrade for this phone so it does not neccesarily need to work completely.
Any help anyone can give will be greatly appreciated,

It may be a silly idea but have you tried flashing the file without the spaces in the file name? Ie fastboot flash rom_mini.zip (you'd have to change the file name to reflect that obviously), but I've had it happen on my nexus before a recovery just wouldn't flash because of the spaces in the zip's file name. It's worth a shot. If it still fails then I'd look into that signature verification error you're getting.

Have you managed to solve the issue? I in exactly the same situation as you are/were.

I'm having similar issues with a One Mini I got off of Craigslist for $40. For me the biggest issue (as far as I can tell) is that the security is still enabled (S-ON) and it appears you have a similar issue ("security: on" result from your "getvar" command). From what I've found on the forums here flashing the original ROM should bring it back to life (which you tried) but it didn't work for me either. I should mention, HTC drivers installed (of course ), fastboot will recognize it but adb won't.
The bootloader screen for me.
Code:
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT—2.22.0000
OS—4.09.631.2
eMMC—boot 1024MB
Jun 23 2014, 13:57:59.0
FASTBOOT USB
etc etc...
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.631.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3B1WA*****
(bootloader) imei: 3564820507*****
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5822000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3850mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.553s

A bit of an update with a couple things I've tried. I was thinking that being unable to find my device with adb could be messed up drivers, and found someone else on the forums that had a post precisely about this [http://forum.xda-developers.com/showpost.php?p=60834905&postcount=7]. Using Ubuntu is apparently an option, and as I dual-boot Ubuntu 14.04 LTS and Win7 x64 I figured I would give it a shot. Followed 'jollywhitefoot's' instructions on installing the necessary repositories, and then fastboot and adb. I could detect the device using 'sudo fastboot devices' but adb still wouldn't recognize it ('sudo adb devices'), returning a blank list. I also attempted to install the latest TWRP, to no avail. Perhaps the person who messed up the phone in the first place never enabled USB debugging.
If anyone out there has an idea of what I'm missing here, I would appreciate a little help. If not, I'll keep plugging away and see what else I can find to try. Thanks!
Code:
[email protected]********:~$ sudo fastboot flash recovery /usr/bin/twrp.img
target reported max download size of 800227328 bytes
sending 'recovery' (11460 KB)...
OKAY [ 1.636s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.777s
-- EDIT 1 --
I should add a few details. I've attempted to unlock the phone using HTCdev from both Windows and now Ubuntu and I supposedly get a valid unlock but never do see the bootloader screen change to reflect that (always stays at '*** LOCKED ***'). I'll post one of the sample outputs below.
Code:
[email protected]********:~/Downloads$ sudo fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s
-- EDIT 2 --
I've tried to flash a few different recoveries, in the hope that one would work. Unfortunately I couldn't find the stock recovery anywhere, I'm guessing that would have the highest chance of working. The three I tried were from here [http://forum.xda-developers.com/htc-one-mini/development/mega-index-roms-recoveries-mods-kernels-t2835180]. I also grapped a dmesg dump, it appears that something with the "SD card" (I know the Mini doesn't have one, but that's what it reports it's storage as) is causing problems, though I'm not sure if this is due to a lack of a formatted partition, or rather super-aggressive writes and thus failing memory.
Code:
(bootloader) [6:9:29.394207] fastboot_command:[erase:cache]
(bootloader) [6:9:29.403677]
(bootloader) eMMC Manufacturer ID: 15
(bootloader) [6:9:29.415209] [ERR] Cmd35 polling status timed out, MCI_ST
(bootloader) ATUS: 0x4C0000
(bootloader) [6:9:29.419677] [ERR] sdcc_command: sdcc_poll_status error,
(bootloader) rc: 2
(bootloader) [6:9:29.421825] sdcc_erase, CMD35 fail
(bootloader) [6:9:29.425520] emmc_erase(2704): sd_erase_sector failed!
Buzz84, I think it's apparent now that my problem could be quite different than yours, I shouldn't have opened up your thread again but I originally thought we had very identical problems!

Anyone made any headway here? My One Mini was sitting in a drawer for months and now that my primary phone got stolen, I need it. Same problem as the others. It just goes right to fastboot and refuses to do anything else. Here's my info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37G*****
(bootloader) imei: ********
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Side note: Does anyone know how to unlock the bootloader without access to the OS? The HTC unlock token requires access to the OS to confirm via pop up.

Solution found
In case anyone still encounter this problem, here's a solution.
everybody has the same cure which is put the phone into constant boot loop so that in between loops the battery takes a little bit of a charge until eventually it has enough, i sorted mine out by plugging in the phone then wrapping a strong elastic band around the bottom of phone and the power button which will keep the power button pressed and the phone will keep looping until it gets enough charge, once you see the htc logo release the band before it goes into another loop.
Click to expand...
Click to collapse

htc mini loop
Hi to all,i just waste 10 hours looking for solution so for now i dont have no luck. Try it all all for one tool,windroid tool,i try from fast boot to just make small step but NO..... htc mini is stuk in fastboot mode,pc see htc as other device tru cmd -powershell everything i try had eror or remote eror. With windroid and htcdev page i got unlock-bin file and after doing steps when they say that my bootlader is unlock it is not. tru cmd the same with unlock bin file. I dont have idea how to bypass that signature chek. if someone have idea Imglad to hear it.

[Q] Problem with XT1032 and everything, not bricked

Hi guys, last day a friend give to me a moto g because he dont know how to repair it.
He said that upgrade to 4.4.4 android and install an app that cause every app stop unexpectedly, u cant do anything cause this popups and every change u do like enable usb debbuging dont work.
At 1st i try to do a hard reset with "Android system recovery <3e> KXB21.14-L1.40", wipe data and cache then reboot but nothing wiped, android boot like nothing happens.
Then i try to install custom recovery with fastboot (CWM, TWRP) and everything looks fine just like all the guides says, the same logs with success.
Then i go to recovery mode from fastboot flash mode in and again load "Android system recovery" no CWM or TWRP.
When this happens i try to install the stock rom from BR with fastboot, no error msg or warning in fastboot and everything looks fine in fastload, i write a batch file to dont misspell something
Code:
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot erase cache
fastboot erase userdata
fastboot reboot
The device reboot and again, nothing happens, just boot like i dont write anything.
I try with a lot of imgs and guides, but nothing work for me.
Someone have an idea of whats happens here? The device looks frozen or something like that, i write-erase-remove and nothing happens.
I dont know if this is a kind of brick or something.
I would greatly appreciate any help you can give me!
PS: Sorry for my bad english, first time here.

Flash TWRP or CWM again, after it flashes, do not reboot the phone, use the volume buttons to go to recovery from the fastboot menu.

In pc
Code:
D:\android-sdk\platform-tools>fastboot flash recovery clockworkmodrecovery.6051
falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (8430 KB)...
OKAY [ 0.296s]
writing 'recovery'...
OKAY [ 0.158s]
finished. total time: 0.458s
In phone
Attached files
Without reboot

Is the stock 4.4.4 ROM available for the phone? I see you tried the BR ROM already.

audit13 said:
Is the stock 4.4.4 ROM available for the phone? I see you tried the BR ROM already.
Click to expand...
Click to collapse
Yup, not working
Code:
D:\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9300GIDO
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: D31D11040F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Aug 21 23:56:54 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxcl/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.AmericaMovil.en.CL
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 05:07:35 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.182s
Don't know if that help

Same problem here... Any solution? I'm on lollipop eu
Sent from my XT1032 using XDA Free mobile app

Halp!

I have the same issue
Is there anything we can try on that phone?

I have the same problem, it's over a month already

Hi,
i sent my phone to authorized service and they said that it is broken motherboard or memory. I had unlocked bootloader so they canceled my warranty and sent it back with note that they won't repair it becouse it is not worth it. So thats all with motorola. It was my first motorola phone and i will never buy their products again. I had this for for 6 months...
Greetings form Białystok, Polska.

damn i guess I'm taking a huge risk here buying this then http://www.kijiji.ca/v-cell-phone/city-of-toronto/moto-g-2nd-gen-2014/1066867806

flash from stable PIE to custom gone bad

I booted into blue_spark_v2 twrp and wiped system, data, and cache. flashed the new 9/24 havoc and blue_spark_v2 and rebooted into recovery to flash open_sapps and magisk. This is where it all went wrong.. I'm not hard bricked as I am in bootloader so I have fastboot options, however, I cannotboot twrp as it gives me :
[email protected]:/home/bkeaver/Downloads/PIE# fastboot boot twrp-3.2.3-x_blu_spark_v9.85v2_op6.img
downloading 'boot.img'...
OKAY [ 0.738s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.754s
[email protected]:/home/bkeaver/Downloads/PIE#
nothing I do is working.. if do a fastboot getvar all I see the following for slot info.:
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
I can't seem to switch to the other slot or get anywhere.. Some help from someone would be great if possible and I would appreciate it. also I am on a linux computer and don't have access to windows...

bkeaver said:
I booted into blue_spark_v2 twrp and wiped system, data, and cache. flashed the new 9/24 havoc and blue_spark_v2 and rebooted into recovery to flash open_sapps and magisk. This is where it all went wrong.. I'm not hard bricked as I am in bootloader so I have fastboot options, however, I cannotboot twrp as it gives me :
[email protected]:/home/bkeaver/Downloads/PIE# fastboot boot twrp-3.2.3-x_blu_spark_v9.85v2_op6.img
downloading 'boot.img'...
OKAY [ 0.738s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.754s
[email protected]:/home/bkeaver/Downloads/PIE#
nothing I do is working.. if do a fastboot getvar all I see the following for slot info.:
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
I can't seem to switch to the other slot or get anywhere.. Some help from someone would be great if possible and I would appreciate it. also I am on a linux computer and don't have access to windows...
Click to expand...
Click to collapse
Go to guides forum and download fastboot flashable firmware and flash full firmware. Just follow the thread instructions and you be fine. Had your problem to

nickwarn said:
Go to guides forum and download fastboot flashable firmware and flash full firmware. Just follow the thread instructions and you be fine. Had your problem to
Click to expand...
Click to collapse
Thanks! I will give it a shot.. I didn't see that when I looked through those threads..

error (mismatched partition size)

i have motorla xt1032 falcon
when flash it have error (mismatched partition size) i cannt flash recovery i can only "fastboot boot twrp.img"
My phone is formatted, but nothing is erased, the previous firmware and information remain. I did this with fastboot and Twrp, and the result was the same. I change the format of the partition in T, it says done, but the format does not change.
i want t change format type to ex4 but no changing only say do it
i thing my device is lock or lost it
please help

Ignore mismatch partition size error and boot into recovery using vol key. then try to install SU then try formatting again.
If problem remains try restoring stock.
Otherwise EMMC error.

engage4 said:
Ignore mismatch partition size error and boot into recovery using vol key. then try to install SU then try formatting again.
If problem remains try restoring stock.
Otherwise EMMC error.
Click to expand...
Click to collapse
i cannt flash anything.when flash show error
i can only load boot twrp and cannot flash anything
now how instal SU?
in fastboot with this command i want to instal it but have error
fastboot flash zip superSu.zip
C:\adb>fastboot flash zip su.zip
(bootloader) has-slot:zip: not found
(bootloader) is-logical:zip: not found
Sending 'zip' (1156 KB) OKAY [ 0.058s]
Writing 'zip' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
for flashing boot have this error
fastboot flash recovery twrp.img
C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (9456 KB) OKAY [ 0.358s]
Writing 'recovery' OKAY [ 0.229s]
Finished. Total time: 0.699s

After flashing twrp do not reboot phone. just use vol button to enter recovery. otherwise stock recovery will overwrite twrp.

engage4 said:
After flashing twrp do not reboot phone. just use vol button to enter recovery. otherwise stock recovery will overwrite twrp.
Click to expand...
Click to collapse
i cannot flash any recovery
only load boot orginal and twrp but dont work all command

Is your phone's bootloader unlocked?

engage4 said:
Is your phone's bootloader unlocked?
Click to expand...
Click to collapse
yes bootloader is unlocki installed lineage os later
after last installation is bricked

amir58hz said:
C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (9456 KB) OKAY [ 0.358s]
Writing 'recovery' OKAY [ 0.229s]
Finished. Total time: 0.699s
Click to expand...
Click to collapse
Log shows twrp successfully written.

engage4 said:
Log shows twrp successfully written.
Click to expand...
Click to collapse
show written ok but in phone show missedmatch partion size error and select recovery and voloume up show recovery not founded
i think data is locked and phone cannot format any thing

Try flashing stock firmware using RSD lite or use xml to bat converter. If stock flashing also fails its probably emmc problem.

engage4 said:
Try flashing stock firmware using RSD lite or use xml to bat converter. If stock flashing also fails its probably emmc problem.
Click to expand...
Click to collapse
i do with rsd convertor but it have error too
boot loader slot not found in fastboot command error
my problem is it( bootloder slot not found) if it is fixed my problem will fix

Can you post getval info. Or you can try flashing https://androidfilehost.com/?fid=24499762636007299

engage4 said:
Can you post getval info. Or you can try flashing https://androidfilehost.com/?fid=24499762636007299
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA92903U33
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 180460020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Mar 6 1:38:41 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retgb/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPBS23.13-56-2/2:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.201.2.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.GB
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld27) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Feb 26 06:48:18 CST 2016
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
Finished. Total time: 0.145s

amir58hz said:
reason: UTAG "bootmode" configured as fastboot
Click to expand...
Click to collapse
Try fastboot oem fb_mode_clear

Your log looks good. use fastboot oem fb_mode_clear and check phone boots or not.
If not try flashing stock with same cid with another pc.
I think its windows driver fault.

engage4 said:
Your log looks good. use fastboot oem fb_mode_clear and check phone boot or not.
If not try flashing stock with same cid with another pc.
I think its windows driver fault.
Click to expand...
Click to collapse
C:\adb>fastboot oem fb_mode_clear
FAILED (remote: '')
fastboot: error: Command failed

Try another pc

engage4 said:
Try another pc
Click to expand...
Click to collapse
thanks bro
you think all thing is good but my conection or pc is noot good for this
i must go to my friend and try another pc or cable usb
THANKS VERY MUCH

The last thing you may try is reflashing motoboot.img. But its too dangerous(probably you will end up with dead phone).
Iam not responsible if you end up with a brick.