Database Develop

Managed to screw up phone, but bootloader still works.... what to do??

Okay, guys...
I have a big, big, big issue and If it's possible, I'd like all the help in the world.
I unlocked my bootloader, upgraded to mm 6.0 and decided to root and install TWRP because bloatware, right?
Anyways, I did a big no-no and after a series of unfortunate events, I don't have a recovery and I can only boot into the bootloader.
Don't ask HOW I got here, I couldn't tell you with a gun to my forehead.
Now, I have tried ways to get myself out of this:
Installed an earlier TWRP recovery - doesn't work
Installed CM recovery - Doesn't work
Looked on motorola.ca for stock images - doesn't work
I can boot my phone with TWRP but I can't install it. (the inapropriate partition size error in pink)
whatever. Whenever I boot into twrp, I see all my partitions and with modifications on, I cannot format my /sdcard/ partition (internal memory)
it was being detected by my pc a few times and after a few more tries to flash ANY rom compatible with my phone, I simply have no luck.
Any advice right now is more than appreciated!
Awaiting answers with impatience.
EDIT: Forgot to mention the model number is the XT1097 canadian Moto X 2014 (Telus mobility)
Thanks for the help in advance

Have you tried this? Put ROM/gapps on internal storage. Fastboot boot twrp, then flash ROM/gapps with twrp. Once booted you should be able to install twrp via playstore without the partition mismatch issue. I had to go this route to get twrp to stick on my XT1096

I cannot access the internal memory for some reason!
I hear my pc make a sound for connected but it doesn't show up in explorer

Have you tried ADB sideload? Try flashing the stock MM Rom Zip located in the Moto X 2014 XDA Thread. It might work, if it doesn't, I can send you a toolkit that might fix the phone.

I did try to sideload and I get the following:
Installation failed: unable to mount (all the partitions are listed)
E: Failed to mount
E: Can't mount
And if you're talking about RDS Lite, I am completely unable to find my phone with it.

What I really need is a tool that will fix the partition table.
I don't know how, but I messed it up REAL GOOD!

also, for some reason I Have 2 recoveries atm.
When I completely power off my phone and then power on, I boot into the CyanogenMod Recovery.
THEN, when I reboot into recovery, I go into the TWRP recovery.
And every time afterwards I Reboot to recovery, I come back to the TWRP

Install Motorola USB Drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Download and keep full firmware VICTARA_RETCA_XT1097_6.0
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
If you are able to flash with fastboot, maybe you can go back to stock, then go on from there.
Try these, one by one:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear

I know you wouldn't, but hope you do. But if you could tell me how you got here, I could assist you better.

Thank you, Mate!
This restored my phone to retail!
I am in your debt!

You're welcome. We are all here to help each other.

Hi, I am in the exact same situation right now. I tried the fastboot method to flash all the files for the XT1096 VZW version. Every time I boot up after flashing everything, the dead andy with read exclamation point 'No Command' logo pops up and blinks every 5 seconds or so. Any help please? Thanks!

So I managed to get TWRP to install. Now I can't flash anything. All the partitions are somehow corrupted and I can't mount anything. Any ideas on how to fix the partitions?

OK

My apologies, Gus. I just posted a new QA thread on here. Can we discuss there? Thanks.

Moto x stuck at bootloader warning screen and won't go anywhere else.

So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.

Slupvee said:
So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.
Click to expand...
Click to collapse
It's always a good idea to put your phone in bootloader mode and do:
fastboot getvar all
So you get all the specs of your phone, and copy the info into a Notepad file.
Did you try reflashing TWRP (twrp-3.0.2-1-victara.img)?
If that's not working, you may be able to reflash stock firmware.
https://firmware.center:8081/firmware/Motorola/
Something like this:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.

Slupvee said:
thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.
Click to expand...
Click to collapse
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?

Gus Ghanem said:
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?
Click to expand...
Click to collapse
Verizon moto x 2014 5.1

Hey did u fixed it?

Moto G6 XT1925-6 - NO RECOVERY & Reboots to bootloader

As the title says, I have no recovery and can't seem to restore the stock recovery. Also, when I boot/reboot the phone, it goes to fastboot mode. Then if I select START, it will boot to the system.
I purchased this phone used and the bootloader was already unlocked. I installed TWRP, rooted it and set it up. When I put my sim in, I could send & receive text messages and mms messages, but I was unable to talk or hear anything while on a voice call. The call is placed and/or received fine. However, once connected, I cannot hear anything nor can anyone hear me.
I want to return for a refund and have restored to factory per this guide. (the problem persists). However, I do not have a recovery. Flashing the stock recovery thru ADB appears to work but trying to boot to it goes to fastboot mode. I cannot boot/reboot the phone without it going to fastboot, then I have to select START to boot to the system. If I cannot correct these problems I will not be able to return the phone...and I can't use it as is because of the phone issue.
Thanks...and help!

Did the phone work fine when you got it?
Sent from my Moto G6 Plus using Tapatalk

Relock-it
Remember you need root to do this and usb-debugging and OEM-unlock enabled in syste settings
Download firmware ALI_RETAIL_8.0.0_OPS27.104-15-10-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
and assuming you know were to extract it to, run this command:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot and run this command ONE BY ONE and wait for each one to finish before adding the next one
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot oem fb_mode_clear

Xplorer4x4 said:
Did the phone work fine when you got it?
Click to expand...
Click to collapse
Booting up and recovery...yes.
xjunior said:
RELOCK IT
Click to expand...
Click to collapse
What will that do for me? I still don't have a recovery.
xjunior said:
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot
Click to expand...
Click to collapse
I don't understand this. How do I erase fastboot reboot? It's a command to reboot.

if you use the firmware from the guide you show in the first post is probably not the right one for your device, I have exactly same model and took me a wile to figure out how to factory reset and relock it.
yes you gonna put the first commands all at once ,
then in the cmd terminal its gonna be the last command "fastboot reboot" but do not press enter otherwise it will reboot,
erase it and
add the second part of the command, line by line not all at once like the first part.
this will bring you device back to factory and relock the bootloader ,

xjunior said:
yes you gonna put the first commands all at once ,
then in the cmd terminal its gonna be the last command "fastboot reboot" but do not press enter otherwise it will reboot,
erase it and
add the second part of the command line by line .
this will bring you device back to factory and relock the bootloader ,
Click to expand...
Click to collapse
OK. Understood. But how will relocking the bootloader help me? It reboots to fastboot...it doesn't reboot to the system/OS. What I need is a recovery to somehow be flashed and to "stick".

mn1968 said:
OK. Understood. But how will relocking the bootloader help me? It reboots to fastboot...it doesn't reboot to the system/OS. What I need is a recovery to somehow be flashed and to "stick".
Click to expand...
Click to collapse
the last command will fix that I had same problem.
if you fallow this guide.
fastboot oem fb_mode_clear
If you want to return the Phone you will need to relock the bootloader other wise they will blame you for messing up the phone.

xjunior said:
the last command will fix that I had same problem.
if you fallow this guide.
fastboot oem fb_mode_clear
If you want to return the Phone you will need to relock the bootloader other wise they will blame you for messing up the phone.
Click to expand...
Click to collapse
OK, with your help I am back in business! I actually re-followed this guide up to step 5. I then ran:
fastboot oem fb_mode_clear
I can have the phone reboot normally now! Thank you very much!!!
As far as returning, I got it used on eBay. The bootloader was already unlocked. It's the phone that doesn't work for actual calls. I just need/wanted to return it exactly like it was.
Thanks again for your help!

My pleasure

mn1968 said:
OK, with your help I am back in business! I actually re-followed this guide up to step 5. I then ran:
fastboot oem fb_mode_clear
I can have the phone reboot normally now! Thank you very much!!!
As far as returning, I got it used on eBay. The bootloader was already unlocked. It's the phone that doesn't work for actual calls. I just need/wanted to return it exactly like it was.
Thanks again for your help!
Click to expand...
Click to collapse
After reflashing stock with OPS27.82-72 (came with OPS27.82-19-4), the phone now actually works too. Very weird. I may have/want to keep the phone now.

Touchscreen not working after flash, Ali Moto G6

Hello,
I followed the steps to install TWRP correctly, and then flashed ALI_RETAIL_9.0_PPSS29.55-24-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC that i got from https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ and the process worked correctly. However, I foolishly thought I had flashed the wrong build and then flashed ALI_OPS27.82-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC that I got from https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292
Now my phone boots fine, but the touchscreen does not work at all, neither in TWRP nor when booted into the firmware. Is there any hope?
Model is ali XT1925-6
If I burnt out a part, what parts are they and how difficult will it be to replace them?
Edit: I now realize that my carrier channel is retus, and I installed retail. However, the touchscreen did not fail on that rom

II firmware that you flashed you only linked to the whole thread, you didn't show the exact firmware that you tried to flash.
Why not just try the one for your firmware and your carrier from mirrors.lolinet.com
The firmware used first time should be fine if it works

madbat99 said:
II firmware that you flashed you only linked to the whole thread, you didn't show the exact firmware that you tried to flash.
Why not just try the one for your firmware and your carrier from mirrors.lolinet.com
The firmware used first time should be fine if it works
Click to expand...
Click to collapse
Thanks for your response,
I installed androidfilehost.com/?fid=818222786056029922 from the second thread.
I tried reflashing the first rom, but the touchscreen does not work there either. I've just downloaded and installed the correct rom, still no dice
Is it possible that the second rom burnt my digitizer?
Edit: the fingerprint sensor doesn't respond on the setup screen either, although I'm not sure if thats because it isn't working or it doesnt do anything on the setup screen

I think part of the problem may be that I cannot wipe system when installing a new rom; using adb shell twrp wipe system returns Error with wipe command value 'system', and I cannot access the touchscreen to do it via the UI. Are there any other ways to wipe system? fastboot erase system -w fails with Permission denied
Edit: I was able to erase system as well as data, cache, and dalvik before flashing. Still no change
The script I'm using to flash roms is
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot

fisher_1 said:
I think part of the problem may be that I cannot wipe system when installing a new rom; using adb shell twrp wipe system returns Error with wipe command value 'system', and I cannot access the touchscreen to do it via the UI. Are there any other ways to wipe system? fastboot erase system -w fails with Permission denied
Edit: I was able to erase system as well as data, cache, and dalvik before flashing. Still no change
The script I'm using to flash roms is
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Download the "newest" firmware for your device with matching SKU and software channel. Don't use someone else's script. The commands for flashing the firmware are in the flashfile.xml in the firmware zip. Extract it and check the commands. You can use XML to batch program to create your own batch script if you must use a script.
It's unlikely that flashing a firmware broke your hardware.
If it's software related, flashing the correct firmware should fix it.
If it's a hardware problem, then it won't. But official firmware isn't likely to cause hardware failure
The firmware package in the first post of that thread is pretty old.

Unfortunately it still is not working. I used the commands from flashfile.xml and flashed XT1925-6_ALI_RETUS_9.0_PPSS29.55-24-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC, the correct firmware, but nothing has changed.
On a side note, when I flash a file, I get the message (bootloader) is-logical: (partitionName) not found, althought I get an OKAY response so I'm assuming it flashes correctly.

I'm having the same issue, got the phone on July 12 and immediately started the unlocking/rooting process (that's what I bought the device for) following dejello's guide. Everything went perfect, phone was working all right for 2 days then on Monday morning after using the device for a while, I placed it in an upper pocket of my backpack drove home and next thing I know the touch screen isn't working, not even on TWRP . Hardware damage seems very unlikely on my case. I did a factory reset using a mouse, but I haven't been able to flash stock back. I'll try that later today and see what happens.
UPDATE: It was a hardware issue. Came home and flashed back to stock, still had no touch response. Since my software troubleshoot had no success I decided to give hardware a shot. I followed this video to disassemble the phone. I started tweaking the digitizer connector. With the phone still disassembled I turned it on and still no touch. Disconnected it again and blew some air with a hair dryer to it trying to remove any debris, connected it again and still no touch. Repeated the process a couple times and eventually the screen was responsive again. I think this specific device came with something loose or some dirt on it.

How to unroot new Z3 play?

So I think I'm going to return this Z3 play. Can someone link me to the process of unrooting?

Hear, HEAR. I second this, I am trying to work my way through the "No SIM Card" or sometimes "Invalid SIM Card" (on Sprint networks) error, and I am just wanting to unroot and relock the bootloader without breaking the thing beyond repair. Any help is appreciated. I located the latest stock firmware on here, but I am not 100% sure on the exact process as of yet.

mroneeyedboh said:
So I think I'm going to return this Z3 play. Can someone link me to the process of unrooting?
Click to expand...
Click to collapse
spyda256 said:
Hear, HEAR. I second this, I am trying to work my way through the "No SIM Card" or sometimes "Invalid SIM Card" (on Sprint networks) error, and I am just wanting to unroot and relock the bootloader without breaking the thing beyond repair. Any help is appreciated. I located the latest stock firmware on here, but I am not 100% sure on the exact process as of yet.
Click to expand...
Click to collapse
I have the Unlocked Z3, as well as the Sprint model, and have flashed between stock/CFW many tines. You simply need to use a flash all bat, paired with the stock firmware (current or newer).
However, please keep in mind that the verity message will remain during boot. Locking the bootloader will NOT fix this. If either of you need the bat file lmk.
Edit:
1. Enter fastboot/booloader on phone. Place bat file in SAME folder as unzipped firmware. Android SDK or adb tools must be installed!
2. Try USB2.0 port before 3+
3. Once done, use keys and switch to recovery mode
4. Perform a format
5. Reboot
https://drive.google.com/folderview?id=15hFa95l6bV1idoRXe5L1gt36jpG9s9DG
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
pause