Database Info

[GUIDE] Installing and Rooting H950PR 5.1.1 from 5.0.1 10b

I caught the deal on ebay for an inexpensive Flex 2 not so long ago and, of course, the first thing I set out to do was update and root it.
The stock image ran 5.0.1, w/ firmware H950 v10b. I attempted an OTA update several days in a row, being told each time that none was available (the phone is AT&T branded and my service is through AT&T), but eventually grew impatient to get that sweet, sweet 5.1.1 action going.
After attempting to flash the 5.1.1 v11x rooted system image provided by randrew87 (here), I was greeted with a nifty little 'Security Error' boot screen and pursuant loop. Sadly, I wound up flashing the stock system dump I created following that tutorial to get back into a usable state.
Left with no other options (assuming, correctly, that I'm being impatient with OTA), I decided to try the 5.1.1 H950PR v15a firmware.
NOTE: Though I chose to flash the unrooted 5.1.1 H950PR image first, you may not have to complete this step; I'm not sure, but it's possible that you could simply write the rooted image instead.
First, I followed this wonderful tutorial by Sj12345: [KDZ] H950PR 5.1.1 compatible with ATT H950 with Video!!!
My initial plan was to write the unrooted system image and root using any of the available tutorials. Unfortunately, I couldn't get any of the tutorials to work for me as my device simply refused to allow r/w operations to /system while using the COM interface, regardless of my approach.
After a little trial and error, I discovered I could write the rooted H950PR-v15A image, provided here by Sj12345, and achieve root.
Here's how:
Download rootedsystem.img (from Sj12345's post)
Download LG Root Tools.zip (attached) and extract to a folder
Copy to the root of your internal sdcard via means of your choice (I used MTP mode and Explorer to drag and drop)
Power off your device
While holding VOLUME UP, insert a USB cable.
Open a Command Prompt window where you extracted the archive (easiest way is by holding Shift then right clicking within the folder > Open Command Prompt Here)
Double click ports.bat (included in the archive). Find the diagnostics port (in my case, COM4)
Type the following:
Code:
Send_Command.exe \\.\COM4
(replacing 4 w/ your com port)
You'll be greeted with a '#' prompt, terminal-style. From there, issue the following command (thanks to randrew87's thread):
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=53248 count=534528 of=/dev/block/mmcblk0
The operation will take a couple of minutes. Once complete, you'll again be greeted with the '#' prompt.
Type LEAVE (all capitals), and hit enter. Your phone will reboot and have a clean, rooted image installed.
Profit.
This guide is obviously very specific, requiring H950v10b 5.0.1 firmware on an AT&T flex 2, no OTA availability, and a myriad of other issues (such as /system being readonly). My hope is that this will aid others who don't fall exactly into the parameters described in existing tutorials.
Thanks again to randrew87 and Sj12345 for their great posts and work; this thread is merely a slightly different approach to their pre-existing methods. They did the work, not me!
Hope this helps someone!
Regards
Smith

Any reason to go with h950pr instead of Ota 5.1.1 or simply just out of frustration of waiting? I'm asking cause I should get my att flex 2 tomorrow.

bL33d said:
Any reason to go with h950pr instead of Ota 5.1.1 or simply just out of frustration of waiting? I'm asking cause I should get my att flex 2 tomorrow.
Click to expand...
Click to collapse
PR rom does not have all of the AT&T bloat. However, the main drawback that I'm aware of is that there is currently no way to go back to official AT&T. Seems everyone who has tried to do so has ended up with a bricked phone. You may also run into issues trying to get warranty honored once you move off the official AT&T version. So.. caveat emptor and all.
Most folks who really want the 5.1.1 OTA have managed to do so by laying down the minimum amount of cash for an AT&T gophone plan then getting on the horn with AT&T's tech support to have them manually push the update through.

Hi smithisize, thank you for your guide A very basic question, how do I know which version of root file to use? I just check in About Phone > Hardware Info and it said the phone was LG-H950.

Smithisize,
Thank you for the guide. I have a question.
My H950 has H950v10d 5.0.1 on it. I am just guessing that it would work for any 5.0.1 version.
Is this right?
Thanks again,
MB

Same here...
As Meatbag_1 written, I have the H95010d release witch rom we take???

Yes it will work for atnt g flex2 on atnt firmware 5.0.1 all subversions
Sent from my Lenovo P780 using Tapatalk

Isn't the latest software version for the US h950 the "v11x" version? Is it possible to flash that instead of the PR firmware?

No
Only OTA from AT&T
No flash
Sent from my LGLS996 using Tapatalk

I tried rooting my newly flashed 5.1.1pr with this method and got authentication error 11. I had to reflash to get out of the boot loop. What am i doing wrong?

Thanks man. How can i root it in the first place?
I was trying HERE but i do not know which to dowload, if H950 V11X or H950 V11Z ... can you help me with that?

H950v10d 5.0.1 not rooted. Tried method from OP using H950PR 5.1.1 rootedsystem.img. Now I am stuck at Security Error bootloop. Where to go from here?
Nevermind... Phone started non stop bootlooping with no way to shut it off. So, I smashed it to bits.

For Android 5.1.1 PR (Puerto Rico)
First Flash the KDZ file from here: http://forum.xda-developers.com/g-flex2/general/kdz-compatible-att-h950-t3180847 using LG Flash Tool. I use Build 03/07/2014 Offline with modded hosts file.
Then download the Rooted H950PR-v15A image file from the link provided and continue with the guide.
btw: thanks for adding; you type: "LEAVE" in caps. No other guide seemed to mention that and when I did, it was the only time it actually rebooted my phone..:good:

dustindavidson900 said:
H950v10d 5.0.1 not rooted. Tried method from OP using H950PR 5.1.1 rootedsystem.img. Now I am stuck at Security Error bootloop. Where to go from here?
Nevermind... Phone started non stop bootlooping with no way to shut it off. So, I smashed it to bits.
Click to expand...
Click to collapse
My Phone did that too but I caught it quickly between boots and got into download mode so I missed the satisfaction of smashing it..

twiice said:
My Phone did that too but I caught it quickly between boots and got into download mode so I missed the satisfaction of smashing it..
Click to expand...
Click to collapse
I was able to get to download mode, but it would just go into bootloop after entering download mode. I have another on the way, so hopefully things go better this time. Will try the method posted above.
Can you send me a link to download "LG Flash Tool Build 03/07/2014 Offline with modded hosts file?"
thanks

Your can download it from here:
http://forum.xda-developers.com/showthread.php?t=2797190
I ignore the warning about the kdz having to be in the flash tool directory. I just browse to the location I downloaded it to, never fails.
And about the hosts file, this version doesn't seem to need a modded hosts file as it won't try to connect. That was sth I had to do from an earlier version a long time ago and forgot.
Fyi: I soft-bricked my phone like many others having the same security error because of tring to install the rooted system image file for 5.1.1 over the top of 5.0.1. And to reboot from download mode I had to hold all three back-buttons.
To install Xposed framework follow this guide: http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593 but USE Flashfire 0.24 or earlier as the latest beta version won't flash sh*t on this phone (or the G4)
If you need detailed instructions let me know.
Good luck!
PS: I bought the AT&T version(5.0.1) for the 3GB of RAM but I live in Australia so couldn't get the 5.1.1 OTA which is why I had to do this way, but apparently if you flash the 5.1.1PR kdz over the 5.1.1 AT&T OTA update(just to avoid AT&T bloatware) it will brick your phone.

so i just purchased the the g flex 2 much like yourself and i have everything ready to go. My only concern before doing so is what to do after the soft brick. Once you reboot from download mode is, doesthe phone start normally? or is there an extra step since you talked about USE flashfire
PS. i dont care to root the phone or is it necessary for this all to work?

Updated H950 5.0.1 ATT to H950PR 5.1.1
had the lg drivers which i downloaded using the lg suite from the LG website ( i originally tried to update my phone using this method...didnt work obviously so i came here)
Used lg flash tool 2014 as provided from this forum.
Placed H950PR15a_00.kdz in the place where it asks in the tool
followed the guide, i had the phone in debugging mode and it was just on my homescreen unlocked, phone shut off restarted into download mode and started the firmware update, phone itself reset at 100% ( keep it plugged in)
Lg flash tool was still going at this point it was around 90%, phone was resetting when the lg flash tool hit 100% and then crashed ( had a panic attack really ) i kept the phone plugged in and it reset to the lg boot screen
Leaving it plugged in , in spanish i saw that it was optimizing my apps, went to the tutorial within the phone and it resarted again... so i started having another attack, i then saw the boot screen claro at this point i unplugged my phone and it is now on 5.1.1 h950PR i have not rooted the phone before hand it was stock from ATT.
Thought i put my experience in here with this phone in hope to ease some tension. it was easier than i thought even though the tool crashed at the end, phone had already accepted the KDZ at that point

twiice said:
For Android 5.1.1 PR (Puerto Rico)
First Flash the KDZ file from here: http://forum.xda-developers.com/g-flex2/general/kdz-compatible-att-h950-t3180847 using LG Flash Tool. I use Build 03/07/2014 Offline with modded hosts file.
Then download the Rooted H950PR-v15A image file from the link provided and continue with the guide.
btw: thanks for adding; you type: "LEAVE" in caps. No other guide seemed to mention that and when I did, it was the only time it actually rebooted my phone..:good:
Click to expand...
Click to collapse
Thanks mate. Ran into this problem when flashing the ATT version before flashing the PR version like I was going to. This solved it, thought I'd wrecked the phone for a sec.
Much appreciated

Flash Android One Firmware to Unlocked Moto X4

Since I have bought this phone I constantly looked around the web to see if their was a way to flash the moto x4 with android one rom. after looking around on the web I have found that the moto x and A1 version are the same phone with no difference at all. however flashing to A1 means no alexa, but I have found that the google assistant has actually been more accurate with my voice than alexa. it wasn't really going to kill me if I never found a solution considering that Motorola actually has the cleanest firmware besides Nexus/Android one. However after looking for so long someone has found a way to find a oreo android one firmware on the web. I will paste the link and that link has the mirror to download the firmware. I unlocked my bootloader before trying as a safe measure in case it didn't work and can reflash back to nougat. you may not have to do that however in my opinion better safe than sorry after spending 399 on a phone. my version is the xt1900-1. this should work for all usa models EXCEPT the amazon prime from what I can gather. i will confirm that this shows as payton_fi with official firmware status and no network issues at all. however in case of something happening i would also download official nougat build as a safe measure. The person who found the firmware made it extremely simple.
03/15/2018- As of now we have found that many have had success in flashing in different countries. HOWEVER, many have said that their software has not changed. the only variant that is receiving updates periodically is the retail united states version. if you have software channel retus, which you can find in settings-system-about phone, then you should have continuous updates. others, for example reteu do not have updates that we know. it is possible that their are just no updates for that region. I honestly do not know. however no matter which variant it is, you will be able to flash the file with or without bootloader unlocked, UNLESS it is the amazon prime version. please do not ask how to change the software channel. nobody has yet found a way to change this on any Motorola device for now.
1-download the firmware and extract to a destination on computer
2- download the ADB and Fastboot file and extract to the firmware destination
3- run the windows batch file with moto x4 in bootloader mode
the batch file runs all the commands without you having to type them separately. make sure you do a full wipe of data/cache and reboot and you should see the android one boot logo. I do not know if i will get the same updates like the original android one moto x4 however i don't think this really will be an issue. in theory i should be getting the updates with the rest of the android ones
xda link to firmware- https://forum.xda-developers.com/showpost.php?p=75377622&postcount=4[/URL]
direct link- https://androidfilehost.com/?fid=962157660013070030
adb fastboot direct link- https://drive.google.com/file/d/1PCQwxaEDHZxBG_FwNWA0ozxfRumI31zd/view
Update 8.1- someone has been able to uploade A1 8.1. confirmed working on retail moto x4. did not work on locked bootloader. adb sideload will not work. I suggest you back up data of calls, texts, pictures, videos, etc. also had issues with sdk. ended up using mfastboot v2. for some reason it kept failing with both minimal adb and platform tools from sdk. mfastboot is just like fastboo9t but commands will have to be addressed as mfastboot. example: mfastboot oem unlock. after flashing I received the may 1st update and installed without issues on unlocked bootloader. I suggest you leave your bootloader unlocked. I believe this may have been the issue in the first place.
link to A1 8.1=https://forum.xda-developers.com/moto-x4/how-to/android-one-8-1-fastboot-flashable-t3805009
mfastboot commands
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
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_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr

I know you recompiled the info and listed the sources so thank you! It is a lot easier having a cohesive thread then searching through multiple sources. Worked great on my European Moto 4x.

Could someone please let us know if they've had success flashing Android One on a Dual Sim variant, or specifically the XT1900-2 variant? I'm looking for an Android One phone in Australia and the XT1900-2 is the only variant that can be obtained easily.

RandomDude said:
Could someone please let us know if they've had success flashing Android One on a Dual Sim variant, or specifically the XT1900-2 variant? I'm looking for an Android One phone in Australia and the XT1900-2 is the only variant that can be obtained easily.
Click to expand...
Click to collapse
I'm using with XT1900-6, it's a Dual SIM variant.

i will confirm that I have received the January patch update from Motorola for the android one and I had no issues. rebooted device and for the 1st minute or two had no cell service however after the update completely installed cell service came back on. also I have heard of some folks able to flash the android one without unlocking their bootloader. it is your choice to flash the firmware but I always feel more secure unlocking bootloader before any flashing to any device for any chance of soft bricks.

Anxious to try this, and while I don't see myself leaving Project Fi anytime soon...how easy is it to go back and do you think with these releases they'll lock you into a certain OS level (ie coming from a long line of sprint LG Gx phones and having to be careful about which version you flashed, else you end up with a brick)

thetolsonator said:
Anxious to try this, and while I don't see myself leaving Project Fi anytime soon...how easy is it to go back and do you think with these releases they'll lock you into a certain OS level (ie coming from a long line of sprint LG Gx phones and having to be careful about which version you flashed, else you end up with a brick)
Click to expand...
Click to collapse
it should be easy enough to go back to stock nougat. I successfully flashed nougat back on to my regular moto x4 without brick. the project fi version and regular version are actually both the same device, same specs, same hardware, but different roms. even if you bought retail instead of fi you can still use project fi sims in either device without hassle. I am pretty sure that is the main reason for google not to add moto x4 stock image for android one. i do not know if they will add a lock in future updates, however i do believe they might. either version in my opinion are great. even stock firmware from Motorola itself are really quite clean compared to other devices that have bloatware from both carrier and device manufacturer. only difference between the two is android one does not have alexa and one button nav on fingerprint scanner like retail. and android one will receive timely updates compared to retail. however retail is getting oreo. so it does feel like moto is stepping up their game with udates

christopher68369 said:
it should be easy enough to go back to stock nougat. I successfully flashed nougat back on to my regular moto x4 without brick. the project fi version and regular version are actually both the same device, same specs, same hardware, but different roms. even if you bought retail instead of fi you can still use project fi sims in either device without hassle. I am pretty sure that is the main reason for google not to add moto x4 stock image for android one. i do not know if they will add a lock in future updates, however i do believe they might. either version in my opinion are great. even stock firmware from Motorola itself are really quite clean compared to other devices that have bloatware from both carrier and device manufacturer. only difference between the two is android one does not have alexa and one button nav on fingerprint scanner like retail. and android one will receive timely updates compared to retail. however retail is getting oreo. so it does feel like moto is stepping up their game with udates
Click to expand...
Click to collapse
Yeah, I knew about the similarities in the hardware, I had bought my x4 to use with Fi through Best Buy because I had gotten a better deal than Google/Moto was offering at the time. My fiance will be receiving her x4 A1 in a few days and I'm a bit OS jealous/impatient to be honest. I don't use the alexa stuff nor do I use the 1 button nav but I very much appreciate the quicker updates.

I just want the Moto fingerprint reader stuff on my Android 1. How could I add that without having to flash to the retail firmware? I just got the January update and don't think the retail version got that.
It would be interesting to see how far behind that channel is.

Jayman007 said:
I just want the Moto fingerprint reader stuff on my Android 1. How could I add that without having to flash to the retail firmware? I just got the January update and don't think the retail version got that.
It would be interesting to see how far behind that channel is.
Click to expand...
Click to collapse
others have made it work using these methods. follow the link. I do not know if these actually work since I have not tried on my device. I also really have no interest for it either. however after doing this in order to get rid of it you may have to do a factory reset. also retail version updates will not be as consistent as the android one updates will be. so no, retail will not have the January update like the android one version. however it does seem that android one versions get updated the following months. so update for January gets received in February and February received in march and etc.
https://forum.xda-developers.com/moto-x4/help/one-button-nav-disabled-android-one-t3716877

for anyone who has done this, how do they compare? any benefit of A1 over retail besides updates? i don't mind being patient for those.

RockinAmigo14 said:
for anyone who has done this, how do they compare? any benefit of A1 over retail besides updates? i don't mind being patient for those.
Click to expand...
Click to collapse
I just received the February update. Some people really like having regular update. The big advantage is that a1 and pixels will be getting Android p over any other device made. Both retail and a1 firmware are actually really quite similar. I did this because I was both bored and curious. The one thing I really do not miss is the Alexa. I really miss the old Moto x commands. For some reason even when I don't say Alexa and the radio or a song says something close to Alexa it would activate the Alexa app. Can be very frustrating at times.

christopher68369 said:
I just received the February update. Some people really like having regular update. The big advantage is that a1 and pixels will be getting Android p over any other device made. Both retail and a1 firmware are actually really quite similar. I did this because I was both bored and curious. The one thing I really do not miss is the Alexa. I really miss the old Moto x commands. For some reason even when I don't say Alexa and the radio or a song says something close to Alexa it would activate the Alexa app. Can be very frustrating at times.
Click to expand...
Click to collapse
Hi, did you install the android one version on a "regular" moto x? Do the updates arrive the same as the Android One version? I have read that by not changing the software channel ota are not installed. If you confirm this I would install it. Thank you.
Sorry for my bad english.

jsis83 said:
Hi, did you install the android one version on a "regular" moto x? Do the updates arrive the same as the Android One version? I have read that by not changing the software channel ota are not installed. If you confirm this I would install it. Thank you.
Sorry for my bad english.
Click to expand...
Click to collapse
yes I have changed it from retail to android one. others have as well.i have not have had a problem since installation. I received the January security install near same time as others. the February update was received yesterday. it would be nice for others to be able to tell others if they installed it and were successful. the only ones I know for sure that will not flash are the amazon prime versions. those are the xt1900-07 models. follow the instructions and you should be good. from what I understand the updates on a1 come straight from google servers. with the amount of money they make I'm sure its no problem sending them out all at once where Motorola sends their update through their servers and roll out in stages, along with making sure the updates are supported through the cellphone carrier.

christopher68369 said:
yes I have changed it from retail to android one. others have as well.i have not have had a problem since installation. I received the January security install near same time as others. the February update was received yesterday. it would be nice for others to be able to tell others if they installed it and were successful. the only ones I know for sure that will not flash are the amazon prime versions. those are the xt1900-07 models. follow the instructions and you should be good. from what I understand the updates on a1 come straight from google servers. with the amount of money they make I'm sure its no problem sending them out all at once where Motorola sends their update through their servers and roll out in stages, along with making sure the updates are supported through the cellphone carrier.
Click to expand...
Click to collapse
What's your software channel? It's retus?

Jayman007 said:
I just want the Moto fingerprint reader stuff on my Android 1. How could I add that without having to flash to the retail firmware? I just got the January update and don't think the retail version got that.
Click to expand...
Click to collapse
You mean the "fingerprint nav" on A1? No problem, see also
https://forum.xda-developers.com/mo...ndroid-one-t3716877/post74841331#post74841331

I have installed the rom of android one but my software channel is still reteu with what it seems that the updates will not arrive to me (now I do not have updates). Can someone confirm it ?.
Info:
Model: XT1900-7
Software variant: google_fi
Software channel: reteu
Version: 8.0.0
Security patch: December 2017
No. Compilation: OPW27.57-25-2

jsis83 said:
I have installed the rom of android one but my software channel is still reteu with what it seems that the updates will not arrive to me (now I do not have updates). Can someone confirm it ?.
Click to expand...
Click to collapse
I also flashed OPW27.57-23-2 on a reteu XT1900-5 device and am also seeing this behaviour.

radjad said:
I also flashed OPW27.57-23-2 on a reteu XT1900-5 device and am also seeing this behaviour.
Click to expand...
Click to collapse
I understand that the software channel has not been changed to retus there are no updates.

jsis83 said:
I understand that the software channel has not been changed to retus there are no updates.
Click to expand...
Click to collapse
Yes, just to be completely explicit my software channel is also still on reteu. Is your bootloader still unlocked?

question about OTA after a custom rom

Hi, i flash the pixel experience rom oreo 8.1 on my moto g 2015 but i dont liked, so i flashed the stock rom 6.0 via adb fastboot and some updates have appeared, i can do?

Twinsen78 said:
Hi, i flash the pixel experience rom oreo 8.1 on my moto g 2015 but i dont liked, so i flashed the stock rom 6.0 via adb fastboot and some updates have appeared, i can do?
Click to expand...
Click to collapse
While I don't know exactly how it is on Moto G3, it seems kind of a game of luck if you get OTA updates back. But necessary steps device independent often are:
- Flash stock ROM with a full wipe
- flash stock recovery
- relock the bootloader
- some devices include a flash counter, for example almost all Samsung devices. This counter has to be reset. Works different for every phone.
- for some devices, for example Sony, specific files MUST be backuped before a flash, otherwise there is no chance of getting OTA back.
But keep in mind that this device doesn't receive updates anymore since about last year. So maybe you just look for the most up to date stock ROM and flash it, which btw on my phone is Android Marshmallow, security patch level April 2017.
I hope this helps a little bit, even though I can't provide very detailed information. Let's hope someone more experienced helps further, or just search around in the web.

BenjyTec said:
While I don't know exactly how it is on Moto G3, it seems kind of a game of luck if you get OTA updates back. But necessary steps device independent often are:
- Flash stock ROM with a full wipe
- flash stock recovery
- relock the bootloader
- some devices include a flash counter, for example almost all Samsung devices. This counter has to be reset. Works different for every phone.
- for some devices, for example Sony, specific files MUST be backuped before a flash, otherwise there is no chance of getting OTA back.
But keep in mind that this device doesn't receive updates anymore since about last year. So maybe you just look for the most up to date stock ROM and flash it, which btw on my phone is Android Marshmallow, security patch level April 2017.
I hope this helps a little bit, even though I can't provide very detailed information. Let's hope someone more experienced helps further, or just search around in the web.
Click to expand...
Click to collapse
are only 3 security patch, i updated and not brick but thanks for the reply.

No more WiFi connection after Security Upgrade December 2019

I have just installed December 2019 security patch via OTA and now I can't connect to any WiFi any more. It scans and detects networks, but it won't connect. It asks for the passphrase of networks which have already been stored, I enter it and then it says "could not save network" and "could not connect to network". Anyone with the same problem?
My idea to solve this was to boot into recovery and clear cache partition, but this option is simply missing in the recovery menu. Any idea how else cache partition can be cleared without root?

Maheshwara said:
I have a Moto Z4 XT1980-3 (Unlocked retail version with RETUS channel) with bootloader locked - no modifications from official state so far. When I got the December 2019 security patch upgrade, something network-related got corrupted - I have not been able to connect to any WiFi at all! This was the origin of all the desaster.
I read through the internet and found the information that it could happen that an OTA upgrade may not have been got on the device properly and if there are any hassles afterwards, it is required to do a full flash of the recent firmware. Okay, no problem, I thought. I am really familiar with ADB, fastboot and so on, and so I did. Took the recent firmware from here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/ (the one uploaded on 6th of December 2019).
The result was that I could flash all parts of the firmware, except of boot, vbmeta and dspso - for these parts I got a "(bootloader) Preflash validation failed" error. So now I am with an inconsistent firmware state and can only access fastboot mode (not even recovery). Plus sometimes when booting it, I get errors of unbootable A/B slots in the bootloader log. After having flashed gpt again, these errors disappear and I simply get the message that my device won't boot because of an invalid operating system.
What I have already tried to do:
- flash a full factory image (see above)
- use RSD lite (this tool detects my device as connected, but with no device information at all (only "?") and says it can not be switched to fastboot mode - but I am in fastboot mode already ???)
- use LSMA Smart Repair Assistant (this tool says my device is not compatible)
- Blankflash (I have not found out yet how to get my device in edl mode from fastboot)
As bricked devices are a more general Android issue and Moto Z4 is not very spread (the corresponding device forum is almost dead), I try to ask my question here in the general Android troubleshooting section. I hope, somebody can give me any advice how to reanimate my device. Maybe, anybody with special Motorola experience who can tell me why I can not flash the full factory image or explain how I can get boot, vbmeta and dspso back to the device. Any help appreciated.
Click to expand...
Click to collapse
Not being able to flash the boot.img likely means you are flashing the wrong firmware.
Either an older version or the wrong software channel.

sd_shadow said:
Not being able to flash the boot.img likely means you are flashing the wrong firmware.
Either an older version or the wrong software channel.
Click to expand...
Click to collapse
This is what I have been supposing, too, in the meantime. Channel is correct, but obviously, the image I have is too old.
Any idea where I can get a factory image of the most recent firmware version from?
Gesendet von meinem Moto Z3 Play mit Tapatalk

Maheshwara said:
This is what I have been supposing, too, in the meantime. Channel is correct, but obviously, the image I have is too old.
Any idea where I can get a factory image of the most recent firmware version from?
Gesendet von meinem Moto Z3 Play mit Tapatalk
Click to expand...
Click to collapse
Unfortunately there is no official way to get Moto firmware.
There has always been people who have access, that reupload firmware.
https://mirrors.lolinet.com/firmware/moto
Is currently the best updated site.
Hopefully a newer version is uploaded soon.
Otherwise you could contact moto support.
Is it still under warranty?
Sent from my mata using XDA Labs

This XDA post contains links to unbricking tools for Moto devices.
RSDLite does not work on Windows 10. If you have a Windows 7 machine, you might want to try that.
Otherwise, go here for a video for converting RSDLite XML files to Windows batch files
The download link is hard to find, so here http://rootjunkysdl.com/files/Android Programs/RSD_Lite_Motorola_XML_To_Batch_Script.zip
Make sure you download the SDK platform-tools from Google, I had problems when using the one included. Replace adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and fastboot.exe from the firmware converter with the ones from the platform-tools package.
If you're not using Windows, make sure you have platform-tools installed and follow this guide to convert the XML file to a shell script yourself, of course adding #!/bin/bash to the first line of the script.
You may also need to edit the resulting batch/script file and replace the target "system" with "system_a" and fingers crossed it'll complete and you'll be golden.

@sd_shadow
I know nothing but the lolinet page for getting firmwares, too. That's where I got the too old image I already have from. I hope, that it will not last too long till a recent image appears there.
In the meantime, I contacted Moto support. My device is still under warranty. They will investigate further how to help me and then get in touch with me again. I hope, I will not need to send it in, because it is easy to solve the problem on my own - I need nothing but such a damn recent firmware.
@Lesking72
Good to know that RSD does not work with Windows 10... My desperation led me to try this. I prefer more platform independent ways of flashing, because my daily driver is Linux (with a Windows 10 VirtualBox which I only use if there is no way around). To transfer the support or flash file of the image to a linux flashing script is quite simple. Fastboot flashing commands are always the same - there is only a need to look which partition to assign which file to. All information about this can be found in the flash file. The main thing for me is, that now, I know where the problem is: I do not have a firmware which is new enough to flash it with bootloader locked. So no RSD, flashfile converters, Blankflash or what else will help me in my situation. I will have to wait for a factory image with a recent firmware. Damn! I can not do anything else! This is what is really annoying to me.
Even more annoying is that I can not even unlock the bootloader to solve the problem, because the "Allow OEM Unlock" flag in developer settings is inactive! At least I think so... Any idea how to find out if this flag is active or not via fastboot without voiding warranty? I can get the unlock data via fastboot and so request the unlock code, but what if when unlocking it says that it can not be unlocked because of this flag being inactive? Then I would have lost my warranty for nothing. Too risky...
I have also played around a bit with this Moto LSMA Tool. It does not even detect my intact Moto Z3 Play in fastboot mode!

@Maheshwara I was watching the rootjunky videos I linked in my previous post and for his device, it threw errors for some parts but still worked. It might be worth it to try flashing again, but replace the "system" target with "system_a"
I haven't tried to downgrade the firmware on my phone though, so I don't know if your issue is because of anti-downgrade features or it's just showing those errors.

@Lesking72
The Moto support has already confirmed me that my problems' reason is the anti-downgrade "feature". And I flashed the same partitions like in the image's flash file. I simply built fastboot commands of the information inside.
The only thing that could solve my problem is to get a recent factory image or find somebody with unlocked Z4 version with RETUS channel, bootloader still locked and recent software version, who could backup all the partitions for me.

I have just seen that there is at least a more recent image for Verizon version here: https://mirrors.lolinet.com/firmware/moto/foles/official/VZW/
That gives me a bit of hope that there will be soon one for the unlocked retail version, too. Or would it be a good idea to try if I can flash boot, vbmeta and dspso of the latest Verizon image to my device? If I am honest, I do not think so...

@Maheshwara If you tried flashing the newest version boot, vbmeta and dspso from the VZW image it would likely not work because your system partition etc. will be from the older unlocked version you tried to flash.
Even if that weren't the case I don't know if you'd be able to flash the VZW firmware without unlocking the bootloader (I figure it's signed differently to stop people from installing the retail firmware on a VZW phone which would make it not work on a retail phone with a locked bootloader)

The odd thing is that I have no OTA update available and when I connect to LMSA it says I'm on the latest version

Are you already with December 2019 security patch?
Gesendet von meinem Moto Z3 Play mit Tapatalk

I live in México, and i have the same moto z4 than you, 1980-3 US retail, and the ota has not arrived yet,
My last OTA is from october, do you know about other users with the same problem than you? MAHESHWARA

@airecomprimido
No, I don't know about other users who already received the December OTA for retail US version. I think, Moto has withdrawn it because of problems it may cause. I seem to be the only unlucky who already got it.
Gesendet von meinem Moto Z3 Play mit Tapatalk

Maheshwara said:
@airecomprimido
No, I don't know about other users who already received the December OTA for retail US version. I think, Moto has withdrawn it because of problems it may cause. I seem to be the only unlucky who already got it.
Gesendet von meinem Moto Z3 Play mit Tapatalk
Click to expand...
Click to collapse
Maybe you will receive the new fixed december OTA, do you know something about android 10?

Maheshwara said:
Are you already with December 2019 security patch?
Gesendet von meinem Moto Z3 Play mit Tapatalk
Click to expand...
Click to collapse
@Maheshwara i get the OTA yesterday, my phone is with de december security patch, and working fine
https://ibb.co/mNHp69X

airecomprimido said:
Maybe you will receive the new fixed december OTA
Click to expand...
Click to collapse
Too late - my phone is already fully bricked! I will have to wait until a factory image with December patch version will appear somewhere. No other way to revive it... No boot, no OTA, but good to know that it seems to have been definitely rolled out now. So there's a bit of hope that the full factory image I need will be available soon.

Got the factory image version I needed this morning. After having flashed it my device got revived. So far so good, but WiFi connectivity was still broken. After having done a factory reset everything was fine.
But no good that a simple OTA security patch upgrade craps a device with necessity of a full reset.
Gesendet von meinem moto z4 mit Tapatalk

[SOLVED] Is it Safe to flash earlier firmware over RETUS 40-95-9?

In case I get another phone with the latest RETUS OTA and run into the same problem where the phone will not accept the Unlock Code sent by Motorola. "FAILED (remote error)" every time. I don't know if this new OTA is the problem, or if the phone I received had a hardware or firmware problem. I posted here about that problem 2 days ago, so the history is in that thread. TIA . . .
= = = = = = = = =
SOLVED. Rollback from 40-95-9 to 40-95-6 --CANNOT-- be done. Anti-rollback "protection" prevents the 95-6 version of bootloader.img from being flashed.
NOTE: Trying to flash older firmware wipes the existing firmware, so attempting to do this will leave you with a systemless phone. If you insist on trying it yourself, BE SURE TO HAVE A COPY OF YOUR CURRENT (OR NEWER) FIRMWARE on hand.

According to my notes, at some point when I was doing OTA updates I did end up with 40-95-9; however, I suspect this update occurred after I unlocked the device. Hence, when I rolled back to the Feb version, I did not run into issues.
That said, I would NOT attempt to roll back with a stock bootloader locked device. You (likely) may run into motorola's implementation of Androids roll back protection which will prevent the device from booting. Without the 40-95-9 firmware file, I don't think it will be easy to get back to a working device. i.e. some form of blank flashing will be necessary. You might be able to recover from this, but I think it will be a headache.
Hopefully someone else will respond with some better advice/info for you.
HTH
EDIT you wrote in your other thread:
I should probably stress, I flashed the entire firmware with no problems at all.
Click to expand...
Click to collapse
but I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
Before flashing anything, be sure to allow OEM unlocking from developer options and get your unlock code from motorola's www site as you did previously.
Even tho it will soft brick the device, I'd flash everything from an older version. Reboot to the now hopefully older bootloader (you can check what bootloader is running with `fastboot getvar all`). If you end up with the red "No valid operating system" screen, just simultaneously hold down the power and volume down buttons until you get back to the bootloader. Assuming you can get into the bootloader (I'm not 100% cerntain that you can) from there you may be able to unlock or at least re-flash the 40-95-9 firmware to recover.
Note I have not attempted this so I can't say this will work. It's just what I would try in this situation if I didn't care about the time spent trying to recover or permanently bricking the device.
Good luck and I hope you don't have to try it.

It's just too hard to guess what might happen with the new arrangement of partitions in Android 10. I've rescued a couple of soft-bricks (Moto and Samsung believe it or not) but they were cheaper or just older. I'd rather not risk hard-bricking a phone after just shelling out $170-200 for it. (That's Swappa prices, everywere else is another $100 or so.) On older partitioning an unlocked bootloader wouldn't have made any difference in whether rollback worked or not. It was (pretty much) all about matching up bootloader versions (or digital signing for locked bootloader etc). Rollback would either work or it wouldn't.
Right now I'm trying to find a phone with something prior to 95-9 firmware. If I can't find that, I think I'll just try to talk my lady into a slightly smaller phone. She's been spoiled by the newer 6.7-6.8" phablets. I hate them myself, but this is not for me.
Thanks a bunch for trying to help.

notmyrealhandle said:
. . . in your other thread:
. . . I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
. . .
Click to expand...
Click to collapse
Forgot to say, I was explaining in the other thread that I had downloaded 95-9 via Lenovo's Rescue and Smart Assistant right off the bat, so I would have that for backup just in case. I did end up flashing it (the old-fashioned way, with a couple dozen fastboot commands) to see if maybe that would fix any possible glitch in the firmware. Also after trying to unlock a few more times, I reconnected to Rescue and Smart Assistant and actually ran the whole rescue deal, thus flashing 95-9 one more time.
I had also downloaded 95-6 from lolinet but didn't get the nerve to try flashing it. Android 10 on this phone is just too weird. Last year I unlocked and Magisk-rooted a Moto G Stylus 2021 on Android 10 with never a hint of a problem anywhere.

NOPE, this cannot be done. See bottom of my first post.