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?

[Q] Moto G XT1032 will not boot after 5.0.1 OTA was ADB Sideloaded

Hi All
I have an XT1032 that I converted to GPE edition successfully but after the 5.0.1 OTA it is no longer booting past the google logo.
Steps Taken :
- Converted Moto G (XT1032) 8GB to the GPE edition
- Booted and logged in, updated some apps
- Checked for system updates and installed OTA Update 4.4.4
- Rebooted again successfully and update went through
- Ran ADB Sideload for the 5.0.1 GPE OTA. It went through without any errors. I saw "OK" and "Success"
- Rebooted phone and it hung at Google logo (waited 30 minutes)
Now it just will not boot. It stays on the Google 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 can still get into the bootloader and into recover so I tried to re-flash the 4.4.x boot images etc using fastboot but it now fails on the Partition and the Motoboot with "Preflash Validation Failed" I can fastboot everything else but not the gpt partition or the motoboot.
View attachment 3059188
View attachment 3059190
ADB sideload of the OTA also fails now, even though it was successful the first time.
View attachment 3059191
As per suggestions online, I have
- Verified the bootloader is unlocked (see recovery screenshot)
- Made sure the battery is fully charged
- Tried mfastboot
- Used different images
- Rebooted a few times and waited up to 30 minutes
- Factory reset, cleared cache and userdata etc
So this is really where I'm stuck. I'm not sure how to fix or get past the errors of "Preflash Validation Failed" for those two commands. I can reflash boot.img, recovery.img, and all the others successfully.
Any help is much appreciated.

I have this same problem with motoboot and partition, when I tried to downgrade from 4.4.4 to 4.4.2, but I can flash the system normally and my Moto G works perfect.

I was able to repeat the instructions here to boot successfully into 4.4.4.
Will probably try the 5.0.1 OTA upgrade again now that I know how to revert to 4.4.4
Edit / Update :
That worked. I am now on the OTA 5.0.1

marsisabar said:
I was able to repeat the instructions here to boot successfully into 4.4.4.
Will probably try the 5.0.1 OTA upgrade again now that I know how to revert to 4.4.4
Click to expand...
Click to collapse
Hey I have same problem, same scenario, which instruction did you follow to boot into 4.4.4 and also let me know if you were able to workout with 5.0.1 OTA.

Did you followed this thread? http://forum.xda-developers.com/moto-g/general/guide-convert-brazilian-firmware-gpe-5-t2969472

Ruturaj001 said:
Hey I have same problem, same scenario, which instruction did you follow to boot into 4.4.4 and also let me know if you were able to workout with 5.0.1 OTA.
Click to expand...
Click to collapse
This instruction set here
http://forum.xda-developers.com/moto...gpe-5-t2969472
My mistake was that I was using those instructions but still using the Android 4.4.2 images or 4.2. Once I re-downloaded 4.4.4 and used the scripts with those images, it worked.
Good luck!

aybarchu said:
Did you followed this thread? http://forum.xda-developers.com/moto-g/general/guide-convert-brazilian-firmware-gpe-5-t2969472
Click to expand...
Click to collapse
Yes! That is the one. I followed it the first few times incorrectly since I had many different Stock images. You have to use the 4.4.4 image that is provided.
You can find many images here
http://www.filefactory.com/folder/c6cdedc45a775d27
I used the 4.4.4 image found on page 4, linked here :
http://www.filefactory.com/file/5p1gt5e7hprf/GPE_4.4.4_XT1032_KTU84P.M003_CFC.xml.zip

followed this one easiest and works like charm and you will still have 5.0
http://forum.xda-developers.com/moto-g/general/fix-android-lollipop-ota-gpe-stuck-t2970842

I have the same problem than you marsisabar, but I have proper 4.4.4 image.
I can go back to 4.4.4 after 5.0.1 failed boot, but have problem with
Code:
fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.117s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.392s
I have fixed partition with gptfix.zip (http://forum.xda-developers.com/moto-g/general/fix-android-lollipop-ota-gpe-stuck-t2970842).
I received OTA and tried sideload. Sideload finish with success but phone is not booting. Any advice?

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

Why I got these, help!

I flash the factory image with the flash-all.bat, but I got these.
What shoule I do?
Code:
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.188s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
{
"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"
}

The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.

Ra6idr0y said:
The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.
Click to expand...
Click to collapse
if the bootloader is unlocked, the flash all command does not work ? If you are on a custom kernel, can't you just download the stock image then run the script then relock the bootloader ?

mikeprius said:
if the bootloader is unlocked, the flash all command does not work ? If you are on a custom kernel, can't you just download the stock image then run the script then relock the bootloader ?
Click to expand...
Click to collapse
The flash all command works fine on an unlocked bootloader. I've used it several times (I play around too much ) As for your second question, I haven't used a custom kernel but I have flashed Magisk which writes to the bootloader and I've never had a problem using the flash-all.bat file. Some people for some reason or another were able to use it (the flash all) for the December update but it would fail to write the bootloader for some reason or another. Some tried flashing the bootloader manually with fastboot and that would fail too. From what I've seen, the only way out for those with that problem was to flash the OTA. I don't know how many of them were using custom kernels so I can't really say if that's the problem or not. I can only tell you I flashed the December update using the flash all and had no problems at all.

Ra6idr0y said:
The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.
Click to expand...
Click to collapse
I have sloved this problem, I changed TYPE-C to TYPE-C cable to TYPE-C to TYPE-A cable and I flashed it.
I think it's google's cable's problem.

Question [CLOSED] FAILED (remote: 'Authenticate failed')

I'm using the stock ROM of p11. I want to unlock the bootloader to root.
If I follow the guide at https://zui.com/iunlock, the following error will occur.
fastboot flash unlock sn.img
{
"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 did OEM unlocking in Developer option and downloaded all required drivers. Please help me.

hyunm0913 said:
I'm using the stock ROM of p11. I want to unlock the bootloader to root.
If I follow the guide at https://zui.com/iunlock, the following error will occur.
Click to expand...
Click to collapse
Where did you get the sn.img? It probably does not match the serial number of your tablet.
Spoiler: In my case OK
FAILED (remote: 'Download is not allowed on locked devices') -- this is in fastbootd mode.
OKAY [ 0.000s] (bootloader) run fastboot oem unlock-go -- in bootloader mode.

f1tm0t said:
Where did you get the sn.img? It probably does not match the serial number of your tablet.
Spoiler: In my case OK
View attachment 5496961
FAILED (remote: 'Download is not allowed on locked devices') -- this is in fastbootd mode.
OKAY [ 0.000s] (bootloader) run fastboot oem unlock-go -- in bootloader mode.
Click to expand...
Click to collapse
Thank you very much!
However, even though I received sn.img by entering the serial number in the packaging box, bootloader, and settings properly, it still doesn't work.
Serial numbers are not recognized even in Lenovo support. Perhaps there is a problem with the serial number.

Look your SN on tablet's screen in bootloader mode, not on package box.
If you got tablet from China, try enter your SN in this page: https://newsupport.lenovo.com.cn

I don't know what the problem is. Isn't the serial number displayed by the bootloader and system a fake serial number?

Try other (newest) version platform-tools (adb-fastboot).
Try to get SN.img again.
Your tablet with global firmware? SN.img no needed, type fastboot flashing unlock

I think I should give up on this. No matter how hard I tried, I didn't know why there was a problem, and I thought again about whether rooting was necessary. Thank you for helping me.

I'm wondering where this problem came from. But let it be as you wish.
Happy New Year!

PS C:\Users\chen\Downloads\Compressed\platform-tools_r34.0.0-windows\platform-tools> .\fastboot.exe flash unlock .\sn.img
Sending 'unlock' (5 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed