Database Info

[Q] If Wi-Fi Xoom is bricked, can (RSD) flashing the 3G SBF, then fastbooting work?

Damn, I can't fit the whole question in the subject.
Let's say someone hypothetically bricked their wifi Xoom. Can't connect with fastboot anymore. However, it does get picked up by RSD Lite.
If the Wi-Fi Xoom is bricked, can flashing the 3G SBF using RSD Lite be used JUST to enable fastboot? And if so, would just doing a "fastboot flash boot boot.img" and "fastboot flash system system.img" (with the right wi-fi files) be able to save it? And possibly the same with recovery.img?
I noticed that the boot.img and system.img files are the same size between the wifi version and the 3G/4G. Same with the recovery partition. That's why I ask.

If you can enable fastboot using RSD then I don't see why you wouldn't be able to unbrick it.
If I were you I would try it. I don't think you can brick anymore than what it already is
Sent from my Xoom using Tapatalk

Kas206 said:
If you can enable fastboot using RSD
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1037094
when i hold power and Volume up restart the xoom and hold power + volume down its show
failed to boot LNX 0x0004
Starting Fastboot protocol support
but the problem the computer not Recognize on the xoom . i installing drivers and still not Recognize
whats i do ?
i have Windows and Mac

try uninstalling your drivers and use this to reinstall
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.0.40_Driver_4.9.0.exe

A Question very important?
Xoom wifi is good or the xoom 3g? information about it,, I appreciate it

At this moment, I can only get the wifi version in Canada. I don't know if I would need it on 3G/4G.
Dinar, I assume you used to be able to connect? But not after the 0x0004 error? Can you get in RSD mode at all? When you are in Fastboot mode, does "fastboot devices" on your computer show a device?

What's wrong with that appears in the
Scourge1024 said:
Dinar, I assume you used to be able to connect? But not after the 0x0004 error? Can you get in RSD mode at all? When you are in Fastboot mode, does "fastboot devices" on your computer show a device?
Click to expand...
Click to collapse
no not show a device
when i connect a xoom in computer the computer never show the xoom
Scourge, what is the error message in your xoom?

It was something like LNX 0x0004 and the following message was about Fastboot or RSD mode 2. It changed depending on if I held the down button on reboot. I lost the ability to scroll through the boot options.
I couldn't get fastboot, adb or RSD Lite to see my Xoom in either mode.

Did you get RSDLite to flash the .sbf file? I tried that on my bricked device and I couldn't see anything happening on the screen of the xoom. I waited for about one or two minutes and stopped the process. What about the drivers? Are there different drivers for adb, fastboot and RSDLite? I have motohelper installed and it says all necessary drivers are installed. Can it be a driver issue? Thats something I haven't tried.

My Motohelper updated itself and I was still not connecting with my first Xoom. There are different drivers. Different ones become active depending on what mode you're in.
But I couldn't even see my Xoom so I declared it bricked as of April 14th at 3:47am. I seriously don't know the exact time.
When I use adb or fastboot from my Mac, I don't need drivers. It just works.

i have Mac and Windows same problem not show xoom
give me steps for the mac i want try

mine is just like yours says failed image LNX 0x0002
starting rsd mode 2
will cycle with the power and up button to the above. push the down button says it is in the fastboot protocol mode but computer doesn see it. cmd module says waiting on device. have current usb drivers. anybody out there can repair it. moto wants an arm and a leg for a repair because it was fastboot oem unlocked and voided warranty

Yeah, if nothing can see it... What exactly does Motorola want to charge to fix it? Can't you return it to where you bought and get an exchange? I'd only feel okay with that if you bought at a big store though and not a mom and pop sorta shop.

I dont know if this will help, but I noticed that in your first post your commands may not be complete:
fastboot flash boot boot.img
fastboot flash system system.img
Your are missing the words in red above. I may be wrong and you dont need them, but Im sure you do. At least all I got was a bunch of command options scroll in my command prompt without the entire command.
I thought I had a bricked xoom after messing around with the frameworks-res.apk through "root explorer" app. I flashed the boot.img like crazy, but it was my frameworks that I had messed with last before the locked boot sequence. I found an image on the boards for the 3g system.img and I was back in business.

cvela said:
I dont know if this will help, but I noticed that in your first post your commands may not be complete:
fastboot flash boot boot.img
fastboot flash system system.img
Your are missing the words in red above. I may be wrong and you dont need them, but Im sure you do. At least all I got was a bunch of command options scroll in my command prompt without the entire command.
I thought I had a bricked xoom after messing around with the frameworks-res.apk through "root explorer" app. I flashed the boot.img like crazy, but it was my frameworks that I had messed with last before the locked boot sequence. I found an image on the boards for the 3g system.img and I was back in business.
Click to expand...
Click to collapse
I did the same. Only thing is after I had WiFi showing "Error" under it and it wouldn't start. Had to insmod the bcm4329.ko and I was back in business.

Scourge1024 said:
Yeah, if nothing can see it... What exactly does Motorola want to charge to fix it? Can't you return it to where you bought and get an exchange? I'd only feel okay with that if you bought at a big store though and not a mom and pop sorta shop.
Click to expand...
Click to collapse
i sent it back to moto

cvela said:
I dont know if this will help, but I noticed that in your first post your commands may not be complete:
fastboot flash boot boot.img
fastboot flash system system.img
Your are missing the words in red above. I may be wrong and you dont need them, but Im sure you do. At least all I got was a bunch of command options scroll in my command prompt without the entire command.
I thought I had a bricked xoom after messing around with the frameworks-res.apk through "root explorer" app. I flashed the boot.img like crazy, but it was my frameworks that I had messed with last before the locked boot sequence. I found an image on the boards for the 3g system.img and I was back in business.
Click to expand...
Click to collapse
You are correct. I'll fix my first post!

I'm getting all the same side effects here from attempting to re-lock the wi/fi xoom. Im debating on what to do here.

Oohh... Relocking is not good... If the images aren't exact factory ones, that's a sure brick. No point in relocating the Wi-Fi version. At least not right now.
If RSD Lite and Fastboot can't see it, look for your receipt...

haa yeah. Thats too bad that I'm just a fewww days over my 14 day store warranty and didnt buy the insurance. I sent in a repair order online where i ship it back to them.....dont know if illl ever get anything back though ha

[Q] Bricked in RSD Mode 2 and PC cannot detect XOOM - help

My XOOM is bricked and show RSD Mode 2 when power on, I can go into the fastboot mode by press VOL UP + Power button, and plan to do fastboot process to restore the system.
However, my problem is the Computer cannot detect XOOM, when I input "fastboot oem unlock", then the command stopped at a "Waiting for device" reply, so I cannot go to next step.
I have installed all of the needed software I see in this forum. Moto USB driver, Android SDK, Java, fastboot.
I have tried the RSDlite 5.0 but with the same reason, the RSDlite cannot detect device so it cannot work out.
anyone with the same problem and how to solve it? Do I need to send back it to Motorola for restore?
Thanks a lot for your help, It is too bad to stay with a bricked XOOM.

Xoom stuck in RSD mode 2
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help

Unbrick RSD Mode 2
I don't know what version xoom you are using, or under what circumstances you bricked your xoom under, but I managed to get mine (3g, USA) out of RSD 2 this way after it wouldn't boot coming out of a botched automated unroot/relock procedure. You may want to try this to get back to stock and working again, and then redo all the rooting and tweaks. I am going to go on the notion that you use windows (I use windows 7 64bit, but the steps should be the same or similar for other versions), have android sdk installed, and know what fastboot is.
... but first a few disclaimers!
1) If everything is fine now, disregard this reply!
2) I am in no way an expert in unbricking xooms, this is just how I figured it out for my situation.
3) Again, this is how I unbricked MY xoom, it may or may not work for you. If something here doesn't work for you, I really can't help.
4) I am not as big of a douche bag as I sound like in the last couple of disclaimers. If you are stuck and there is something I forgot to mention, I'll try to help.
4) You are probably having the same problem as someone else. As much as I hate to say it... GOOGLE IT! Just make sure you have all the error codes and include how you bricked your device. Horrible example: " R2D2 mode after I tried to turn my xoom into an autonomous killing machine by feeding my device crepes error code xx42" Bad example, yet it's very (odd) specific.
5) Don't be offended if I go into details that seem way below you. Someone else may need to read this, and may not understand everything you or I do. I try to break everything down as much as I can. Also, if I didn't go far enough into detail, let me know.
6) I inserted two 4's to see if you are really taking the time to read the entire post so the first 4 may not be true!
7) Once you get fastboot working, and the bootloader unlocked, the brick may be undone. I have you get the stock images just in case. Following the last part of the post will wipe your data.
Now back to our regularly scheduled programming...
1) Download the correct stock system software (wifi/3g) from motodev.
motorola.com/products/software/?utm_campaign=xoomsoftware&utm_medium=motorolacom&utm_source=supportforums&utm_term=unlockboard&pubid=987654
You have to register on the site. I would attach the files, but I agreed to a nice end user agreement saying I will not redistribute them. Also, I can't post links yet since I am still new so the beginning of the url is missing. There are posts in the xoom development forum that link to the file.
2) Unzip the contents to the folder where fastboot is located. Usually located in C:/program files/android/android-sdk/tools, or C:/program files (x86)/android/android-sdk/tools if you use a 64bit version of windows.
3) Power on the xoom and get into fastboot by holding the volume down button as soon the moto logo shows. I noticed it took a little while longer than usual for fastboot to show up. I noticed in the original post that the user said Volume up + Power. That is how you hard reboot... or do a dragon punch...I forget.
4) Once the device shows fastboot is running, Open a command prompt ( start, all programs, accessories, command prompt, or type cmd in the search bar ). Next type/copy these commands minus any comments marked by "<---". Note that every new line is a new command:
ON THE PC:
cd c:/program files/android/android-sdk/tools <---May be different depending upon what version of windows you are using. Replace 'programs files' with 'program files (x64)' if using 64 bit windows. If all else fails, type cd then copy one of the paths from step 2.
fastboot oem unlock <---This MAY solve your problem right here
should say check your device for instruction. On the xoom, hit volume down, then volume up, voulme down again, and volume up again to confirm the unlock.
When I did that my xoom rebooted, and I was back in business; however, if the unlock worked and you are still not able to boot, let's get back to stock. Get the xoom back into fastboot again by holding the volume down button while it starts.
ON THE PC:
You should still be in the same command prompt from earlier.
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot oem lock
This will wipe your xoom completely, but your nice shiny paperweight should be less paperweight like. I do the relock for good measure just because I think I left it unlocked, then I received an OTA update, and got good RSD Mode 2 again for some reason. If you want, try it without the fastboot oem lock command in case you want to get right back into rooting, flashing recoveries, etc... Well, hope all this helped. Again if clarification is needed, let me know and I will try to help. Hope this works. Take it easy!

zanzebar said:
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Click to expand...
Click to collapse
I have the same issue. Looks like I now own a brick!

zanzebar said:
I'm having the same issue. I'm at the boot screen with the Moto symbol and I have an error in the top right that says "Failed image SOS 0x0002" and below that "Starting RSD mode 2". My computer does not see my xoom. I've tried other links to this problem but they are not the same. They all mention RSD mode 3. Damn my stupidity . Someone please help
Click to expand...
Click to collapse
1) Turn the xoom on and leave it plugged into USB.
2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\
*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked
it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.

This doesn't work!
i have two motorola xoom, one of them have the failed image sos 0x0002 starting rs mode 2.
When i plug in the bricked motorola xoom nothing respons in the computer. i have the fastboot on with the waiting for device activated with fastboot oem unlock and RSD Lite v4.9 or 5.0 doesn't detect it too..
What can we do? i'm from spain and i bought the tablet in new york. Can i send it to the garanty?

The only way to do this is as follows:
Download rsdlite 4.9 or earlier only and install it on your computer.
Downlaod the latest moto drivers and install them.
Search for and download the stock SBF file for your Xoom wifi or 3g.
Get your Xoom to the rsd mode 2 screen and plug it in your computer
Use rsdlite to push the SBF file to the Xoom.
It will probably say it failed after a long wait. Its OK. Just restart your Xoom and your back to factory.
Good luck

csseale said:
The only way to do this is as follows:
Download rsdlite 4.9 or earlier only and install it on your computer.
Downlaod the latest moto drivers and install them.
Search for and download the stock SBF file for your Xoom wifi or 3g.
Get your Xoom to the rsd mode 2 screen and plug it in your computer
Use rsdlite to push the SBF file to the Xoom.
It will probably say it failed after a long wait. Its OK. Just restart your Xoom and your back to factory.
Good luck
Click to expand...
Click to collapse
i believe there is no SBF file for wifi xoom right now.

So I haven't had a chance to try anything you all have said since I've been at work all night. I have to agree with the last post though. I have looked everywhere and cannot find the.sbf I hope it leaks soon though so I dont have to deal with the shame of sending it to moto.

I still can't get the xoom to receive commands. I need that .sbf. I'll definitely be checking every minute for the wifi version leak.

The above means does not work.
I end up with a RSD re-enumaration failed error.

I'm on wifi xoom and can make it into "Starting Fastboot protocol support" but when i attempt to flash any of the images posted above or do a fastboot oem unlock I simply get <waiting for device> and nothing responds. Help?

Your Xoom is completely Bricked
At this point there is nothing you can do. You can A. wait patiently for .SBF for wifi only xoom or B. explain to motorola what happened and if it is under warranty they will replace or repair your xoom in 1 week.

Mayday
I am having the same problem, will someone be kind enough to find get the sbf out... aint android open source?

BlueEditionE6 said:
I am having the same problem, will someone be kind enough to find get the sbf out... aint android open source?
Click to expand...
Click to collapse
Android is open source but google is not releasing the source code for honeycomb yet.not exactly the same thing. You might be ****ed...

rockhumper said:
Android is open source but google is not releasing the source code for honeycomb yet.not exactly the same thing. You might be ****ed...
Click to expand...
Click to collapse
As long as you didn't reformat your internal sdcard you're probably not really bricked. It's not impossible but is really hard to brick the Xoom. I would suggest you go to the IRC #[email protected] freenode and see if any of those guys can help you. If anyone can, they can.
Good luck!

[Q] Can't unbrick. Tried nigh everything.

Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=

If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!

Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
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
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
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
As Always If This Was Helpful Hit the Thanks!

Yeah, what Mjamocha said...

okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.

okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?

Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.

slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.

Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.

slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.

I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.

slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).

Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?

slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?

How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.

slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?

I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?

I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium

I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?

cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium

[Q] Atrix 2 won't boot past "M" Motorola logo

Hey guys,
Forgive me for being frantic and (probably) not taking the steps needed to research this issue, or not taking the time to do so, but I'm sure you can all presumably imagine -if you've not been in this situation before- that it SUCKS not having a phone in this day in age...
My problem: Atrix 2 (Rooted + CWM Recovery) now won't boot passed the "M" Motorola logo upon start up. It won't even allow me to access the factory Android Recovery by holding down Volume Up, Volume Down, and Power. I think I inadvertently bricked the phone? (Hope not!)
Further, the "M" Motorola logo is skewed in appearance, like its not even loading correctly. I'm not sure what to do. This is my first time rooting and getting experienced with custom ROMS.
Anyone able to help this helpless sap?
Thanks is advance to your replies...

Step 1 is where you tell what you did to get into the state you are in. You wouldn't believe how far it goes toward fixing something if you know how it got broken.
Sent from my MB865 using XDA

If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.

KEB64 said:
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
Click to expand...
Click to collapse
Agreed pull the battery. If you run out of juice you'll be in some serious trouble.
Did you try to flash the fkz? Unless you have CWM on Boot it's the only way you can get your phone working.

Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.

pull the battery, put it back in, and hold vol up and down while turning on. choose ap fastboot at the menu. go to the thread in my signature and under the mirrors there is also a download of the return to stock script. run it while in fastboot and plugged in with usb. DO NOT pull the chord until it is done. when it is you should be good.

Apex_Strider said:
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
Click to expand...
Click to collapse
Yeah wiping the system partition is a no no unless you flash another rom afterwards. Do like ikrasner says and you should be back to normal.
Sent from my MB865 using XDA

Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!

can you read chinese?
Maybe I can solve your question,but poor of my english.
and what is your phone type?
at&t hktw or china ?
Sent from my ME865 using xda premium

Apex_Strider said:
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
Click to expand...
Click to collapse
It should ask you to install 2.3.6. Just go into setting>about phone>check for updates. Or you could go and install one of the roms that are based on 2.3.6 such as Lithium Sonya or SCv5.

Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.

Apex_Strider said:
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Click to expand...
Click to collapse
do not flash this. unzip it on your computer, choose to boot into fast boot in the same place you chose recovery, then run the .bat file that was in the zip.
Sent from my MB865 using XDA

What that file does is reflash your system.img, basically restoring your phone to factory default. And just as a sidenote you cannot flash things with the standard Android Recovery. You need CWM.

did you try apboot mode and ise fastboot to flash system.img ?
Sent from my ME865 using xda premium

Still not working... not sure how to flash from fastboot. I don't have any options to run a file from there, or at least not sure ow to go about that.

Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium

dickluo said:
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!

Apex_Strider said:
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Click to expand...
Click to collapse
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.

jfrank1485 said:
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
Click to expand...
Click to collapse
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!

Apex_Strider said:
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Click to expand...
Click to collapse
I'm glad it work , keep it at hand before doing anything to your phone, it really helps

Failed root

Hey,
Tried to root my phone and things got messy.
I'm at a point where when I try to access the bootloader I get the "No command" screen, which I can bypass with the Power+Up keys and reach the "Android Recovery" screen.
I used "Wipe Data/Factory Reset" which didn't help much.
I can't do much more than that because Windows doesn't recognize my device and so I can't apply anything through ADB.
I tried to install the drivers again, but still nothing. My phone doesn't appear on the Device Manager.
Windows does make a sound of connected USB when I enter bootloader, but soon as it hits the "No Command" screen I hear the sound of a disconnected USB device.
Any idea how to make Windows recognize the device again so I could try to install things back with ADB?
Thanks!

OK, managed to solve this part after some reboots.
I'm now failing to ADB the stock image.
The phone says on top of "Andoird Recovery" that it's 7.1.2/NZH54D.
That's the stock image I've downloaded and when I try to ADB it I get on the windows terminal
"cannot read 'sailfish-nzh54d-factory-127f0583.zip'".
How do I move on from this?

OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.

I would start over from scratch. This guide is really good, it's for Pixel XL, but should be interchangable for Pixel 1 (non-XL), just be careful of the model specific files (salefish vs. marlin)
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591

TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
Can't you acces bootloader with "adb reboot bootloader"?
Also make sure u switched on usb debugging in developer options.
Sent from my Google Pixel using XDA Labs

If you get to the screen where you can choose to enter recovery, that is the bootloader. The no command thing is something you always get when you choose to boot to recovery. When on the screen before the no command thing, plug it into your PC. If the PC recognizes it, use fastboot to access it. "Fastboot devices" will show your phone. Adb devices doesn't work there. Bottom line is, it sounds to me you're getting to the bootloader. Just not realizing it.

TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.

Milly7 said:
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.
Click to expand...
Click to collapse
Yup. I think I'm good now. Gave up on the ROM thing. Too much headache to maintain it. Sticking to stock. Imperfect, but less headaches.
I wanted to root my device mostly for Titanium backup.
The rest isn't that important to me.
Thanks for the help!