Database Develop

Locked bootloader,NO OS and failed to flash??

hi guys
have some problem here and it s serious
so my man locked the bootloader with a tutorial from a Moto g and write wrong
locked the bootloader then flash it the system then erases the userdata and all cache etc
so no recovery,no boot.
now when is trying to unlock the bootloader says OEM allowed unlock or something similar
i was trying to flash 4..4.4 RETBR but got some errors
bootloader invalid sytem img
bootloader invalid prefailed flash
how can i make it work?
the phone stays in fastboot always
can t boot to recovery
please some help here
i was thinking 3 solutions.
unlocking the bootloader but how?
waiting for Lollipop img
or calling Motorola to unlock the bl
thank u

why would you relock your bootloader?
solution its simple, if you dont want to unlock it again, use rsd lite 6.2.9 and flash the firmware from the country of your moto maxx, if its a mexican moto maxx flash mexico ,if its puerto rico, PR or if its brasil, then brasil. you can flash them, those are flasheable with locked bootloader because they are signed, just the one where your phone was

Jaocagomez said:
why would you relock your bootloader?
solution its simple, if you dont want to unlock it again, use rsd lite 6.2.9 and flash the firmware from the country of your moto maxx, if its a mexican moto maxx flash mexico ,if its puerto rico, PR or if its brasil, then brasil. you can flash them, those are flasheable with locked bootloader because they are signed, just the one where your phone was
Click to expand...
Click to collapse
But RSD doesnt recognize the phone

guivalli said:
But RSD doesnt recognize the phone
Click to expand...
Click to collapse
You need your phone on fastboot and use rsd 6.2.4

Jaocagomez said:
You need your phone on fastboot and use rsd 6.2.4
Click to expand...
Click to collapse
Yes!! rsd 6.2.4 recognize!
But result fail gpt.bin
---------- Post added at 04:33 AM ---------- Previous post was at 03:48 AM ----------
guivalli said:
Yes!! rsd 6.2.4 recognize!
But result fail gpt.bin
Click to expand...
Click to collapse
i replace gpt.bin than lollipop OTA and its ok!
but fail in boot.img, recovery.img and system.img_sp...0,1,2,3,4 fail too

guivalli said:
Yes!! rsd 6.2.4 recognize!
But result fail gpt.bin
---------- Post added at 04:33 AM ---------- Previous post was at 03:48 AM ----------
i replace gpt.bin than lollipop OTA and its ok!
but fail in boot.img, recovery.img and system.img_sp...0,1,2,3,4 fail too
Click to expand...
Click to collapse
Please don't do that, lollipop it's supposed to install via recovery and not thru fastboot, please check that you downloaded the retail version of your Moto maxx and not carrier one.

Jaocagomez said:
Please don't do that, lollipop it's supposed to install via recovery and not thru fastboot, please check that you downloaded the retail version of your Moto maxx and not carrier one.
Click to expand...
Click to collapse
i tired both and same errors
before that problem in my moto, i was in lollipop...
do u think thats the problem?

guivalli said:
i tired both and same errors
before that problem in my moto, i was in lollipop...
do u think thats the problem?
Click to expand...
Click to collapse
First things first, it's your Moto maxx from mexico, puerto rico or Brasil?

Jaocagomez said:
First things first, it's your Moto maxx from mexico, puerto rico or Brasil?
Click to expand...
Click to collapse
Brasil

guivalli said:
Brasil
Click to expand...
Click to collapse
It's retail version or from claro or another company?

Jaocagomez said:
It's retail version or from claro or another company?
Click to expand...
Click to collapse
Retail

guivalli said:
Retail
Click to expand...
Click to collapse
Download this firmware and then flash it with rsd lite
https://mega.co.nz/#!KtYX2A7S!LTexE6weRap6e2g9l_ve8aBdShW-sGMpp2ZI4-xT_EA

Jaocagomez said:
Download this firmware and then flash it with rsd lite
https://mega.co.nz/#!KtYX2A7S!LTexE6weRap6e2g9l_ve8aBdShW-sGMpp2ZI4-xT_EA
Click to expand...
Click to collapse
i tried this one...
Failed everytime... i think its cause i used a Lolli before

guivalli said:
i tried this one...
Failed everytime... i think its cause i used a Lolli before
Click to expand...
Click to collapse
Then you have to manually flash all the files with fastboot, unzip all the contents to your fastboot folder and flash them one by one let me look for the fastboot commands

Jaocagomez said:
Then you have to manually flash all the files with fastboot, unzip all the contents to your fastboot folder and flash them one by one let me look for the fastboot commands
Click to expand...
Click to collapse
Jaocagomez,
i tried flash manual, 2danger try to me too
But with bootloader locked + impossible unlock cause lolli demand check one option in settings to unlock... all failed

guivalli said:
Jaocagomez,
i tried flash manual, 2danger try to me too
But with bootloader locked + impossible unlock cause lolli demand check one option in settings to unlock... all failed
Click to expand...
Click to collapse
You flash those files in fastboot mode, lollipop has nothing to do with it
This is fastboot mode:
http://forum.xda-developers.com/showthread.php?t=3011311

Jaocagomez said:
You flash those files in fastboot mode, lollipop has nothing to do with it
This is fastboot mode:
http://forum.xda-developers.com/showthread.php?t=3011311
Click to expand...
Click to collapse
Yes, my Moto doesnt exit fastboot mode

guivalli said:
Yes, my Moto doesnt exit fastboot mode
Click to expand...
Click to collapse
Do you have android sdk installed on your pc? You need that to flash without rsd

Jaocagomez said:
Do you have android sdk installed on your pc? You need that to flash without rsd
Click to expand...
Click to collapse
I have fastboot, mfastboot, adb... everything =/

guivalli said:
I have fastboot, mfastboot, adb... everything =/
Click to expand...
Click to collapse
ok unzip all the contents of firmware you downloaded on the fastboot folder.
using cmd write
Code:
fastboot devices
if a device show with any code like d654654
then your phone its detected
after that write this in cmd:
you can copy and paste it:
Code:
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
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
fastboot erase cache
fastboot erase userdata
fastboot erase clogo
fastboot oem fb_mode_clear
and your phone will work.

[Q] Unable to upgrade rooted Nexus 6 to 5.1.1

I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin

rambo8wtv said:
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
Click to expand...
Click to collapse
no matter how many times you try, you will never ever be able to update your rooted n6 via ota. if any system files changed from stock, an ota will download but will always error out. you can update several ways.. a. you can flash a 5.1.1 ROM via twrp. or b. you can fastboot flash 5.1.1.

2 things.
1. You must be 100% stock, no root, no custom recovery to OTA
2. The 5.0.2 message if you look probably.mentions deestroy..this is.because TWRP is using 5.0.2 sources - butnits irrelevant anyway give point 1

I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?

rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
twrp can not flash the ota or system img. you flash the system img via fastboot(not adb) and while you're in your bootloader.

rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
You cannot use the OTA file no matter what vehicle you use.

danarama said:
You cannot use the OTA file no matter what vehicle you use.
Click to expand...
Click to collapse
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data

starfish_001 said:
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
Click to expand...
Click to collapse
He'll probably want to not flash recovery. And if he has a custom kernel, may not want to flash boot either.

Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.

rambo8wtv said:
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
Click to expand...
Click to collapse
here too, many people try it with adb then claim it doesn't work. but its fastboot that you need, and while you are in the bootloader. adb will never work in the bootloader, only fastboot.

Turbo firmware?

Hello need help tracking down stock turbo firmware. The Motofirmware website (http://motofirmware.center/files/category/23-droid-turbo/downloads) are corrupted. The links in this thread are all dead: http://forum.xda-developers.com/moto-maxx/general/quark-stock-firmware-moto-maxx-droid-t3063470. Does anyone know of another source for stock 5.1?

http://motofirmware.center/

Stanleywinthrop said:
Hello need help tracking down stock turbo firmware. Does anyone know of another source for stock 5.1?
Click to expand...
Click to collapse
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637

Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.

jalal-jap said:
http://motofirmware.center/
Click to expand...
Click to collapse
Thanks, classic, i'll give this a try.
classic757 said:
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Click to expand...
Click to collapse

Stanleywinthrop said:
Thanks, classic, i'll give this a try.
Click to expand...
Click to collapse
No problem. Please let me know how it turns out.

Stanleywinthrop said:
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
Click to expand...
Click to collapse
i have same problem. extract it whit "7ZIP" and no corrupted for me.

http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1

TheSt33v said:
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
Click to expand...
Click to collapse
I get this error:
http://i.imgur.com/EOPsxnB.png

dmginc said:
I get this error:
http://i.imgur.com/EOPsxnB.png
Click to expand...
Click to collapse
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
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_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.

Oh thanks. Good info. Is there a write up on using fastboot anywhere? These forums are pretty poorly maintained and no good stickies anywhere
Edit: Oh, you edited your post. Awesome. Thanks.

The root junky fxz is that for rsd lite when I look at the contents the system image is in several sections and says system.img sparsechunk and has 10 sections. I have never seen this in an fxz. Is this a new way of flashing the system image.

TheSt33v said:
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
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_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Click to expand...
Click to collapse
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.

When in fastboot, type "fastboot oem lock" (without the quotations"

Btrusa said:
When in fastboot, type "fastboot oem lock" (without the quotations"
Click to expand...
Click to collapse
Wouldn't that lock the bootloader?
Is it even possible to re-lock?
From what I understand he wants to avoid locking the bootloader...
Edit: nevermind I looked it up... Should have just done that the first time... ("I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.")

dmginc said:
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
Click to expand...
Click to collapse
Nope

So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Sent from my XT1254 using Tapatalk

dmginc said:
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Click to expand...
Click to collapse
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin

unhappybirthday said:
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?

dmginc said:
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
Click to expand...
Click to collapse
I can only speak from my experience. I was on the KitKat bootloader and used mofo to flash lollipop. I unlocked with sunshine and installed twrp. Then I flashed the lollipop bootloader with the fastboot command . Still unlocked.
Sent from my DROID Turbo using Tapatalk.

Updating from 5.1.1 to 6.0

Lol. I'm totally lost. I usually don't make these types of threads. I'm trying to update to 6.0. I'm assuming I would need to update the Bootloader to 6.0 before hand. How would I go about doing so? Would I need to flash the factory images straight from google? ?Currently running 5.1.1 dirty unicorns v9.8. Thank you.

houstonsveryown said:
Lol. I'm totally lost. I usually don't make these types of threads. I'm trying to update to 6.0. I'm assuming I would need to update the Bootloader to 6.0 before hand. How would I go about doing so? Would I need to flash the factory images straight from google? ?Currently running 5.1.1 dirty unicorns v9.8. Thank you.
Click to expand...
Click to collapse
So, what you wanna do is download a stock image for the version of Android you're trying to flash, make SURE it's for your device! And assuming you know where to get fastboot and how to use the tool correctly, enter these commands!
fastboot flash bootloader bootloader[press tab]
fastboot reboot-bootloader
fastboot flash radio radio[press tab]
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format userdata
fastboot format cache
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot reboot
EDIT: Also worth noting that flashing system.img takes a few minutes, it may seem to hang, this is normal!
Sent from my Nexus 6

Okay. I appreciate that!! I just wanted to make sure I was taking the right steps to do so lol. Thank you!!

H4X0R46 said:
So, what you wanna do is download a stock image for the version of Android you're trying to flash, make SURE it's for your device! And assuming you know where to get fastboot and how to use the tool correctly, enter these commands!
fastboot flash bootloader bootloader[press tab]
fastboot reboot-bootloader
fastboot flash radio radio[press tab]
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format userdata
fastboot format cache
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot reboot
EDIT: Also worth noting that flashing system.img takes a few minutes, it may seem to hang, this is normal!
Sent from my Nexus 6
Click to expand...
Click to collapse
Okay so is flashing the latest 6.0 MRA58X okay? I'm on AT&T by the way.

houstonsveryown said:
Okay so is flashing the latest 6.0 MRA58X okay? I'm on AT&T by the way.
Click to expand...
Click to collapse
The latest Android version is 6.0.1. But if you want to flash that version, it's fine! As long as you make sure it's for your device! If you're using a Nexus 6, make sure it's for the "shamu"! And glad I could help! No problem!

H4X0R46 said:
The latest Android version is 6.0.1. But if you want to flash that version, it's fine! As long as you make sure it's for your device! If you're using a Nexus 6, make sure it's for the "shamu"! And glad I could help! No problem!
Click to expand...
Click to collapse
okay last thing. will the old root method still work on 6.0?

houstonsveryown said:
okay last thing. will the old root method still work on 6.0?
Click to expand...
Click to collapse
For 6.0, you will need a custom kernel. In short, Google added these "system is corrupt" messages to their stock kernels for Android 6.0, you will need a custom kernel. I used elementalx personally, you can get that at elementalx.org if you choose to, for Android 6.0.1, that's a different story. Let me know if you need any other help on this! PM me if you need to!

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?