XT1575 Stuck in bootloop - X Style (Pure) Q&A, Help & Troubleshooting

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.

Related

[Unresolved] [Bricked?] [Fastboot] Factory images won't flash

Hey all,
A little background: I was a little late to the Lollipop scene, and seeing as my phone wasn't getting an update anytime soon, I thought I'd crack out my ol' Nexus 7 2012 Wifi-edition. This thing was running an old version of Paranoid Android and was pretty slow and unreliable, I'd assumed I'd flashed a bad kernel or made some bad configurations or something. I very promptly downloaded the Lollipop factory image, fired up fastboot and wiped the device and attempted to flash the image.
It didn't work. I then assumed the image was bad, so I figured, as I had done in the past for KitKat, I'd download an older image and just accept the OTA. Once again the image refused to flash. It got stuck at the bootloader every time, but stubborn as I am, I tried yet an older image. flashing different versions of Jellybean, I discovered that my Nexus 7 wouldn't take any bootloader version higher than 4.18, and that if the bootloader did flash, the system.img would fail.
The procedure for flashing went as follows:
Download and extract nakasi gzipped tar images
cd into the folder containing an image
Run ./flash-all.sh, manually erase partitions and flash the zip, or extract the zip archive and manually erase partitions and flash the contained images
I noticed that the script wasn't working at all, so I took to manually flashing each image myself, and discovered that the issue usually occured with system.img and bootloader-group-x.xx.img
Looking for a solution to my problem. I'm running out of images to flash, and I have no way of transferring files to the tablet. I tried loading CWM so I could flash an unofficial image to get the thing booting, but I received errors when I tried to mount the USB storage.
Any and all help would be appreciated, I'm thinking this is a flash memory issue (i.e. one or more partitions is corrupt or formatted incorrectly), and I don't have the slightest clue how to fix it. Thanks!
EDIT: Errors and the actual process output are probably relevant.
Note that I run an Arch Linux box, but also tried the equivalent procedure using my other Windows 8.1 machine, to no avail.
Using the 4.3 jwr66y image as an example, this was the full manual process:
Code:
nakasi-jwr66y $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.978s]
finished. total time: 0.978s
nakasi-jwr66y $ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.787s]
finished. total time: 0.787s
nakasi-jwr66y $ fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.526s]
finished. total time: 2.526s
nakasi-jwr66y $ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
nakasi-jwr66y $ fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.423s
Using the 4.1.2 image as an example, this was the full manual process:
Code:
nakasi-jzo54k $ fastboot erase boot
erasing 'boot'...
OKAY [ 1.125s]
finished. total time: 1.125s
nakasi-jzo54k $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.633s]
finished. total time: 0.633s
nakasi-jzo54k $ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.601s]
finished. total time: 0.601s
nakasi-jzo54k $ fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.526s]
finished. total time: 2.526s
nakasi-jzo54k $ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
nakasi-jzo54k $ fastboot flash bootloader bootloader-grouper-3.41.img
sending 'bootloader' (2092 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 9.212s]
finished. total time: 9.498s
nakasi-jzo54k $ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.808s
nakasi-jzo54k $ fastboot flash boot boot.img
sending 'boot' (4896 KB)...
OKAY [ 0.643s]
writing 'boot'...
OKAY [ 1.967s]
finished. total time: 2.610s
nakasi-jzo54k $ fastboot flash recovery recovery.img
sending 'recovery' (5240 KB)...
OKAY [ 0.699s]
writing 'recovery'...
OKAY [ 1.120s]
finished. total time: 1.819s
nakasi-jzo54k $ fastboot flash system system.img
erasing 'system'...
OKAY [ 2.608s]
sending 'system' (446268 KB)...
OKAY [ 58.787s]
writing 'system'...
FAILED (remote: (Unknown error code))
finished. total time: 63.412s
Flashing the 4.1.2 image produced another strange error where the tablet would continually output (in a loop) the phrase "Neither USP nor CAC partitions found" after the flash failed.
EDIT: I managed to successfully flash bootloader 4.23 from the KRT16S factory image, but I still can't get the system.img from any KitKat or Lollipop factory image to flash. I keep getting "FileWriteFailed" error messages. Anyone know how I can fix this?
Bumping because I'd like to fix my tablet at some point :$
Narwhal73 said:
Bumping because I'd like to fix my tablet at some point :$
Click to expand...
Click to collapse
I'm on the same situation as you, but mine initially started after trying to install an f2fs lollipop ROM. I also think it's because of some sort of partition screwup.
My tablet won't let me install a bootloader, always saying invalid state. Luckily mine seems to still work on 4.23.
It let's me install the boot and recovery images every time,but it always fails at the system image.
What also happens when trying to flash the system image is that it will sit saying sending image for ages. Then eventually it fails with the errors of either too many links or unknown error.
Only once has it actually sent the image using jwr66v and got the tablet booting again, but it wouldn't update and kept giving errors, so I'm trying again to see if I can manually update to latest.
I was told to try using Linux instead of windows, which I'll attempt this weekend. I'll let you know if it works, but am not too optimistic.
Sent from my LG-D802 using XDA Premium HD app
Got mine to work again, by just trying once again the terminal fastboot erase of all the partitions and then flash bootloader, reboot bootloader, then flash recovery, flash boot, flash system and finally flash userdata.
This is the same thing that wasn't working earlier but took on first try again after a break. So unfortunately I can't say I fixed it in a specific way, it just seems to be a case of persistence paid off.
Flashed the latest Google lollipop image.
Try to do the manual erase and flash again. Maybe it will take eventually like mine did.
Hope you come right.
Sent from my LG-D802 using XDA Premium HD app
I had issues flashing factory images to my N7 yesterday too. At first I did the flash all script. It hung just like yours did at flashing the system image. I did it again with trying to flash everything manually and it still wouldn't work. Finally, I rebooted into fastboot and opened a new terminal window and everything worked as it should.
Persistence doesn't work as a solution for me. Trying with multiple machines, many different terminal instances, and several attempts with each has lead to no results. I'm thinking that for some reason the partition scheme might be broken, though of course it could be something else . Anyone know how I can go about diagnosing the issue properly, or repartitioning this thing? I don't even care about the Google images anymore, as long as I can get a functional OS back on it.
Currently the Nexus 7 is sitting with bootloader version 4.18, and no other functional images flashed to it. I can't seem to get the official bootloader version 4.23
to flash.
(Sorry for letting the thread die, I was away on vacation)
Narwhal73 said:
Persistence doesn't work as a solution for me. Trying with multiple machines, many different terminal instances, and several attempts with each has lead to no results. I'm thinking that for some reason the partition scheme might be broken, though of course it could be something else . Anyone know how I can go about diagnosing the issue properly, or repartitioning this thing? I don't even care about the Google images anymore, as long as I can get a functional OS back on it.
Currently the Nexus 7 is sitting with bootloader version 4.18, and no other functional images flashed to it. I can't seem to get the official bootloader version 4.23
to flash.
(Sorry for letting the thread die, I was away on vacation)
Click to expand...
Click to collapse
Check the md5sum of your "Official" 4.23 bootloader if it isn't THIS:
df53028033c9eccf4fe5ba7bc198ce24
Then it is Wrong...
http://forum.xda-developers.com/showthread.php?t=2573015
http://forum.xda-developers.com/nexus-7/general/guide-nexus-7-2012-factory-image-root-t2937833
Those two post will explain in further details.
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
sponix2ipfw said:
Check the md5sum of your "Official" 4.23 bootloader if it isn't THIS:
df53028033c9eccf4fe5ba7bc198ce24
Then it is Wrong...
http://forum.xda-developers.com/showthread.php?t=2573015
http://forum.xda-developers.com/nexus-7/general/guide-nexus-7-2012-factory-image-root-t2937833
Those two post will explain in further details.
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
Click to expand...
Click to collapse
I'm not sure what F2FS is, so I'm pretty sure I wasn't trying to do that. I'm just trying to get an actual bootable OS back onto the tablet. Stock Lollipop is preferable to anything else right now and I'll worry about customising it again at a later date...
I was unaware that Google/ASUS fudged up the bootloader images for the last few major releases (that would explain my inability to flash 4.23 to the device), so I'll try the instructions in the threads you've pointed me to when I get a chance. Thanks!
I'll report back with any successes or failures at some point next week; I have exams to study for in the meantime...
Hi dude, you can Try to install Firmware stock 4.2.2 and after upgrade it using ota. My friend resolved same problem in this way.
Inviato dal mio Nexus 7 utilizzando Tapatalk
Okay, so I found time to try to fix this thing tonight. The bootloader from KRT16S flashed fine, so my N7 is once again running bootloader version 4.23. The issue with flashing the system.img persists however.
The error I get is:
Code:
writing 'system'...
FAILED (remote: (FileWriteFailed))
finished. total time: 93.175s
What is so frustrating about this is that a "write failed" error message isn't very descriptive. A write could fail for any number of reasons. Is there a way I can enable more verbose error output in fastboot?
The only thing that I can think of pinning this on is an improperly sized partition. Unless there is something someone else can think of, could someone point me to where I can get the stock partition layout, and how I can repartition the device?
EDIT: not sure of the relevance, but I have just noticed that as soon as fastboot begins sending the image for writing, the bootloader on the device freezes up. Like I can't scroll through the options, not see any live text on the screen. Same goes for userdata.img.
EDIT: Here's all the bootloader variables (S/N changed in this post for privacy), can someone make sense of the partitions? What's with the hexadecimal?:
Code:
$ fastboot getvar all
(bootloader) version-bootloader: 4.23
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: no
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000727f00000
(bootloader) partition-type:userdata: ext4
sponix2ipfw said:
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
Click to expand...
Click to collapse
Bumping this again because I'm still having issues, anyone have any ideas about how I could go about getting my N7 back to working stock? It's recognisable by Fastboot, and I can get a working ADB connection through PhilZ recovery, but apart from that I can't do anything. It's a nice tablet and I'd like to get it back to a usable state.

MOTO G4 plus flash problem

I recently bought a new android phone (Moto g4 plus). I was eager to root it and take advantage of all the features.
The problem is that whenever I try to flash a recovery image, I get this error:
C:\Users\myuser\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12496 KB)...
OKAY [ 0.400s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.197s]
finished. total time: 0.601s
Keep in mind that the bootloader IS unlocked, I even get the warning when restarting the phone. Also this does not happen with just one image file. Every single image file gets this error. I have tried many different versions of TWRP, CLW, etc and all of them get this same error. Does anyone know how to solve this?
OKAY [ 0.197s]
finished. total time: 0.601s
Click to expand...
Click to collapse
Did you try and boot recovery after doing this? The message reports success.
When you back into fastboot you then select recovery. Is it loading the stock recovery when you do this? Don't forget it boots fastboot screen then you load the recovery in the scroll down option.

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!

Moto X-PLAY recovery TWRP

I have Moto X-PLAY running OTA stock Android 7.1.1 (SKU:XT1562) I have successfully unlocked the bootloader, but I'm having a problems installing recovery TWRP (twrp-lux-3.1.1-r1.img) following a youtube video using a Moto X PLAY.
Using the command: fastboot flash recovery twrp-lux-3.1.1-r1.img
I get this back:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 268435456 bytes
sending 'recovery' (8272 KB)...
OKAY [ 0.283s]
writing 'recovery'...
OKAY [ 0.192s]
finished. total time: 0.504s
reboot phone into ‘Recovery Mode’ and get the error:
No command (with an Android on it’s back’!’)
I have had looked for newer img file on TeamWin site. But does not list my device in it’s list.
I would like to know what is going wrong and how would I fix this problem.
Thanks for any help.
Maybe installing a new firmware fix it but if you install 7.1.1 by OTA you need to install again 7.1.1 but by firmware..
Ok problem solved after flashing TWRP over stock recovery, it will be overwritten by stock on reboot. You have to reboot into the bootloader using command: fastboot reboot-bootloader
then choose Recovery, and than after it boots, You can safely reboot to system as it won't be overwritten anymore.
Good to know that you solved it
Can you explain it a bit clearly. I am confused. But i am facing the same issue which you mentioned in your question..
He did explain clearly (including the command you need after installing TWRP). Just follow the steps.
After installing TWRP don't boot into system, boot into boot-loader first! Otherwise TWRP will be overwritten by stock recovery.

Categories

Resources