Hello! I have a droid turbo which was updated to 5.1 via OTA. I then downgraded it to 4.4.4 and took an OTA , during this upda my phone got a blank screen and on my windows it is recognised as QHSUSB_BULK . I have tried the blankflash methos but it looks like I need mbm-ci files for this? Can anybody help please ?
i have the same question and i use ilia3367‘s tools to save my phone .
i think it may help you
this is my post http://forum.xda-developers.com/showpost.php?p=64812708&postcount=7
and this is the tools
http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
and thank for ilia3367
Related
Good night friends!I am new to the community, and I have a problem and I am desperate !!! have a Moto G 2014 (xt1069), and updated it to the android 6.0 using a zip (Blur_Version.22.56.3.titan_retbr_dstv.retbr.en.BR), and everything went well ... after three days the device hung alone and then did not call more! I can enter the fastboot, I've tried flashing with a rom android 4.4, 5.0 and 6.0, it supports the standard all commands more after doing all the process, it still does not work (I think it is because it is not enabled USB debugging mode) there is another way to relive it ?? porfavor help me I'm desperate! already agrdeço attention of all ...
PS: HE HAS BOOTLOADER UNLOCKED
not notice in my English because I am from Brazil!
:crying::crying::crying:
ErickNeris said:
Good night friends!I am new to the community, and I have a problem and I am desperate !!! have a Moto G 2014 (xt1069), and updated it to the android 6.0 using a zip (Blur_Version.22.56.3.titan_retbr_dstv.retbr.en.BR), and everything went well ... after three days the device hung alone and then did not call more! I can enter the fastboot, I've tried flashing with a rom android 4.4, 5.0 and 6.0, it supports the standard all commands more after doing all the process, it still does not work (I think it is because it is not enabled USB debugging mode) there is another way to relive it ?? porfavor help me I'm desperate! already agrdeço attention of all ...
PS: HE HAS BOOTLOADER UNLOCKED
not notice in my English because I am from Brazil!
:crying::crying::crying:
Click to expand...
Click to collapse
Im sorry, im in the same situation, and i will not give up, but i dont really understand you.. can you put your problems in a different format? like this:
Recovery version: #####
Android version: #####
Problem: #####
How: ####
etc.. etc...
I will do my best to help you find all the info and im trying to find help myself
My phone is totally bricked not even opening in bootloader. It's only recognized by pc as "qhsusb_bulk". so I signed my phone with "Riff BOX JTAG drivers Driver Signature Enforcement Overrider". after this my phone is recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Then I extract Motorola qboot utility and then run blank-flash.bat file after that this is showing (flashing singleimageFAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet).
maybe that singleimage.bin file is problematic.
So I need correct blank-flash file for my phone.
Help me guys. thanks in advance.
deleted. Reason : OP edited.
sagar846 said:
Have you tried giving it CPR? (jk)
Just reflash stock firmware.
Link : Click Here
Click to expand...
Click to collapse
edit..
zman01 said:
Very useful post.. Did you read the OP or you're just guessing here?
Click to expand...
Click to collapse
Op edited post. Before there was only hard brick problem given (when I posted).
Well, there is a good chance that you can't do anything about it. But, give as some info about what you did to it, what was the last version of Android or Rom on it, and so on.
Addy K said:
My phone is totally bricked not even opening in bootloader. It's only recognized by pc as "qhsusb_bulk". so I signed my phone with "Riff BOX JTAG drivers Driver Signature Enforcement Overrider". after this my phone is recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Then I extract Motorola qboot utility and then run blank-flash.bat file after that this is showing (flashing singleimageFAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet).
maybe that singleimage.bin file is problematic.
So I need correct blank-flash file for my phone.
Help me guys. thanks in advance.
Click to expand...
Click to collapse
I get the same place in my moto g 2014 xt1069. Do i have any chance to create a blackflash from original lollipop ROM?
EDIT: blankflash*
marcoslucianops said:
I get the same place in my moto g 2014 xt1069. Do i have any chance to create a blackflash from original lollipop ROM?
Click to expand...
Click to collapse
Nope, you don't have any
Addy K said:
...
Click to expand...
Click to collapse
Can you give me the files you used?
Well this guide might work for you guys. Its for the moto g1 but everything used in the guide is kind of the same for all moto devices except the firmware. Don't forget to download the correct firmware for your phone :
Click Here
sagar846 said:
Well this guide might work for you guys. Its for the moto g1 but everything used in the guide is kind of the same for all moto devices except the firmware. Don't forget to download the correct firmware for your phone :
Click Here
Click to expand...
Click to collapse
This won't work, ^^ the "blank flash" in the tutorial you've sent us, is only for the Moto G 1st gen, i've already tried it ^^ this is not compatible :/
This is why we need the blank flash for the Moto G 2014, then this tuto will work ^^
Miiick3y said:
This won't work, ^^ the "blank flash" in the tutorial you've sent us, is only for the Moto G 1st gen, i've already tried it ^^ this is not compatible :/
This is why we need the blank flash for the Moto G 2014, then this tuto will work ^^
Click to expand...
Click to collapse
Check the firmware download link again (file factory). There are 5+ pages. Find the right firmware for your phone (Itll be labelled TITAN CFL blah blah)
Flash it.
Direct link : Click Here
sagar846 said:
Check the firmware download link again (file factory). There are 5+ pages. Find the right firmware for your phone (Itll be labelled TITAN CFL blah blah)
Flash it.
Direct link : Click Here
Click to expand...
Click to collapse
Thanks for help, but i can't flash anything, my phone is only recognized on my pc as a qualcomm communication port ^^
Addy K said:
My phone is totally bricked not even opening in bootloader. It's only recognized by pc as "qhsusb_bulk". so I signed my phone with "Riff BOX JTAG drivers Driver Signature Enforcement Overrider". after this my phone is recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Then I extract Motorola qboot utility and then run blank-flash.bat file after that this is showing (flashing singleimageFAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet).
maybe that singleimage.bin file is problematic.
So I need correct blank-flash file for my phone.
Help me guys. thanks in advance.
Click to expand...
Click to collapse
@Andy K
Found the reason why it didn't work. That is because that method is used to rescue Qualcomm Snapdragon devices. Our device is Qualcomm based so yeah. Here's a kinda detailed explanation
Owners of Qualcomm based LG’s, HTC’s, Samsung’s, Sony’s and Motorola’s, im afraid this tool is not suitable for you, because those liers mostly have chosen not to use default options of this platform, they dont (cant) want us to rescue our phones so easly, what would have happened to their service centers all around the world then ? They need to change “The Motherboard” in spite of the ability to fix this problem so easly to earn more and more and more money.
Site Link : Click Here
I was on stock Marshmallow 6.0 rom. Then I flashed stock Lollipop 5.0.2 rom in my phone and then I was updating my phone to new stagefright patch but after switch off my phone didn't turn on again.
My last android version was Marshmallow 6.0. I downgraded my phone to Lollipop 5.0.2 and tried to update latest stagefright patch from system update. But after switched off my phone never turn on again. Whenever I connect my phone to the charger it's shows nothing but white led light for 10 seconds. And my phone recognised by my PC as "qshusb_bulk".
Need Moto G 2nd Gen "blankflash image" to flash new bootloader.
As the bootloader of my phone has been collapsed so I need to flash a new bootloader to my phone to relive. But I don't have the right file. And I don't think there is any blankflash image of my phone (XT1068) is available on the net. So I just need to know that is there any way to extract these file from Stock ROM?
Addy K said:
As the bootloader of my phone has been collapsed so I need to flash a new bootloader to my phone to relive. But I don't have the right file. And I don't think there is any blankflash image of my phone (XT1068) is available on the net. So I just need to know that is there any way to extract these file from Stock ROM?
Click to expand...
Click to collapse
No there is no way. I think they already got 5.0 singleimage, but the problem is with programmer.mbn. Without motorola signature it won't flash the bootloader..
still no hope...
Do you have 5.0 or 6.0 singleimage file?
am stuck in the same position. the company has to come up with the new bootloader file. or upload the xt1068 bootloader. one method is throught riff jtag . but very few repair guys have that box. in mumbai they charge 1000-1500rs to repair such phones
One morning i restarted my phone( Moto G 2nd gen.) with Android Marshmallow because it went slow, but after that it restarted in fastboot mode when i pressed the power on button. Normal startup or recovery were also not working.
I checked this forum, then unlocked the bootloader and downgraded to Android 4.4.4 . My phone operated well, then at night it started asking for lollipop update again and again, i allowed for OTA update (that was my biggest mistake), and after downloading the data and during update, my phone went off and didn't start again.
Although the indicator light glows solid for sometime when connected to wall charger or to PC via USB cable.
I have tried blankflash, ADB and fastboot utility, Volume down + Power combination, pressing power button for over 120 seconds, but all in vain.....
Please suggest me a way to solve this problems, i have important data in my phone and i want to save those too.
Welcome to the hardbrick club ^^
They all did the same mistake like you did. When you go throught the motoG Threads you will see all did the same.
The only solution is a clean flash what is not given from motorola for moto g2. The only existing is for moto g what did not work for our phones
Feel blessed, you don't have to use moto g anymore.
Anniepoo said:
Welcome to the hardbrick club ^^
They all did the same mistake like you did. When you go throught the motoG Threads you will see all did the same.
The only solution is a clean flash what is not given from motorola for moto g2. The only existing is for moto g what did not work for our phones
Click to expand...
Click to collapse
I tried with blankflash which supports android 4.4 but not 5.0, so it must be a requiring MBM-CI 5.0 ? is it available or any expected month of arrival?
aninishu said:
I tried with blankflash which supports android 4.4 but not 5.0, so it must be a requiring MBM-CI 5.0 ? is it available or any expected month of arrival?
Click to expand...
Click to collapse
. I wish I could say it was, but unfortunately Motorola won't release this file. There have been some serious attempts to solve this problem but none have succeeded.. As far as I know the only way to fix this problem is by getting a new motherboard..
Hellow
friend, do not know if motorola and released this file, or if there are already solution ?, I appreciate your answer
Diego799 said:
friend, do not know if motorola and released this file, or if there are already solution ?, I appreciate your answer
Click to expand...
Click to collapse
no blankflash.zip for our model available
if you are from india then you can try out this solution for xt1068 by an guy mobile unbrick something contact him but remember it will be paid not free
Code:
https://www.youtube.com/watch?v=WynBaVyW0oU
if you from another region then need to wait for blank flash zip
There are some methods to extract the partition layouts...one can be using dd cloning & extracting img files...another can be through B2bSupportLg Tool, also calleld BoardDiag. It does have MSM8226 chipset option, but that device is W7 G2MDS. Take a working Moto G 2014 from someone, ask them to use this tool to extract the partition schemes, then you'll get .mbn files, especially prog_emmc_filehorse_msm8226.mbn . Use that to dump into the bricked device using either QFIL Tool or use this blankflash tool, replace it's singleimage files with the one you got, then execute blank-flash.bat.
Also I had some emmc prog firehorse files, all 4 related to 8x26...You can try those & confirm me if they work or not
Hi everyone,
I own a Motorola Moto G2 (XT1068, dual sim) that came used with Android 6.0 on it.
I installed TWRP (twrp-3.0.2-3-titan.img) on it but failed to root Android 6.0 as well as 5.0 for whatever not yet understood reason. I don't do Android development for a living but I'm an IT professional, so handling adb and fastboot as well as reading and understanding instructions isn't a problem.
I flashed stock Android 4.4.4 (RETDEALL_XT1068_4.4.4_KXB21.85-14) which I successfully rooted by installing SuperSU via TWRP.
Next I updated SuperSU, verified that root access is indeed working and installed FlashFire, which I hoped to use to install OS upgrades, possibly without losing root. FlashFire is new to me (as of yesterday), everything else mentioned up to here is not.
I used the "Flash ZIP or OTA" action from within FlashFire and the previously downloaded update file in the /cache directory. I can't reproduce the file name since the phone is currently unusable and I didn't write the file name down prior to using FlashFire.
The state of the phone after this unsuccessful attempt was that of a broken USB device, i.e. unable to even register as whatever type of USB device. I learned that this can be fixed by holding the power button down for more than one minute, after which I managed to
get the phone to be shown as working "RELINK HS-USB QDLoader 9008" USB serial device in Windows 7 device manager.
I used the information in these two threads:
http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Since I started with Android 4.4.4 trying to upgrade to 5.0, I had hoped that the blank flash package for one of these Android versions would help fix my problem, but as of now, this doesn't seem to be the case. At the end of the blank flashing process, I get the message
FAILED <blank-flash:sdl-transfer-image:sdl-hello: error sending packet>
After that, the phone still has a black screen and cannot boot into anything. Repeating blank flash works after resetting whatever part of it is still working by holding the power button down for about 30+ seconds.
Is there anything obvious (or maybe even not so obvious) that I missed?
Thanks for reading and any help and/or pointers in the right direction.
hey , contact me on pm
salkollizz said:
hey , contact me on pm
Click to expand...
Click to collapse
Did you solved the problem of hard brick of Moto G 2014?
I need help with my corrupted moto g7 bootloader. I need someone who has the file mmcblk0.img to help me, because it would be the only way to try to recover my moto g7.JA I tried several options here on the forum, but my case would be a little different, unlocking the bootloader then I tried to root and corrupted everything, I'm a little bad at it and ended up doing nonsense.Now my moto g7 doesn't turn on, there is no charging and nothing appears on the screen, it doesn't connect normal usb so qualcomm 9008, it doesn't run adb, it doesn't recognize rsd .. . Could someone please help me ... The only option I saw would be a mmcblk0 file for the moto g7 to try to boot from memory card, because it was the only way I haven't tried it and unfortunately with my smatphone without working I can't extract it mmcblk0.img. Wait with a good heart to help me?
How did you find the info about needing this file? I've been searching around for several years... (not for the phone or any Motorola phone I am referring to).