Phone refuses to comunicate at bootloader - Moto G7 Plus Questions & Answers

Hello, recently i had some issues with my phone, and i thougt. well i should do a factory reset, just in case, but when i did the reset, the phone was in the same condition as before, so my next step was to reflash the stock rom, im not in custom ones btw, and my phone is still locked, long story short, with every program comand, and even oficial software, my phone refuses conection, with android cmd tools, its always stuck forever in a line called, sendig partition (45kb) and thats all it can be there for hours, the phone is just doing nothing, also the booloader oficial cmd, cant extract the key just sit there doing nothing, however, my phone is not bricked, bootloader devices detect my phone but i cant reflash the phone, i already tried the blank flash cmd, just say waiting for device. can someone help me with this issue? im not a noob, i already save one moto x with blank flash and rooted several past generations of moto phones.

priviet.toledo said:
Hello, recently i had some issues with my phone, and i thougt. well i should do a factory reset, just in case, but when i did the reset, the phone was in the same condition as before, so my next step was to reflash the stock rom, im not in custom ones btw, and my phone is still locked, long story short, with every program comand, and even oficial software, my phone refuses conection, with android cmd tools, its always stuck forever in a line called, sendig partition (45kb) and thats all it can be there for hours, the phone is just doing nothing, also the booloader oficial cmd, cant extract the key just sit there doing nothing, however, my phone is not bricked, bootloader devices detect my phone but i cant reflash the phone, i already tried the blank flash cmd, just say waiting for device. can someone help me with this issue? im not a noob, i already save one moto x with blank flash and rooted several past generations of moto phones.
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

I had a similar problem just now - could not do anything in fastboot mode, LMSA failed as well. To solve it, I switched to another PC, and stopped using USB3 to USB-C custom cable, and used the original one I got with the phone (USB-C to USB-C). So my guess is, you need to connect to the PC with the original cable, directly, or just with a better cable than the one you were trying with.

my motog7 Lenovo android is stuck in bootloader mode tried to reset or restart nothing keeps jus sitting there Help

Gingerale2020 said:
my motog7 Lenovo android is stuck in bootloader mode tried to reset or restart nothing keeps jus sitting there Help
Click to expand...
Click to collapse
What does getvar all say
Code:
fastboot getvar all [/Code
[url]https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039[/url]

Related

[Q] File recovery after soft-brick

I have an HTC One M7 on T-Mobile, v4.4.3, with a locked bootloader and no root access (never got around to rooting). So the phone is basically completely untouched from a developer standpoint. I had previously accessed the developer options and I'm pretty sure I left USB debugging checked although not 100% positive.
The past few days my phone has been randomly rebooting, and then today I randomly found it in a state of apparent upgrading even though there are no new OTA updates (I checked yesterday). Then it was "optimizing apps" and going through all of them. Then it rebooted and ever since that point it has been stuck on the HTC ONE logo and will not boot to the home screen. I'm able to access the bootloader (HBOOT 1.57). I'm also able to access the stock recovery, from which I wiped the partition cache and rebooted with no success.
I have a ton of pics and videos from the first year of my son's life on the phone and stupidly did not back them up. I really want to avoid doing a factory reset if possible. Is there any way to recover these files?
I installed minimal ADB and fastboot. From within fastboot on the phone, I can see my device when typing "fastboot devices" in the command prompt. However, it does not list any devices when I enter "adb devices" in the command prompt, regardless of whether my phone is in the bootloader, fastboot, recovery, or stuck on the logo screen. I reinstalled updated HTC drivers and also tried with a universal ADB driver. I've tried multiple usb cables and all USB 2.0 ports, using Windows 7. While in fastboot, when I connect my phone to PC via usb cable, the computer makes the typical sound that it does when a USB device is connected and unconnected, however no drive/mount shows up.
All I want to do is find my device somehow on the PC and extract my photos and videos. I was hoping to use "adb pull" to do this but it just won't find my device. At this point, unlocking the bootloader and installing a custom recovery will wipe all data anyway, correct? Is there any way that I can recover my data in this situation?
Any help would be greatly appreciated since I'm at a complete loss and losing this data would be terrible. Thanks so much in advance!
mac12383 said:
I have an HTC One M7 on T-Mobile, v4.4.3, with a locked bootloader and no root access (never got around to rooting). So the phone is basically completely untouched from a developer standpoint. I had previously accessed the developer options and I'm pretty sure I left USB debugging checked although not 100% positive.
The past few days my phone has been randomly rebooting, and then today I randomly found it in a state of apparent upgrading even though there are no new OTA updates (I checked yesterday). Then it was "optimizing apps" and going through all of them. Then it rebooted and ever since that point it has been stuck on the HTC ONE logo and will not boot to the home screen. I'm able to access the bootloader (HBOOT 1.57). I'm also able to access the stock recovery, from which I wiped the partition cache and rebooted with no success.
I have a ton of pics and videos from the first year of my son's life on the phone and stupidly did not back them up. I really want to avoid doing a factory reset if possible. Is there any way to recover these files?
I installed minimal ADB and fastboot. From within fastboot on the phone, I can see my device when typing "fastboot devices" in the command prompt. However, it does not list any devices when I enter "adb devices" in the command prompt, regardless of whether my phone is in the bootloader, fastboot, recovery, or stuck on the logo screen. I reinstalled updated HTC drivers and also tried with a universal ADB driver. I've tried multiple usb cables and all USB 2.0 ports, using Windows 7. While in fastboot, when I connect my phone to PC via usb cable, the computer makes the typical sound that it does when a USB device is connected and unconnected, however no drive/mount shows up.
All I want to do is find my device somehow on the PC and extract my photos and videos. I was hoping to use "adb pull" to do this but it just won't find my device. At this point, unlocking the bootloader and installing a custom recovery will wipe all data anyway, correct? Is there any way that I can recover my data in this situation?
Any help would be greatly appreciated since I'm at a complete loss and losing this data would be terrible. Thanks so much in advance!
Click to expand...
Click to collapse
unfortunately, you need a booted rom or a custom recovery to use adb commands, so you can't pull your files from the bootloader or from the stock recovery. You already wiped cache and tried to reboot... Not much you can do except maybe to try reflashing the firmware and see if your phone can boot. Can you post the output of "fastboot getvar all" except imei and serialno?
alray said:
unfortunately, you need a booted rom or a custom recovery to use adb commands, so you can't pull your files from the bootloader or from the stock recovery. You already wiped cache and tried to reboot... Not much you can do except maybe to try reflashing the firmware and see if your phone can boot. Can you post the output of "fastboot getvar all" except imei and serialno?
Click to expand...
Click to collapse
Thanks for the quick reply. Here's the info.
Would reflashing firmware require the bootloader to be unlocked? It wouldn't wipe my data?
mac12383 said:
Thanks for the quick reply. Here's the info.
Would reflashing firmware require the bootloader to be unlocked? It wouldn't wipe my data?
Click to expand...
Click to collapse
no with s-on, bootloader must be locked to flash firmware.
What you could try is to download the 6.10.531.9 RUU and extract the firmware.zip and flash it to your phone.
Firmware.zip must be in the same folder where adb and fastboot are then open a command prompt (minimal adb/fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fasboot reboot
If this doesn't work I think theres nothing we can do (to access your files) At least you can restore your phone using the complete RUU
alray said:
no with s-on, bootloader must be locked to flash firmware.
What you could try is to download the 6.10.531.9 RUU and extract the firmware.zip and flash it to your phone.
Firmware.zip must be in the same folder where adb and fastboot are then open a command prompt (minimal adb/fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fasboot reboot
If this doesn't work I think theres nothing we can do (to access your files) At least you can restore your phone using the complete RUU
Click to expand...
Click to collapse
Thanks, I'll give that a try soon, probably tomorrow, and let you know how it goes. Appreciate the help
mac12383 said:
Thanks, I'll give that a try soon, probably tomorrow, and let you know how it goes. Appreciate the help
Click to expand...
Click to collapse
I flashed it successfully, but unfortunately the phone still did not boot to the home screen. I'll hold off on wiping everything for a little longer in case anyone has any other ideas. Thanks for the help!
HTC and T-Mobile were of no help, as suspected. I guess I just find it strange that there's NO WAY to recover data from a soft bricked phone. If I was some big-time criminal who was arrested by the FBI and my phone was seized in this condition, their analysts would have no way of getting into my phone and recovering the data? Maybe I just watch too many crime shows, I don't know...but that seems a bit unbelievable. Is there no way to (carefully) take it apart and access the hard drive in some other way? I'm desperate...
mac12383 said:
HTC and T-Mobile were of no help, as suspected. I guess I just find it strange that there's NO WAY to recover data from a soft bricked phone. If I was some big-time criminal who was arrested by the FBI and my phone was seized in this condition, their analysts would have no way of getting into my phone and recovering the data?
Click to expand...
Click to collapse
Yes they would disassemble the phone, de-solder the emmc chip and extract its data which is not an easy task...
Maybe I just watch too many crime shows, I don't know...but that seems a bit unbelievable. Is there no way to (carefully) take it apart and access the hard drive in some other way? I'm desperate...
Click to expand...
Click to collapse
There is no hard drive in your phone, its a memory chip (emmc). It is soldered to the main board and can't be removed by the user.
see the chip highlighted in orange? This is where your data is stored.
If you can't boot to the OS, your bootloader is still locked, and you have already tried to erase cache and reflashed the firmware, afaik, there's nothing more you can try
alray said:
Yes they would disassemble the phone, de-solder the emmc chip and extract its data which is not an easy task...
There is no hard drive in your phone, its a memory chip (emmc). It is soldered to the main board and can't be removed by the user.
see the chip highlighted in orange? This is where your data is stored.
If you can't boot to the OS, your bootloader is still locked, and you have already tried to erase cache and reflashed the firmware, afaik, there's nothing more you can try
Click to expand...
Click to collapse
I was afraid of that. Thanks for all your help though

[Q] [ q ] how to repair bricked (bootloader) moto x 1052

How to repair my bricked moto x xt 1052
Hi everybody...
Im new here.
I hope someone resolve it.
My moto x xt 1052 is bricked, means it is not powerup normally, no any screen displayed, no boot image, boot animation, but goes into fastboot mode sometimes on trying to go in it using hardware key pressing i.e. Power and volume down keys.
Here is the brief description what was happened......
My moto was on stock kitkat 4.4.4 for upgrading it to lollipop On 19th jan i was tried to flash cm12 over cm11 nightly as described in that thread , for that i was unlocked my bootloader, rooted it, flashed CWM touch recovery, flashed superSu zip file and flashed cm12 nightly over cm11 as described. But my device was stucked at boot logo. For resolving that issue i was flashed boot.img of prev nightly release(i.e. 1/15) through command promp using commands '' cd Downloads... cd fastboot... fastboot flash boot boot.img.
It flashesh image file successfully and device is booted successfully. I was used it till last 4days and regularly updated cm12 nightly via cmupdater.
But 4days back i was tried to remove warning message of device is ulocked bootloaded which was irritated me using same flash method and logo.bin files which was given in another thread by other members. But my BOOTLOADER IS DAMAGED and no any display was seen. I read many threads to repair it but no anyone give easy step by step guide. I was tried to repair it using motoflasher given in 1 thred. But as shown there no my device was not shown in device manager asQUSB****9** THERE is only adb interface in device manager. Also it says in motoflasher that no device was connected and output was incorrect COM port, which was refused to flash bootloader. Another thred of rescurrection of bootloader is not so easy and also download links are not useful,shows item was removed.
There is no another way, i thought bootloader is a kernel, so i was flashed zwiel kernel by same flashing method by cmd.
The problem remaims same, moto care told thay it will cost 6k for repairong which is too high. The descreltion is given in details for anyone who finds my mistakes and tell me angd give me suggestion. Xda is big deveopers forum, i know someone will help me.. So plzzz help me.
HOW CAN I REPAIR MY BOOTLOADER AND SAVE MY MOTO which will not useful then usable as a paperweight.
Have you tried to simply re flash your stock 4.4.4 firmware via fastboot since you say you can get into fastboot mode? Or rsd your 4.4.4 firmware. If you can get into fastboot mode I think you should be able to fastboot your stock 4.4.4 and be back up and running.
When in fastboot mode and phone plugged in and you type "fastboot devices" does it display a string of numbers for your device? If yes then you are good to go.
I am having a similar issue with a Sprint Moto X (1st Gen). I am able to get to fastboot mode and I have flashed the stock image for 4.4.4 using mfastboot (also re-did it using RSD lite as the boot.img gave errors using mfastboot) but the phone only still boots to a dark screen and vibrates roughly every 15 seconds.
Anyone have an idea on what else I can try? I've been scouring the boards and youtube, but haven't really come across anything on this type of issue.
Has been RDS flashing process totally completed without any errors?
The flash finishes with no errors when it goes to reboot the phone I end up at the same spot of a black screen that vibrates like its powering on then repeats every 15 seconds like its stick in a loop. Odd... I never get the smallest hint to a picture on the screen.
​
chousue said:
The flash finishes with no errors when it goes to reboot the phone I end up at the same spot of a black screen that vibrates like its powering on then repeats every 15 seconds like its stick in a loop. Odd... I never get the smallest hint to a picture on the screen.
Click to expand...
Click to collapse
Your symptom I'm quoting is what I've seen when a bad logo.bin has been flashed to the phone.
Can you try another? Some are in http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
Thanks for the suggestion.
I tried a dew different logos but the end result is still the same. Vibrates on power up, no display at all and repeats until I hold the volume down and count to like 10 when the next buzz cycle would happen so I can get into fastboot mode again. I should note that I can't see anything in this screen as well. I was starting to wonder if it was the screen that was the issue but the bootloop has me thinking otherwise.
I have another one with a bad screen and a replacement is on the way. I guess I can test it on this one as well but I'm sure the result will be the same.
I took a gamble on this one thinking I could bring i back to life, I figured the last owner just soft bricked it and flashing the latest stock would override what mess they did. I'll tinker around some more if there are some other options otherwise I can just flip it for parts i guess.
If I run the fastboot getvar all I get all the phone info so it gives me hope that something can be done, I just don't know what, it seems like I keep cycling through the same few processes hoping for a different result. I even tried the power + Volume down for two minutes thing that's supposed to bring up the "other" recovery menu, but with no display, i don't know what happening.
In a last ditch effort I did a tear down and connection check for all the parts so everything has been removed and firmly re-attached, certainly was nice to do that there instead of on the one I know will work once I replace the screen, but it sucks to still come up empty handed. Sorry for the long rant, it's just been a long few days of trying to find ways to bring this phone back to life.
Solved with downgrading
Sorry for bad english.
I had same issue.
But solved prev saturday hole day.
Using manual method instead of rsd.
Make sure u properly installed adb and mfastboot. For that open cmd and type adb. It shows command lines and then mfastboot. It also shows command lines then you are ready to go. If not, google it for how to install adb and also for mFastboot
Then download proper stock firmware for ur device. unzip it, u will get files of system, boot etc. Copy all this files and paste into mfastboot folder. Open command prompt in that folder by pressing shift and right key of mouse.
Then boot your moto into fastboot mode by pressing power and volume down key for a seconds. If u will not get in to fastboot mode try for many times unless u get it. I will get it after trying half hour.
Connect ur device to pc and run commans given in the following link. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
End with-- fastboot adb reboot. It will reboot ur device.
Enjoy.
Thanks for the steps, I feel like I have done that already save for the few end steps with the oem commands.
So I flashed the print image using that guide and it still vibrates every 15 seconds and no display. I grabbed the retail file from the motorola site (oddly enough they only have TMO on the file name for some reason) and I flash this and it doesn't vibrate every 15 seconds, but still no display... Maybe in the end the display is bad after all...
Like mentioned before, I already have one coming in black for the one that works for sure...so I guess I'll test it on this one as well. Just wish it was as easy to disconnect/connect as my Nokia Lumia was, that took less than 10 minutes!
So, in the end it was the display afterall. I ended up getting another replacement screen as I really did not feel like attaching it and detaching it (yeah, I'm lazy sometimes). After setting up the new screen I plugged it in to charger and what do you know, battery at 0% then the motorola bootloader unlock screen after 5 or so minutes.
Now I have two phones, lol. One screen came without the speaker on the to fro some reason... And I think I just messed up my main phone removing the frame to add in that piece so lint and such doesn't get into the phone so easily... Dang it!
Edit - Yep, now it has a nice rainbow line display across the bottom where the navigate soft button would be... Guess I have to get one more screen!
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
sadik2112009 said:
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
Go to the General Forum there's a dedicated thread with official roms for your particular model. Use download the ROM and flash through rsdlite. Always make a backup since it will wipe your internal storage clean.
Sent from my XT1058 using Tapatalk
sadik2112009 said:
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
If you installed 5.1 by using one of the TWRP backups, and did NOT flash the leaked OTA zip files, then you should have only touched /system and /boot partitions.. in that case, it would be safe to flash 4.4.4.
thank u so muchh......
KidJoe said:
​
Your symptom I'm quoting is what I've seen when a bad logo.bin has been flashed to the phone.
Can you try another? Some are in http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
Click to expand...
Click to collapse
thank you so much... this post saved my moto x...... i am facing this issue from last 15 days. so many pages visited but nothing help, but, after doing this it rebooted. may god bless you!:angel::angel::angel::angel:
Having same problem.
Please help if anyone can!
I can't resolve it by Fastboot in cmd.
I also tried typing mfastboot in all commands.
Having same problem.
Please help if anyone can!
I can't resolve it by Fastboot in cmd.
dont display anything
not charging not boot not start anything
Travisdroidx2 said:
Have you tried to simply re flash your stock 4.4.4 firmware via fastboot since you say you can get into fastboot mode? Or rsd your 4.4.4 firmware. If you can get into fastboot mode I think you should be able to fastboot your stock 4.4.4 and be back up and running.
When in fastboot mode and phone plugged in and you type "fastboot devices" does it display a string of numbers for your device? If yes then you are good to go.
Click to expand...
Click to collapse
I have a moto x of my friend xt1053, dont not what he has done with it.
but
it is in Encryption Unsuccessful Condition.
When I connect to pc. Windows show that motorola xt1053 is connected. device manager shows MTP device under portable devices.
Mototrola USB drivers have been installed successfully.
I can not boot xt1053 into fastboot mode or recovery. Neither by adb/fastboot nor by buttons. (volume down + Power).
adb devices command does not show any numbers as it normally does when device is connected.
how get it back to working condition. any expert to help or happen to be in the same boat?

Moto G xt1072 won't boot at all after installing TWRP+SuperSU

Hello everyone,
I've just tried installing twrp-3.0.2-3-thea.img (md5sum: 35c37561f0c22bfe23cd01b5c388e8b5) and BETA-SuperSU-v2.62-3-20151211162651.zip (md5sum: 7fcb30bcbcd18b5f0b0f5848a096d4ed) on a Moto G LTE 2014 "Thea".
Unfortunately something didn't work. The device first was stuck in the boot animation, then started booting correctly a few times, but now it's completely bricked:
I've been unable to turn the phone on using either pressing power+button down for 10 secs or just pressing the power button for 2 mins while being connected to an usb charger. Obviously it won't connect to adb/fastboot/etc.
I'm really puzzled. Is it even possible to brick a device like this just by trying to root it? Any suggestions?
Alright, found the issue - it seems that for some reason or another flashing TWRP or SuperSu caused fastboot to stop working, hence the hard brick. Now It shows up as "qhsusb_bulk" - unfrotunately there's no way to fix this by myself given that the only fastboot images ( "MBM-CI") available are for Android 4.4.4.
If your bootloader is unlocked you shouldn't have any problems reflashing. You do however have to make sure you are flashing the correct recovery IMG for your phone there are a very large number of ROMS and each is device specific. Try leaving LTE out of your search criteria when searching for images to flash with, rather just Moto G 2nd gen 2014 and you will be on your way to finding the correct IMG. I found a Titan IMG that works with my XT1072 and believe you me that was after the 5th/6th time of reflashing! Another handy tip is that in order to enter into fast boot or recovery mode there's are a few things to consider, namely
The version of fastboot adb you have installed on your PC, some versions behave strangely? Don't ask me I know nothing!
Secondly and very importantly you need to have latest drivers for your make and model of phone installed on your PC.
Thirdly before you connect your phone via its USB cable to PC you must first start up fastboot if you are just using fastboot. I have mine sitting as shortcut on desktop right next to adb shortcut for convenience.
Fourth: hold power button plus vol down for about 3-5 seconds, continue to hold vol- button but let go of power button (this is an important detail that many people on the forum forget to mention) with Motorola specifically!!!! Trust me do it this way and you will almost certainly always boot into recovery/fastboot mode
5th connect your phone to your PC ( not to teach your grama how to suck eggs but don't forget to select USB debugging under dev options on your phone) hopefully you did this??? Otherwise I don't know what the work around is for that, other than factory reset and start over?!
Anyway after connect to PC in the shell terminal run the adb devices command if you are in adb or
run the fastboot devices if you are in fastboot to see if your computer can detect your device? This is a clear indication of whether or not your bootloader is unlocked and/or whether USB Debugging is selected, shouldn't be hard to work out which device is yours as only one device should then show up. There are threads on XDA about how to unlock BL. Aquire root and flash recovery images, obviously, but I couldn't begin to tell you how to do that as each scenario is so different from the next, best of luck!:good:
None of those solutions would obviously work, considering the bootloader/fastboot partition has been altered to the point the device won't boot at all, forget about Drivers or USB Debugging.
By the way, I've just got my device from motorola, after roughly two months since they took it to the repair centre. Their official response has been "We won't fix devices who had been tampered with".
Oh well. When I got it back the clerk could only congratulate me for my really nice new paperweight.
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Now It shows up as "qhsusb_bulk"
Click to expand...
Click to collapse
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
LuuchoRocha said:
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Click to expand...
Click to collapse
Completely blank screen. No response whatsoever.
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
Click to expand...
Click to collapse
That's right. It's the same error which occurs on some MSM89xx SoCs when the bootloader/blankflash gets steamrolled. But contrary to what happens to some devices like the Galaxy SIII, there are no available bootloader image files available anywhere, and it looks like the SoC used on mot g devices does not provide any failsafe boot mode from sd.
In other words, it's a really nice paper weight until a disgruntled Lenovo employee leaks the required files somewhere. Actually, according to the Motorola tech guy I've spoken to, there's the chance that clearing the bootloader triggers an efuse making it impossible to recover from altogether, but I really hope this is not the case.

Phone in Hard Brick mode

I was trying to install Arrow OS custom ROM to Motorola one power using TWRP. It got flashed, when I flashed the Gpps Rom with it, it didn't flashed and I rebooted the phone right there. The phone is now in a hard brick mode and is not responding to anything, is there anything I can do to fix it? Could you please guide me with the complete procedure?
You must use a blankflash to boot bootloader.BlankFlash available for
Moto One Power (Chef) https://mirrors.lolinet.com/firmware/moto/chef[/
.1 install Motorola drivers,2 install quallcom drivers for Motorola procesor(gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows) .3 use flashbat in blankflash directory,4 press volume down and power on phone.5 connect phone with pc and proces will be starting.if your phone starting in bootloader mode ,you can flash stock room
Thank you for your help and response. I followed the steps as you mentioned. On step 3 when I run the Flashbat file, It gives the below error, and the phone never started
[112.478] ReadFile() failed, GetLastError()=0
[125.434] ReadFile() failed, GetLastError()=0
when blankflash starting you can release the wolume and power.try differrent usb port in pc.I have the same problem with custom roms,You see port com in device manager on pc?
It worked, but how did you know all this? Just spot on :good:
I tried this method but not working on my phone, xt1942-1. This is the Chinese version p30 note I got from AliExpress. I see the device in device manager as port 9008
Any help would be appreciated!
Hi,you are try change a port USB in PC?this method works,my phone is the same like your,Moto p30 note from aliexpress
Thanks, I tried all usb ports on my pc but same problem. Should we press power and volume down buttons after connecting to pc? Please help I just got this phone today and bricked right away ...
Also there are two blankfash versions on the link you provided which one to use?
Hello again.you can reinstall drivers,change partition with blankflash folder.last time when I'm bricked my phone ( trying flash customrom )I waste half day to recover my moto.im change drivers,folders,USB port,try the same on laptop and nothing.But when I'm wakeup morning and try one more time it's works!I don't no why,maybe I'm stupid,but I think is a problem with drivers or something.You must try more and more,and do not give up!I'm use blankflash from Android 9
dadm said:
Hello again.you can reinstall drivers,change partition with blankflash folder.last time when I'm bricked my phone ( trying flash customrom )I waste half day to recover my moto.im change drivers,folders,USB port,try the same on laptop and nothing.But when I'm wakeup morning and try one more time it's works!I don't no why,maybe I'm stupid,but I think is a problem with drivers or something.You must try more and more,and do not give up!I'm use blankflash from Android 9
Click to expand...
Click to collapse
I tried again today and Voila its working! Blankflash literally tests your patience. Thanks @dadm for your suggestions and now I have a working moto one power as my daily driver!
htcmusic said:
I tried again today and Voila its working! Blankflash literally tests your patience. Thanks @dadm for your suggestions and now I have a working moto one power as my daily driver!
Click to expand...
Click to collapse
Hi @dadm I could not get my SIM card detected in RR rom and tried to flash stock again. Now I am in a bootloop whatever I do. Which stock did you use to revert back? And is your SIM card detected?
I have a few questions if anyone could answer. I am looking to get hands on this phone but making sure everything goes as I expect.
1.Does any member have knowledge which of this Device variants (XT1942-1, XT1942-2, XT-942-3) qualify for "Unlocking Boot-loader" and which variant does not support unlocking. I am lookig for 4/64gb Chef.
2. Is there Any Custom Pie Rom with Solid stability + Efficient & Effective Kernel?
3. Does stock Motorola Camera app works 100% in a custom flashed Rom as it does in Stock Rom or we have to use Google Pixel Camera apps as an alternative?
4. Is there anyway to get back to stock image from Custom rom.
5. How to recover the device from a Hard Brick.
6. Not but least. How well this device performs while playing PUBG.
Phone flashing locked and stuck at fastboot mode
I have done a stupid thing after flashing stock ROM I have flashed twrp and my stock ROM was stuck at loop after that I have locked the device and it showing it device is corrupted and will not boot
Could any body help me plss.??
I tried this blankflash.bat but it showing <waiting for device> my phn is already connected to pc
Ravi2730 said:
I have done a stupid thing after flashing stock ROM I have flashed twrp and my stock ROM was stuck at loop after that I have locked the device and it showing it device is corrupted and will not boot
Could any body help me plss.??
I tried this blankflash.bat but it showing <waiting for device> my phn is already connected to pc
Click to expand...
Click to collapse
Phone must be in EDM to flash blankflash
Sent from my ali using XDA Labs
Thanks for reply
sd_shadow said:
Phone must be in EDM to flash blankflash
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Actually how to enter EDM mode could you pls explain in steps my phone just start into fastboot,no recovery, no boot. Pls help me bro.
Problem solved
Ravi2730 said:
Actually how to enter EDM mode could you pls explain in steps my phone just start into fastboot,no recovery, no boot. Pls help me bro.
Click to expand...
Click to collapse
Anyone stuck in fastboot when it shows your phone is corrupt and will not boot just flash the command
fastboot boot boot.img file in stock room phn will automatically start everything working it work as a flash...?

How do I unbrick my unrooted HTC 626G?

(I couldn't find this exact problem on the forums, forgive me if I overlooked it)
I tried booting my mom's old phone, an HTC Desire 626G, but it is stuck in a bootloop. When I try to enter recovery mode (by pressing power + volume down), it just enters the loop again.
I can however enter what I think is the bootloader menu, giving me three options: recovery, fastboot or normal boot. Fastboot freezes the phone, the other two options just start the bootloop. I've never installed a custom ROM.
I disassembled the phone, un- and replugged the battery to no avail. I tried ADB but I never enabled USB debugging in the first place, so that doesn't work either.
Do you have another idea that might work?
dulfried said:
(I couldn't find this exact problem on the forums, forgive me if I overlooked it)
I tried booting my mom's old phone, an HTC Desire 626G, but it is stuck in a bootloop. When I try to enter recovery mode (by pressing power + volume down), it just enters the loop again.
I can however enter what I think is the bootloader menu, giving me three options: recovery, fastboot or normal boot. Fastboot freezes the phone, the other two options just start the bootloop. I've never installed a custom ROM.
I disassembled the phone, un- and replugged the battery to no avail. I tried ADB but I never enabled USB debugging in the first place, so that doesn't work either.
Do you have another idea that might work?
Click to expand...
Click to collapse
Bro You need to flash the factory firmware using a pc with that fastboot mode.....
The existing firmware might have been got corrupted or the storage might have been damaged, since its an old device(which is very rare),
To do so u can find many articles on the internet very easily,
brokenbrain939 said:
Bro You need to flash the factory firmware using a pc with that fastboot mode.....
The existing firmware might have been got corrupted or the storage might have been damaged, since its an old device(which is very rare),
To do so u can find many articles on the internet very easily,
Click to expand...
Click to collapse
Thanks a lot, I'm finally able to communicate with my phone via PC now. Booting still doesn't work but now I can at least format the storage and hopefully flash the factory ROM.

Categories

Resources