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

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.

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.

Unlocking Bootloader

Is there any up to date and free way to get a Bootloader Unlock code for the Huawei Mate 10 lite RNE-L21?

Chaosdave34 said:
Is there any up to date and free way to get a Bootloader Unlock code for the Huawei Mate 10 lite RNE-L21?
Click to expand...
Click to collapse
Look here
https://forum.xda-developers.com/t/unlock-bootloader-for-free.4054619/post-84195325

What does this mean: Short testpoint and iron shield on the motherboard.
I know the test point is somewhere on the main board, bus what should I do with it. Sorry I'm German, so my English is not so good.

Chaosdave34 said:
What does this mean: Short testpoint and iron shield on the motherboard.
I know the test point is somewhere on the main board, bus what should I do with it. Sorry I'm German, so my English is not so good.
Click to expand...
Click to collapse
short test point to the ground , use tweezers, paper clips etc.
{
"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"
}

Chaosdave34 said:
What does this mean: Short testpoint and iron shield on the motherboard.
I know the test point is somewhere on the main board, bus what should I do with it. Sorry I'm German, so my English is not so good.
Click to expand...
Click to collapse

Any way to enter edl mode without openinv cove4?

Chaosdave34 said:
Any way to enter edl mode without openinv cove4?
Click to expand...
Click to collapse
No way on phones with Kirin SoC.
But you can get unlock code for 4euros . It's worth it.

Does this works with Android 8 and newest security patch (1. September 2020)?
Where to I get these?

Chaosdave34 said:
Does this works with Android 8 and newest security patch (1. September 2020)?
Where to I get these?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/root-for-huawei-mate-10-lite.4146535/post-83263929

Hisuize isnt offering th possibility anymore.

Can you help me find an download for firmware for my rne-l21 which is old enough, that dc unlocker works

UPDATE: I fixed the following problem by entering "Dwonload mode" with sound up+down, got the error failed to update device, hit reboot Button and got back to emui. Dow you have any working recovery for my device and the right commands?
I need help another time: I succsessfully unlocked bootloader with edl mode. Then I installed TWRP recovery. But im stuck on the recovery splash screen and every reboot brings me back to the frozen recovery splash screen:
I did the following things:
adb reboot bootloader
fastboot flash TWRP.img (canceled this command with CTRL+C, because i forgot recovery option)
fastboot flash recovery TWRP.img (got an Error, think, failed to get partition size, or something like that)
* downloader othe TWRP.img*
fastboot flash recovery_ramdisk
fastboot reboot
Now stuck on Splash Screen: "teamwin By KingofMezi @xda-developers"

deleted

deleted

Chaosdave34 said:
Now stuck on Splash Screen: "teamwin By KingofMezi @xda-developers"
Click to expand...
Click to collapse
Recommeded TWRP:
https://forum.xda-developers.com/t/unlocking-bootloader.3920127/post-84266739

Null

Thank your very much for the help you gave me. Just one little question:
fastboot flash recovery twrp.img
or
fastboot flash recovery_ramdisk twrp.img

I flashed the Oreo TWRP on recovery_ramdisik
(LOG:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24790 KB)...
OKAY [ 1.075s]
writing 'recovery_ramdisk'...
OKAY [ 0.121s]
finished. total time: 1.196s
)
And it hangs again on the splash screen

Chaosdave34 said:
And it hangs again on the splash screen
Click to expand...
Click to collapse
Okay,
in fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results please.

fastboot oem get-build-number:
"
(bootloader) :RNE-L21 8.0.0.360(C432)
"
fastboot oem get-product-model
"
(bootloader) RNE-L21
"
fastboot getvar vendorcountry
"
vendorcountry: hw/eu
"
fastboot oem oeminforead-CUSTOM_VERSION
"
FAILED (remote: Read oeminfo failed!)
"
fastboot oem oeminforead-SYSTEM_VERSION
"
(bootloader) :RNE-L21 8.0.0.360(C432)
"