Database Info

[Q] htc m9 flash demo rom to stock rom

hi i have htc m9 with demo flow rom. by following htcdev instructions i managed to unlock bootloader
i flashed twrp-recovery-2.8.6.0-hima-cptb and rooted the devise with UPDATE-SuperSU-v2.48
with help of sunshine managed to s-off then i done super cid all good till now
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
i tried alot to flash it with lots of stock rom but i failed
one of the roms i tried 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed
always getting this :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip 0PJAIMG.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (74921 KB)...
OKAY [ 5.427s]
writing 'zip'...
(bootloader) HOSD CL#493992
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 7.565s
i want to flash it to stock rom. demo flow make my m9 useless phone.
plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz help

Hi I have demo unit but as per the Instructions from HTCDev I can't find and option to boot into fastboot mode.. how did you manage to do it?

Trouble Unlocking Bootloader with bricked HTC Sensation XE

Hello. I have a problem because I flashed HTC Sensation PG58IMG.zip minimal version for recovery and hboot, not the RUU.
Now I cannot even unlock bootloader needed to flash a recovery file like TWRP.
Code:
fastboot oem get_identifier_token
(bootloader) [ERR] Command error !!!
OKAY [ 0.026s]
finished. total time: 0.026s
Using adb doesn't work at all.
Code:
adb shell
error: no devices found
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.17.0011
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.50.401.1
(bootloader) serialno: SH1AWV806609
(bootloader) imei: 359118040549062
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 92e53710
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s
Looks hopeless.
What do I now?
Has anyone successfully removed the internal memory card? I have the beats audio version.

kgpdeveloper said:
Hello. I have a problem because I flashed HTC Sensation PG58IMG.zip minimal version for recovery and hboot, not the RUU.
Now I cannot even unlock bootloader needed to flash a recovery file like TWRP.
Code:
fastboot oem get_identifier_token
(bootloader) [ERR] Command error !!!
OKAY [ 0.026s]
finished. total time: 0.026s
Using adb doesn't work at all.
Code:
adb shell
error: no devices found
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.17.0011
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.50.401.1
(bootloader) serialno: SH1AWV806609
(bootloader) imei: 359118040549062
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 92e53710
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s
Looks hopeless.
What do I now?
Has anyone successfully removed the internal memory card? I have the beats audio version.
Click to expand...
Click to collapse
you are on S-OFF
you are unlocked
just a flash a custom recovery from fastboot and flash a custom rom
by the way can you boot to the android?

rzr86 said:
you are on S-OFF
you are unlocked
just a flash a custom recovery from fastboot and flash a custom rom
by the way can you boot to the android?
Click to expand...
Click to collapse
I cannot.
Plus, I cannot flash anything.
Code:
fastboot flash zip PG58IMG.zip
sending 'zip' (5333 KB)...
OKAY [ 1.457s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.477s
Or fix the issue.
Code:
fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.026s]
finished. total time: 0.026s

kgpdeveloper said:
I cannot.
Plus, I cannot flash anything.
Code:
fastboot flash zip PG58IMG.zip
sending 'zip' (5333 KB)...
OKAY [ 1.457s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.477s
Or fix the issue.
Code:
fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.026s]
finished. total time: 0.026s
Click to expand...
Click to collapse
have you enabled usb debugging mode from settings?
also don't forget to select fastboot from bootloader when you are connecting the device to the pc(in the screen should say fastboot usb)
by the way if you are trying to unlock the bootloader from htcdev site there is no need to because you are on S-OFF
do this ,flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums (important)

Google Pixel bricked: No bootloader in active slot.

Hi all, I have a google store pixel that is stuck booting only into the bootloader. It was on 7.1.1, I downgraded to 7.1 by "flash-all.bat"-ing factory image, then relocked right after. Later updated back to 7.1.1 with OTA. I was transferring files through MTP and had a random reboot while doing so. I tried again twice only to be thrown into bootloader. I suspect the phone decided to swap boot slots when I had random reboots 3 times in a row.
Never rooted, never installed TWRP.
It shows:
Code:
BL: N/A
Baseband: N/A
Product/Variant: Sailfish-US-PVT
Serial Number: FAXXXXXXXX
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Recovery does not work. It just says:
"Failed to boot recovery mode
Press volume up or down to back to menu"
"fastboot flashing unlock" does not work. The "OEM bootloader unlock" option in developer settings was not ticked.
"fastboot continue" does not work. It switches to Google logo but if I press volume up or down, it just shows the boot options on top of the Google boot splash.
"fastboot --set_active " commands do not work without bootloader unlock
Trying to use a stock recovery image with "fastboot boot boot.img" does not work.
Flashing a factory image does not work.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.775s]
writing 'bootloader_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.877s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_b' (57192 KB)...
OKAY [ 1.402s]
writing 'radio_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.503s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: XXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1610061102'.
finished. total time: 0.308s
Press any key to exit...
Here's my getvar
Code:
C:\Users\xxxxx>fastboot getvar all
< waiting for device >
(bootloader) version:0.5
(bootloader) hw-revision:PVT
(bootloader) mid:G-2PW4100
(bootloader) version-main:1.0.0.33
(bootloader) imei:xxxxxxxxxxxxxxxx
(bootloader) ramdump-mode:false
(bootloader) boot-mode:normal
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:pg2fs:no
(bootloader) has-slot:pg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slot:persist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) slot-retry-count:b:2
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4262000
(bootloader) variant:US
(bootloader) secure:yes
(bootloader) unlocked:no
(bootloader) version-baseband:N/A
(bootloader) version-bootloader:N/A
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1c8d800000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:XXXXXXXXXXXX
(bootloader) kernel:lk
(bootloader) product:sailfish
all:
I don't think I did anything wrong. I flashed only stock firmware and relocked while totally stock. It's possible that I'm just a dumbass and glossed over something when relocking my bootloader leaving slot_b with no bootloader. But as far as I know, the phone was returned to "factory" condition with the flash-all.bat file.

As far as i can tell you can't even overwrite the bootloader on snapdragon 821 cpu's.
Did you try this command: fastboot update /path/to/your/RomFile.zip
The ROM file would named after something like this: image-sailfish-nmf26o.zip

Are you the Google or Verizon version. Not sure about the Google version but I thought I read something about not/don't or can't downgrade the VZW Pixel.

Fed2x said:
As far as i can tell you can't even overwrite the bootloader on snapdragon 821 cpu's.
Did you try this command: fastboot update /path/to/your/RomFile.zip
The ROM file would named after something like this: image-sailfish-nmf26o.zip
Click to expand...
Click to collapse
Fails. Bootloader is registered as N/A. Can't flash unless I'm on the specific bootloader that the package states
FernBch said:
Are you the Google or Verizon version. Not sure about the Google version but I thought I read something about not/don't or can't downgrade the VZW Pixel.
Click to expand...
Click to collapse
It's a google store pixel that can't be unlocked because I can't boot into android to enable oem unlock in the dev settings.

Perhaps downgrading caused the issue?

LeoYL said:
Perhaps downgrading caused the issue?
Click to expand...
Click to collapse
No, many did this because of bad battery life.
---------- Post added at 02:14 PM ---------- Previous post was at 02:07 PM ----------
ursubpar said:
Fails. Bootloader is registered as N/A. Can't flash unless I'm on the specific bootloader that the package states
It's a google store pixel that can't be unlocked because I can't boot into android to enable oem unlock in the dev settings.
Click to expand...
Click to collapse
Have a talk with google. I spent already several hours with google and any way to enable adb through fastboot and so on, just to realize that i neither have a real clue what has gone wrong nor what could turn your high end brick into a Pixel again.
What do you say to this?

Fed2x said:
No, many did this because of bad battery life.
---------- Post added at 02:14 PM ---------- Previous post was at 02:07 PM ----------
Have a talk with google. I spent already several hours with google and any way to enable adb through fastboot and so on, just to realize that i neither have a real clue what has gone wrong nor what could turn your high end brick into a Pixel again.
What do you say to this?
Click to expand...
Click to collapse
Had a talk with them a few days ago, should be getting a replacement soon!

Literally have the same exact issue, and tried everything I could think of. Only difference is mine was rooted with an unlocked bootloader and I still couldn't flash a stock image. I think RMA is the only course of action here.

Have you tried using Linux instead of Windows.
Use .sh instead of .bat
Sent from my Pixel using XDA-Developers mobile app

I got a similar problem today. However I did nothing to my phone, it powered off itself (I didn't know when), and can't boot anymore. When I boot into bootloader I noticed BL and Baseband became N/A.
If anyone can help please read my post with details:
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-bricked-bootloader-n-baseband-n-t3537379

--set-active = slot a
If I remember correctly
Sent from my Pixel using XDA-Developers Legacy app

Either one works:
Fastboot set_active _a
Fastboot --set-active=_a

quangtran1 said:
Either one works:
Fastboot set_active _a
Fastboot --set-active=_a
Click to expand...
Click to collapse
I have the same issue with my pixel 128gb, which btw is out of warranty, so looking for a way solution.
Since bootloader is locked, the second command gives the output as
X:\adb>fastboot --set-active=_a
Setting current slot to 'a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.107s

Sprint A9 - cyclic reboot after update

I'm having issues after OTA update to Android 6.1 for my HTC A9 Sprint.
After it only cyclic reboot (white screen with HTC)
I try update from .exe and fastboot - but all firmware discontinued with error (sample below, I tested 1.10.651.1 / 1.57.651.1 / 1.60.651.4 / 2.18.651.2 - WHL for Sprint):
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>htc_fastboot flash zip 2PQ9IMG_HIA_AERO_WH[email protected]51008_15.00_F_CNV_CNV_HIAE_SPCS_1.15_003_release_453722_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 1.10.651.1
found large-zip header, file count: 23
processing file 1/23...
sending 'zip' (98243 KB)...
OKAY [ 7.336s]
writing 'zip'...
(bootloader) HOSD CL#635870
(bootloader) ERR Tag name out of size
(bootloader) ERR [SD_UPDATE_ERR] Parse zipped android_info fail!
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14 RU_ZIP_INFO_ERROR android-info missing or malformed )
finished. total time: 12.260s
htc_fastboot finished. total time: 12.954s
My CID and MID:
(bootloader) kernel: lk
(bootloader) product: htc_hiaewhl
(bootloader) version: 1.0
(bootloader) imei: 990005706399921
(bootloader) version-main: 2.18.651.2
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ930000
(bootloader) cid: SPCS_001
all:
finished. total time: 0.006s
htc_fastboot finished. total time: 0.183s
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x638000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc6000000
(bootloader) serialno:HT5BXSZ00380
all:
finished. total time: 0.069s
htc_fastboot finished. total time: 0.236s
I need help for resolved this trouble.
Thanks for help and understanding.

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.