Database Develop

[Q] Razr XT890 flashes screen

Hello.
From the beginning. I took part in the tests, Motorola 4.4.2. but KK is crap for me, so I unlocked the bootloader, I installed version 6.1 RSD .... and I threw the system 4.1.2 EU (Germany phone I) .All went well with a small problem. when I flash information appears:
dismatched partition entry array crc32
fastboot reboot reason this bootloader.
However, the phone back to 4.1.2,starts normal.,updates are ok,working good but the phone screen flashes regularly when unlocked(in recovery flashes to).I tried with several firmwares EU and GB., with edited and not edited file CFC.XML ( lines gpt and partition).
How to fix it step by step?
Maybe should I install different rom,or again install 4.4.2.
Please help.
Thank you

The KK update updates the gpt.bin (partition table). So when going down to 4.1.2 u flash the system/recovery/boot images on a partition that may be smaller or larger than intended and could cause this problem. This is maybe not true. U maybe can go back by flashing the gpt.bin from the KK update. Can be found in any of the zip files from the BR KK update. Flash it through fastboot. The command on how to flash it should be in one of the xml files in an rsd-lite zip. And than again flash the system/recovery/boot through mfastboot on your device and not rsd-lite.
Use this at your own risk obviously!!!

Oh my so it's not so simple to repair phone.Difficult to find broken files and weak knowlegde of fastboot for me.What do you think...Maybe I should try install unofficial rom based on JB or KK to Razr I ? Are there any roms unofficial?
Yesterday I have read :
INDEX/GUIDE, ALL Things RAZR I and downloaded some files.I have an idea .Maybe should now downgrade from JB to ICS and after that update OTA to JB ? Unfortunally links SBF with firmwares are dead and don't know where to find working.What you think about that ? Is it bad idea?Much easily will be just find gpt.bin (I found it and downloaded from Brasil version of KK ) and flash it somehow?
OK here is solution :
From some reason my phone wasn't recognised in fastboot but command line worked well.
OK so I've installed fresh rom(4.1.2 EU) via mfastboot .
Commands :
mfastboot flash gpt.bin from KK version (oryginaly was gpt gpt_signed from4.1.2)
mfastboot flash motoboot motoboot
mfastboot flash boot boot_signed
mfastboot flash recovery recovery_signed
mfastboot flash motobp motobp
mfastboot flash system system_signed
mfastboot flash cdrom cdrom_signed
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
After few minutes starts to flashing again.Even on screen "warning unlocked bootloader"
Phone back to life after installing: [ROM][Kitkat] Unofficial Cyanogenmod 11 via TWRP . Nothing flashes ,no problems,everything works great!
THX HAZOU for your help .

[Q] Bricked! XT1092

Hi guys,
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did. So I re-flashed the 5.0 firmware that had worked previously. Same thing.
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?

Sorry, but there is nothing you can do if it says that. You will have to send it in for repair.
Sent from my XT1095

OP said:
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did.
Click to expand...
Click to collapse
When you did that, you upgraded the bootloader and partition table to 5.1.
OP said:
So I re-flashed the 5.0 firmware that had worked previously. Same thing.
Click to expand...
Click to collapse
When you did that, it did not downgrade the bootloader and partition table - they stayed on 5.1.
OP said:
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Click to expand...
Click to collapse
When you did that, it did not downgrade the BL and PT - they stayed on 5.1.
OP said:
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
Click to expand...
Click to collapse
When you did that, the OTA tried to patch the 5.1 BL and PT as if they were the 4.4.4 BL and PT. But you were running the 5.1 BL and PT. That caused a brick.
OP said:
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Click to expand...
Click to collapse
Wait for someone to release the blankflash files for 5.1 (which were never leaked for 4.4.4 or 5.0 so they may never be leaked) or send it in for warranty replacement.

unfnknblvbl said:
Hi guys,
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did. So I re-flashed the 5.0 firmware that had worked previously. Same thing.
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Click to expand...
Click to collapse
Well, I see you used my post to downgrade to 4.4.4 and worked for you. And that's odd, because you flashed the "official" firmware of your model previously and got a bootloop. And some people are saying that downgrading your firmware from 5.1 to 4.4.4 will brick and that's not your case.... You bricked after taking the OTA and that's weird because after flashing the 5.1 of your model you upgraded your partition and your boot loader. What I am guessing here is that maybe the partitions and the boot loader of a different version like yours are incompatible with the pure edition. Maybe you can share with us what did you do after the first bootloop to downgrade to the 4.4.4, like what files did your use and what fastboot commands did you use too.
Sorry for your phone, but in several post people are warning that after downgrading from a 5.1 soak you don't have to take OTA.

juliospinoza said:
Sorry for your phone, but in several post people are warning that after downgrading from a 5.1 soak you don't have to take OTA.
Click to expand...
Click to collapse
These aren't Nexus devices. People can't flash whatever they want, downgrade and then take OTAs and never have to worry about bricking.
Rule of thumb - when in doubt don't flash the bootloader or partition table and never take an OTA after downgrading the bootloader.

JulesJam said:
These aren't Nexus devices. People can't flash whatever they want, downgrade and then take OTAs and never have to worry about bricking.
Rule of thumb - when in doubt don't flash the bootloader or partition table and never take an OTA after downgrading the bootloader.
Click to expand...
Click to collapse
That's exactly what I said, but you made it more "sophisticated" taking Nexus devices as an example. Don't see the point to repost.

juliospinoza said:
Don't see the point to repost.
Click to expand...
Click to collapse
My response was succinct, used a memorable distinction as well as a catchy rule of thumb and had adequate paragraph breaks. IOW easier to understand with a nice rhythm to it.

Try to sent to warranty centre , but in my case Motorola didn't cover me this issue.

juliospinoza said:
Maybe you can share with us what did you do after the first bootloop to downgrade to the 4.4.4, like what files did your use and what fastboot commands did you use too.
Click to expand...
Click to collapse
Right, so here's what I did.
1) the 5.1 OTA never worked for me - would always fail during flashing for some reason. So when I found the above post, I flashed the "VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml" package with the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Then seeing as it didn't want to work, and from prior experience with TWRP being annoying, I then flashed the recovery with "mfastboot flash recovery recovery.img"
Then came the bootloops. Now, I say "bootloops" but it was more complicated than that. What would happen is the boot animation would load up, then once the screen "dimmed" it would turn off. As I didn't clear userdata the first time, it would do the whole "android is upgrading x/65749823562743 apps" message... then reboot after the last one, and start again from the start. I cleared cache and userdata and then something else happened; after the screen dimming, it would turn 'off' but apparently still load. Every now & then, the screen would flash on for just an instant. Long enough for me to see some kind of error, but not long enough to find out what.
2) Giving up on this, I re-flashed the 5.0 "RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml" package with the following script:
Code:
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash recovery twrp-2.8.6.0-victara.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Nothing remarkable there, although I notice that I didn't flash gpt.bin. Can't think why I didn't do that right now, tbh
Anyway, exactly the same issue occurred!
3) not having the patience to deal with that **** as it was nearing 3am, I flashed 4.4.4 "TMO_21.21.42.victara_tmo.tmo.en.US" with the following script:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
...which worked! The phone started normally and all seemed good. I was pretty chuffed.
Then, without thinking I accepted the 5.0 OTA when I awoke all bleary-eyed this morning, and she died. And here we are.
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.

unfnknblvbl said:
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
Click to expand...
Click to collapse
They should give you a warranty replacement - their OTAs should have checks in them to fail to update rather than brick a device when you are running a newer BL than the one the OTA was written to update. This is their fault. Poor coding on the part of the software devs who wrote the OTAs.
The OTAs should check the bootloader version. If it is not the version the OTA was meant to update, the OTA should simply fail to update. End of problem. One simple IF-THEN statement would prevent this.

you'd think so....

unfnknblvbl said:
Right, so here's what I did.
1) the 5.1 OTA never worked for me - would always fail during flashing for some reason. So when I found the above post, I flashed the "VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml" package with the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Then seeing as it didn't want to work, and from prior experience with TWRP being annoying, I then flashed the recovery with "mfastboot flash recovery recovery.img"
Then came the bootloops. Now, I say "bootloops" but it was more complicated than that. What would happen is the boot animation would load up, then once the screen "dimmed" it would turn off. As I didn't clear userdata the first time, it would do the whole "android is upgrading x/65749823562743 apps" message... then reboot after the last one, and start again from the start. I cleared cache and userdata and then something else happened; after the screen dimming, it would turn 'off' but apparently still load. Every now & then, the screen would flash on for just an instant. Long enough for me to see some kind of error, but not long enough to find out what.
Click to expand...
Click to collapse
I think I know what generated the bootloop, happened to me two days ago. When you upgraded your system and data partition and didn't erased your data, the old data tried to "fit" the new partition, that's why the system the first time was trying to update your apps, but after failing entered again on bootloop. Don't know why this happens, from 4.4.4 to 5.0 you could upgrade without erasing data and nothing happened.
unfnknblvbl said:
2) Giving up on this, I re-flashed the 5.0 "RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml" package with the following script:
Code:
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash recovery twrp-2.8.6.0-victara.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Nothing remarkable there, although I notice that I didn't flash gpt.bin. Can't think why I didn't do that right now, tbh
Anyway, exactly the same issue occurred!
Click to expand...
Click to collapse
Although you didn't flashed the gpt nothing would happened, just an error on fastboot, because you can't downgrade bootloader, the first time you flashed the new version 60.16 and the version on 5.0 is the 60.11.
The bootloop happened because the same reason, your data was there and the system wasn't able to make it "fit" to the new partition, the one you flashed with the 5.1.[/QUOTE]
unfnknblvbl said:
3) not having the patience to deal with that **** as it was nearing 3am, I flashed 4.4.4 "TMO_21.21.42.victara_tmo.tmo.en.US" with the following script:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
...which worked! The phone started normally and all seemed good. I was pretty chuffed.
Then, without thinking I accepted the 5.0 OTA when I awoke all bleary-eyed this morning, and she died. And here we are.
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
Click to expand...
Click to collapse
OK. After your final flash you flashed the system and erased data and cache, and the partitions were "clear" from all apps and other stuff, so the system was able to "fit" your data to the partitions properly, that's why your phone booted as brand new, am I right??? Seems that the partitions are compatible from 4.4.4 to 5.1 only if you erase data.
The problem is the next. The first flash set the new bootloader 60.16 and the new partitions, but when you didn't erase your data and cache the phone created a conflict with the old data and new partitions (that's the reason of the bootloop) but, when you flashed the 4.4.4 and erased your data the phone was able to boot with the new partitions. The brick was caused because of the OTA of 5.0 and that's because 5.0 uses bootloader version 60.11 and you were already on 60.16 and, the big problem with motorola OTA's is that they didn't check the mismatch between bootloaders like fastboot does, so the OTA forced the downgrade "thinking" it was an upgrade and bricked your phone. Fastboot didn't allow you to downgrade bootloader, but clearly OTA does and that's the reason of bricked devices.
Your phone should be on warranty because it wasn't your fault (not entirely) because of faulty OTA's.
Resuming. After you are on bootloader version 60.14 or 60.16 you can't take any 5.0 OTA because the mismatch between old and nw bootloaders.
Glad to see that motorola are taking to warranty. And thanks for your well explained situation so everybody could take it as reference!

juliospinoza said:
I think I know what generated the bootloop, happened to me two days ago. When you upgraded your system and data partition and didn't erased your data, the old data tried to "fit" the new partition, that's why the system the first time was trying to update your apps, but after failing entered again on bootloop. Don't know why this happens, from 4.4.4 to 5.0 you could upgrade without erasing data and nothing happened.
Click to expand...
Click to collapse
I forgot to mention; before attempting the downgrade to 5.0, I was able to enter recovery and do a factory reset - I wiped userdata and even the sdcard, and that's where it started just 'looping' with the odd screen flicker.
The fact that it still shows up as something in Windows Device Manager gives me hope. If it were completely out of warranty, I'd try to hack the Qualcomm rescue tools for other phones that report that same QHSUSB_BULK device into doing something with this.

unfnknblvbl said:
I forgot to mention; before attempting the downgrade to 5.0, I was able to enter recovery and do a factory reset - I wiped userdata and even the sdcard, and that's where it started just 'looping' with the odd screen flicker.
The fact that it still shows up as something in Windows Device Manager gives me hope. If it were completely out of warranty, I'd try to hack the Qualcomm rescue tools for other phones that report that same QHSUSB_BULK device into doing something with this.
Click to expand...
Click to collapse
The issue isn't the tools. The tool for reflashing is there. But you need a bin and hex file specific to your device/bootloader that only Moto has right now. Unless it is released/leaked, SOL right now unfortunately.
Sent from my Moto X 2014 Pure Edition using Tapatalk

So, the phone has been sent back to me on the same day they received it. No call, no email. nothing. Weird. I hope they fixed it - I assume they did, otherwise they would have contacted me for payment info.
I'll report back!

Success!
Replaced main PCB, rear inlay - software upgraded to current version 5.1.1 - checked current drain - QC/CIT passed to manufacturer's specifications. New IMEI.
Click to expand...
Click to collapse
...this is probably because I'm in Australia though, and the warranty-voiding disclaimer about unlocking your bootloader isn't legal here. I think. I am not a lawyer.
New bootloader: 60.16
Bam.

Same Model .. Hard Bricked xt1092
i bought it a month ago from flipkart.
when i was doing the OTA update from 4.4.4 to 5.0.2 the installation finished from the recovery and never booted.
when i try to plug in to PC its shows QHUSB_BULK
i tried blankflash but it says FAILED
all the drivers are installed something that ends with Qualcomm.. 9008
is there any way that i cn unbrick it myself?

warmachine68 said:
i bought it a month ago from flipkart.
when i was doing the OTA update from 4.4.4 to 5.0.2 the installation finished from the recovery and never booted.
when i try to plug in to PC its shows QHUSB_BULK
i tried blankflash but it says FAILED
all the drivers are installed something that ends with Qualcomm.. 9008
is there any way that i cn unbrick it myself?
Click to expand...
Click to collapse
Sorry it is impossible to fix yourself. You will have to send it in for repair.
Sent from my XT1095 using Tapatalk

Moto G 2014 LTE ( XT1079 ), How to relock bootloader

I downloaded Android Marshmallow after reading news about it through settings/about/system updates.
After downloading, the phone restarted but updatation was stuck after flashing TWRP screen (error screen photo attached)
My phone is
bootloader unlocked,
recovery TWRP
rooted
ROM is stock.
It seems the OTA update will be completed once I have stock recovery,
I have following queries
Is it necessary to revert to stock recovery to complete OTA update?
If yes, how to achieve it, what i learnt through search, I need to find Stock ROM zips and extract recovery (boot.img) and then flash it through adb?
where to look for thea stock rom and is there any easier method

It's risky, a lot of users here for some reasons got stuck whit locked/unlocked bootloader unable to boot and flash anything.
Here you can find all the motog stock roms http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
You should wait for the complete rom image for your country/model to pop there instead doing that risky thing you want do.

Thanks
Recently stock rom for xt1079 has been added to the list.
But I m trying to download from filefactory since yesterday but due to some reason, it stops in between and resume isn't supported.
Are there any other hosts

Are you sure the region of that xt1079 is right for your phonr ? check the phone box and the info inside settings to know which region/carrier you have, you must use the same identical 100% stock to avoid problems
And, do no relock bootloader !!!

yes i bought this through online retailer in India.
It is xt1079 Asia
I see in xda forum of moto g 2nd gen most of the time ppl are talking about xt1078.
What's the difference between xt1078/1079 and can't I use xt1078 ROM.
Rooting procedure meant for xt1078 worked fine for me
And Sir is relocking bootloader very risky ? suppose something goes wrong wont I be able to unlock or restore nandroid backup.

Thanks to support from Dr.nic I am finally on android 6.0
Although I have relocked my bootloader, but it is recommended to leave as it is.
If anyone stumbles here with same problem like mine i.e. unable to upgrade to android 6.0 just because of custom recovery, then pls download the firmware from filefactory.com link and flash. I'll add flashing commands as well to this post in near future.

if you have already done this rom change etc, the you must already be having fastboot, adb etc.
after connecting in fastboot mode holding VolDown and Power for few secs
run following commands
[this is for android 6.0 firmware]
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I am not great expert, do this only if you have some idea, I may not be able to help you much if something goes wrong.
I can only say it worked for me

Flashed Stock MM, now can't complete setup wizard

I was on 5.1, bootloader unlocked by sunshine. I rooted to enable tethering, and after did a full unroot. Once the OTA MM update came it couldn't install. Android on back and then rebooted. Instead of trying to fix the software, I decided to get MM from XDA. I flashed TWRP, updated bootloader from computerfreek's thread and flashed his rom for non-verizon.
Now once it turns on I can choose language. At the next page it says select wi-fi netowork, but no wifi networks show up and the Skip button is grayed out.
I followed the directions again and reflashed a few times, but the same result.
I then tried the Brazilian MM from iiwoodstock but with the same result. I flashed his with and without the linked kernal, but again, with the same results.
Any ideas? I was hoping to avoid flashing the stock images, but if that's my only option....

Well I got irritated enough and flashed stock. All is working now.
It was a pain because I only have Windows 10, so RSDLite was being irritating.
Here are the steps I wish someone had put together for me.
This is for flashing this version (and only this version) of stock by using fastboot:
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Having ADB Everywhere helps. Just install this:
https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
Make sure your drivers are installed. I needed to go to motorola to download their software to get fastboot drivers to work:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/103535/p/30,6720,9277
Have a copy of fastboot.exe
(Google it or just do a search on your computer. You probably have a copy of it somewhere if you've ever done anything to a phone)
Here is a link to the .bat file I made that will flash it without needing RSD.
https://nofile.io/f/sh00er98rzM/servicefile.bat
In case someone finds this thread and the file is no longer hosted, here it the text of the .bat file (use Notepad++ or something):
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.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 system system.img_sparsechunk.10
fastboot erase clogo
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
(Have phone connected in fastboot mode - power plus volume down)
1. Extract the stock image into a folder
2. Put the .bat file in that folder
3. Put a copy of fastboot.exe into the folder as well
4. double click the .bat file
(wait for it to finish. If there's errors, don't worry, it should be fine. Worry when it's worth it. This is not a big deal)
done
I figured this out primarily because of RootJunky.com's youtube video.
https://www.youtube.com/watch?v=njXQYn53SPc

gr8hairy1 said:
This is for flashing this version (and only this version) of stock by using fastboot:
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
any reason you wanted to flash an older version and the newest?
You flashed this:
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5 (January 2017)
But this is much newer (March 2017):
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334

ChazzMatt said:
any reason you wanted to flash an older version and the newest?
You flashed this:
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5 (January 2017)
But this is much newer (March 2017):
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
Click to expand...
Click to collapse
No reason. That was the first one I had come across. At the time I was out of state visiting family and their internet was extremely slow.
I didn't feel like waiting another 2+ hours downloading what seemed like a minor update.
....or does it fix anything? I haven't found anything showing the reason that update was pushed

gr8hairy1 said:
No reason. That was the first one I had come across. At the time I was out of state visiting family and their internet was extremely slow.
I didn't feel like waiting another 2+ hours downloading what seemed like a minor update.
....or does it fix anything? I haven't found anything showing the reason that update was pushed
Click to expand...
Click to collapse
Release notes here:
https://www.verizonwireless.com/support/droid-turbo-update/
Sent from my carrier unlocked LG V30+ US998

I bricked my device after doing some stupid thing, what stock ROM do I get to fix it?

I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?

If your phone is defined in the device manager as COM port 9008, you can restore it according to this instruction.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
The file 'blank-flash.bat' can be taken in the folder "mbm-ci", the cat will be in the unpacked firmware.
https://mirrors.lolinet.com/firmware/moto/chef/official/RETAIL/fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After installing this file, the phone will be able to boot into fastboot.
After that, you can restore the phone by flashing the same downloaded firmware using the method described here.
https://web.telegram.org/#/[email protected]
[1:27:03 PM]
smyaknti.tar.gz
:
admin
Set your device in fastboot mode do the following and skip the
fastboot -w
step if you don't want to format everything :
fastboot oem fb_mode_set
fastboot -w
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.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
(If you have more or less sparsechunk files then continue or terminate beforehand accorfingly)
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem fb_mode_clear
fastboot reboot
Just yesterday, I so restored my phone from a brick, obtained after installing an unofficial TWRP and firmware RR.
Good luck.

https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This is the January Patch Stock ROM

NitrodiumSK said:
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
Click to expand...
Click to collapse
You did not "Brick" your device per se. Probably some improper file was flashed. If you have not wiped your phone, you can just simple try to fastboot flash the stock boot image. It may solve the issue. If not then do a clean flash to either the stock ROM or any custom ROM from this AFH link.
Note that the Custom ROMs are still in beta due to a VoLTE issue and thus are not released on XDA Dev DB yet. They are safe to flash though and are stable if you do not need VoLTE.
You can also ask for more help at the official telegram channel for the device.

smyaknti said:
You did not "Brick" your device per se. Probably some improper file was flashed. If you have not wiped your phone, you can just simple try to fastboot flash the stock boot image. It may solve the issue. If not then do a clean flash to either the stock ROM or any custom ROM from this AFH link.
Note that the Custom ROMs are still in beta due to a VoLTE issue and thus are not released on XDA Dev DB yet. They are safe to flash though and are stable if you do not need VoLTE.
You can also ask for more help at the official telegram channel for the device.
Click to expand...
Click to collapse
I thank you very much for your help. I was able to successfully flash the stock firmware from the link you provided. I only have a small question. The stock ROM zip, is it updated after every security patch OTA update?

NitrodiumSK said:
I thank you very much for your help. I was able to successfully flash the stock firmware from the link you provided. I only have a small question. The stock ROM zip, is it updated after every security patch OTA update?
Click to expand...
Click to collapse
Yes, the complete firmware file is different with every new build released. You can install OTA with the current fastboot flashed stock ROM but provided it has to be "FULLY STOCK". Else the update will fail.

smyaknti said:
Yes, the complete firmware file is different with every new build released. You can install OTA with the current fastboot flashed stock ROM but provided it has to be "FULLY STOCK". Else the update will fail.
Click to expand...
Click to collapse
Alright gotcha! Thanks a lot for your help

Hello dear Mates!
I purchased a cellphone yesterday Motorola Power One. its working fine, but I want to ask n know two things,
1. It has unlocked "bootloader" and on all restart it says to relock it to secure it. If I relock it, will still work or stop working?
2. It has Android 8.1.0 SKU XT1942-1 BUILD NUMBER OPT28.81-45 When I click update it shows Your Device is up-to-date
Android version 8.1.0
Current Version OPT28.81-45
Security Patch level September 1, 2018
But today I saw this update
XT1942-2_CHEF_RETAIL_9.0_PPTS29.74-29-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I want to know can I update this version and how to?
Please help me as quickly as possible
Thanks and regards
azhar

No issue downgrade
You can downgrade one power there is no issue of you downgrade it don't worry
NitrodiumSK said:
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
Click to expand...
Click to collapse

Any how can anybody provide stock rom oem fastboot mode with March update???

azhar63 said:
Hello dear Mates!
I purchased a cellphone yesterday Motorola Power One. its working fine, but I want to ask n know two things,
1. It has unlocked "bootloader" and on all restart it says to relock it to secure it. If I relock it, will still work or stop working?
2. It has Android 8.1.0 SKU XT1942-1 BUILD NUMBER OPT28.81-45 When I click update it shows Your Device is up-to-date
Android version 8.1.0
Current Version OPT28.81-45
Security Patch level September 1, 2018
But today I saw this update
XT1942-2_CHEF_RETAIL_9.0_PPTS29.74-29-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I want to know can I update this version and how to?
Please help me as quickly as possible
Thanks and regards
azhar
Click to expand...
Click to collapse
Yeah bro flash this room via fastboot commands

motorola one power
my moto one power starts freezing and when i restart its touch stop working....i flashed stock rom using twrp but still same problem and also try to flash rom using fastboot but still its system ui not responding and phone freezes and touch not working after reboot...please help please!!!:crying:

aum25 said:
Yeah bro flash this room via fastboot commands
Click to expand...
Click to collapse
Did you flash that rom in 1942- 1 ??? I have the same model num and running oreo... Want to update pie??? Were you successful in doing that ? Because that firmware file was for 1942-2 ? Plz share experience.

rudranshrajput said:
my moto one power starts freezing and when i restart its touch stop working....i flashed stock rom using twrp but still same problem and also try to flash rom using fastboot but still its system ui not responding and phone freezes and touch not working after reboot...please help please!!!:crying:
Click to expand...
Click to collapse
Did you install any third party app or it happens by itself? I had the same problem but i was messing around with the moto app launcher. Anyhow, try flashing this stock rom with latest june security patch. Don't use TWRP, it is a full rom. Use Fastboot mode. Also backup your device, if you want your files back. This will do a clean install of the rom.
Here is the link: https://drive.google.com/file/d/1lLmDvX4R4o2Jqrhp1RQflap27jxe4hXS/view
Steps:
1) Boot your device into fastboot mode
2) Open flashall.bat and wait for flashing
3) Reboot

colorist said:
If your phone is defined in the device manager as COM port 9008, you can restore it according to this instruction.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
The file 'blank-flash.bat' can be taken in the folder "mbm-ci", the cat will be in the unpacked firmware.
https://mirrors.lolinet.com/firmware/moto/chef/official/RETAIL/fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After installing this file, the phone will be able to boot into fastboot.
After that, you can restore the phone by flashing the same downloaded firmware using the method described here.
https://web.telegram.org/#/[email protected]
[1:27:03 PM]
smyaknti.tar.gz
:
admin
Set your device in fastboot mode do the following and skip the
fastboot -w
step if you don't want to format everything :
fastboot oem fb_mode_set
fastboot -w
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.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
(If you have more or less sparsechunk files then continue or terminate beforehand accorfingly)
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem fb_mode_clear
fastboot reboot
Just yesterday, I so restored my phone from a brick, obtained after installing an unofficial TWRP and firmware RR.
Good luck.
Click to expand...
Click to collapse
thanks by you my device just boot up in fastboot mod
thank you very much
best regard

Need help with phone bricked.
I was installing the Arrows OS in Motorola one power and after rebooting, the set is in the bricked mode now it's not responding to anything. Can anyone please guide how can I fix it?

I got similar problem.when I'm flashing arrows or others custom ROMs(1custom ROM,2twrp installer)and restart my phone no restarting only bricked.help only blankflash

Phone bricked after installing arrow is on p30 note xt1942-1
I tried the blankflash method but not working, I'm getting I/O error
Any ideas?