Database Info

[Q] Pls help me recover bricked my xoom

dear all,
I have a MZ600 Xoom with original state (not yet unlocked or rooted)
Yesterday, it informed me upgrading new software (OTA). After rebooting, it asked me for a password to enter android (not the lock screen password, since I have not set any). I searched google for this case but didn't find any problem like that. So I decided to boot into Recovery Mode and did factory reset, but strangely the xoom would ask a password again.
Then I booted it into fastboot mode and do some command with HRI39 img. All command failed (except for flash userdata.img) Here is the result:
C:\Android\android-sdk\tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 0.571s]
writing 'boot'...
FAILED (remote: (19000008))
finished. total time: 1.533s
C:\Android\android-sdk\tools>fastboot flash system system.img
< waiting for device >
sending 'system' (262144 KB)...
OKAY [ 17.376s]
writing 'system'...
FAILED (remote: (19000008))
finished. total time: 18.540s
the image
{
"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"
}
When I used Rsd Lite 5.0 with sbf HRI39 to flash the xoom. But the process failed, too
Any help would be most appreciated.
Thank in advance

Longshot here, but the SBF always says it fails, even when it works. Did you verify it actually failed?

I've verified already.
The HRI39 Sbf zip comes with two files. If i flash the smaller file, it will be ok. But when I flash the larger one, RSD Lite stuck at "...switching device to pass through..." and failed. Now my xoom could enter to RSD, Recovery, Fastboot mode and cannot boot into Android any more.
I try RSD Lite on WinXP 32bit, also Win7 Ult 32bit, all failed
I attach the log from RSD Lite here.
thank you

You could try downloading clockworkmod and installing it by doing:
fastboot flash boot recovery.img
This will get your device to boot to cwm. From there i have no idea what you can do. You could maybe download the stock images, create an MD5 for them, and try to nandroid restore them.

Have you tried RSD Life 4.9 yet? There's an SBF file for Verizon XOOMs floating around you can flash from RSD Life.

Strangely, I could not flash anything with fastboot except for userdata.img. All failed like the image i attached. So, I tried to flash the cwm recovery, but got failure again.
With RSD Lite 4.9 (and also 5.0), I flash HRI39 sbf from the topic http://forum.xda-developers.com/showthread.php?p=13077237 and got stuck at 2% of process.
Do I have to change some parameters in Rsd lite?

Userdata isn't vital though. Mostly Boot and
I see in your pics the Xoom has already been unlocked. Maybe try unlocking it again? Just do not lock it. It'll probably get bricked even worse.
I heard that setting Config > DeviceID options to First come first serve helped someone. Never tried myself.

thank you
in the pic, when I select accepted choice for unlocking, it said "Error: failed to format UDA", and if I do oem lock, i aslo said failed.
And how to set DeviceID for flashing the xoom?

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

Downgrade CM13 to stock failed

Hi,
i tried to downgrade CM 13 to the Stock Android 5.0.2 and relock it (I know that Motorla has the unlock indicator, but this doesn't matter here).
So I tried the following steps as descripted in a lot of posts, but every command failed:
Code:
fastboot oem lock begin //success
fastboot flash partition gpt.bin // Preflash validation failed ->version downgraded for primary gpt
fastboot flash motoboot motoboot.img // Preflash validation for tz -> version downgraded for tz
fastboot flash boot boot.img // Preflash validation failed -> version downgraded for boot
So how can I solve the problem? I think it has something to do with downgrading

You may need to use mfastboot.
However, if you have updated your Bootloader; you may no longer be able to flash a firmware image older than Android 5.1. If that turns out to be the case flash the latest 5.1 Factory Firmware Image for your model using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

Unfortunately it makes no difference, same errors.
I already flashed this stock image some time before and it works. And the bootloader is on 41.18.
{
"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"
}

Try with the firmware files in the same folder as mfastboot.exe.
mfastboot flash partition gpt.bin​

Nope, same error

You could simply skip that command. And there is always the option to flash the Stock ROM via TWRP.
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection​[ROM][FALCON][6.0][STOCK] Identity Crisis 6​

The problem is that all commands failes (including boot.IMG, which is obviously needed). TWRP would be possible, but then I can't relock it.

Waishon said:
The problem is that all commands failes (including boot.IMG, which is obviously needed). TWRP would be possible, but then I can't relock it.
Click to expand...
Click to collapse
Flash ROM via TWRP, then relock via fastboot. I would expect it to work.

Does relocking work with a custom recovery? Interesting

Waishon said:
Does relocking work with a custom recovery? Interesting
Click to expand...
Click to collapse
I'm not aware of any relationship between recovery and relocking - but I have no personal experience. If you did need to flash the Stock Recovery, this can be done via TWRP.

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