Database Info

TWRP won't flash properly

Hi,
When flashing TWRP through fastboot I don't get an error in the command line so everything goes fine.
But when i try to boot i get the android error log.
But when i try booting to TWRP (fastboot boot TWRP.img) everything works fine?
Extra information:
Stock android 5.0.1 with sideloaded latest update
Stock kernel
Flashing from linux
Fastboot state unlocked
Command line output
HTML:
target reported max download size of 1073741824 bytes
sending 'recovery' (14000 KB)...
OKAY [ 0.633s]
writing 'recovery'...
OKAY [ 1.100s]
finished. total time: 1.734s
Error logo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would like a working recovery before starting to flash. I'm not new to flashing, but can't seem to find the issue here.

fastboot flash recovery recovery.img is what you should be using
You MAY have written over the kernel with what you did. So just in case use fastboot flash boot boot.img after too
Or have i read it wrong what you've done?

I have used fastboot flash recovery recovery.img
And i can still succesfully boot in the os so the kernel is fine.
It's just weird that i can boot the recovery with fastboot boot recovery.img but cannot boot to it when flashed.

aropop said:
I have used fastboot flash recovery recovery.img
And i can still succesfully boot in the os so the kernel is fine.
It's just weird that i can boot the recovery with fastboot boot recovery.img but cannot boot to it when flashed.
Click to expand...
Click to collapse
Try this
fastboot boot recovery.img
Flash supersu in recovery, then
fastboot flash recovery recovery.img
Sent from my Nexus 5 using XDA Free mobile app

Thanks that fixed it!
Still wondering why, never rooted my nexus 5 before, bought it unlocked it flashed cm11 ...

XT1033 india. Tried to Lock the Bootloader but Bricked the Phone instead. Help.

Hey there, thanks for viewing. Before posting here, I have well enough spent 6+ effective hours (whole day yesterday) to find a solution for this. Unfortunately, I was not successful.
I own a Moto G (XT1033) Dual Sim India Version. Initially, I was running an android 5.02 stock (rooted) with unlocked bootloader when I get a notification about a system update (for 5.1.1). Exited, I downloaded the update and tried to install it, but the OTA wouldn't install. Later, I figured it may be because my phone had an unlocked bootloader. As a result, I tried to re-lock the bootloader by installing 5.0.2 stock again from this guide: http://forum.xda-developers.com/showthread.php?t=2700502 .
Everything was successful and the bootloader was locked again . But this time instead of OTA, I pasted this file Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip which I found in some webpage I don't remember. The update was successfull. Now due to some stupid reason, I wanted to do the whole thing again and and do the OTA udpate this time. This is where the problem begin.
In the bootloader I typed the exact same commands and used the exact same files, but this time, this is what I got:
HTML:
C:\Users\Prasannjeet\Desktop\TWRP\Fastboot>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.103s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.425s
Attaching the screenshot, please have a look.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also adding a pic of my phone's bootloader screen for the error message it receives.
Note that I get the same error for sparsechunk command which comes later. I have tried 10-20 guides, most of them from XDA for the same "Preflash Validatin Failed" error, but none of them fixes my problem.
Bottomline, whatever on earth I do, whatever recovery, stock ROM's, fastboot's I download and install, as soon as I type the command "mfastboot.exe flash partition gpt.bin", I get the same preflash validation failed error message again and again and again!!! :crying: I get the same error for the rest of the commands.
Note that if I try to flash any other custom ROM's via TWRP or any other recovery, I am easily able to do it, but that way I won't be able to lock the bootloader ever again. The only way we can lock the bootloader is something which is not working.
Is it really impossible for me to downgrade now?
Few posts which I have went through already but didn't work:
http://forum.xda-developers.com/moto-g/help/gpe-pre-flash-validation-failed-gpt-t2836073
http://forum.xda-developers.com/moto-g/help/bootloader-preflash-validation-failed-t2834023
I have tried more, but can't find the links now.
Please help :crying:
Thanks!

Have officially 5.1 ROM, you try to flash it again.
And why did you want to re-lock bootloader? Still update OTA when unlocked bootloader.

thuybang said:
Have officially 5.1 ROM, you try to flash it again.
And why did you want to re-lock bootloader? Still update OTA when unlocked bootloader.
Click to expand...
Click to collapse
Thanks for replying! Can you share the link of 5.1 ROM, if you have?
I tried to OTA when bootloader unlocked, but it didn't happen

Link ROM :http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
OTA fail because root or you modified system. You only flash stock ROM then update OTA ok. No need relock B.L

Stucked on Initial Settings

I got this Moto G 2015 (XT1453) and it is stucked on the following screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It doesn't allow me to connect to any wifi network and doesn't skip the initial configuration.
I've tried reinstalling the stock rom doing this http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
I can't access any of the phone settings, so I had to reboot the phone into Bootloader mode using hardware,
but when I type the command "fastboot flash partition gpt.bin" I got this message:
" sending 'partition' <32 KB>...
OKAY [-0.000s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.438s"
This is the first time I try to use Fastboot, so I assume this isn't right. Even with this message I did all the following steps but I got stuck on the same screen again.
I would be really grateful if someone helps me on this.

r_gomes said:
I got this Moto G 2015 (XT1453) and it is stucked on the following screen:
It doesn't allow me to connect to any wifi network and doesn't skip the initial configuration.
I've tried reinstalling the stock rom doing this http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
I can't access any of the phone settings, so I had to reboot the phone into Bootloader mode using hardware,
but when I type the command "fastboot flash partition gpt.bin" I got this message:
" sending 'partition' <32 KB>...
OKAY [-0.000s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.438s"
This is the first time I try to use Fastboot, so I assume this isn't right. Even with this message I did all the following steps but I got stuck on the same screen again.
I would be really grateful if someone helps me on this.
Click to expand...
Click to collapse
Preflash Validaton Errors occur when you are trying to flash newer and older bootloaders. In that case,what you have to do is, skip the following commands and flash everything else:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you haven't discovered it, the best way to flash is copy all the commands and just paste them into the cmd window instead of typing them one at a time.

Tel864 said:
Preflash Validaton Errors occur when you are trying to flash newer and older bootloaders. In that case,what you have to do is, skip the following commands and flash everything else:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you haven't discovered it, the best way to flash is copy all the commands and just paste them into the cmd window instead of typing them one at a time.
Click to expand...
Click to collapse
Thank you. I made what you said and it worked, but now I got the message:
"This device was reset. To continue, sign in with a Google Account that was previously synced on this device."
I've looked in many forums and it seems like there is no way to pass this screen without the first email used in the phone. My friend bought this phone from a guy, so I have no idea who was his first owner or the first email account. What should I do?

Have you ever been able to log in with this phone? Was the phone purchased used and what version of Lollipop came on the phone. If 5.0 came on it, then you may have to flash back to 5.0 and log in with a new account. If it was purchased used with 5.1 then the seller will need to provide you with the login so the old Google account on the phone can be removed. Maybe someone else has an idea but since 5.1 it's harder to get into a phone that was purchased used.

My X3 NFC is Bricked

Hello Everyone !
unfortunately I Bricked my POCO X3 NFC (Surya)
Now my phones shows this message that "the system has been destroyed" and I can only go to fast boot mode.
I've tried flashing official MIUI 12.0.8 Global version but my phone does not accept any data. I have used miflash tool and XiaomiADBFastbooltool.jar to flash the firmware but both are failed. miflashtool kept showing the status of "Flashing" till 2 hours even I tired waiting and I pulled cable from phone. then I decided to try command prompt. but with every image flash command same error is received " Target didn't report max-download-size "
I'm attaching screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now my brain can't suggest any stupid thing next. kindly help me recover my phone.
Thanks in Advance

why dont you try a different recovery image? 3.4 for example
[RECOVERY][3.4.0-15][surya]TWRP Xiaomi Poco X3
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
if you cant flash it directly try just booting without flashing
`fastboot boot twrp,img`
then use TWRP to flash a custom ROM see if that works

I have seen solution for system destroyed from a telegram group here it is,
"System destroyed fix
1. Boot to fastboot mode(Hold power+ vol down)
2. Flash vbmeta (#vbmeta)
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
3. Flash recovery img
4. Reboot to recovery and flash rom"
Also I've attached vbmeta.img file here never tried it though, proceed at your own risk and best of luck getting your phone running again.

Also TWRP has been know to cause system destroyed issues so i would suggest orangefox recovery instead its better than TWRP in many ways.

Mak.b said:
I have seen solution for system destroyed from a telegram group here it is,
"System destroyed fix
1. Boot to fastboot mode(Hold power+ vol down)
2. Flash vbmeta (#vbmeta)
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
3. Flash recovery img
4. Reboot to recovery and flash rom"
Also I've attached vbmeta.img file here never tried it though, proceed at your own risk and best of luck getting your phone running again.
Click to expand...
Click to collapse
My Poco x3's System Destroyed itself as it showed a glitch screen and turned off, So now I am trying to flash my phone but never unlocked my bootloader before so Mi flash tool showing can't flash as the bootloader is locked

[FIXED] Weird MSN error message - BRICKED MY DEVICE!

So I accidently bricked my device for the first time. I think it was TWRP flash on the boot or something, still trying to figure this.
RIGHT NOW. my OP8t is still bricked, after hours of trying everything I came here.
Currently my device is constantly on the "current boot/recovery image have been destroyed and can not boot."
MSN saying there is a problem but I can't find a solution to it.
I can only access EDL so MSN Download tool is my only way to fixing this issue.
Thanks in advance
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MystikalE said:
So I accidently bricked my device for the first time. I think it was TWRP flash on the boot or something, still trying to figure this.
RIGHT NOW. my OP8t is still bricked, after hours of trying everything I came here.
Currently my device is constantly on the "current boot/recovery image have been destroyed and can not boot."
MSN saying there is a problem but I can't find a solution to it.
I can only access EDL so MSN Download tool is my only way to fixing this issue.
Thanks in advance
View attachment 5721413
Click to expand...
Click to collapse
Try another MSM version.

Rootk1t said:
Try another MSM version.
Click to expand...
Click to collapse
I managed to fix the brick using this answer, thank you.

MystikalE said:
I managed to fix the brick using this answer, thank you.
Click to expand...
Click to collapse
Next time, if you break your boot again and get the "current boot/recovery image have been destroyed and can not boot." error.
Try to boot to bootloader
if you can, then fastboot flash boot, recovery, vbmeta, and vbmeta_system images of the ROM you are trying to flash. On vbmeta and vbmeta_system images, flash them like this. Copy and paste if needed.
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img && fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Once finished, try to boot to recovery using the volume key to select "Recovery" and power button to make it boot.
If you boot to recovery successfully, sideload the ROM using adb sideload command. If you need to format data for a clean flash, I like to do it before I sideload the ROM.
This should help you to avoid using MSM unless you can't get to your bootloader. You can also go back to OOS from a custom ROM using this method, instead of MSM