Flashed Build HWI69 for US Retail on a Canadian wifi MZ604 xoom..tired of
waiting for 3.1 update.
adb reboot bootloader
fastboot oem unlock
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
It is stuck on Starting RSD mode 2.
I can not get it to fastboot protocol...device does not turn off.
Any solutions?
Fastboot OEM lock is where you went wrong. Anyway see this thread.
OK I did this procedure yesterday but did not relock (I know it says to on the moto site but the guide I read said not to).
Anyway, pressing power and vol up will force a reboot. Unsure what will happen when it boots back up though...!
You should be fine. Only trying to relock will cause this error.
To get back to fastboot after a bad lock do this.
Power button and volume up, this will reboot the device.
As soon as the screen turns back on holds down power and volume down. In about 60 seconds your device should go to fastboot. Do not let go until it gets there.
Sent From My Evo
Thanks for the reply . It now says Failed to boot LNX 0X0004
Starting Fastboot protocol support
However it will not connect to xoom.
<wait for device> when issue fastboot command.
What the hell is going on?
you need to read this thread
http://forum.xda-developers.com/showthread.php?t=1108518
The exact thread I linked to...(-__-)'
I followed instruction from motorla dev support site.
"h**p://developer.motorola.com/products/software/?pubid=987654"
It uses command "fastboot oem lock"! So why did locking brick the device?
here it is:
Device Software Images
Select the appropriate device software image to download and re-lock your device. If you need to find your build number on your Motorola device go to Settings and About Phone or About Tablet.
The commands to flash and re-lock your device are as follows:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata
The Moto instructions are for locking the device back to it's own image. You are not using your device's own image. Every guide I've seen on here tells you not to relock, regardless of what Moto say. Believe the devs.
Thanxs
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.
tfx1 said:
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.
Click to expand...
Click to collapse
Try making or obtaining a factory cable which its different from an OTG cable. Start with the two links below. This might save the day.
http://forum.xda-developers.com/showthread.php?t=1077414
http://forum.xda-developers.com/showthread.php?t=1108518
I used Recovery-Tools to flash TECNO-P5_130916__recovery_140106-193223.img onto my phone. The process completed and I was prompted to boot into recovery. The reboot did not complete.
I can get into the boot menu (Volume Up + Power), but when I select Recovery mode or Normal mode the phone gets into a boot loop. Fastboot mode woks and I can connect from Windows 7.
The problem in Fastboot is that I cannot flash a ROM since the bootloader is locked (I get the error "Security deny - Err:0x2017").
Is there a tool that can either unlock the bootloader or reset the phone to factory settings so it can boot normally?
I already tried fastboot oem unlock and it just hangs at "..." No "fastboot oem ...." commands work
fastboot devices shows "mt6572v1_phone fastboot"
HI
I was flashing the GPe image on my XT1033 and while flashing the boot.img and logo.bin i got an error - out of memory , but rest of the parts like system.img etc flashed properly and now my phone won't boot giving me the error "failed to validate boot image'.
I am stuck at the bootloader screen and now neither can i flash some other image since my phone isn't being recognized anymore with cmd showing the message 'waiting for device'
Can someone please provide a solution?
Hello.
I faced the same problems when installing the 4.4.4 br firmware and trying to revert to my original firmware.
This happens because you have a locked bootloader and/or maybe you flashed a wrong boot.bin and you can't reflash boot.img because the bootloader is locked!
What I did is unlock the bootloader and all my problems vanished.. -_- reflash all the files using mfastboot, if it gives you errors on gpt.bin and motoboot.img dont worry and go on with the rest.
Oh, and one strange thing that I luckily figured out, is that to get the device recognized by the PC in the fastboot mode you got to enter fastboot MANUALLY. THat is, press volume down 3 seconds and then power on.
It's gotta say: Fastboot reason: Volume-down key pressed.
If you try to boot and it enters fast boot and gives you the error, for some reason doesn't recognize.
I have mate 7 TL10, while i was trying to update it got bricked, and stuck on "Fastboot mode& Rescue mode", so i unlocked the boatloader and tried to flash a recovery image but nothing happend . After the command " Fastboot reboot", the phone to restart back to "Fastboot mode& Rescue mode"!!!!
Any Suggestion?
Try flash twrp
Send frome globe
Hello. So I've restored my old XT1032 to 5.1 stock and locked the bootloader again but I'm still getting the unlocked bootloader warning message when booting. I've tried to reflash the logo.bin but that didn't work.
Any ideas?
Thanks
flash the logo.bin from here:
http://forum.xda-developers.com/showthread.php?t=2548530
and then it will go away. Motorola did this beacuse the bootloader was unlocked before and relock it doesn't bring back the original boot logo. In bootloader mode you can see that you have now STATUS CODE: 2 instead of 0 when never was unlocked.