Related
Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.
shartwell said:
Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.
Click to expand...
Click to collapse
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X
flashallthetime said:
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!
shartwell said:
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!
Click to expand...
Click to collapse
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X
flashallthetime said:
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.
Follow what flashallthetime is suggesting.
btw, Rogers firmware is correct for your phone as there is no Fido specific firmware.
shartwell said:
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.
Click to expand...
Click to collapse
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X
flashallthetime said:
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X
Click to expand...
Click to collapse
Getting somewhere...
The command prompt can seemingly now interface with my device. It runs commands but clearing the cache didn't fix the problem. I've ran the command though so if there is a next step...
EDIT: Okay it's charing and I can interface with it via cmd. I can now use RTDlite with it as it's battery is charging. Should I flash the other Rogers now? I have my unlock code for the bootloader if that's what I've got to do first.
Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA
Steve-x said:
Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA
Click to expand...
Click to collapse
It's all fixed up. Thank you everyone who contributed to this! Time to enjoy my phone.
Last thing would be flashing twrp. Does someone have a link to the proper files?
Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X
flashallthetime said:
Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X
Click to expand...
Click to collapse
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?
shartwell said:
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?
Click to expand...
Click to collapse
Here's twrp http://forum.xda-developers.com/showthread.php?t=2458449
Flash with fastboot( fastboot flash recovery twrp 2.6.3.IMG)
Place the recovery image in platform tools folder. After it flashes make sure you go directly to recovery by pressing the volume up bottom to make it stick
Sent on my Moto X
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?
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.
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]