Database Develop

[Resolved!] OPWS27.2.1 - does not install

Hi !
So, my Moto X4 has some problem. I got a notification today that it's got a system update waiting (OPWS 27.2.1), so naturally I clicked the install button.
It downloaded whole 118MB package, but then, after 3 steps of installation it says that my Moto X4 has encountered some problems and the installation has not been finished (and no changes were made to the phone)
Now, I am not sure what to do, I've tried to factory reset the phone (no success after this, update does not install).
I think it maybe because I've flashed my phone with official software for european retail units (it was initially running T-Mobile branded software variant).
But what to do now ?

Seems that I have used incorrect script to flash official Android 8. Just one line is missing from it, it's not affecting phone functionality... but not allowing OTA update to install.
This is how the complete, working script should look like :
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
PAUSE
fastboot reboot
In the script that I have used primarly, there was the line flashing logo.bin missing. After I added this line, and reflashed the phone, OTA installed without problems.
I suppose that the Moto Updater is calculating maybe filesystem checksum after OTA update installation, and because there was one component not updated, this failed every time. But this is just my, well, "wild guess".

XT1900-1 root issues

Hi, I am a frequent visitor in xda, but this is my first post. I just purchased a Moto X4 on project fi. I installed all the updates and decided I wanted to try to root it. I've had several rooted Android devices from the mytouch 3g to my Nexus 7 2013. I read several posts on how to root, and install magisk for safety net to work (a must for me). After several errors and workarounds, I managed to unlock my bootloader. I followed a guide to install twrp, but it only has me fastboot boot it, and never actually installs twrp to the recovery. I also tried a modified boot image for February updates (which I had) and it just caused a boot loop. After 12+ hours of fighting with this thing (8 or more stock flashes) I've decided to go back to stock and relock the bootloader. Unfortunately, after a fresh flash of the 8.0 firmware and relocking the bootloader, I'm still unable to pass safety net check. I still get a warning when I boot up that I've installed custom software, and it looks like that will never go away, but I'm not sure what to do now. I'm fine with stock room passing safety net. I'm also fine with root and magisk for passing. Any help from someone with more experience would be appreciated. Thanks so much!

Do you have Magisk Manager installed? Doing so will trip Safety net even if not rooted. Also may need to wipe userdata and ddr completely again.
-- Starfox

No magisk installed at all. Does a factory reset clear user data and ddr?

I would create a batch file with the following and run it in the directory you have the stock firmware extracted:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I've also found that Magisk-patched boot tends to easily bootcrash, so after making sure it boots from stock like this, I would then use fastboot boot <patched boot.img>, install Magisk Manager, let it patch boot partition, reboot, and make sure it comes up. Right now with this setup, Safety net check passes both. If/when 8.1 stock is released, I'll probably need to go through the whole process again.
-- Starfox

I just reflashed stock again, installed updates and relocked bootloader again. Still failing safety net check. Cts profile match failed. I'll try reflashing with your script, but it looks almost identical to mine. Also, I'm using the 8.0 fi stock ROM. Should I try a different one?

Success
Following your script, using stock 8.0, everything works great! Rooted and passing safety net. Thanks for your help.
Next question, I still have stock recovery. Should I flash TWRP? I had issues with that the first time.
Secondly, do ota updates with with magisk?

Touchscreen not working after flash, Ali Moto G6

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

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

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

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

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

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

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

Followed a guide as stuck in boot loop. Now device is corrupt, help please.

Hi there, my device was having boot loop problems, I followed this guide using files uploaded by a user, then I was able to update using otg cable but it got stuck at 25%, after a reboot I get the message that my device is corrupt and cannot be trusted.
This is the guide i followed :
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527
Now I have tried to flash at fastboot the following images:
En_wpj0O_v115
En_wpj0O_v207
En_wpj0O_v209
En_wpj0O_v210
Chinese 2.31
I used the following commands each time:
fastboot oem nubia_unlock NUBIA_NX629J
Fastboot erase boot
Fastboot erase recovery
Fastboot erase system
Fastboot erase userdata
Fastboot erase cache
Fastboot erase data
fastboot erase system
fastboot erase modem
fastboot erase dsp
fastboot erase vbmeta
fastboot erase dtbo
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash dtbo dtbo.img
fastboot flash dsp dspso.bin
fastboot flash vbmeta vbmeta.img
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
Each time I've tried I just end up with the device is corrupt message, I have read that the command 'Fastboot flashing unlock' can solve the problem but when I enter it I get an error message that it's not allowed.
I would really appreciate some help getting this back up and running, maybe I'm doing something wrong or not using the correct images but I'm now at a loss.
Also my battery is now getting low which is worrying me.
Many thanks,
John.
Edit also followed this:
https://forum.xda-developers.com/red-magic-3/how-to/stuck-fastboot-mode-check-ub-debugging-t3951498
I used the files from global 2.31 and system.img uploaded by a user in that thread.
Then the following commands:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash -S 500M system system.img **I have to do it this way else it fails**
fastboot reboot
Unfortunately I still get the device is corrupt and cannot be trusted message. I am really stuck now
One thing I have noticed is when I flash system.img although it completes with all ok messages I cannot send any fastboot commands after doing this although fastboot devices shows the phone.
Should also mention that I cannot enter recovery from fastboot, just get the corrupt message.

Success.
I had to do:
fastboot flash -S 100M system system.img
Sending in larger chunks must have corrupted the image, I'm now back at the recovery and hopefully can go from here.
Update
Flashed latest EU rom over otg after clearing data and cache, all working.
What a relief!

Red magic 3 software crupt
My friend I'm facing same problem
I can't go to the recovery to restore flash file from usb OTG
Also fastboot is not allowed to unlock flash
How can i get back ok my device?

How to unroot new Z3 play?

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

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

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