Database Develop

[Q] Fastboot 'FAILED (remote: signature verify fail)

This error happens whenever I try to use Fastboot. I don't think it is dependent on the file being flashed, as I have tried a number of recoveries and a few system.img files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can I fix this? I need a working fastboot to be able to install a ROM and fix my recovery.

Okay, this is solved. I was rooted using the one-click method, but it seems I can't flash anything in fastboot unless my bootloader is unlocked. So I used the command
fastboot oem unlock
Click to expand...
Click to collapse
And now everything works perfectly.

same error is there with my wildfire s..
nothing is working..
it gives error..
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
please help..!!!!

1) You're in the wrong forum.
2) To use fastboot you have to unlock your bootloader with HTCDev tool, and you still won't be able to flash radio/splash/some other partitions.

Jack_R1 said:
1) You're in the wrong forum.
2) To use fastboot you have to unlock your bootloader with HTCDev tool, and you still won't be able to flash radio/splash/some other partitions.
Click to expand...
Click to collapse
i tried unlocking the bootloader.. but after running the RUU, during update something went wrong and a htc logo came up with "!" in all corners..
what do i do now? please help..!!

To unlock the bootloader, you don't need RUU. You should have just used the HTCDev tool.
I don't know what went wrong, soI can't help you. Try looking for help in Wildfire S forum.

Jack_R1 said:
To unlock the bootloader, you don't need RUU. You should have just used the HTCDev tool.
I don't know what went wrong, soI can't help you. Try looking for help in Wildfire S forum.
Click to expand...
Click to collapse
now the things are changed..
the phone booted with the command,
fastboot oem boot
but again when i restart it, its not goin into the bootloader..

Same problem here
sameer.patil291 said:
now the things are changed..
the phone booted with the command,
fastboot oem boot
but again when i restart it, its not goin into the bootloader..
Click to expand...
Click to collapse
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem boot
...
(bootloader) [ERR] partition_read::Failed to read page 19840 or it is emp
(bootloader) ty
(bootloader) [ERR] boot image does not exist!!!
FAILED (status read failed (Too many links))
finished. total time: 0.218s
I tried HTCDev and it fail.
Probably Bootloader is gone.

sameer.patil291 said:
same error is there with my wildfire s..
nothing is working..
it gives error..
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
please help..!!!!
Click to expand...
Click to collapse
The Wildfire S needs S-OFF, currently that is not possible on the device because of the advanced security on the bootloader,
Sent from my Nexus One using xda app-developers app

same on my inc s,
since i root install custom rom & need update to ICS so I roll back to stock room
here from my CMD :
C:\android>fastboot flash hboot vivo_downgrade.img
sending 'hboot' (1024 KB)...
OKAY [ 0.421s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.546s
+++++++++++++++++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
++++++++++++++++++++++++++++++++++++++
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
++++++++++++++++
need advise and help.
thanks
++++++++++++++++++++++++
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.16.0000
(bootloader) version-baseband: 3805.09.03.27_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.30.707.1
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d3a3895d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++++++++

analog problem

same problem
Is there no solution for this? I have tried everything that I could find on the internet and nothing seems to work. I consistantly get the FAILED <remote: signature verify fail>
And this is what I get when I tried the fastboot oem boot. Getting really frustrated. At the end of my string. Does anyone have any ideas?
... INFOBoot/Recovery signature che
INFOBoot/Recovery signature checking...
INFOsetup_tag addr=0x80400100 cmdline add=0xC02F4554
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x2ED01
INFOTAG:hero panel = 0x2940043
INFOTAG:engineerid = 0x0
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x0
INFODevice CID is not super CID
INFOCID is ROGER001
INFOsetting->cid::ROGER001
INFOserial number: HT265W405171
INFOcommandline from head: console=ttyHSL0,115200,n8
INFOcommand line length =718
INFOactive commandline: poweron_status=1 reset_status=0 board_vi
INFOlle.disable_uart3=0 diag.enabled=0 board_ville.debug_uart=0
INFOuserdata_sel=0 androidboot.emmc=true androidboot.pagesize=20
INFO48 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.sf=1 td
INFfs=328 td.prd=1 td.dly=0 td.tmo=300 imc_online_log=0 andr
INFOoidboot.efuse_info=NFSL androidboot.baseband=0.17.31501S.10_
INFO2 androidboot.cid=ROGER001 androidboot.devicerev=3 androidbo
INFOot.batt_poweron=good_battery androidboot.carrier=Rogers andr
INFOoidboot.mid=PJ4011000 androidboot.keycaps=qwerty androidboot
INFO.dq=FAIL androidboot.mode=normal androidboot.serialno=HT265W
INFO405171 androidboot.bootloader=1.13.0000 androidboot.nledhw=0
INFO zygote_oneshot=off kmemleak=off rpm_debug.enable=0 console=
INFOttyHSL0,115200,n8
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=local
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOaARM_Partion[7].name=devlog
INFOaARM_Partion[8].name=pdata
INFOaARM_Partion[9].name=fat
INFOaARM_Partion[A].name=extra
INFOaARM_Partion.name=radio
INFOaARM_Partion[C].name=adsp
INFOaARM_Partion[D].name=dsps
INFOaARM_Partion[E].name=wcnss
INFOaARM_Partion[F].name=radio_config
INFOaARM_Partion[10].name=modem_st1
INFOaARM_Partion[11].name=modem_st2
INFOpartition number=18
INFOValid partition num=18
INFOTZ_HTC_SVC_SET_DDR_MPU ret = 0
INFOsmem 90006000 (phy 90006000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
INFOTZ_HTC_SVC_LOG_OPERATOR ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
INFOjump_to_kernel: machine_id(3751), tags_addr(0x80400100), ker
INFOnel_addr(0x80408000)
INFO-------------------hboot boot time:198169 msec
FAILED (status read failed (Too many links))
finished. total time: 6.947s

I have a verizon inc 2, unlocked and I want to update the radio. I noticed
2) To use fastboot you have to unlock your bootloader with HTCDev tool, and you still won't be able to flash radio/splash/some other partitions.
Click to expand...
Click to collapse
and have tried putting it on the SD Card and running it thru the bootloader, but it just sits there. the only reason I even want the radio updated was because I saw that I *might* be able to access the 4G signal and use it. otherwise, I would just like to get a ROM of any kind, even stock, working on my phone

I was having this same issue. Can I install TWRP with the bootloader locked?
Jack_R1 said:
1) You're in the wrong forum.
2) To use fastboot you have to unlock your bootloader with HTCDev tool, and you still won't be able to flash radio/splash/some other partitions.
Click to expand...
Click to collapse
I have the same issue in the original thread with my bootloader. ATT HTC one mini I seem to get signature fail When I try flashing a recovery and "connection error" with the RUU. My bootloader is locked Ive tried the RUU with different cables and different ports on my laptop. No luck. SIM Lock says "SD init fail." but the RUU detects the OS version ## ADB detects a device but the RUU wont. PLease help

yumcax said:
Okay, this is solved. I was rooted using the one-click method, but it seems I can't flash anything in fastboot unless my bootloader is unlocked. So I used the command
And now everything works perfectly.
Click to expand...
Click to collapse
With SDK?

https://postimage.org/

i neeed help
i got the same problem after flashing ruu file to my htc evo view 4g tab
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.007s
pleeease help

Problem with bootloader
Hello to ALL.
I can not LOCK my bootloader (unlocked by another person).
When tried to fastboot oem lock - always got FAILED.
c:\Android>fastboot oem lock
... INFOLock failed!
FAILED (status read failed (No such file or directory))
HTC 609d (UNLOCKED)
HBOOT-1.03.0001
RADIO-1.02.10.0917
OS-
eMMC-boot
Oct 18 2013,22:38:27.0
By the way, can not flash any files (boot \ recovery or system):
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)
c:\Android>fastboot flash boot boot.img
sending 'boot' (4508 KB)... OKAY
writing 'boot'... FAILED (remote: image update error)
deatails of getvar:
c:\Android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.03.0001
INFOversion-baseband: 1.02.10.0917
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HC3CTMR02037
INFOimei: 355195000000017
INFOmeid:
INFOproduct: cp3dcg
INFOplatform: HBOOT-8x25Q
INFOmodelid: PO4710000
INFOcidnum: HTCCN702
INFObattery-status: good
INFObattery-voltage: 3840mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-a87dbd86
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
Thanks in advance for you assistance.

HTC D516d
Hello to ALL!
When i put (adb \ bootloader) a command "getvar all" fastboot don`t reply me with PHONE INFORMATION:
c:\Android>fastboot getvar all
all:
finished. total time: 0.003s
Now installed ROM from HTC Desire 516 Dual Sim, but seeking for original for my device STOCK - HTC D516d.
Thanks in advance.

[Q] Corrupted partitions?

Hello, I have a problem with my razr i xt890 and I can't find out the solution.
I had omar's rom (sept 2013 versions) on my phone (unlocked bootloader) and I tried to flash a new version using twrp but it stops/freezes when I wipe /system or /cache.
Also I can't mount /data.
I've tried with all recovery images from this thread [RECOVERY] New Installer for CWM / TouchCWM / TWRP / STOCK Recovery, but no luck.
I can get into fastboot and in recovery without problems, but I can't wipe the partitions.
Right now I'm trying to wipe /system, /data & /cache using cwm but it can't mount /data and it's stuck on formatting /cache.
Do you have any ideas?
Thank you.
[Details from fastboot]
AP Fastboot flash mode (secure boot)
20.25 (sha - )
IFWI Info: 42.26
eMMC Info: Size 8GB
Barcode: N/A
Battery (Okay): 4.09v
Transfer Mode: USB Connected
ROM-Key: Motorola-key
Modem Status: NA
C:\>fastboot getvar all
(bootloader) version-bootloader: 0x2025
(bootloader) product: smi
(bootloader) secure: yes
(bootloader) rom-key: motorola-key
(bootloader) model-id: 0268
(bootloader) cid: 7
(bootloader) version: 0.5
(bootloader) uid:
(bootloader) max-download-size: 104857600
(bootloader) emmc-size: 8GB
(bootloader) qe: qe 1/1
(bootloader) unlocked: yes
(bootloader) is-warranty-void: yes
(bootloader) ifwi: 42.26
(bootloader) cpu: Intel(R) Atom(TM) CPU Z2480 @ 2.00GHz
(bootloader) kernel: droidboot
(bootloader) battery: capacity: 73, voltage: 4053750, temperature: 290
(bootloader) modem-status: n/a

U could try to wipe the partitions through fastboot

I can't erase partitions from fastboot.
Output from device (fastboot)
read from /dev/block/mmcblk0 failed: I/O error
E:read_intel_version_from_mmc: Failed to read OSIP header from sector0!
E:Failed to read version for bos
read from /dev/block/mmcblk0 failed: I/O error
E:Failed to read partition gpt_main
I tried to flash the original rom from motorola with rsd lite but still no luck.
Can't write to mmc
I have also tried the solution from this thread http://forum.xda-developers.com/showthread.php?t=2184877, but still no luck
Is the internal sd card damaged/broken?

U did use JB versions of ifwi, motoboot and the other file? If so and it won't flash through the xfstk flasher, we can't help u. Sorry.

maybe you have to flash a stock rom with RSD lite, maybe with that, it'll be resolve...

I did flash with xfstk flasher successfully, but when i'm in fastboot the phone can't read or write to internal sd.
I have tried with rsd lite to flash the original but failed since the device can't write to the internal sd.
Any suggestions (or may I have to give up)?

flashed wrong partition (gpt.bin) and other images

Problem: As after having the notification of latest update regarding stagefright exploit on my XT1052 RetailAsia version of moto x (2013), I downloaded a file named "ghost_retail_51_lpa2312-15_cid9_cfc.xml.zip", and tried flashing.
At first I started my flash-all.bat file which has all the command starting from "fastboot oem fb_mode_set" to "fastboot oem fb_mode_clear" which include commands for partition, system, boot, logo, recovery, modem, fsg, in between .(not in the order the same order as mentioned)
after all the commands done, i start checking the results from the first command, the first one i.e. fastboot oem fb_mode_set was quiet successfully done but starting from second command i.e., from fastboot flash partiton gpt.bin, all command shows same error i.e.
Code:
C:\Ajay\GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml>mfastboot flash partition gpt.
bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.265s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.562s
my devices info got from fastboot getvar all
Code:
C:\Ajay\GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml>fastboot getvar all
INFOversion-bootloader: 30BE
INFOversion: 0.5
INFOcpu: MSM8960 Pro CS
INFOram: 2048MB Samsung S4 SDRAM DIE=4Gb
INFOemmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
INFOproduct: ghost
INFOrevision-hardware: 0x8300
INFOradio: 0x3
INFOsecure: yes
INFOmid: 026b
INFOserialno: TA6---30[COLOR="black"]X4[/COLOR]
INFOqe: qe 1/1
INFOunlocked: yes
INFOiswarrantyvoid: yes
INFOmax-download-size: 805306368
INFOuid: 4EABB2050C000100000000000000
INFOimei: 3532---5[COLOR="black"]13--9[/COLOR]9-
INFOmeid:
INFOsku: 000000000000000
INFOcid: 0x07
INFOiccid:
INFOdate: 04-27-2014
INFOcust_md5:
INFOreason: Key pressed
INFOro.build.date: Fri May 8 07:37:44 CDT 2015
INFOro.build.id: LPA23.12-15
INFOro.build.tags: release-keys
INFOro.build.type: user
INFOro.build.user: hudsoncm
INFOro.build.version.codename: REL
INFOro.build.version.incremental: 19
INFOro.build.version.release: 5.1
INFOro.mot.build.customerid: RETASIA
INFOro.product.name: ghost_retasia
INFOro.build.fingerprint[0]: motorola/ghost_retasia/ghost:5.1
INFOro.build.fingerprint[1]: /LPA23.12-15/19:user/release-key
INFOro.build.fingerprint[2]: s
INFOro.build.version.full[0]: Blur_Version.222.21.15.ghost_row
INFOro.build.version.full[1]: .AsiaRetail.en.03
INFOkernel.version[0]: Linux version 3.4.42-g030aaa2 (h
INFOkernel.version[1]: [email protected]) (gcc version
INFOkernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Fri M
INFOkernel.version[3]: ay 8 07:51:10 CDT 2015
now the phone doesn't booting up nor it is going into recovery|
A "No Command" photo with an Android image into it.
i got that file from Here ,
Please tell me what to do!
in my view i thought the file i got is not AsiaRetail version or possibly the file name indicates its a CID9 version and when i checked on my phone using "fastboot getvar cid" it shows mine is 0x07. i.e,
Code:
C:\Ajay\GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml>fastboot getvar cid
cid: 0x07
finished. total time: 0.109s
While flashing partition gpt.bin it shows following message on bootloader screen
Downgrading security version
Update gpt_main version fail
Preflash validation failed for GPT

BLU R1 HD Boot Loop after OTA

Hello,
I have an Amazon BLU R1 HD which I flashed with a standard OEM ROM based on the instructions in this forum, its been working great for months until I stupidly accepted an OTA (this one)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since the update the device is stuck in a boot loop. I no longer have adb access to it (adb devices shows nothing) and I've tried to unlock the bootloader using SP Flash Tool and method 2 from here https://forum.xda-developers.com/r1-hd/development/r1-hd-amazon-bootloader-unlock-method-t3426104 but I just get a s_brom_download_da_fail error. I've tried on Windows and Linux, same results.
Can anything be done? Does anyone have any thoughts on this?
Thanks!

g00s3m4n said:
Hello,
I have an Amazon BLU R1 HD which I flashed with a standard OEM ROM based on the instructions in this forum, its been working great for months until I stupidly accepted an OTA (this one)
Since the update the device is stuck in a boot loop. I no longer have adb access to it (adb devices shows nothing) and I've tried to unlock the bootloader using SP Flash Tool and method 2 from here https://forum.xda-developers.com/r1-hd/development/r1-hd-amazon-bootloader-unlock-method-t3426104 but I just get a s_brom_download_da_fail error. I've tried on Windows and Linux, same results.
Can anything be done? Does anyone have any thoughts on this?
Thanks!
Click to expand...
Click to collapse
Since you had converted to OEM version. You most likely already had unlocked bootloader. Also when you take an ota with unlocked bootloader you end up with half re-locked bootloader and a boot loop.
We have already seen this in the forum , and have an easy solution.
But to verify the situation before making changes do this:
Hold volume up while phone is boot looping. it should eventually go to the boot menu. Select fastboot. Connect to your pc.
Open cmd window. type this "fastboot devices" you should get almost instant response. " *your serial number* fastboot"
now that you verified you have the connection type this "fastboot getvar all" the response is a list of partitions then near the end there is the bootloader status
"unlocked = yes"
and
"secure = yes"
if this is true then my assumption is correct. It should be "secure = no" for an unlocked phone.
Now type "fastboot oem unlock" followed by volume up button on phone.
follow that with "fastboot format userdata"
obviously this will factory reset your phone.

mrmazak said:
Since you had converted to OEM version. You most likely already had unlocked bootloader. Also when you take an ota with unlocked bootloader you end up with half re-locked bootloader and a boot loop.
We have already seen this in the forum , and have an easy solution.
But to verify the situation before making changes do this:
Hold volume up while phone is boot looping. it should eventually go to the boot menu. Select fastboot. Connect to your pc.
Open cmd window. type this "fastboot devices" you should get almost instant response. " *your serial number* fastboot"
now that you verified you have the connection type this "fastboot getvar all" the response is a list of partitions then near the end there is the bootloader status
"unlocked = yes"
and
"secure = yes"
if this is true then my assumption is correct. It should be "secure = no" for an unlocked phone.
Now type "fastboot oem unlock" followed by volume up button on phone.
follow that with "fastboot format userdata"
obviously this will factory reset your phone.
Click to expand...
Click to collapse
Thank you, your assumption was correct and that has fixed the problem. Obviously my search foo failed me.
I appreciate the quick reply and assistance.

mrmazak said:
Since you had converted to OEM version. You most likely already had unlocked bootloader. Also when you take an ota with unlocked bootloader you end up with half re-locked bootloader and a boot loop.
We have already seen this in the forum , and have an easy solution.
But to verify the situation before making changes do this:
Hold volume up while phone is boot looping. it should eventually go to the boot menu. Select fastboot. Connect to your pc.
Open cmd window. type this "fastboot devices" you should get almost instant response. " *your serial number* fastboot"
now that you verified you have the connection type this "fastboot getvar all" the response is a list of partitions then near the end there is the bootloader status
"unlocked = yes"
and
"secure = yes"
if this is true then my assumption is correct. It should be "secure = no" for an unlocked phone.
Now type "fastboot oem unlock" followed by volume up button on phone.
follow that with "fastboot format userdata"
obviously this will factory reset your phone.
Click to expand...
Click to collapse
confirmed working. one more phone has been saved. Thanks!

OEM version - boot loop
My BLU R1 HD from Amazon, is stuck at reboot. I have not made any changes to the ROM except OTA updates.
I have provided the fastboot getvar all - details below.
Kindly guide me how to unbrick the phone. I am not looking to root the phone. Thanks in advance.
The values are different from what you had mentioned above
(bootloader) unlocked: no
(bootloader) secure: yes
C:\>fastboot devices
4SPFSKDUOVQWMBFE fastboot
C:\>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
I ran the unlock bootloader and it fails as well
C:\>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 90.128s

praxtwin said:
My BLU R1 HD from Amazon, is stuck at reboot. I have not made any changes to the ROM except OTA updates.
I have provided the fastboot getvar all - details below.
Kindly guide me how to unbrick the phone. I am not looking to root the phone. Thanks in advance.
The values are different from what you had mentioned above
(bootloader) unlocked: no
(bootloader) secure: yes
C:\>fastboot devices
4SPFSKDUOVQWMBFE fastboot
C:\>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
I ran the unlock bootloader and it fails as well
C:\>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 90.128s
Click to expand...
Click to collapse
Don't have any proven information to give you in your situation. All previous boot loops after taking an OTA have been a result of already having bootloader unlocked.
I would normally suggest trying to do a factory reset in a boot loop situation . So if you can get into recovery mode try to do a reset. If you cannot get into recovery you can try to do a "fastboot format userdata" and / or. "fastboot format cache"

mrmazak said:
Don't have any proven information to give you in your situation. All previous boot loops after taking an OTA have been a result of already having bootloader unlocked.
I would normally suggest trying to do a factory reset in a boot loop situation . So if you can get into recovery mode try to do a reset. If you cannot get into recovery you can try to do a "fastboot format userdata" and / or. "fastboot format cache"
Click to expand...
Click to collapse
Thanks for your suggestion. Unfortunately, Recovery mode doesn't seem to work. I did Factory reset , and then reboot, it stays on white BLU screen.
Additional Info: I did a ROOT INTEGRITY CHECK. It fails stating several files modified. I am not sure if that is an indication of any problems.
So I fastboot'ed again and tried format userdata and cache.
Both result in Failure - Not Allowed.
C:\>fastboot format cache
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
target reported max download size of 134217728 bytes
erasing 'cache'...
FAILED (remote: format for partition 'cache' is not allowed
)
finished. total time: 0.005s
Is this because I do not have ROOT access, that I am not able to format?
Do you think there is anything I could do to get the phone working again. Appreciate your help so much.

praxtwin said:
Thanks for your suggestion. Unfortunately, Recovery mode doesn't seem to work. I did Factory reset , and then reboot, it stays on white BLU screen.
Additional Info: I did a ROOT INTEGRITY CHECK. It fails stating several files modified. I am not sure if that is an indication of any problems.
So I fastboot'ed again and tried format userdata and cache.
Both result in Failure - Not Allowed.
C:\>fastboot format cache
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
target reported max download size of 134217728 bytes
erasing 'cache'...
FAILED (remote: format for partition 'cache' is not allowed
)
finished. total time: 0.005s
Is this because I do not have ROOT access, that I am not able to format?
Do you think there is anything I could do to get the phone working again. Appreciate your help so much.
Click to expand...
Click to collapse
You are not allowed to format from fastboot because , not bootloader unlocked. So not unlocked, no custom recovery, and integrity check says system files are changed.
It is most likely end of line for that device. Only option I can think of is factory repair. Phone must be less than 1 year old. (released July 2016) They have 12 month warranty I believe.

I have the Amazon R1 HD and I too fell victim to the update install that relocked my phone so its stuck in the reboot format. My problem seems to be when attaching my phone to the computer as instructed previously to another Blu...after typing in "fastboot devices" I receive an error code stating the Android device has no drive. I am almost past exasperated. Help, please!

Please help
I tried the spitting flash tool method to get my phone out of bootloop it won't work because I can't turn it off. It's battery has to die out then when I plug it. It automatically goes to the BLU screen and stays there for a bit then powers off and turns on again. I tried plugging it in to my pc and using fastboot devices but I get this error.
'Fastboot' is not recognized as an internal or external command operable program or batch file
And I can't power it off to begin the flash every time I get a timeout and I have all the mtk drivers install and the MT65xx USB vcom drivers I'm so confused I have a week working on this issue

Ghost0711 said:
I tried the spitting flash tool method to get my phone out of bootloop it won't work because I can't turn it off. It's battery has to die out then when I plug it. It automatically goes to the BLU screen and stays there for a bit then powers off and turns on again. I tried plugging it in to my pc and using fastboot devices but I get this error.
'Fastboot' is not recognized as an internal or external command operable program or batch file
And I can't power it off to begin the flash every time I get a timeout and I have all the mtk drivers install and the MT65xx USB vcom drivers I'm so confused I have a week working on this issue
Click to expand...
Click to collapse
You are throwing a lot of different things together, but sounds like none of the steps are right.
If you have been stuck in a boot loop after an OTA update (like title of thread you are in) , and your phone was bootloader unlocked before taking the OTA update, then the following information should help.
If you are in a boot loop for other reason then this will not help.
While the phone in Turing on / off, hold volume up. Eventually it should come to the boot select screen. Use volume button to scroll to fastboot and power button to select.
Now plug usb into pc and open CMD window. Verify you have the fastboot program on pc, and it sees phone by typing "fastboot devices"
Your statement said you got response that fastboot was not recognized command. I suspect you may not have fastboot on pc, but it no fastboot on pc how did you unlock bootloader?
Moving on., Once you have fastboot recognizing the phone , type "fastboot oem unlock"
Should be message on phone screen asking to confirm by pushing volume up.
Next , if phone has stock recovery you can just reboot and stock recovery will wipe /data and phone should reboot.
If phone has custom recovery (twrp) need to format userdata and cache. Type "fastboot format userdata" then "fastboot format cache"
And again I must state that if phone is boot looping for other reasons then this may not help.

XT1929-5 brickado

Galera, preciso de ajuda.
Instalei a ressurection remix no meu moto z3 play (XT1929-5) e depois tentei voltar para a stock rom. O problema é que eu acho que bloqueei o bootloader e deu loop infinito.
Já tentei:
- Desbloquear o bootloader novamente e recebo o retorno de que tenho que ativar a opção no modo desenvolvedor;
- TWRP, mas sem sucesso;
- Várias Stock Rom pelo fastboot, mas dá "Flash Permission Denied";
- Várias Stock Rom pelo RSDLite, mas dá "The phone failed to switch to fastboot mode.".
Ps.: Drivers Motorola estão instalados.
Pesquisei e vi que dá pra colocar stock rom caso seja da versão atual ou superior. Mas nenhuma funciona.
E:\Recuperar Celular\ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-3f845b6-181030
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0047858774
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 9039D011
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 06-14-2018
(bootloader) sku: XT1929-5
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4242
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.2.r1-07200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf ([email protected]
(bootloader) kernel.version[1]: j-1) (gcc version 4.9.x 20150123 (prerel
(bootloader) kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Sat Sep 15
(bootloader) kernel.version[3]: 02:19:10 CST 2018
(bootloader) git:abl: MBM-3.0-uefi-3f845b6-181030
(bootloader) git:xbl: MBM-3.0-uefi-03d7120-181030
(bootloader) gitmic: MBM-3.0-uefi-03d7120-181030
(bootloader) git:rpm: MBM-3.0-uefi-75767ea-181030
(bootloader) git:tz: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:hyp: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:devcfg: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:cmnlib: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:cmnlib64: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:keymaster: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) gitrov: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:storsec: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.228s

forum rules bro speaka english

Sorry, I did not know.
People, help me, please.
I installed the rom "Ressurection Remix" on my moto z3 play (XT1929-5) and i then tried to go back to the stock rom. The problem is: i think i blocked the bootloader and ocurred infinite loop.
I tried:
- Unlock the bootloader again. Results: "check allow OEM unlock in developer options.";
- Boot in TWRP, but without sucess;
- Many stock roms in the fastboot mode. Results: "Flash Permission Denied";
- Many stock roms in the RSDLite. Results: "The phone failed to switch to fastboot mode";
*The Motorola Drivers are installed*
I searched and saw i can put stock rom if it is the current version or higher, but none work.
*Specifications*
E:\Recuperar Celular\ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-3f845b6-181030
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0047858774
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 9039D011
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 06-14-2018
(bootloader) sku: XT1929-5
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4242
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.2.r1-07200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf ([email protected]
(bootloader) kernel.version[1]: j-1) (gcc version 4.9.x 20150123 (prerel
(bootloader) kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Sat Sep 15
(bootloader) kernel.version[3]: 02:19:10 CST 2018
(bootloader) git:abl: MBM-3.0-uefi-3f845b6-181030
(bootloader) git:xbl: MBM-3.0-uefi-03d7120-181030
(bootloader) gitmic: MBM-3.0-uefi-03d7120-181030
(bootloader) git:rpm: MBM-3.0-uefi-75767ea-181030
(bootloader) git:tz: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:hyp: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:devcfg: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:cmnlib: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:cmnlib64: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:keymaster: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) gitrov: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) git:storsec: MBM-3.0-uefi-9a58d2e-dirty-181030
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.228s

First, look for "Lenovo MOTO Smart Assistant" and install it.
It includes a "Rescue" option, and if your phone and FW version are eligible, downloads the firmware and flashing it.
if not, download the lastest firmware according to your carrier and model
https://mirrors.lolinet.com/firmware/moto/beckham/official/
And you must flashing it via fastboot commands

GuzXT said:
First, look for "Lenovo MOTO Smart Assistant" and install it.
It includes a "Rescue" option, and if your phone and FW version are eligible, downloads the firmware and flashing it.
if not, download the lastest firmware according to your carrier and model
And you must flashing it via fastboot commands
Click to expand...
Click to collapse
Lenovo MOTO Smart Assistant results:
"Failed to match the connected device. Please plug it out, and try again."
Flashing via fastboot results:
"Flash Permission Denied"
any suggestion?

Neri23 said:
Lenovo MOTO Smart Assistant results:
"Failed to match the connected device. Please plug it out, and try again."
Flashing via fastboot results:
"Flash Permission Denied"
any suggestion?
Click to expand...
Click to collapse
My sugestion is : Do not mess with your phone, i bricked a G4 play and a G5s, i regret badly.

Neri23 said:
Lenovo MOTO Smart Assistant results:
"Failed to match the connected device. Please plug it out, and try again."
Flashing via fastboot results:
"Flash Permission Denied"
any suggestion?
Click to expand...
Click to collapse
These are the correct commands according to your device active slot (A)
fastboot oem fb_mode_set
fastboot flash gpt_a gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot

GuzXT said:
These are the correct commands according to your device active slot (A)
fastboot oem fb_mode_set
fastboot flash gpt_a gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thanks for help me, but it didn't works. :crying:
"Flash Permission Denied"

Does anyone know which version of this rom? (RETUS, RETBR, RETAIL...)?

Neri23 said:
Thanks for help me, but it didn't works. :crying:
"Flash Permission Denied"
Click to expand...
Click to collapse
eestou com o mesmo problema me ajuda se conseguir

[email protected] said:
eestou com o mesmo problema me ajuda se conseguir
Click to expand...
Click to collapse
Então, mano, depois de tentar de tudo e não conseguir resolver o problema, o jeito foi recorrer a assistência. Eles não levaram em conta que o bootloader estava desbloqueado e eu evitei falar sobre isso. Parece que precisou trocar a placa. Agora está rodando lisinho.

The Smart Assist will not work, once you unlock the bootloader it will not work. When they say you are voiding your warranty, they mean it. All I got was "this devie is not supported."

Neri23 said:
Então, mano, depois de tentar de tudo e não conseguir resolver o problema, o jeito foi recorrer a assistência. Eles não levaram em conta que o bootloader estava desbloqueado e eu evitei falar sobre isso. Parece que precisou trocar a placa. Agora está rodando lisinho.
Click to expand...
Click to collapse
Olá, quanto te foi cobrado pra fazer a reparação do aparelho?
No meu caso consegui flashear uma stock porém sem rede nem wifi nem do chip, os imeis estao em "0 e 00"
vc conseguiu achar algum blankflash do aparelho?
Agradeço desde já

Hey everyone,
Just a reminder that when you post, you should be using the English language. As per the XDA Forum Rules, "We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice."
Thanks!
rwilco12

z3 play beckham
[email protected] said:
eestou com o mesmo problema me ajuda se conseguir
Click to expand...
Click to collapse
o meu telefone tambem esta da mesma forma instalei a Resurrectionremix e agora deu pau
socorrrrrrrrrrroooooooooo
ja tentei de tudo mais nao da certo nada
C:\Users\elizeu\Desktop\mfastboot>fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
C:\Users\elizeu\Desktop\mfastboot>flash fastboot gpt_a gpt.bin
'flash' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>fastboot flash bootloader_a bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (9520 KB)...
OKAY [ 0.312s]
writing 'bootloader_a'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.392s
C:\Users\elizeu\Desktop\mfastboot>fastboot flash modem_a NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (97831 KB)...
OKAY [ 3.107s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.119s
C:\Users\elizeu\Desktop\mfastboot>flash fastboot fsg_a fsg.mbn
'flash' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>fastboot apagar modemst1
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot apagar modemst2
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot piscar bluetooth_a BTFM.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot dsp_a dspso.bin
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot logo_a logo.bin
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot boot_a boot.img
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot SYSTEM_A system.img_sparsechunk.0
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot SYSTEM_A system.img_sparsechunk.1
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot SYSTEM_A system.img_sparsechunk.2
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>de flash fastboot SYSTEM_A system.img_sparsechunk.3
'de' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>fastboot flash system_a system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (517994 KB)...
OKAY [ 16.435s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.448s
C:\Users\elizeu\Desktop\mfastboot>fastboot flash system_a
unknown partition 'system_a'
error: cannot determine image filename for 'system_a'
C:\Users\elizeu\Desktop\mfastboot>sistema.img_sparsechunk.5
'sistema.img_sparsechunk.5' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
C:\Users\elizeu\Desktop\mfastboot>fastboot sistema de flash_b system_other.img fastboot flash vendor_a fornecedor.img_sparsechunk.0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot flash vendor_a fornecedor.img_sparsechunk.1
error: cannot load 'fornecedor.img_sparsechunk.1'
C:\Users\elizeu\Desktop\mfastboot>fastboot flash oem_a oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (122148 KB)...
OKAY [ 3.884s]
writing 'oem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.897s
C:\Users\elizeu\Desktop\mfastboot>fastboot flash oem_b oem_ouro.img
error: cannot load 'oem_ouro.img'
C:\Users\elizeu\Desktop\mfastboot>fastboot apagar portador
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot apagar ddr
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\elizeu\Desktop\mfastboot>fastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\Users\elizeu\Desktop\mfastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Users\elizeu\Desktop\mfastboot>

One question, do not you have to see open developer options before all this?

The same thing happened to me after installing RR
After looking for some files I managed to revive my motorola z3.
It's just a matter of flashing the stock rom using flash bank.
First step have all the drivers installed on the pc. 2- Having installed the Qualcomm drivers. 3- Have the stock firmware
---------- Post added at 05:38 PM ---------- Previous post was at 05:31 PM ----------
The same happened to me after installing a few roms. But if you have a solution to that I invite you to follow the steps to revive your motorcycle z3

Benlly said:
After looking for some files I managed to revive my motorola z3.
It's just a matter of flashing the stock rom using flash bank.
First step have all the drivers installed on the pc. 2- Having installed the Qualcomm drivers. 3- Have the stock firmware
---------- Post added at 05:38 PM ---------- Previous post was at 05:31 PM ----------
The same happened to me after installing a few roms. But if you have a solution to that I invite you to follow the steps to revive your motorcycle z3
Click to expand...
Click to collapse
Hi Benlly, how are you? could you do a step by step guide explaining how to fix it? thank you, i aprecciate it

How can I not publish the files I use to help you find the internet flash bank for moto z3 and follow the steps or add me to telegram and I'll explain it better 5.5.4.0.5.6.8.2.5.9 nmro

Hi friends, I did all the procedures and my Moto Z3 Play went into Brick mode and turned into a brick. I have company and experience in TWRP, Bootloader, Unbrick of all Motorola line. But this Moto Z3 Play could not resurrect. Any suggestion ?
The screen goes blank but when I connect the data cable it beeps. Brick occurred after installing ROM RR.