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.
Related
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?
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).
Can someone explain this
bwtmanagement said:
Can someone explain this
Click to expand...
Click to collapse
I've not experienced this.
Are you rooted / bootloader unlocked?
Do you have any idea what caused it?
Were you able to recover?
If so, what did you have to do?
bwtmanagement said:
Can someone explain this
Click to expand...
Click to collapse
Did you do anything to the bootloader by flashing any files? Did you unlock the bootloader? If the answer is yes then you might have an issue with flashed files.
If no and you have not touched the device then you might have a rare error. If you have a carrier phone with Verizon you might want to try their "repair assistant" which is the same as what is mentioned on the phone screen. It seems to have a repair function. You will have to connect the phone via USB to your computer. Download the assistant from here. https://www.verizonwireless.com/support/knowledge-base-209211/
If you don't have a Verizon moto x4 or you have another carrier then either still give the software a shot or take it to a Motorola service centre.
Can pretty much confirm the same with an old moto z force post on the Lenovo forums. If you have Verizon downloading the software will solve the problem.
I know that I was trying to flash to stock and that was the result, rsd can see the device but when I flash it it says failed to switch to fastboot
Yea bootloader has been unlocked for weeks and started acting up and I was trying to clear it and start over and no I can't get it to flash spar_chunks
Any ideas
Notice you mentioned RSD failing to switch to fastboot... I assume you tried reflashing the GPT/bootloader directly from fastboot?
If you hit volume up/down from the screen you posted, does it go through the other fastboot screens?
No i get the quausb or whatever that is in my comp for deviecs now...and no screen mow and yes the parition was compermised by error on my part
I have the Moto E5 Play, the XT1921-5 model from Boost. I was given it by a friend who asked if I could save it. Apparently, he must have flashed a wrong kernel or rom and it will only go to a screen telling me Startup Failed and to hook it up to the Software Repair Assistant to fix it. Well, The Software Repair Assistant is for the Verizon models. This is the Boost version. Tried flashing stock firmware but won't let me do it. If you notice on the fastboot screen it reads the correct model but the eMMC and DRAM say SAMSUNG. Also, the baseband version it says does not exist. Does anyone have any clue as to what this dude did or if it is even possible to repair? It's a brand new phone just can't install an OS. Any ideas would be appreciated
The device is booting into what is called [circa AOSP @ https://developer.android.com/docs] a Yellow-Boot mode. Unfortunately, without the device's bootloader unlocked,a yellow boot bricks a device. That's my guess.... I would go ahead and try the software repair assistant (even though it's for vzw devices) & just see if you can salvage it at all..... I know I had a vzw great play and after rooting it with the Magisk 13.3 tethered exploit, I came to this screen after flashing a modified boot.img w/ a locked bootloader, and I had to use the software repair assistant to salvage it. If that doesn't fix it, maybe try to sideload the stock firmware through recovery..?
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