Database Info

Bricked stuck on RSD mode 3

Hi everyone, so my father's tablet booted and bricked itself, it was working fine for about 2 months since last update. he says it froze on lock screen, he forced a reboot and then the problem happened
Problem:
Motorola xoom tablete MZ604 (wifi only) is stucked on Motorola Logo with "starting RSD mode 3" , if I press & hold " Volume Up & Power" it rebootss back into the same screen. If I press & hold "Volume up & power" then release and press Volume Down, it sticks at the Motorola Logo but without the "starting RSD Mode 3 ".
Already tried
Cant turn it off, get to fastboot or recovery options.
when displaying the Starting RSD mode 3, if I connect the tablet to my pc I hear the Dond dong and I can see the computer running the Motorola flash interface driver on the device manager BUT no adb devices are listed on command prompt or anything on Computer but C:..
I even tried bridgeing ( I believe that's the correct word in english) the micro usb cable so line 1 and 4 had the voltage, ( I saw this as a solution for having the "factory cable" ) but NO RESULT
all sort of combination of pressing volume and power buttons for 20 secs. no result
Background info
I was able to unlock it, root it , and I was running team eos wingray and the gpu OC and all that sweet stuff for several weeks my pc has the sdk tools and google usb driver package all updated.
Im desperate please HELP

mate, i literally just had this problem, right now! Was trying to do some fastboot stuff and something went wrong (obviously because otherwise i wouldn't be here). The way i solved it was:
Hard reboot it (power and volume up)
Then as the splash screen comes (even a bit before) keep pressing the volume down button repeatedly. With me the RDS mode 3 onwire thing then didn't come up, turns out it was in fastboot mode when I connected it to the PC to see if was in luck. Turns out I was. Then I fastboot flashed a recovery.img and now it's all gravy.
Hope this works for you

[Q] Has My xoom bit the bullet ?

Yesterday I went to go on my Motorola xoom wifi and boot logo was displayed and the back was very warm. Reset the device and it stayed on boot logo. Tablet was running fine the day before. I tried fastboot, RSD and recovery and the pc only discovers Xoom in RSD mode, Recovery does not even load. I grabbed RSD lite and tried to flash a sbf file. program detects tablets flashes rom and reboots tablet when finished. then the program sits there counting up to 100% then says "please manually power up this phone". If I reboot tablet stays at logo screen. Is there any way to sort, bear in mind I cant only connect to tablet in RSD mode. tried 2 computers and four cables and still fastboot is waiting for device.
Thank you for reading this post.
Current device Properties in RSD Lite.
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Boot Version: N / A
DRM Version: N / A

Your battery might be bad but try these with your xoom plugged into a power source.
Can you get into recovery? with power off press the power button 3 seconds after moto logo press volume down you will see recovery across top press vol up. If you can do a factory wipe
Have you tried getting into fastboot mode? with power off press press power while holding vol down. if you can we can try and fastboot the files.

If I select recovery I get
-->Android Recovery
Entering Android Recovery Mode
and the Motorola Logo in center of screen. Nothing else Happens.
In Fastboot mode Nothing shows in Device Manager and all I get at cmd is Waiting for device after "fastboot devices" command
I managed to flash "HUBWF_W5.H.6.4-20_SIGNED_UCAHUBLWFRTCOREEU_P010_A010_M004_HWwifi_hubble_AP1FF" in RSD Lite but same prob loads boot logo and nothing else. Is it possible this could be a cpu error ? as rom was running at 1.5ghz and if stuck in boot at 1.5ghz for a few hours more likely damage would occur.

I don't think it is the cpu overclock because when you flash a new rom it would wipe your settings.
Do you have adb install on your pc?

I have adb installed on pc yes but no way to talk to the tablet.
Thank you for your response.

Do you have another device such as your phone you can plug in to your pc and see if adb is working by typing adb devices.

dfib1 said:
Do you have another device such as your phone you can plug in to your pc and see if adb is working by typing adb devices.
Click to expand...
Click to collapse
If I plug my HTC one X into the computer both fastboot and adb list it.
Thank you for your response.

The only thing I can think of is that the battery is going bad and causing issues. Since you flash new software, can't get out of the bootloop and the back is hot I would see about replacing it. You can try a soft reset but I don't think it will help. hold down both vol buttons and the power button until your xoom restarts.
I am not 100% sure if it is your battery but I am out of suggestions. I know when the batteries go bad in our devices it can cause issues.
http://www.portatronics.com/product_info.php?info=p9278_Motorola-Xoom-Battery-Original.html

[Q] Xoom upgraded yesterday and now the M Dual Core Image random pixels and stuck

I Have an original Xoom upgraded to 4g
It started yesterday saying it was upgrading, when it was done everything constantly crashed when it got to the home screen. I eventually could hit the OK buttons on the unfortunately XX has crashed quick enough to go into the settings and say factory reset. In the middle of the reset it froze.
Let it sit for a good long while, now when it starts up I have three states
By holding down the power button it just goes to a distorted Dual Core picture
By holding down power and vol+ it says
"Starting RSD protocol support 0
OneWire: Charger is connected...
Battery charge Level : XX%"
By holding down the power and vol-
"Starting fastbook protocol support"
At this point it does not seem to respond at all except for vol+ and power to reset. Am I missing a key combination, or are there other tricks to get past this point?
is there ANY way to get this to running again or should I chuck it in the garbage? It was $800 at the time of purchase would hate to see it be useless... Of course the warranty is no longer available
Here is a picture of what it looks like
imgur DOT com / pasr9Gm

You may have to fastboot a boot.img Grab a compatible boot.img for your device
1. Go to Android SDK, platform tools, place the boot.img in there.
2. Plug in your Xoom to your pc, on your Xoom go to the fastboot prompt.
2. On your pc, go to command prompt from platform tools.
At the prompt Type
Code:
fastboot flash boot boot.img
Then after that is done
Code:
fastboot reboot

Mjamocha said:
You may have to fastboot a boot.img Grab a compatible boot.img for your device
1. Go to Android SDK, platform tools, place the boot.img in there.
2. Plug in your Xoom to your pc, on your Xoom go to the fastboot prompt.
2. On your pc, go to command prompt from platform tools.
At the prompt Type
Code:
fastboot flash boot boot.img
Then after that is done
Code:
fastboot reboot
Click to expand...
Click to collapse
Thank you - I am looking EVERYWHERE and can't seem to find the HRI66 or HRI39 for the XOOM verizon version... I keep finding links to go to the motorola site - but its not on there anymore
is there a repo somewhere of these?

[Completed] fastboot does not accept command / recovery no command problem

Hello.I have a Gigaset qv1030 with Nvidia Tegra 4 cpu.
The main idea is that i cannot enter the android due to not knowing the password.So i ''tried'' to went to recovery for a fresh wipe/factory reset.Problem is no key combination does start up recovery.
Power+volume up does only power up the tablet / Power volume down does nothing and freezes the tablet (need to hold power for it to resests).
Only thing that does work however is if i press Volume up and power , after first vibration pressing volume down (with all 3 button now pressed) goes me into bootloader (says Unlocked) , and have the following options continue , reboot , fastboot protocol , recovery kernel , power off.
Fastboot protocol only restarts the tablet at the same point back into the bootloader (useless i guess)
Recovery kernel brings up an green android sitting on it's back with a red triangle saying no command. (tried every combination found , nothing seems to work)
Adb debugging is not set up in the settings i guess , and fastboot does appear in device manager if connected to a PC but it just does not accept any drivers (neither the modified google_usb drivers with tegra enabled , neither some found on the internet trough drivescape).So no device is found by the PC .
I did however finally installed the drivers using the drivescape driver with extracting driver , restarting with no driver signature and installing the driver using device manager update driver.Fastboot still does not see the tablet.
Connecting it while on the password screen, PC does recognize the tablet but that's it . No adb recognition.
This is as far as i got , idk what to do . Please help?
# PS yes i did not own the tablet , i got scammed by someone , and hoped to do the best out of the situation.
i think it is android 4.2

Duplicate, Please see my response from here:
http://forum.xda-developers.com/general/xda-assist/recovery-command-t3519232
Closed.

ADB Devices is EMPTY but phone is connected

My phone stuck on Realme Powered by Android.
I googled, installed ADB and connect my phone with my PC.
Then I do ADB Devices, but the list is empty.
Anyone know how to fix this?

If USB Debugging is enabled in Android settings then wrong Android USB driver in use: download and install the one matching your phone:
Download And Install Realme USB Drivers With How To Guide
From this tutorial, you could download and install the latest Realme USB Drivers onto your PC. The smartphone market is brimming with new offerings. Among
www.getdroidtips.com

adb daemon requires android booted. stuck at splash screen = not booted. force device in fastboot mode with Vol down + Power, install drivers as suggested and fix from fastboot.exe (no adb/usb-debugging required)

aIecxs said:
adb daemon requires android booted. stuck at splash screen = not booted. force device in fastboot mode with Vol down + Power, install drivers as suggested and fix from fastboot.exe (no adb/usb-debugging required)
Click to expand...
Click to collapse
According to Google's documentation - what hasn't changed over the last years - ADB consists of 3 softwares
1. ADB Server ( Desktop PC - establishes TCP connecion with Android Device )
2. ADB Client ( Desktop PC - sends ADB commands to Android Device )
3. ADB Daemon ( Android Device - processes ADB comannds sent )
So it should be clear that to execute ADB commands all these 3 softwares must be present and running.

So how to solve it if the phone only stuck at the powered by android screen?
xXx yYy said:
According to Google's documentation - what hasn't changed over the last years - ADB consists of 3 softwares
1. ADB Server ( Desktop PC - establishes TCP connecion with Android Device )
2. ADB Client ( Desktop PC - sends ADB commands to Android Device )
3. ADB Daemon ( Android Device - processes ADB comannds sent )
So it should be clear that to execute ADB commands all these 3 softwares must be present and running.
Click to expand...
Click to collapse
I tried with volume down + power but nothing happen.
aIecxs said:
adb daemon requires android booted. stuck at splash screen = not booted. force device in fastboot mode with Vol down + Power, install drivers as suggested and fix from fastboot.exe (no adb/usb-debugging required)
Click to expand...
Click to collapse
Any ideas guys?
Thanks in advance.

we don't know what is the reason for, you didn't tell anything what you did to cause this state. we don't know why you want adb access, I can only tell you that fastboot is available without usb-debugging.
power off device, check for proper key combo especially for your device model to enter fastboot mode.
https://www.hardreset.info/devices/realme/realme-5/fastboot-mode
if still no success, it might be fastboot mode is disabled intentionally (to prevent bootloader unlocking). in that case you are left with MSM Download Tool

Actually,you'l need to long-press the power button till the phone reboots then power + volume down IMMEDIATELY.

aIecxs said:
we don't know what is the reason for, you didn't tell anything what you did to cause this state. we don't know why you want adb access, I can only tell you that fastboot is available without usb-debugging.
power off device, check for proper key combo especially for your device model to enter fastboot mode.
https://www.hardreset.info/devices/realme/realme-5/fastboot-mode
if still no success, it might be fastboot mode is disabled intentionally (to prevent bootloader unlocking). in that case you are left with MSM Download Tool
Click to expand...
Click to collapse
So actually the phone have the volume up button and power button damage. at one time, it suddenly keep restarting. Then I let it be until the power fully gone. I ordered new volume and power button and change them.
Then I connect power supply to turn it on. But it seems it is stuck in "Realme Powered By Android" screen.
I tried to force shut down it and restart but still the same.
So I want to fast boot the phone but I am not successful.
Any Idea how I can do it?

sd369888 said:
Actually,you'l need to long-press the power button till the phone reboots then power + volume down IMMEDIATELY.
Click to expand...
Click to collapse
I tried 3 minutes pressing power button but nothing change. Then I restart using volume up + power button then immediately press volume down + power when it is turned off. But it seems it is the same too.