Hello everybody! I need help with my Moto e5 play XT1921-3 the problem that I have been facing is that the phone won't turn on like it used to. It still, charges, but I can only get it into ap fastboot mode and it does not let me access any of the features like recovery mode, because when I select it, it just turns the phone off and flashes a charging logo over and over again. I have never rooted my phone or have done anything riskful with it. It is very difficult to get it into ap fastboot with the battery inserted in the phone, but it is possible. This problem happened out of nowhere. All I did was take out the battery of my phone, after Shutting it off all the way. Then when I put the battery back in, this is when this problem started happening. This has happened to me before and I have fixed it before, using rsd lite, but now when I try to use rsd lite, I get a failed error everytime saying "failed partion gpt.bin/32" I also tried to fix that error, but I just keep getting an error after error message, I even took it to the T-Mobile store and they told me to keep it charged overnight. This is starting to get very stressful because I need my phone. If anyone can please help me, that will be very appreciated. Thank you.
Here's some stuff that should get you going again. The 3 links I posted all contain the necessary files to flash your phone to stock. You'll need the latest firmware for your phone as well. Install the Moto drivers, adb and fastboot files, and use the xml to batch converter to convert the firmware to a Windows batch script (assuming you use Windows). All the links will have instructions on installation and usage. If you need any more help let me know. I have the same device. http://www.rootjunkysdl.com/files/Android Programs/RSD_Lite_Motorola_XML_To_Batch_Script.zip
http://rootjunkysdl.com/files/?dir=Adb Fastboot Files
http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola
Related
I tried flashing back from 2.2 to 2.1 and now its stuck at bootloader.
When flashing it I saw a flash error but afterwards it said success...
The SBF flashing was a lot faster than I remembered it (it was almost instant) so I'm really thinking I might have flashed the wrong file or skipped a step.
Point being. I can no longer boot the milestone's OS, all I can do is access the bootloader.
It displays the following message: err:a5,69,4e,00,3d
Not only that, but after a few tries trying to use different SBFs with no success I got the following message on the bootload "low bttery, cannot program".
I left the device hooked on its charger all night to no avail. When plugging it onto the PC through USB it doesn't even read it.
Would someone please save my phone?
UPDATE: I managed to charge the battery by peeling an usb cable.
But the other problem still remains. I boot the device and it takes me to bootloader.
It says err:a5,69,4e,00,3d and something like ok to program
lonesomefolly said:
UPDATE: I managed to charge the battery by peeling an usb cable.
But the other problem still remains. I boot the device and it takes me to bootloader.
It says err:a5,69,4e,00,3d and something like ok to program
Click to expand...
Click to collapse
Try flashing an sbf from here "http://and-developers.com/sbf:milestone"
Let me know...
I have the same problem with boot loader 90.74 I've tried flashing using an SBF from here and-developers.com/sbf:milestone. After which the screen returns to the same error message.
Does anyone know how to reload, repair or replace the boot loader? If this was working I think my milestone could be resurrected.
Help please and thank you in advance.
need right sbf file took awhile to hunt down my cells right sbf file but mines not milestone idk if its the same or i would send it to u
Hi, my best friend she had a HD phone, one day got stuck into the M logo, the only thing I can do is get into the fastboot, no recovery no nothing.. So i try to reinstall the rom, have download several tools but i cant do anything, after several intents to install roms i hace in AP fastboot flash mode, device is unlocked status code 1fastbookt Reason sticky bit factoy_fastboot. for a 2nd time but i can install roms, I dont know if phone bootloader unlock and cant check... I dont know if phone is usb debugging cause it wont load the system. I dont see any internal files from phone I also try rsd lite, but the same it says that it start doing the process but nothing else happen.. any ideas on how to get a rom install there..
thanks
SAME thing..
Please do help us...No recovery...No debugging...stuck at logo..!!
If you don't have an unlocked bootloader, I don't think you can use Myth or RSD to flash an ICS rom over a JB rom.
Did you load the latest Motorola USB drivers? When you connect the phone, run adb to list the devices. Does your phone appear?
not for me doesnt show any devices... and while trying to do other commands always get stuck ad *daemond started succesfully* but doesnt do anything.. also when trying to use motorola device manager it says it will update and never connect to server and close the app.
if i do fastboot commands like reboot-loader it does work it reboots the phone, but if i try to flash something doesnt it doesnt do anything.. i try using mfastboot also and the same happen.
Is there a way to flash a rom or something so i can fix this phone or it is dead?
On the Fastboot screen, if it says UNLOCKED in capitals next to "Device Status:" , then this problem is easily fixable.
Download RSD Lite from here: http://forum.xda-developers.com/showthread.php?t=2231249
Download Motorola Stock Firmwares:
Stock Jellybean for AT&T: http://sbfdownload.droid-developers...MB886_NII_TA-2-16-release-keys-NII-MX.xml.zip
Stock Jellybean for Bell Canada: http://sbfdownload.droid-developers...FFW-11-4-release-keys-BellMobility-CA.xml.zip
Open up your zip file and replace the .xml with the new XML you will download from this link: https://www.box.com/s/num1eshkf0c2or2h4160 You really can't forget to do this!
Launch RSD, connect device to PC, make sure RSD recognizes it. Navigate to your firmware file, select it, and press the start button. Sit back, relax, and let it do its work. It will take around 5-10 minutes. Do not unplug the cable, and do not attempt if you are in a situation in which you think you may lose power (especially if running from a desktop PC).
If RSD Lite won't work, then this thread will show you how to manually flash your stock firmware: http://forum.xda-developers.com/showpost.php?p=40929335
Basically, you repeat all the instructions I just gave you and then manually input some lines in Command Prompt.
Hi,
so I rooted my phone, unlocked the bootloader, installed TWRP, put in 3 different ROMs on my External SD card, went ahead, deleted EVERYTHING from the phone, tried flashing ROMs, not a single one worked.
I rebooted the phone because I saw no other option, TWRP said that there is no OS, I went ahead and did it.
Now the phone won't start, I tried returning it to stock firmware as per lg-phones website guide (worked before, though my phone was not this messed up, I could access download mode and now I can't), but I keep getting connection problems. I have tried doing this with the phone just "turned on", it hangs on LG logo for infinity.
When I try putting the phone in download mode, the only thing I get is fastboot. When I try to use adb devices and other similar commands, it says device not found or simply does not list it, regardless of the "mode" the phone is in. However if I try and use LAF RECOVERY MULTITOOL, it detects my phone and I can use fastboot commands. I have custom recovery, boot and laf imgs on my PC, I tried flashing them all, PC and phone tell me everything's ok, but when I restart the phone, I get nothing... what am I doing wrong, and can this be fixed? If you have any questions, I'll answer to the best of my ability.
Thanks in advance!
SOLVED!!!!
Just found a backup laf.img that enables download mode... PHEW!
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.
I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!
ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk
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]