Database Users

XT1575 Stuck in bootloop

My phone was working great (rooted), and just this morning it freezed.
I hard rest it, and it reloaded to system and then freezed again after a short time.
Tried to re load it and it was stuck for more than 15 min in the boot animation.
Tried to get into TWRP, it showed the TWRP image but then rebooted.
Re flash TWRP 3.0.2, tried to enter into it but again rebooted.
Reinstalled the phone using
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
with "Moto X Pure 3rd Gen (2015) XT1575 MPH24.49-18-3.zip" (using all the fastboot other than fastboot erase userdata)
After the reboot the phone shows the "warning bootloader unlocked" screen, a short vibration, keep this screen for 30 sec, and then turns off and do it all again.
When I try to get into recovery mode I see the "warning bootloader unlocked" screen followed by a broken droid image with the writing "No command."
Any idea on what can be done to save my phone?

Trying to restore on my other pc.
using "Moto X Pure 3r Gen (2015) - X2 WE-LTE-2CA - North America US Retail XT1575 MPH24.49-18_18.zip"
witch I once downloaded from Motorola, I run the first command:
>fastboot flash partition gpt.bin
And get this error:
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.098s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.819s
what's wrong?

You might need a newer version of ADB/Fastboot. I remember having a similar issue previously when flashing a stock ROM and had to update my software. It's not a guarantee, just a suggestion.
HH
Ooms

on my primary PC I downloaded "Minimal ADB and Fastboot"
and still the same error.
tested on my laptop (on it i did my first try) and here i can run this command
D:\Temp\Open\Moto X Pure 3rd Gen (2015) XT1575 MPH24.49-18-3>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.662s]
finished. total time: 0.662s
but still cannot enter recovery or boot into the system
did a test and took a motorola logo from here http://www.droidviews.com/remove-un...ng-on-moto-g-moto-x-purestyle-using-fastboot/
opend and flashed it.
Now I have the M logo instead of the "warning bootloader unlocked" screen but still on the boot loop.
Very strange, but after only flashing the logo.bin, the phone menus in the fastboot changed abit (look to me like the old version) but still no recovery.
Also see that on "fastboot flash system system.img"
I get an error:
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
but than it sends the file and keep writing OKAY
So some thing is still working down there.... juts need to find the correct stuff to flash on it?

Solved!!
Ive tried some more images to flush.
at the end used XT1575_CLARK_RETUS_6.0_MPHS24.49-18-3_cid9_subsidy-DEFAULT_CFC
The phone did a very long boot but at the end it loaded into the system and managed to get my lost photos.
Then reflashed TWRP -> restored my last image and every thing is now working as before.

US996 stuck in fastboot

I was using LineageOS (latest official build). I was trying to flash an updated bluetooth modem image, and the boot screen said my image was corrupt.
I was able to use LGUP to reinstall US99610f. Now I'm stuck at the fastboot screen on very boot, even after removing the battery. The phone is locked again, and I can't flash the unlock key through fastboot.
Code:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.026s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.068s
I'm unsure where to go from here, I've tried:
LGUP again
Hard power down/reboot
LG Mobile Flash Tool (CSE mode?), but that failed
Thanks,
Doug

DougWare said:
I was using LineageOS (latest official build). I was trying to flash an updated bluetooth modem image, and the boot screen said my image was corrupt.
I was able to use LGUP to reinstall US99610f. Now I'm stuck at the fastboot screen on very boot, even after removing the battery. The phone is locked again, and I can't flash the unlock key through fastboot.
Code:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.026s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.068s
I'm unsure where to go from here, I've tried:
LGUP again
Hard power down/reboot
LG Mobile Flash Tool (CSE mode?), but that failed
Thanks,
Doug
Click to expand...
Click to collapse
I have this same ****ing error, you get anything fixed
?

Silentwidow said:
I have this same ****ing error, you get anything fixed
?
Click to expand...
Click to collapse
I used LG's Web Chat Support, told them what happened. They were very accommodating and sent me a prepaid shipping label. They classified it as an "In Warranty - Software Failure", fixed it and shipped it back to me.
They did this even though they knew it was bootloader unlocked. Took about 2.5 weeks total to get it back.
Doug

us 996 fixed
i had a h910 flashed over to us996 that was stuck in fastboot. i had tried everything from flashing all the us996 firmwares to frp reset and came up with nothing. i then flashed H91510c_00_VTR_CA_OP_1007.kdz it not only successfully flashed but got me out of fastboot mode. i am now reflashing the us996 10f and will re root and twrp .. hope this helps someone out.

How can I repair my soft bricked XT1622?

Hello!
Something went wrong, I think it's called a soft brick, although I'm not sure.
I was trying to root my Moto G4 / Athene / XT1622, which was running Android 7.0 (NPJ25.93-11). I followed the sticky guide, except for the backup (I lacked a free microSD card) and ElementalX kernel parts, AND I forgot to wipe dalvik cache when it was asked. I did a lot of mistakes, it'll teach me to be more careful. :-/
After flashing Magisk, when I tried to reboot into Android, all I got was a black screen. I'm still able to boot to bootloader or recovery using the volume down + power buttons combination.
So I went back to TWRP and tried to flash LineageOS 14.1 + pico OpenGApps, then stock NPJ25.93-11 (Android 7.0), then stock MPJ24.139-23 (Android 6.0.1), none of which worked.
It looks like that at some point in the process I messed up the partition table (TWRP reports errors about them when trying to flash LineageOS).
Yet, as soon as I launch "fastboot flash partition gpt.bin", which is the first part of a stock recovery, I get:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.040s
(Same result with Android 6.0 or Android 7.0 factory images)
Any suggestion please?

try flash using RSDLite

Oops, I forgot to reply to myself, but I've been able to unbrick it following these steps: https://forum.xda-developers.com/showpost.php?p=75005815&postcount=5
So my problem is solved, thank you anyway!

Please assist! P10 lite (WAS-LXA1) bricked.

Hi guys,
I had 7.0/5.1 with TWRP installed and root etc. I tried to flash an Oreo ROM but now the phone just remains on a black screen. Holding down either up or down with power button just does nothing. I do have fastboot access though and able to flash but not boot at all!
fastboot devices
2XJDU17719015729 fastboot
sending 'boot' (16612 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.124s]
finished. total time: 0.540s
sending 'recovery' (35992 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.540s
fastboot boot RECOVERY.img
creating boot image...
creating boot image - 36857856 bytes
downloading 'boot.img'...
OKAY [ 0.902s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.902s

korval said:
Hi guys,
I had 7.0/5.1 with TWRP installed and root etc. I tried to flash an Oreo ROM but now the phone just remains on a black screen. Holding down either up or down with power button just does nothing. I do have fastboot access though and able to flash but not boot at all!
fastboot devices
2XJDU17719015729 fastboot
sending 'boot' (16612 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.124s]
finished. total time: 0.540s
sending 'recovery' (35992 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.540s
fastboot boot RECOVERY.img
creating boot image...
creating boot image - 36857856 bytes
downloading 'boot.img'...
OKAY [ 0.902s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.902s
Click to expand...
Click to collapse
The easiest method to install oreo but be careful after this method you will get bootloader locked. If you want method which will not lock your bootloader try HwOta.

eldorado999 said:
The easiest method to install oreo but be careful after this method you will get bootloader locked. If you want method which will not lock your bootloader try HwOta.
Click to expand...
Click to collapse
Thanks for your reply but the phone is permanently stuck on a totally black screen with fastboot. Pressing power+vol keys do nothing. I can't get to erecovery or the normal white screen/bootloader/fastboot screen. I am still able to send fastboot commands.
:crying:
C:\Windows\system32>fastboot oem get-product-model
...
(bootloader) WAS-LX1A
OKAY [ 0.003s]
C:\Windows\system32>fastboot oem get-build-number
...
(bootloader) :WAS-LX1AC432B198
OKAY [ 0.003s]
finished. total time: 0.003s
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.001s

If anyone has any suggestions please share them, I cant believe how easy it was to brick this phone! I've flashed and rooted at least 5x samsung phones prior to this but never bricked one!

korval said:
If anyone has any suggestions please share them, I cant believe how easy it was to brick this phone! I've flashed and rooted at least 5x samsung phones prior to this but never bricked one!
Click to expand...
Click to collapse
I don't know if you installed a custom Rom or not, but install the stock Huawei recovery. Than in a microSD card put the stock ROM. Than press vol up+voldown+lockscreenbutton.

Tiagohsoares said:
I don't know if you installed a custom Rom or not, but install the stock Huawei recovery. Than in a microSD card put the stock ROM. Than press vol up+voldown+lockscreenbutton.
Click to expand...
Click to collapse
I tried to install Elite ROM v7.7 for P10 Lite via TWRP using the zip file. It installed with some errors but after rebooting the phone does not come on at all. Screen is black. but I do have fastboot access. I've tried using the factory ROM in the dload folder but when I hold in the buttons it just makes the USB connect/disconnect sound in windows as if you plug or unplug a usb device, screen stays black. I'm starting to lose all hope now. I just payed a lot of money for this phone only to brick it...

korval said:
I tried to install Elite ROM v7.7 for P10 Lite via TWRP using the zip file. It installed with some errors but after rebooting the phone does not come on at all. Screen is black. but I do have fastboot access. I've tried using the factory ROM in the dload folder but when I hold in the buttons it just makes the USB connect/disconnect sound in windows as if you plug or unplug a usb device, screen stays black. I'm starting to lose all hope now. I just payed a lot of money for this phone only to brick it...
Click to expand...
Click to collapse
If you can flash and boot recovery try with hwota7 to install to install stock rom...

The bootloader has changed and phone is bricked; what should I do?

So I have run CandyOS for a while, but since it got bricked for some reason (possibly something to do with magisk modules) I decided to run another ROM instead. This is what I've done, keep in mind my bootloader has been unlocked the whole time:
1. booted into TWRP
2. flashed LOS 17.1 (gave error 18)
3. booted into bootloader in order to boot into LOS native recovery which I here realized existed (although their installation page says to use TWRP)
4. phone reboots into a changed bootloader which now claims "oem_locked"
The bootloader:
Code:
(in the middle of screen) Power off
AP Fastboot Flash Mode (Secure)
BL: MBM-2.1-river_retail-0ff2095b20-200404
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
oem_locked
I've tried a couple of things, results below:
I tried to unlock the bootloader (I have the unlock code saved):
Code:
fastboot oem unlock XXXXXXXX (bootloader) feature disabled
OKAY [ 0.003s]
Finished. Total time: 0.008s
Tried to flash a recovery:
Code:
fastboot flash recovery lineage-17.1-20200719-recovery-river.img
target reported max download size of 536870912 bytes
sending 'recovery' (20318 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.701s
..boot into recovery:
Code:
fastboot boot lineage-17.1-20200719-recovery-river.img
downloading 'boot.img'...
OKAY [ 0.702s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.702s
The exact same things happens with TWRP
I have also tried the Lenovo recovery program with no success, it refuses to recognize my device.
So what would be my next steps? Any help would be appreciated as I've tried to ask in a couple of places with no success

Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:

Andvark said:
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Click to expand...
Click to collapse
No this actually didn't occur to me, I'll try it as soon as I get home and see what happens. Thank you!

Andvark said:
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Click to expand...
Click to collapse
It didn't work:
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.093s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.125s
Code:
fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.365s
Did I do something wrong?
Edit: just realized I should've tried the same with 9 instead of instantly jumping to 10, I'll report back in a bit!
Edit 2: Nevermind, same result with 9 so the above still applies

yarnbomb said:
It didn't work:
Did I do something wrong?
Edit: just realized I should've tried the same with 9 instead of instantly jumping to 10, I'll report back in a bit!
Edit 2: Nevermind, same result with 9 so the above still applies
Click to expand...
Click to collapse
Manual flashing rarely work with locked moto bootloaders anymore.
Sent from my ali using XDA Labs

sd_shadow said:
Manual flashing rarely work with locked moto bootloaders anymore.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Oh, didn't know that. What would be my options with this?

yarnbomb said:
Oh, didn't know that. What would be my options with this?
Click to expand...
Click to collapse
LMSA's Flash Rescue or RSD Lite
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
LMSA's Flash Rescue or RSD Lite
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
The former didn't recognize my device, the latter I didn't know about, I'll try it asap

yarnbomb said:
The former didn't recognize my device, the latter I didn't know about, I'll try it asap
Click to expand...
Click to collapse
RSD Lite doesn't work with most windows 10 machines, try windows 7 if you can.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs

timba123 said:
You need blankflash
Click to expand...
Click to collapse
Not if it's in fastboot mode.
Sent from my ali using XDA Labs

timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
Fastboot OEM blankflash doesn't work if bootloader is locked.

timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
Timba, can you hook me up with the Telegram group for the G7?
Wondering if they have a blankflash for Android 10 or something.

timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
you are absolute about this because same issue happen to me and all has failed this definitely did the fix on my moto g7 power I just want to Thank You for this really appreciate it

timba123 said:
He stated he unlocked bootloader already. I did too and had same problem. Its saying oem locked due to a bad flash or didnt flash copypartitions zip in twrp. Can we contact him and try it? I bet it will work. I'm on XT1955-5 but it's the same issue I and many others have been in and fixed.
Click to expand...
Click to collapse
yes worked on mine xt1955-5 and yes was cause on flashing a custom rom thought was brick for good till had to came arcoss this fix and the only fix that got it out of that ap fastboot bullshits and yes had oem lock before it happen and when it bricked oem say's it's lock which got me thinking how in the hell going get out of this tryed all other method mention non work glad this did again thanks