Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
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
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
On the real though, if you can get to Fastboot (or even the Moto "Android Recovery" state), you're not THAT bricked you've got to relock and go back to out-of-box; just keep a known-good boot.img around somewhere.
You just saved my life!
Thanks for sharing OP.
I take it this method is the same for 3.1?
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Lcsglvr said:
I tried reverting back to stock using the "one click" root/unroot tool that was the first to come out for the Xoom.
Anyway, I tried the unroot process and everything was going fine, until something occurred. Now, it tries to boot up and says at the Moto Dual Core Technology screen, "Failed to boot LNX 0x0004 // Starting RSD mode 2".
Can someone help
Click to expand...
Click to collapse
Can anyone help!
Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
same here, anyone help ((
Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Honestly, I almost went through all of this last night when my WIFI Xoom got stuck in a boot loop.
However, I noticed that when my recovery went to flash the new 3.1 file, I felt like it didn't take as long as it should have. The file was the right size and all and it even said that everything installed successfully, but it just kept boot looping regardless of trying over and over. So I went ahead and re-downloaded the 3.1 file and repeated the steps to flash it and everything worked.
So, before you spend a whole lot of time restoring your Xoom, simply re-download the files and try it one more time. It worked for me.
rebill said:
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Click to expand...
Click to collapse
Thanks! Finally have some hope to recovering. I'll post steps I took later once I get this damn thing fixed.
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Lcsglvr said:
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Click to expand...
Click to collapse
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Hmm honesty. I'll give it a shot.
Sent from my ADR6300 using XDA App
Is the final OEM lock necessary? It's quite a pain as your userdata gets wiped if you unlock it...
I was stuck on bootloop, with unrecognised device, through adb was able to get back into clockwork recovery somehow at first boot, think twice down volume? Could be wrong.
I was able tto rreflash zip 3.1 over thet top again.
sry if this is different and unhelpful, bu imagine things are pretty desperate if you are considering returning the device
zerin said:
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Click to expand...
Click to collapse
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
jbartcaps said:
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
Click to expand...
Click to collapse
You were likely in RSD 3, which is recognized by the computer. RSD 2 means adb and fastboot cannot see the device at all, so no flashing images is possible.
There's several states that all look very similar. Because some success was had with one doesn't mean it works for all. Motorola recognizes and is telling users that, in this state, the device needs to be sent back to them.
Can someone help us wifi xoom. Im stuck on the motorola screen and have a lil experience. I can fast boot reboot/fastboot device and it work but cant get the files from the hwi69 to fastboot on to it. I think im entering the commands wrong. Any advice would be appreciated
TheRedDroid said:
Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
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
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
Click to expand...
Click to collapse
Very good info to get into fastboot protocol:
Much thanks for the info. Worked like a champ. On an updated 3.2.1 XOOM I did an unlock, re-locked the wrong way, soft bricked, unbricked back to locked state. Finally followed your steps applied stock files and XOOM is re-locked and stock rocking back at 3.01. I needed to do all this to make sure I could get it back to stock in case it goes back to BB in 2 weeks. I was lucky enough to find one at a BB just not sure if I'll keep it. I plan on trying out some roms plus I heard Motorola is planning on doing an ICS push to the XOOM. ICS is very nice. It runs great on my unlocked Verizon G-Nex.. Again Thanks..
This post not only saved my half-bricked non-rooted Xoom, but also let me flash it from the Singapore firmware (bought if from Amazon, don't ask lol) to the regular USA firmware so that I can properly root it!
Thank you so very much!!
Hello
I have a XT920 with root and this night I received an update for my XT920. After update my phone becames in loop while booting. I found a lot of threads about this problem because the phone was rooted. And to solve this problem the solution was flash another rom to the phone. I started the procedure below:
Fastboot flash boot boot-sign.img
Fastboot flash system system-sign.img
Fastboot flash recovery recovery-sign.img
Fastboot flash flex flex.img
When I executed the second command, I noticed that the first activity was erasing the partition. I wait about 20 minutes in this activity, but it doesn't finish. So I disconect the phone from the USB cable.
Now when I enter in the boot menu, no action works and the phone reboot. So I can't enter in recovery mode, fastboot mode and can't do a factory reset on the phone. All other the procedures (with fastboot, RSD NetConnected, RSD Lite) that I find in the forum needs the fastboot mode to recover thhe phone and flash the ROM again.
There is another way to save my phone? Can somebody help me?
Tks!
ps: sorry for my poor english.
Same Problem
I have the same problem,
Hi guys,
My Nexus 5 (hammerhead D821 (E) ) died on me two day ago. It's showing the google logo without any progress and then restarts itself.
I can boot into bootloader from the device. If I issue <adb devices> command it won't show any devices however when using <fastboot devices> it finds the device's ID.
My devices was running the latest official marshmallow 6 when it happened (it was working just fine for more than a week).
Currently my device is in <lock state - Locked> I tried issuing <fastboot oem unlock> command without any success. The phone would run the command shows the <lock state - Unlocked> then it shows <erasing...> (I left the phone for 10Hours, no change) .
It won't finish nor respond unless I reboot the device into bootloader again.
I'm using the google USB drivers and universal drivers for my phone, they seem to be working, showing as android bootloader interface in my system (win7). I can't boot into recovery mod from the bootloader it will just show a black screen until I restart the phone.
I'm suspecting my eMMC is dead, my knowledge with adb and fastboot is limited, I would appreciate to hear your feedback regarding the issue.
Is there are way I can run some low level diagnostics commands to understand if its dead?
Can I revive my phone in anyway as I can't flash anything at the moment while the device is in <lock state - Locked> .
Waiting to hear from the experts =) thanks in advance guys!
Alex
Fish7 said:
Hi guys,
My Nexus 5 (hammerhead D821 (E) ) died on me two day ago. It's showing the google logo without any progress and then restarts itself.
I can boot into bootloader from the device. If I issue <adb devices> command it won't show any devices however when using <fastboot devices> it finds the device's ID.
My devices was running the latest official marshmallow 6 when it happened (it was working just fine for more than a week).
Currently my device is in <lock state - Locked> I tried issuing <fastboot oem unlock> command without any success. The phone would run the command shows the <lock state - Unlocked> then it shows <erasing...> (I left the phone for 10Hours, no change) .
It won't finish nor respond unless I reboot the device into bootloader again.
I'm using the google USB drivers and universal drivers for my phone, they seem to be working, showing as android bootloader interface in my system (win7). I can't boot into recovery mod from the bootloader it will just show a black screen until I restart the phone.
I'm suspecting my eMMC is dead, my knowledge with adb and fastboot is limited, I would appreciate to hear your feedback regarding the issue.
Is there are way I can run some low level diagnostics commands to understand if its dead?
Can I revive my phone in anyway as I can't flash anything at the moment while the device is in <lock state - Locked> .
Waiting to hear from the experts =) thanks in advance guys!
Alex
Click to expand...
Click to collapse
Sounds like it (eMMC) died.
beekay201 said:
Sounds like it (eMMC) died.
Click to expand...
Click to collapse
Thanks for the feedback beekay201. I hope someone will know if this can be confirmed with some sort of test etc...
I think my emmc is dead too because my n5 does the same thing in fastboot - unlocked, locked, unlocked. Also, I can't mount partitions or perform a factory wipe in stock recovery. Also tried flashing TWRP right after unlocking the bootloader. Fastboot says recovery was successfully flash but, when I immediately boot to recovery, I still have stock recovery.
Time for me to find a n5 with a smashed screen
audit13 said:
I think my emmc is dead too because my n5 does the same thing in fastboot - unlocked, locked, unlocked. Also, I can't mount partitions or perform a factory wipe in stock recovery. Also tried flashing TWRP right after unlocking the bootloader. Fastboot says recovery was successfully flash but, when I immediately boot to recovery, I still have stock recovery.
Time for me to find a n5 with a smashed screen
Click to expand...
Click to collapse
Hi audit13,
My Nexus is locked. I can't unlock it at all. It's stuck in "erasing" if I run <fastboot oem unlock> command.
Hello, I am wondering what can I do with my phone, when I did the system upgrade from my phone, it was downloading, then for the install it showed up 2 options install later and install now, I press install now and the phone was rebooted to recovery mode, but then this message appeared:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2016-09-25 16:26:59)
eMMC Info: Size 32GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
I really dont know what to do because whenever I turn it on, it stays like 10 seconds on and then power off.
please help, Im not much familiarized with this issues.
Thanks a lot guys any response could be helpful
PD: hopefully I didn't mess it up.
I tried to factory reset myt MOTO ONE POWER , when it restarted , it showed "your device is corrupted and cannot be trusted and will not boot "
after 2-3 restarts , it goes to fastboot mode , showing
AP fastboot Mode (secured )
SSM: abl csv roll back 0.128
NO bootable S/B slot
Failed to boot LInux, falling back to fast boot
my bootloader is not unlocked , most of the fastboot command s not working
Sorry for bumping an old thread. I have the same issue. Did you figure it out?