Database Users

vz 1060 dev &*^()(**^

I am unlocked
fast boot still works
ok I downloaded the OTA
went to root it and everthign went to hell
the recovery dlahed but would nto entere recoivery
tried a couple differnt twrp
tried cwm
tried other 5.1 recovereis after verifying that they had the same sizes
still wont entere recovery
treid to use the kk factoryu image and "most of it flashed
Code:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.114s
C:\Users\Zookeeper\Desktop\android_sdk\XT1060 Moto X\VZW_212.56.26.ghost_verizon.Verizon.en.US>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.383s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.137s
flashed a different boot image and moto boot image form 5.1 t mobile
still no joy
there is a brazil 1053 which I am told Mosley works. but I cant find it
no 1060 factory image yet.
so has anybody created a factory type image yet. NOT a flashable zip. unless I can get twrp working that wont help me.
FAST BOOT WORKS

I'm not 100% sure, but you may have to use "mfastboot" which is the motorola version of fastboot. You can find it with a quick search.

So you were on 5.1 and downgraded to Kit Kat? You can't downgrade the bootloader.

dcooterfrog said:
I am unlocked
fast boot still works
ok I downloaded the OTA
went to root it and everthign went to hell
the recovery dlahed but would nto entere recoivery
tried a couple differnt twrp
tried cwm
tried other 5.1 recovereis after verifying that they had the same sizes
still wont entere recovery
Click to expand...
Click to collapse
I'm going to stop you right there,.
To install an OTA, you need STOCK reocvery. If you have a 3rd party recovery like TWRP or CWM, the OTA process might reboot your phone into Recovery but it will fall to install.
If you have 4.4.4 on your phone, you need to get that exact Recovery.img and flash it. You can't use a 5.1 recovery because the pre-flash validation checks that happen as part of the OTA will likely complain that its not the right version.
dcooterfrog said:
treid to use the kk factoryu image and "most of it flashed
Code:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.114s
C:\Users\Zookeeper\Desktop\android_sdk\XT1060 Moto X\VZW_212.56.26.ghost_verizon.Verizon.en.US>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.383s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.137s
flashed a different boot image and moto boot image form 5.1 t mobile
still no joy
there is a brazil 1053 which I am told Mosley works. but I cant find it
no 1060 factory image yet.
so has anybody created a factory type image yet. NOT a flashable zip. unless I can get twrp working that wont help me.
FAST BOOT WORKS
Click to expand...
Click to collapse
You can't downgrade from 4.4.4 to 4.4.2 without risking turning your phone into a brick.
What state is your phone in now? WHat bootloader version does it have on it?
If you have bootloader 30.B7, consider downloading the 4.4.4 XT1060 SBF/FXZ moto has on their web site, and visit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 read post 1 and 2... From Post 2, use the Requirements section, then skip to option 5 to get to stock 4.4.4. then try the OTA

ok lest start over
i was rooted with twrp
i returned to stock and flashed system and recovery from
VZW_212.56.26.ghost_verizon.Verizon.en.US
took both OTAs got onto lolipop seemd to be working
went to flash twrp it said flashed OK
but I could not boot into recovery
tried to laod a cuple differnt recoveries.
then tried to restore the whoel thing
VZW_212.56.26.ghost_verizon.Verizon.en.US
gpt failed
recovery failed
then I tried to install a recovery boot and moto boot frfom a different 5.1. ( after verifying that a couple 5.1 roms had the same size moto boot and boot) flashed but gpt is messed up and wont restore.
either I have broke it or I need a factory image from lollipop
i will try to check my boot loader version. but i bet its updated as a resultof th OTA

got twrp working
does any one have a complete nanadroid of verizon lolipop

got twrp working
does any one have a complete nanadroid of verizon lolipop
slowly am getting back up.
i am not at VZW_212.55.26.ghost_verizon.Verizon.en.US
not 56
Blur_Version.212.166.3.ghost_verizon.Verizon.en.US seems to fail.
ill try flashing system and recovery again.
flashd system, revcovery, boot and motoboot
moto boot failed
update unsuccessful so somthing in moto boot muts ba failing the assert. I think I have a NEWER moto boot.

How did you get TWRP working under 5.1? Someone else had similar issues here:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt1060-recovery-5-1-t3201391

Well that was me... Eventually I got twrp working but I don't know what kind of bastard kitkat lolipop Frankenstein thing it was. Phone will not boot. It is on its way back to motorolla
Sent from my Venue 8 7840 using Tapatalk

Hey bud, when you say the phone won't boot do you mean you can't even boot into the bootloader, or do you mean the screen goes black after the boot animation?
If it's the latter the same thing happened to me today and I know how to fix it.

Won't boot. It went back to Motorola yesterday. Love extended warranty. Backup phone droid incredible 1 with KitKat . loving the 3g
Sent from my ADR6300 using Tapatalk

dcooterfrog said:
Won't boot.
Click to expand...
Click to collapse
I was asking you to clarify what you meant by "won't boot" since that could mean multiple things, but it doesn't matter if you already sent the phone back. Glad you have the extended warranty.

yes extended warranty is great.
sorry by wont boot i meant complete brick, not boot loop. no boo tlogo, no motorolla logo, no bootloader unlocked warning screen. just dark dead, as a doornail.
it wold not even get int eh boot loader.
i have never bricked a phone before. i want trying to downgrade. i have been rooting ( the hard way) since eclair on my lg ally, so not a newb.

MOTO X PLAY XT1562 Bricked

I accidentally bricked my xt1562 while attempting to flash a rom. I wiped the phone using twrp and when it rebooted it was stuck on the 'WARNING BOOTLOADER UNLOCKED' screen.
I attempted to flash the stock rom using adb but it shows the following error.
C:\Users\devya\Desktop\Fastboot+ADB\Win32>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.505s
PLEASE HELP!

can u paste the commands here to see them?

devyadav0399 said:
I accidentally bricked my xt1562 while attempting to flash a rom. I wiped the phone using twrp and when it rebooted it was stuck on the 'WARNING BOOTLOADER UNLOCKED' screen.
I attempted to flash the stock rom using adb but it shows the following error.
PLEASE HELP!
Click to expand...
Click to collapse
I'd advice you use the original image to flash for your country and device which was 5.1 via ADB following the steps described in the forum.
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486

Dio-Genes said:
I'd advice you use the original image to flash for your country and device which was 5.1 via ADB following the steps described in the forum.
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
Thanks dude for the quick response. I'll get onto it.

if u flash the stock marshmallow firmware...u have to add sparsechunk 7,8 and 9 in the commands with the same way they appear...
bytheway...here is the latest with october patch yesterday new flashable rom zip...u only have to flash supersu after flashed rom.good luck.
https://forum.xda-developers.com/showthread.php?t=3533559

kos25k said:
if u flash the stock marshmallow firmware...u have to add sparsechunk 7,8 and 9 in the commands with the same way they appear...
bytheway...here is the latest with october patch yesterday new flashable rom zip...u only have to flash supersu after flashed rom.good luck.
https://forum.xda-developers.com/showthread.php?t=3533559
Click to expand...
Click to collapse
I tried that once before and got the same error message until I used the original firmware, 5.1 which was the one it was originally shipped with. That's why I gave that advice.

ok dude glad to hear.now from twrp i think u can flash latest MM flashable. (not sure through if u first have to flash 6.0 MM)

Yet Another Bootloop Thread

Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!

Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.

jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?

bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps

Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.

bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 oem lock
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that

[Q] How to find correct stock rom for my model?

I'm sorry of this is a noob question, but I found this: http: // www . filefactory . com/folder/c6cdedc45a775d27 <--- which contained a bunch of stock roms. (I'm a new user, so I can't post links; just remove the spaces)
I bricked my phone with an incompatible SuperSU (stuck on Moto boot screen), so I need to flash 6.0.1 for XT1644 (I think it's unlocked/USA variant but idk)
I tried one that I found called "XT1625-XT1644_ATHENE-RETUS_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml_2.zip" which said that it was 6.0.1, but when I tried to flash, it said:
Code:
C:\Users\Mateo\Downloads\Extracted ROM>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.044s
Apparently, I'm flashing the wrong version of the firmware, but there's like 10 pages of downloads on the filefactory link, and it takes about an hour to download each... Can anyone help me out here?
Thanks!

That firmware should be okay, however that error is normal if you're attempting to flash a build older than the build you currently have/had. I'm guessing you had either MPJ24.139-64 or Nougat on your device before? Your updated bootloader and gpt blocks any downgrades (and thus reduces the chances of bricking your device).
You may be able to flash your older firmware (and downgrading in the process) if you do not flash gpt or bootloader, omit:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
The rest of your flashing commands should be the same. Of course, verify your bootloader is unlocked (which it should be if you were flashing SuperSU), else you won't be able to downgrade.

Thanks for your quick response!! I downgraded without problem! Also rooted with a compatible SuperSU this time... Then disabled the OTA daemon, so it wouldn't​ auto update, and brick myself, since I'm running an earlier version of the bootloader (correct me if I'm wrong...) Thanks again! :good:

matetoes said:
Thanks for your quick response!! I downgraded without problem! Also rooted with a compatible SuperSU this time... Then disabled the OTA daemon, so it wouldn't​ auto update, and brick myself, since I'm running an earlier version of the bootloader (correct me if I'm wrong...) Thanks again! :good:
Click to expand...
Click to collapse
Woo, good to hear you've got your device working I think with the OTA, you should be okay as the bootloader blocked earlier attempts to downgrade and your subsequent flashes won't have affected those partitions, so it's unlikely you'll brick your device!

fastboot flash boot failed

trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?

Did you solve the problem?

i think you can try https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461

ISCYamil said:
Did you solve the problem?
Click to expand...
Click to collapse
Nope. The reason I want to flash stock boot image or patch boot image because of every time flash new flyme rom via TWRP, the phone always rooted and Magisk is not working to hide root. Now I just use as is. The banking app cannot be working with rooted phone.

hall060679 said:
trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?
Click to expand...
Click to collapse
I had the same problem just earlier today. What did the trick for me was installing the ROM using TWRP recovery. Move the stock ROM (you need to zip it for the process) into phone's root directory using your computer and then in TWRP tap on "Install" and find the zipped stock ROM and confirm. Let us know.

try fastboot flash bootimg instead.