I'm pretty savvy at this stuff but yo guys are on another level. And it's awesome. But when I compile the xmls mbn's etc. Am i doingit inside the blankflash zip so that qfil knows where to look or am i making no sense? Kind of learning this as I go at this point
[GUIDE] Unbrick MOTO Z Play (not working yet)
- Thread starter benzinerwin
- Start date
I just got the blank-flash out of the 7.0 full ROM. I was able to run the blank-flash.bat file and it got stuck after about 8 mins and cancelled. If you know how to edit this and tweak such you think you can bring it out have at it. I have no clue what to do from there... I hope someone can figure it out soon though!
moto z play brick
Good afternoon! I'm with moto z play bricked I can not connect someone has a solution, motorola wants to change motherboard, but I know that with blankflash I can revive help me
Blankflash could come out tomorrow, next week/month/year, or never.
There are some other 3-4 year old phones that never got one yet - blankflash are not official releases and have to be leaked at risk to the employee that leaks them.
Also realize that there may not be a blankflash that can fix these - blankflash could primarily be a way to prepare new phones on the factory line.
A phone that has been used and upgrades installed on it could have had efuses blown on the CPU that could prevent a blankflash from being able to work correctly as part of the upgrades.
Motorola may not need to make a new blankflash, and if they do not need to - why would they?
If you want your phone for sure fixed so you can use it - change the motherboard.
If you want to wait, then wait, but just know that you may be waiting for a solution that may not come - but we all hope that it will.
There are some other 3-4 year old phones that never got one yet - blankflash are not official releases and have to be leaked at risk to the employee that leaks them.
Also realize that there may not be a blankflash that can fix these - blankflash could primarily be a way to prepare new phones on the factory line.
A phone that has been used and upgrades installed on it could have had efuses blown on the CPU that could prevent a blankflash from being able to work correctly as part of the upgrades.
Motorola may not need to make a new blankflash, and if they do not need to - why would they?
If you want your phone for sure fixed so you can use it - change the motherboard.
If you want to wait, then wait, but just know that you may be waiting for a solution that may not come - but we all hope that it will.
please help-me....
Hello, I need as much help as you, I also hardbrick my motorola moto z play xt 1635-02, pardon my English, I use google translator, I see that the last post is already old, my moments of brilliance are over, With "star.exe" where I extracted the files from singleimage.bin, I looked, edited the xml, files, tried to put the update files inside singleimage.bin, without success in blank-flash, need help, if not I have not been able to use the gpt, mbn, or gpt file, but I have not been able to do it.
Hello, I need as much help as you, I also hardbrick my motorola moto z play xt 1635-02, pardon my English, I use google translator, I see that the last post is already old, my moments of brilliance are over, With "star.exe" where I extracted the files from singleimage.bin, I looked, edited the xml, files, tried to put the update files inside singleimage.bin, without success in blank-flash, need help, if not I have not been able to use the gpt, mbn, or gpt file, but I have not been able to do it.
I assume the motherboard houses the IEMI and the RETUS/EU etc.? The rest is just auxliary things right?Blankflash could come out tomorrow, next week/month/year, or never.
There are some other 3-4 year old phones that never got one yet - blankflash are not official releases and have to be leaked at risk to the employee that leaks them.
Also realize that there may not be a blankflash that can fix these - blankflash could primarily be a way to prepare new phones on the factory line.
A phone that has been used and upgrades installed on it could have had efuses blown on the CPU that could prevent a blankflash from being able to work correctly as part of the upgrades.
Motorola may not need to make a new blankflash, and if they do not need to - why would they?
If you want your phone for sure fixed so you can use it - change the motherboard.
If you want to wait, then wait, but just know that you may be waiting for a solution that may not come - but we all hope that it will.
From what I have seen in a tear down - yes the motherboard houses all storage.
talvez ajude (sorry, language is PT-BR)
observando o arquivo appsboot.mbn que é escrita em aboot, me deparei com algumas mensagens, talvez os ajude a ter uma luz : D
porem tambem vi a seguinte mensagem de mbm....
("*** Welcome to MBM Next Generation ***")
isso me assustou, como assim bem vindo a nova geração de mbm? a ferramenta ainda não foi lançada....
bem as mensagens sobre mbm do arquivo são:
*MBM version is %02X.%02X (%s)
loglevel.uart loglevel.ui loglevel.ram Serial number: "%s"
Syncing up for BOTA
* mbm ttyHSL0,115200,n8 null bp-tools on-dev-diag normal Boot up failed Volume down key pressed Failed to initialize partition table UTAG "%s" configured as fastboot Last time flashing failed Reboot mode set to fastboot Entering fastboot mode
* %s%s androidboot.emmc=true androidboot.serialno= androidboot.baseband=apq androidboot.baseband=msm androidboot.baseband=mdm androidboot.mode= androidboot.hwrev= androidboot.radio= 0x%08X androidboot.powerup_reason= androidboot.last_powerup_reason= androidboot.bootreason= androidboot.device= msm_poweroff.download_mode= androidboot.fsg-id= androidboot.wifimacaddr= androidboot.btmacaddr= 0x%04X androidboot.bootloader= androidboot.carrier= channel-id-map Unable to fetch channel ID from devtree ??? undefined latam emea asia androidboot.build_vars= androidboot.hardware.sku= androidboot.num-sims= bare_board_config max_cpus maxcpus=%d androidboot.memtest= androidboot.poweroff_alarm= app/mbm/linux_boot.c dst != NULL disabling console
* app/mbm/fastboot.c boot.img validated: kernel_size=0x%x, ramdisk_size=0x%x
* %s: using current path [%s] %s: fixed name %s invalid type specified name too long not a boolean value app/mbm/fastboot_oem.c ((void *)0) == "should not reach here" DEBUG %s: allow empty value
* %s[%d]: Done listed above raw ext2 ext3 ext4 vfat yaffs2 jfss2 iso version-bootloader storage-type cpu channelid securestate iswarrantyvoid max-download-size max-sparse-size current-time poweroffalarm sbl1.git rpm.git tz.git devcfg.git keymaster.git cmnlib.git cmnlib64.git prov.git aboot.git partition-type partition-size qe frp-state fboot_usb_write_wait fboot_usb_write_queue app/mbm/fastboot_usb.c usb_read(): len = %d
* No settings for %s in FDT
Not found invalid mbm fdt
Failed to get product/hw revision
/%s,[email protected]%d No setting for %s
* MBM_LOGGER sbl1_log_buffer_base sbl1_log_buffer_size smem not found: %s
ao meu ver o arquivo sbl1 refere-se a frequencia do processador, gerenciamento dos nucleos, (um possivel overclock seria ai)
de verdade estou tentando ajudar para que eu tambem possa ser ajudado....
links dentro do arquivo me levaram a permissões negadas, solicitações de acesso.
"não posso postar links"
espero que isto ajude :rolar os olhos:
oi!!!
observando o arquivo appsboot.mbn que é escrita em aboot, me deparei com algumas mensagens, talvez os ajude a ter uma luz : D
porem tambem vi a seguinte mensagem de mbm....
("*** Welcome to MBM Next Generation ***")
isso me assustou, como assim bem vindo a nova geração de mbm? a ferramenta ainda não foi lançada....
bem as mensagens sobre mbm do arquivo são:
*MBM version is %02X.%02X (%s)
loglevel.uart loglevel.ui loglevel.ram Serial number: "%s"
Syncing up for BOTA
* mbm ttyHSL0,115200,n8 null bp-tools on-dev-diag normal Boot up failed Volume down key pressed Failed to initialize partition table UTAG "%s" configured as fastboot Last time flashing failed Reboot mode set to fastboot Entering fastboot mode
* %s%s androidboot.emmc=true androidboot.serialno= androidboot.baseband=apq androidboot.baseband=msm androidboot.baseband=mdm androidboot.mode= androidboot.hwrev= androidboot.radio= 0x%08X androidboot.powerup_reason= androidboot.last_powerup_reason= androidboot.bootreason= androidboot.device= msm_poweroff.download_mode= androidboot.fsg-id= androidboot.wifimacaddr= androidboot.btmacaddr= 0x%04X androidboot.bootloader= androidboot.carrier= channel-id-map Unable to fetch channel ID from devtree ??? undefined latam emea asia androidboot.build_vars= androidboot.hardware.sku= androidboot.num-sims= bare_board_config max_cpus maxcpus=%d androidboot.memtest= androidboot.poweroff_alarm= app/mbm/linux_boot.c dst != NULL disabling console
* app/mbm/fastboot.c boot.img validated: kernel_size=0x%x, ramdisk_size=0x%x
* %s: using current path [%s] %s: fixed name %s invalid type specified name too long not a boolean value app/mbm/fastboot_oem.c ((void *)0) == "should not reach here" DEBUG %s: allow empty value
* %s[%d]: Done listed above raw ext2 ext3 ext4 vfat yaffs2 jfss2 iso version-bootloader storage-type cpu channelid securestate iswarrantyvoid max-download-size max-sparse-size current-time poweroffalarm sbl1.git rpm.git tz.git devcfg.git keymaster.git cmnlib.git cmnlib64.git prov.git aboot.git partition-type partition-size qe frp-state fboot_usb_write_wait fboot_usb_write_queue app/mbm/fastboot_usb.c usb_read(): len = %d
* No settings for %s in FDT
Not found invalid mbm fdt
Failed to get product/hw revision
/%s,[email protected]%d No setting for %s
* MBM_LOGGER sbl1_log_buffer_base sbl1_log_buffer_size smem not found: %s
ao meu ver o arquivo sbl1 refere-se a frequencia do processador, gerenciamento dos nucleos, (um possivel overclock seria ai)
de verdade estou tentando ajudar para que eu tambem possa ser ajudado....
links dentro do arquivo me levaram a permissões negadas, solicitações de acesso.
"não posso postar links"
espero que isto ajude :rolar os olhos:
Well...here's another Moto Z Play brick. Was on 7.0.1. stock/rooted and accidentally accepted ota (brain fart moment). After that, the phone was stuck in TWRP and flashing other ROMS would not work, the device kept rebooting to TWRP. Used ADB to flash MM restore files, phone booted up (now fully stock with no root) and I accepted Nougat OTA. Went through OTA process, after the install, phone is now a brick and has not/will not boot anywhere...All hope is now lost
Well, after countless posts telling you not to accept otas if you downgrade to MM, no one will feel sorry for you. You should've flashed twrp flashable and update whenever the new flashable is out, and you would still have a working phone.Well...here's another Moto Z Play brick. Was on 7.0.1. stock/rooted and accidentally accepted ota (brain fart moment). After that, the phone was stuck in TWRP and flashing other ROMS would not work, the device kept rebooting to TWRP. Used ADB to flash MM restore files, phone booted up (now fully stock with no root) and I accepted Nougat OTA. Went through OTA process, after the install, phone is now a brick and has not/will not boot anywhere...All hope is now lost
All needed to flash was just the 10.sparsechunks,OEM.img and boot.img.Well...here's another Moto Z Play brick. Was on 7.0.1. stock/rooted and accidentally accepted ota (brain fart moment). After that, the phone was stuck in TWRP and flashing other ROMS would not work, the device kept rebooting to TWRP. Used ADB to flash MM restore files, phone booted up (now fully stock with no root) and I accepted Nougat OTA. Went through OTA process, after the install, phone is now a brick and has not/will not boot anywhere...All hope is now lost
I gotta keep saying this DO NOT FLASH OTA'S or Do NOT FLASH THE BOOTLOADER.BIN FILES, cause eventually your going to end up bricked.
Sorry for the translation I'm using the google translator, I'm also waiting for a solution to resurrect the bike z play, I wish all the luck for the smartest to find a solution. Good luck.
Seems ArykTech people finnished the work on Loader.img files, for the XT1635-02. They are "selling" (a small contribution) the file for 11.99 USD. Anyone here managed to unbrick using the method?
I saw that as well. But since I replaced my broken phone I no longer need the fix/have a reason to test it. Here is hoping some one gives it a shot and that it works!
If it is a valid solution - I may even unlock my replacement phone. (I miss root)
If it is a valid solution - I may even unlock my replacement phone. (I miss root)
Last edited:
Por favor assim que alguém conseguir pelo metodo do loadeer.img nos informe, pois tenho medo de pagar e não funcionar!!
English only on XDA
Translated below
"Please as soon as someone can get through the method of loadeer.img inform us, therefore I am afraid to pay and not work !!"
Sent from my XT1096 using XDA Labs
If someone works with certainty I will pay to recover my XT1635-02 Moto z Play.
http://www.aryk.tech/2017/07/moto-z-play-unbrick-solutions.html?m=1
If it works, I'll pay them as well. Haven't paid yet, because my device isn't bricked
.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone