Hello, to start my English is very bad so I'll try to explain what's going on with my device.
I bought the XT1068 defective, apparently in the photos would be simple the process, I would install the ROM stock and it would remove the message bootloader and ready. I've tried absolutely everything
It appears the error "Invalid boot image header!"
If I try for a ROM on it it gives some errors, for example "failed to validate ftm image that means its not fih mode load and validate boot image" other "version is downgraded primary_gtp" (this when I tried for the ROM 4.4.4 ).
When I try to install the ROM on mfastboot so it appears these errors "C: \ Users \ PEDRO \ Desktop \ adb> mfastboot flash partition gpt.bin
Reported target max download size of 536870912 bytes
sending 'partition' (32 KB) ...
OKAY [0.050s]
writing 'partition' ...
(Bootloader) Preflash validation failed.
What do I do ?? please help me
---------text in portuguese----------
Olá, pra começar meu ingles é péssimo então vou tentar explicar o que está acontecendo com meu aparelho.
Eu comprei o XT1068 com defeito, aparentemente nas fotos seria simples o processo, eu instalaria a ROM stock nele e tiraria a mensagem de bootloader e pronto. Já tentei absolutamente de tudo
Ele aparece o erro "Invalid boot image header !"
Se eu tento por uma ROM nele ele dá alguns erros, por exemplo "failed to validate ftm image that means its not fih mode load and validate boot image" outro "version downgraded for primary_gtp" ( isso quando eu tentei por a ROM 4.4.4 ).
Quando vou tentar instalar a ROM no modo mfastboot ele aparece esses erros "C:\Users\PEDRO\Desktop\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Preflash validation failed.
O que eu faço ?? por favor me ajudem
hello. in advance sorry for my bad english did the best i could thanks for all the help this is my first post
I own a xt1058 at&t version, bootloader is unlocked and its also rooted, it used to run XT1058_GHOST_ATT_5.1_LPA23.12-21.7_cid1_CFC.xml note that its LPA23.12 not LPAS23.12 it has an (S).
one day it went off(discharged) and now it just turns on and shows bootlogo, bootanimation (both are custom )then it goes black stays there for hours, if i try to go into twrp its stuck on the teamwin image. // un dia se descargo y ahora solo prende me muestra el bootlogo luego el bootanimation ambos son customizados mios y luego se queda en negro al igual cuadno quiero entrar en twrp se queda en la presentacion teamwin
ive tried almost everything I have good Knowledge about flashing // ya he probado casi todo pero necesito de su ayuda tengo buen conocimiento acerca de flashear celulares
tried to flash via rds lite it flashes well it sends the phone to reboot but nothing changes and it stays black after boot image and boot animation so i downloaded more version for it:
XT1058_GHOST_RETAR_5.1_LPA23.12-21.7_cid12_CFC.xml
XT1058_GHOST_NIIBR_5.1_LPA23.12-21.7_cid3_CFC.xml
XT1058_GHOST_ATT_5.1_LPA23.12-21.7_cid1_CFC.xml
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml
XT1058_RETAIL-AR_4.4.4_KXA21.12-L1.26_62_cid12_CFC_1FF.xml
XT1058_GHOST_TIMBR_5.1_LPAS23.12-21.7-1_cid12_CFC.xml
FUNNY thing about all is that i have a custom bootlogo and a custom boot animation so when i flash the stock ones, doesnt change a thing and it flashes with no error I WOULD LIKE THAT PEOPLE SEE THIS FIRST AND THE WISE GUYS TRY HELP ME EXPLAIN THIS FIRST lo mas RARO de todo es que como tengo el bootlogo y animation customizado cuando flasheo todas esas rom stock no cambia nada y deberia hacer incluso proba solo con esos archivos a ver si lo delvolvia al warning del bootloader y a el planeta motorola y nada me gustaria que nos enfocaramos en esto ya que puede ser una buena explicacion del por que no esta hagarrando flash
BOOTLOADER DISPLAY:
AP Fastboot Flash Mode (s)
30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
emmc: 16GB sandisk rv=06 PV=07 TY=17
DRAM: 2048 samung s4 SDRAM DIE=4GB
uptime: 2minutes
device is UNLOCKED. Status code:3 (this is highlighted in yellow)
Baterry ok (charging) (this is highlighted in green)
Transfer Mode: USB Connected (highlighted in green also)
PD 1: I always use MFASTBOOT not FASTBOOT but ive tried wit both // he probado con ambos
PD 2: no matter what rom im flashing i always get the same error if i try downgrading it wont let me because of the security thing gpt and stuff, also have modified the lines when flashing with rds nothing works
Got this info in cmd with the following command: fastboot getvar all // esto lo obtuve en CMD con el comando "
fastboot getvar all "
version-bootloader: 30BE
version: 0.5
cpu: MSM8960 Pro CS
ram: 2048MB Samsung S4 SDRAM DIE=4Gb
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
product: ghost
revision-hardware: 0x8300
radio: 0x1
secure: yes
mid: 026b
serialno: TA1760BX0Y
qe: qe 1/1
unlocked: yes
iswarrantyvoid: yes
max-download-size: 805306368
uid: 9F8110040C000100000000000000
imei: 354984054025132
meid:
sku: 000000000000000
cid: 0x0c
iccid:
date: 11-12-2013
cust_md5:
reason: Key pressed
ro.build.date: Mon Aug 17 05:52:36 CDT 2015
ro.build.id: LPA23.12-21.7
ro.build.tags: bldacfg,release-keys
ro.build.type: user
ro.build.user: hudsoncm
ro.build.version.codename: REL
ro.build.version.incremental: 6
ro.build.version.release: 5.1
ro.mot.build.customerid: att
ro.product.name: ghost_att
ro.build.fingerprint[0]: motorola/ghost_att/ghost:5.1/LPA
ro.build.fingerprint[1]: 23.12-21.7/6:user/bldacfg,releas
ro.build.fingerprint[2]: e-keys
ro.build.version.full[0]: Blur_Version.222.26.7.ghost_att.
ro.build.version.full[1]: ATT.en.US
kernel.version[0]: Linux version 3.4.42-gfff16c8 (h
kernel.version[1]: [email protected]) (gcc version
kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Mon A
kernel.version[3]: ug 17 06:05:02 CDT 2015
all:
finished. total time: 0.245s
just for recon purposes but everthing still the same error, tried to reflash the twrp with FASTBOOT it says:
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\Root Moto X\Root Moto X
>fastboot flash recovery twrp.img
sending 'recovery' (8498 KB)...
OKAY [ 0.769s]
writing 'recovery'...
OKAY [ 0.849s]
finished. total time: 1.619s
NO LUCK STILL GET STUCK also tried a diferent version of twrp same thing.
FLASHING CWM pretty much the same:
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\Root Moto X\Root Moto X
>fastboot flash recovery recovery.img
sending 'recovery' (8488 KB)...
OKAY [ 0.780s]
writing 'recovery'...
OKAY [ 0.869s]
finished. total time: 1.649s
everytime I flash CWM or stock recovery it seens to be overwrited by twrp. Even if I boot right after flashing it. // cada vez que flasheo CWM o Stock recovery pareciera que lo vence el twrp y no se deja cambiar, incluso si hago el flash y de inmediato quiero verificar
MFASTBOOT does give and error with XT1058_GHOST_ATT_5.1_LPA23.12-21.7_cid1_CFC.xml <bootloader> Variable Not supported but not with RSD lite // MFASTBOOT ME DA ERROR <bootloader> Variable Not supported pero rsd lite no da tal error
everyting went just fine but "status" stays on reboot beacause the phone never finish booting so i have to re-enter bootloader so it can say PASS // el rsd todo parece haber ido bien pero el "status" no pasa de reboot debido a que el telefono nunca termina de encender
FLASHING XT1058_GHOST_NIIBR_5.1_LPA23.12-21.7_cid3_CFC.xml with fastboot
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.130s]
finished. total time: 0.130s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.120s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.359s]
writing 'motoboot'...
flashing tz ...
flashing rpm ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
OKAY [ 5.090s]
finished. total time: 5.450s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash logo logo.bin
sending 'logo' (245 KB)...
OKAY [ 0.310s]
writing 'logo'...
OKAY [ 0.879s]
finished. total time: 1.189s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 1.069s]
writing 'boot'...
OKAY [ 1.348s]
finished. total time: 2.418s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash recovery recovery.img
sending 'recovery' (8488 KB)...
OKAY [ 0.940s]
writing 'recovery'...
OKAY [ 0.908s]
finished. total time: 1.849s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash system system.img
sending 'system' (786432 KB)...
OKAY [ 58.986s]
writing 'system'...
OKAY [ 22.717s]
sending 'system' (663972 KB)...
OKAY [ 50.521s]
writing 'system'...
OKAY [ 19.100s]
finished. total time: 151.327s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash modem NON-HLOS.bin
sending 'modem' (54272 KB)...
OKAY [ 4.180s]
writing 'modem'...
OKAY [ 2.378s]
finished. total time: 6.559s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.459s]
finished. total time: 0.459s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.441s]
finished. total time: 0.441s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash fsg fsg.mbn
sending 'fsg' (226 KB)...
OKAY [ 0.330s]
writing 'fsg'...
OKAY [ 0.799s]
finished. total time: 1.129s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.679s]
finished. total time: 0.679s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.552s]
finished. total time: 0.552s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase customize
erasing 'customize'...
OKAY [ 0.159s]
finished. total time: 0.159s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.538s]
finished. total time: 0.539s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot oem fb_mode_clear
...
OKAY [ 0.166s]
finished. total time: 0.166s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot reboot
rebooting...
finished. total time: 0.001s
I tried to cover the most i could so theres no doubt about what im doing please help..!// trate de cubrir el mayor terreno prosible tal vez en cuanto a sus preguntas es mi primer post si falto algo me avisan se los agradezco
sinceros saludos ..almerHDSerViceS:..
Moto X XT1058 (Ghost)
ROM: Lollipop 5.1 Stock (AT&T) | Kernel: Stock | Root: SuperSU | BL: Unlocked | Recovery: TWRP 2.8.6.0
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.
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
@alanduda65 Please use the English language!
XDA Forum Rules:
Spoiler: Rule No. 4
4. Use the English language.
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.
alanduda65 said:
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
Click to expand...
Click to collapse
Hi!
Same thing here, Asus zenfone 5 ZE620KL, after trying to install twrp, phone got stuck in fastboot mode, can't get anywhere else, not recovery or boot to OS
Tried on AMD pc and Intel too, any ideas on how to get the phone working again?
You'll have to use QFIL to unbrick the phone. A quick google should show you how to do this
asusasus55 said:
You'll have to use QFIL to unbrick the phone. A quick google should show you how to do this
Click to expand...
Click to collapse
Do we really need to open the back?
alanduda65 said:
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
Click to expand...
Click to collapse
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...
Any command I try to put to flash the device it crashes and doesn't complete. I've tried recovery flash, boot, bootloader and none of them finish sending the file. I've already downloaded other files from other sites and it still doesn't send.
The device doesn't start recovery mode and I need to change roms.
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot devices
0047929849 fastboot
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot getvar max-sparse-size
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: 0.004s
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot oem fb_mode_set
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot flash partition gpt.bin
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'partition' (37 KB)...
-----------------------------------------------------------------------------
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>adb devices
List of devices attached
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot devices
0047929849 fastboot
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.4.0-beckham-v2.img
target reported max download size of 536870912 bytes
sending 'recovery' (33308 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.004s
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.4.0-beckham-v2.img
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'recovery' (33308 KB)...
I had similar problem with old ROM, device fails to receive any file (for boot or flash); the solution was to update ROM using it's internal update.
MagusWRM said:
I had similar problem with old ROM, device fails to receive any file (for boot or flash); the solution was to update ROM using it's internal update.
Click to expand...
Click to collapse
could you tell me how i do this update?
kauankas said:
could you tell me how i do this update?
Click to expand...
Click to collapse
Configurations > System > Advanced > System update
But there are a chance that there is no update avaiable; in that case you can try ADB after boot: enable developer mod and then activate ADB from there, try the commands again.
Spoiler: Huehuehue
Configurações > Sistema > Avançado > Atualizações do sistema
Há grandes chances de não ter atualização disponível; nesse caso recomendo tentar ADB pelo sistema (depois do boot): ativar modo desenvolvedor e de lá ativar ADB; tentar os comandos novamente.
MagusWRM said:
Configurations > System > Advanced > System update
But there are a chance that there is no update avaiable; in that case you can try ADB after boot: enable developer mod and then activate ADB from there, try the commands again.
Spoiler: Huehuehue
Configurações > Sistema > Avançado > Atualizações do sistema
Há grandes chances de não ter atualização disponível; nesse caso recomendo tentar ADB pelo sistema (depois do boot): ativar modo desenvolvedor e de lá ativar ADB; tentar os comandos novamente.
Click to expand...
Click to collapse
There's only one problem, the device after the lineageOS update doesn't turn on anymore, it gets stuck in the boot animation. huehue
Do you have an AMD processor? Several devices do not like AMD processors for some reason. In my experience they have anything from Nextbit/Razer, Moto Z3 series, and Essential Phone PH-1. They all work fine for me on any Intel based processor.
christian.farmerf said:
Do you have an AMD processor? Several devices do not like AMD processors for some reason. In my experience they have anything from Nextbit/Razer, Moto Z3 series, and Essential Phone PH-1. They all work fine for me on any Intel based processor.
Click to expand...
Click to collapse
You have no idea what you're talking about. I've rooted/rom'd hundreds of devices, including a few dozen RP2's, PH-1's, Pixel's, and International Samsungs... all on an amd cpu. Root and Rom doesn't care AMD or Intel. Something was just wrong with your setup.
KaptinBoxxi said:
You have no idea what you're talking about. I've rooted/rom'd hundreds of devices, including a few dozen RP2's, PH-1's, Pixel's, and International Samsungs... all on an amd cpu. Root and Rom doesn't care AMD or Intel. Something was just wrong with your setup.
Click to expand...
Click to collapse
I have every idea what i'm talking about. Older bootloader versions on some phones don't work by default with an AMD CPU. There is a fix for Windows users that just adds a few registry keys but linux users like myself are more or less out of luck. I suggest the OP and yourself check out this thread: here
Boom roasted.
christian.farmerf said:
Do you have an AMD processor? Several devices do not like AMD processors for some reason. In my experience they have anything from Nextbit/Razer, Moto Z3 series, and Essential Phone PH-1. They all work fine for me on any Intel based processor.
Click to expand...
Click to collapse
por incrivel que seja acabei de fazer no meu celular, pelo meu desktop que é um amd não estava indo nem com reza, mudei para note com intel e deu certo