Related
Due to att for 6.0 moto G does not turn over any way
resulting in a hard brick or better one bricked bootloader
because I can not access it.
Anyway, I install the Qualcomm drivers but when I use the blankflash.bat simply will not
I've tried other methods and also all the blank says only "<waiting for device>"
and I'm currently without mobile phone and hope the fastest possible response, thanks.
First of all. Why you changed your Thea/XT107X's bootloader, if it's fine for running all 5.X/6.X ROMs? A bad OTA is a possibility. Also there is no blankflash for 6.0 AFAIK. Give me more info and I might find a solution.
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
help pls
i have nexus 6 and it just stuck on fastboot icant unlock bootloader and cant boot recovery i cant flash it even with rsd its not show as motorola device
just adb reinstalled the windows and just put driver for motorola and its read android again
tested the driver with moto e and its work
so how i can recover my device if i cant flash it :crying::crying::crying::crying:
Slow down...
Give some (as much as possible really) details as to what you've done to end up where you are.
Preferably in a normal non-centered text because what you've done there is hard on the eyes (read: annoying) and almost put me off answering...
Prince_Eugen said:
help pls
i have nexus 6 and it just stuck on fastboot icant unlock bootloader and cant boot recovery i cant flash it even with rsd its not show as motorola device
just adb reinstalled the windows and just put driver for motorola and its read android again
tested the driver with moto e and its work
so how i can recover my device if i cant flash it :crying::crying::crying::crying:
Click to expand...
Click to collapse
Well as you get the info ready, I will give you some advise. RSD is useless on the nexus 6. It is moto software for moto software and the nexus is is moto in name only.
Also the drivers for the moto E and nexus 6 might not be the same thing. Just because it is a moto doesnt mean anything.
zelendel said:
Well as you get the info ready, I will give you some advise. RSD is useless on the nexus 6. It is moto software for moto software and the nexus is is moto in name only.
Also the drivers for the moto E and nexus 6 might not be the same thing. Just because it is a moto doesnt mean anything.
Click to expand...
Click to collapse
ok thaks but what should i do now ?
Provide details. LOTS of them.
Basically, we need to know what you're attempting to do here.
Strephon Alkhalikoi said:
Provide details. LOTS of them.
Basically, we need to know what you're attempting to do here.
Click to expand...
Click to collapse
wake up found it stuck in bootloader i didnt do anything
i cant flash rom or do any thing
If you have no ROM, cannot enter recovery, and did nothing to bring this state of affairs about, your phone most likely has a dead EMMC storage chip. You can verify this by trying to flash a stock ROM using the fastboot command, but be aware that attempting to use that Lenovorola program you mentioned could have done significant damage to the device, as that program is not intended for this device.
Should we be able to confirm a dead EMMC chip, there's not that many options available. If you are still under manufacturer warranty you can send the device to Lenovorola for repair at no cost. Otherwise, you'd have to pay for the repair. You could instead purchase a replacement, or purchase a device with a broken screen and swap motherboards (and SIM trays).
Hello guys, I'll try to explain what happened giving just a few context that may help give me some right direction to recover the user data that were in the phone.
As this thread got longer than I expected, summarising:
Moto G XT1033 drained battery, got into bootloop, only fastboot was working, couldn't get into recovery mode ("boot up failed"). When I tried to replace battery, after power on it's now bricked (as "qhsusb_bulk" in PC). My main goal, save user data (whatsapp folder mainly), to flash and restore Android.
Whole situation detailed, what happened:
I have a Motorola Moto G 16GB Music Edition Dual SIM XT1033 (Music edition) 2014, sold in Brazil. It was working for all these years fine, avoided upgrading Android KitKat from 4.4 because it just worked fine. In past months I noticed the battery holding less and less charge, but as I intended to buy a new phone soon I didn't care.
Unfortunately, couple days ago I heard the sound of notification "low battery... powering off". Then I plugged the charger cable and waited some time, after that, I thought it would just boot up normally, it showed "M" loading screen, with the animation etc, but it went to black screen and loop to loading screen again and again.
I tried to hold power and volume down, it went to fastboot, and when I tried start "recovery mode" but it would just say "boot up failed".
I searched for threads and people who had issue like mine and in fact, I found someone who described exactly the same problem I had, user named @ravibhat here: https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
While he didn't say he was able to fully flash his smartphone and get it back working, he said he was able to recover all his user data. I was really trying to follow his steps to at least, recover all user data, BUT, before that, my Moto G got hard bricked.
As I have another Moto G XT 1033, the exact same model as this one, but with a working battery, I thought it would be plausible to replace the battery so I could have more safety when fixing the phone, but it didn't work as that. Instead, after I disconnect and reconnect the battery, the Moto G is now hard bricked, as it doesn't boot up anymore, not even holding power + volume buttons, holding for 60s or 120s, none, nada. Rarely, the LED light blink once, nothing more. I connected to PC and it recognized as "qhsusb_bulk", after disconnecting and connecting the phone back to Windows 7, it automatically tried to install drivers and now it would just show "Qualcomm HS-USB QDLoader...." in device manager .
Now I have two issues, first, make it come back to state where I could open fastboot. Second, try to dump/save all user data, to then make a total flash/factory reset to see if I can get it working again.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) and this (https://forum.xda-developers.com/moto-g/general/guidy-to-unbrick-hard-bricked-moto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
I don't want to just go and try a bunch of (possible danger) commands and guides without having some experienced people giving advices on how to perform actions, or even if it's possible to "make some backup" of current situation, "copying whole partition", etc, before installing and flashing anything.
Device INFO:
Android version was 4.4. No Root. Bootloader is LOCKED. No customizations.
ADB Debugging state is unknown, probably it was just the default value.
What I want:
I want to get a copy of all my internal storage data, eg: WhatsApp folder, etc. Better if I could get whole storage image and just flash OS and boot loader to get back as it was...
Trying to flash it in any way that causes data loss would be my last option, but @ravibhat who had same issue few years ago couldn't even get it back working again.
What @ravibhat found out:
He thought bootloader UNLOCK would wipe all internal memory user data, but he did it and still could get all files using TWRP 2.8.x.x.
"To root the phone, I’ll have to UNLOCK the Bootloader."
"ADB can be used to backup using PUSH, PULL (may or may not require Android USB Debugging enabled)": he couldn't get it to work using adb push/pull.
Please, I would really appreciate any help from anybody, also from following users @ravibhat , @lost101 , @Teddy Lo , @Kamin4ri , @oversleeper , @jdawc7 , @sd_shadow , @SahilTech , @liveroy , @bouba148 , @bejunk , @Wolfcity, @skad00sh, @FabioSan.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/mot...oto-g-t2833798) and this (https://forum.xda-developers.com/mot...oto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
Click to expand...
Click to collapse
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
oversleeper said:
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
Click to expand...
Click to collapse
Thanks @oversleeper, I was a bit afraid because of the "blank-flash.bat" name.. but as I don't know of any other method of beginning this recovery other than unbricking using this qboot bat script, I will end up giving it a chance.
As I said before, Windows 7 auto installed the "Qualcomm HS-USB QLoader 9008" driver as soon as it recognized the "qhsusb_bulk". Do you think I should try to uninstall it and start from step 1 on this guide (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) installing the "Riff BOX JTAG drivers + Driver Signature Enforcement Overrider"?
Yes, I suggest that you install the driver's as advised in that old thread. Also, you will need to use the right qboot utility, for the right model and version of the bootloader that you have or it won't work. Unfortunately I can't help with that, you will need to search the internet and may luck be with you.
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
i think this vid will help
Greetings everyone. Sorry if I posted this in the wrong forum. Please move this in appropriate forum if I made a mistake. Believe me, for the last 7 days I have searched all of xda and internet, followed innumerable guides, FAQs and workarounds and none worked. So, as a last resort I am starting this thread
Device: Motorola Moto G5s Plus XT1804 ......4GB _64GB variant
Problem: 1) Baseband not found (unknown) Original Baseband: M8953_52.61.07.98R SANDERS_INDIADSDS_CUST
2) IMEI 0 (Sim cards are not detected).
I bought this refurbished phone about an week ago after my last LG went kaput. I was happy by the build quality of the phone. But it only ran Android 8.1 Oreo. So, I decided to put a custom ROM in it. I am not exactly a newbie to the world of CyanogenMods, Lineage OSes and Pixel Experiences. Or, so I thought. Anyways, after a lot of searching I finally decided on Dot OS 5.2 Official Android 11 version. The ROM looked very pleasing and the reviews looked positive. So, I got the unlock key from Motorola website, unlocked the bootloader, put in official TWRP recovery in it. Everything went like a breeze and in all that excitement I forgot to take a backup of the persist, efs and other partitions. A very costly mistake it seems. DotOS booted fine and looked really fresh till I found that there is a small cross near the SIM card network signal triangle up righthand side corner and the signal is only LTE and not VOLTE. I was using a Vodafone Sim card at the time. Although VOLTE option was enabled in SIM settings. To confirm my doubts regarding VOLTE I switched to a JIO Simcard and alas I was not able to make a call without redirecting through the horrid JIO calling app. VOLTE was indeed not working. So, I looked up for a fix and I found a Volte ZIP file from here https://www.google.com/url?sa=t&sou...0QFnoECBAQAQ&usg=AOvVaw0YgJvCjQWXXV8WQSJkxBOK . This was the starting of my troubles. I flashed the universal VOLTE fix zip from TWRP and it flashed fine. On rebooting, I found to my shock that my phone was not turning on. I pressed and held the power key and there was no sign of life. I couldn’t go to the fastboot bootloader or recovery. Only the white led blinked at the top when connected to the charger. My phone was apparently hard bricked. I searched frantically for a solution in this forum and YouTube wherein I found that one can bring it back to life by doing a blankflash. Found the blankflash file here https://www.google.com/url?sa=t&sou...wQFnoECAsQAQ&usg=AOvVaw1eVdBWGVFr8aiqLdP-ZkeT followed the instructions and it flashed my bricked device back to fastboot. I was relieved for a moment but the next I found that the Bootloader version has downgraded from BL C2 07 to BL C0 05. I knew something was wrong as bootloader downgrade shouldn't be possible. Also the unlock and rooted status were also lost and the baseband was unknown at this point. Anyways the device was recognised as a fastboot device and I tried to flash the stock ROM latest version using the fastboot. But, only then I realised there was something wrong with the bootloader. It gave errors like security downgrade, permission denied, preflash validation failed, remote command failed. At this point I was truly confused and worried. Why would it think the latest bootloader to be a security downgrade to a supposedly old bootloader and prevent me from flashing it. However it did flash the other files like gpt.bin for partition, oem.img, boot.img, system.img sparsechunks and everything else. I booted back to Android 8.1 Oreo and everything seemed working except my IMEI now read zero and my Simcard was not recognised by the device. After that I again unlocked my bootloader. Somehow the original unlock key worked and the bootloader screen said flashing unlocked but the bootloader didn't behave like an unlocked bootloader. The TWRP installed fine but couldn’t install the latest Pixel Experience. The flash screen said PE 11 was for Sanders and my device is (blank no name). I tried both the normal and plus and both behaved similarly. Lineage OS unofficial builds behaved similarly. I again tried Dot OS and Arrow OS and both installed fine except there was no signal. For a moment I tried to forget about the bootloader but concentrated on recovering my IMEI and Baseband but I couldn’t. For nearly 5 days I tried different guides including a detailed guide using Validus Sanders ROM but none worked. My EFS folder has files around 12 megabytes but my Persist seems deleted at zero bytes. The IMEI keeps changing between null, zero and unknown depending on the 20 something ROMs I tasted on this device. At this point, I am at a loss. This was to be my main phone and I am financially crunched. I can't buy another phone right now. I think that blankflash bootloader is corrupted and it is giving me permission denied errors. Even Magisk won't work properly. I even tried using the official rescue and smart assistant tool by Lenovo and it failed at 47 percent. I tried in different computers and Win7 to Win 11 OSes but it was of no use. I also tried getting a QCN file but I couldn’t get one for the device to recover the IMEI. Please suggest something if anyone of you can save this poor device of mine. Thanks in advance
Raghaov said:
i think this vid will help
Click to expand...
Click to collapse
Thanks for the quick reply but my phone is soft bricked now. It was hardbricked and I uses a faulty blankflash bootloader to bring it back to life. My device is softbricked now. I have lost my baseband and I have no IMEI. I cannot take calls and no mobile data. Can you show me a way to go to edl mode in my device. Thanks again.
can your phone turn on if yes can you root it with magisk
if yes then pls tell me i will tell you
I can do everything except calling and mobile data. Yes, I have rooted with Magisk and have root access. But my baseband is unknown and my IMEI is showing zero. I can't call or access mobile data. Although I can use wifi
I have tried what is shown in this video already. Didn't work
I think the blank flash bootloader was corrupt or of a different region.
so go to magisk manager and on top-right corner you will see setting click the button right next to it and click on reboot to edl
I didn't even knew that. Trying asap. Will update
Doesn’t work. Reboots back to system.
Updated Magisk to latest and tried both edl and download mode like you said brother. Everytime boots back to system. Am I missing something. The phone was not connected to the PC at the time
I am on stock Oreo now. Rooted and twrp installed
An interesting observation while installing Xposed, it gave an error that the device is not rooted properly
I have an untouched dump file for my model. The whole thing. Could you please guide me how I can restore my smartphone from that.
can you flash it through adb sideload fastboot twrp etc
I don't know but I sold the device. I bought a new one. Thanks @Raggaov for the help.
you're welcome