Database Info

Stuck on red M - Dual Core Logo

Hello, i recently bought a xoom (wifi only) and now im in a quite frustrating situation.
When i got it first i flashed CWM recovery and rooted it successfully, it worked all fine for a few days.
yesterday i left the xoom on charger over night and today morning it was stuck on the red M logo saying "Dual Core Technology".
well, my situation is like:
- i can restart the xoom using power + volume up, but every time it stucks on the M logo again
- i can boot into RSD with volume up while starting
- i can boot into fastboot with volume down while starting
- i can NOT boot into recovery, when i try it gets stuck at "Reading ODM fuse: 1"
i reflashed the original ROM from MOTODEV, but the device still behaves the same like before..
normal boot gets stuck at the M logo, recovery gets stuck on Reading ODM fuse: 1, just fastboot working fine (unlocking & flashing works fine)
i also searched for similar problems on the forums, but any promising solution links to filesonic links wich are not working/down
any ideas what i can do now? any help is appreciated
thanks

unlock the bootloader and flash Rogue Recovery v1.3.0
then try to enter cwm
are u on stock? or customrom? and have u tried to lock the bootloader using a customrom? cauz locking the bootloader with customrom = not good

hi, thanks for your reply.
im on stock rom and my bootloader is unlocked. i did relock the bootloader once, but only after flashing the original ROM from MOTODEV to my device, now it is unlocked again.
i first flashed the CWM 3.2.0.0 wich is available as .img via fastboot, but it does not start (Stuck on "Reading ODM Fuse: 1").
now i flashed the recovery.img inside of Rogue Recovery 1.3.0 (since i read in the corresponding thread that it works also this way), but again: Stuck on "Reading ODM Fuse: 1"

Maybe u r 2 quick? Turn on your xoom - if u see the M wait 3 sec then press vol down and then vol up
But as i said wait 3 secs - if u r 2 quick it will stuck at entering recovery

okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?

There should be a command to reboot the device to recovery? A function reboot to recovery is possible on eos 1.0 maybe theres a adb or fastboot command 4 that?

llama-power said:
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
Click to expand...
Click to collapse
after flashing the recovery, i can read
"Flashing StorMgr partition recovery STATUS: done!" on the xoom
the recovery image is fine, and until today i was able to boot into CWM 3.2.0.0
what is the thing with the factory cable?

about the factory cable: seems to be a modified usb-cable with two terminals on the micro-usb end being connected with each other. As far as I read, it should enable you to write to the xooms memory as long as the hardware is still okay, no matter how much you f***ed up your software I haven't had to use yet, though.
@what Unholy said: sure, adb reboot recovery will boot your xoom into recovery, but only if you have a working android running and usb-debugging enabled.
Reading ODM Fuse: 1, according to my information, means that the thing is trying to boot into recovery. Why nothing else shows up: I have no clue.
here is a thread where some us-users had a similar problem. They tried to root their xoom after getting the 4g-upgrade and ended up with the red M-Logo. After some screwing around, they even managed to wreck the fastboot-mode, thus only enabling rsd access. So no help on that side.
What especially bothers me about your problem is that it just appeared on its own. Right before your xoom showed its issues, you weren't flashing anything. Just charging shouldn't cause any of this.
I am beginning to suspect a hardware failure that can naturally be only fixed by motorola. But that's only my current opinion.
If I was you, I would try downloading the files from motorola again, check their md5-sums and then flash those using fastboot using these instructions.
If that still doesn't help, there may be a way to get a .sbf file from motorola for your xoom. That is a file which can be flashed using the windows software rsd-lite, but I haven't used that in a long time and it has been reported to not work really well with the xoom.
Next, I'd research a little on the factory cable thing, but I'd be careful with that.
As a last resort, I'd send the xoom to my dealer. Unluckily, there is a way to determine if you have had your bootloader unlocked, at least as long as fastboot is still working...

About the factory cable - with that cable u can flash your xoom if nothing else is working anymore (adb or cwm)
To build a factory cable u have to tie pin 1 (+) to pin 4 on the micro usb plug
I build one but never used it and hope i will never have to

i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...

The_Revenge said:
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
Click to expand...
Click to collapse
does the xoom charge when connected to ac power? I know that other devices (cellphones) wouldn't charge without working os.
However, I do not think that letting the battery run low will help you. Lithium ion batteries should not be low discharged as that will most likely destroy them and lead to a massive risk of explosion upon the next charge. Because of that, devices powered by a lithium ion battery will power down before depleting the battery, the xooms mainboard itself will most likely still be supplied with some power.
If you really want to cut the power supply to the mainboard, you'll have to open the xoom (two screws) and unplug the battery (the connector is held down by another two screws) for a couple of seconds. (here is a teardown of the xoom with pictures)
by the way, if you want to track your battery status without booting android (as that would obviously not work), you can use fastboot getvar battery-status.

well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?! is there maybe any way to update the bootloader itself?
yeah, i can also check the battery status when i'm booting with power and volume up (RSD) =)
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..

The_Revenge said:
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?!
Click to expand...
Click to collapse
not neccessarily. Maybe the xoom just doesn't need any software to charge the battery.
The_Revenge said:
is there maybe any way to update the bootloader itself?
Click to expand...
Click to collapse
don't know, but since fastboot works I suspect that the bootloader itself is still fine.
The_Revenge said:
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
Click to expand...
Click to collapse
have fun, but I wouldn't get my hopes up too high. I still suspect some sort of a hardware failure... Also, opening the device might leave some traces (botched screws, etc) that could lead motorola to say that you messed with your xoom if you should finally decide to send it in

well thats the same i thought about opening the device..
do you know any way to dump the partitions to the pc (maybe with fastboot?)

The_Revenge said:
do you know any way to dump the partitions to the pc (maybe with fastboot?)
Click to expand...
Click to collapse
nope, not without a working recovery.
fastboot erase partition_name should be able to clear your partitions, though. Replace partition_name with boot, system, userdata, cache or recovery

http://www.xoomforums.com/forum/xoo...ery-stuck-red-m-logo-fastboot-works-help.html
apparently that user seems to have had the same problem, he says he fixed it using 1.35 Everest Bootloader (SBF).
i also had that idea some time earlier and found a thread with the SBF files here on xda, also for the wifi model, but the only links i could find to SBF files were filesonic links wich are not working ._.
i'm now up to googling for SBF files (for the wifi only model), if i cant find anything promising i'll send it back tomorrow.
btw, erasing the partitions does not help, i've already tried that

Have u done the lte update?

UnholyX said:
Have u done the lte update?
Click to expand...
Click to collapse
he's got an wifi-only model (as stated in post #1) and is from germany (at least that's what his location and flag says). LTE upgrade is neither available in germany, nor for wifi-only-xooms. So I'd say no
@OP: that sounds quite promising. .sbf-files still seem to be available on some sites, downloading one for my xoom right now, just in case that site goes down in the future...

Yes he got the wifi version like me but something must happened ,-)
I also charge my xoom and nothing happens. He got wifi version but he maybe flashed a false update or so
There r people flashing stingray instead of the wingray version etc. - just asking what happened before - thats the reason - something must happened before ;-)

it seemed promising, but i cannot find any usable sbf file
i think i'll send the unit back tomorrow

[Q] Am I Screwed?

So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?

Is it recognised via ADB?

Send to service center and they should have special tool to recover it!

re-flashing Rogue Recovery
mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.

Grege50 said:
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.
Click to expand...
Click to collapse
Thanks for the help guys,
So I tried re-flashing the Rogue Recovery, and other kernels, but the Xoom says,
"Device still locked. Device must be unlocked first.
Failed to process command error (0x8)"
I'll be some research too and let you guys know what happens

mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2

cdexsw said:
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
Click to expand...
Click to collapse
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .

mikeay93 said:
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .
Click to expand...
Click to collapse
the problem is when you relocked the bootloader. It was a "bad lock". You need to UNLOCK the bootloader then the device should boot up normal......RSD will recognized your device but with a screwed up bootloader nothing will flash.......also fastboot and adb will have the same result because of this
**here is what to do**
Option#1 - Try this first
1. connect Xoom to PC with Moto USB Cable (the one shipped with Xoom if possible)
2. ADB command: fastboot reboot-bootloader
3. It will show
4. Then Press Pwr + Vup (reset xoom)
5. When Xoom go into black screen (before the Moto logo appear), press and hold volume down button. I was then successfully get into Fastboot.
In step no. 5, you must press and hold the volume down button, if you release the button, Xoom will reset by itself and you will again caught in the "Failed to boot LNX 0x0004" screen. If you accidentally let go the volume down button, repeat step 4 - 5, and make sure you will not let go the volume down button this time.
Then, one of your hand is holding the volume down button, use your another hand to enter an ADB command: "fastboot oem unlock", you will be able to unlock your bootloader, and xoom will reboot normally.
Yes, I understand your xoom is not working proper but this may take 5 or 6 tries......keep at it. This has had many successes.
-------------
Option#2 - If option#1 does not work
Follow these steps to modify your USB cable to a programming cable
http://forum.xda-developers.com/showthread.php?t=1108518&page=2
Here is a tutorial if you decided to go this route
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
This too works......but make sure your contacts/wires do not touch other wise you zoom may die when everything gets plugged making the cable is a pain but it's a life saver.
------------
Those are your ONLY options for recovering from this brick.
NOTE - DO NOT RELOCK BOOTLOADER WHEN CONVERTING FROM 3G TO WIFI ONLY. I recommend never touching it after it is unlocked, ever.
The only time locking the bootloader will work is only when you return the device to its original factory condition..........and the only time. Best advice.......after you unlock the bootloader never touch it again.
I hope this helps. Good luck.
Sent from my Xoom using Tapatalk 2

Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.

mikeay93 said:
Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.
Click to expand...
Click to collapse
Do you know what version of the bootloader you currently have on your Xoom?
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2

I've been swamped with work and finals guys I didn't forget about this. As soon as school finishes I'll put more time into trying to find a solution in case anyone is going through the same thing. Thanks to anyone trying to help out.

Hey guys I'm back. My memory is a little rusty on the topic so let me just tell you where I'm at.
I will be convinced that I have a messed up bootloader once someone explains me this... the Xoom model number on the box says MZ600. Using RSD lite, I have several sbf files downloaded: MZ600, MZ602, MX604. Running the program under administrator, I can only start RSD with the MZ604 sbfs loaded. But once again, my model is a MZ600 yet it will not load that sbf file. Can someone explain to me what is going on here?
Cdexsw, as for the bootloader I have no idea which one is installed.

The error I get from RSD when I flash the mz600 is "Failed flashing process. Unable to retrieve installation values from INI file. (0x7029); phone connected"

The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2

cdexsw said:
The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I tried flashing various boot, system, recovery, and userdata files and they all successfully get flashed through. But on reboot, I still get stuck on the Motorola logo. I tried several 604 images, because those are the only ones that actually start in RSD, but those fail as well. I tried finding out my bootloader information with the command fastboot oem get_unlock_data but the command fails and gives an error on the xoom saying Failed to process command error(0x120000)
So I'm really stuck on what to do next...

Where did you buy it
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.

Grege50 said:
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.
Click to expand...
Click to collapse
U.S.A....

mikeay93 said:
U.S.A....
Click to expand...
Click to collapse
OK, I will butt out. My only other thought is going into recovery and using the format option to re-format the internal partitions, then re-flash.

Read this thread
http://forum.xda-developers.com/showthread.php?t=2069809

[Q] Stuck in ap fastboot

okay so i just updated my droid razr hd and i had an unlocked bootloader, but no root, when i looked it was still unlocked and when i tried to restart my phone it would go to ap fastboot and i couldnt pass it and this happens everytime i turn it on, does anyone have any suggestions i can do? My android version is 4.1.2 and my system version is 9.20.1.XT926.Verizon.en.US. Anything would help.

D4V3Y said:
okay so i just updated my droid razr hd and i had an unlocked bootloader, but no root, when i looked it was still unlocked and when i tried to restart my phone it would go to ap fastboot and i couldnt pass it and this happens everytime i turn it on, does anyone have any suggestions i can do? My android version is 4.1.2 and my system version is 9.20.1.XT926.Verizon.en.US. Anything would help.
Click to expand...
Click to collapse
When you end up in Fastboot, what does it give for a reason? If you enter it because of the power/volume combo it will say so. If your update didn't work, it might say reason: flash failure (something like that...flash failed, flash something)
If you get the flash failure, I'd have to think something got mucked up during your update and now its just not able to boot, garbage or corrupted data where it expects good data.
If that is the case, there are tools/scripts in the developer portion of the forums (http://forum.xda-developers.com/showthread.php?t=2307439) that you can use to get your phone back to stock (pre OTA). You can reload the ROM fresh and reload your recovery fresh. It will erase everything on your phone...all your personal files. This should give you a functioning phone though.
You can try taking the update again after that.
Lenny

Thanks it worked

Motorola Razr HD LTE XT925 4.1.2 boot loop

I'm stumped with this issue of my Motorola Razr HD LTE XT925 Rogers version 4.1.2 being in a boot loop. It started when I did a factory reset to try and fix some camera issues that I was having it started up with the Motorola red M icon then went to proceed with the factory reset with the android icon with the spinning blue object then restarts and just does a loop I have tried some steps that I found that I will list but all are unsuccessful and I did try them several times. It is stock firmware but was rooted with one click rooting program can't remember the name I did nothing else to the firmware.
Power + volume down for 10 seconds (simulates a battery pull)
Stock recovery tried wiping data and cache and then rebooting
Tried to use the boot menu normal start up and factory options
I did however get it to boot to the Rogers logo screen once but it just froze and had to restart it
I am currently trying get ADB tool to installed and get it working to see my phone as well as RDS Lite 6.1.6 it wont show any info about the phone but when in fastboot mode RDS Lite see it as connected in fastboot but no info about the phone shows up in the top left box as it has shown before also tried Super ADB Tool it show nothing at all I will continue to try and get the tools working.
Any help in getting the phone to boot normally is greatly appreciated.

I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.

OK so I have ADB installed and working I think put my XT925 in fast boot mode then I put in code adb devices in to the windows command console but show nothing listed and my phone says it is in fastboot mode and usb is connected and windows sees it as well but not ADB. There is no errors ether I am so confused as to why ADB and RSD show no info about my phone? I will see if its any of my drivers that are missing.
I went ahead and tried to flash my phone with RSD lite 6.1.6 with no luck the boot loop is preventing it from proceeding with the flash is this just a lost cause and there is no fix for it. The only thing I can think of is that I have to unlock the boot loader is that even an option when I can't even get boot into android? Any one got any ideas?

I was messing a round with my phone and try to get it working with any of the tools and had turned of the phone to stop it from constantly showing the red M icon and the android icon with the blue spinning object over and over but still had the phone plugged in to the computer and was looking in device manger in windows and seen this QHUSB_DLOAD with no drivers for it and looked at the VID & PID ids (USB\VID_05C6&PID_9008
) and searched for drivers thinking that is what is missing for my phone as I have never see it before and it is Qualcomm modem flashing port I don't know what to do did really mess up my phone by just doing a factory restore?
Some help or clarification would help a lot now as it is a bit troubling that I am unable to fix the Motorola Razr XT925 and might be bricked just by doing a factory restore. :silly:

OK I am getting desperate here I will do anything to stop it from looping I have even tried house of motos way just the same thing still if I can stop it from looping I can get it to work but does anyone knows a way to wipe the phone completely or stop it from this infuriating loop???
Just as a side note I found that forcing it in to normal start up with the wall charger plugged in it will charge when done then it will show the rogers logo like its booting but does nothing.

I have searched the forms and google now for 2 days about any way to fix the boot loop but all just say to do things that I have tried many different ways many times and the tools don't work or will work like RDS but it is unable to continue do to the loop of it doing a factory restore then restarts.
If any body has any ideas at all or can at least point me in the right direction would be a life saver I will even jtag the phone if i have to, if even that's possible

Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?

Darbness said:
Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?
Click to expand...
Click to collapse
Thanks for the reply, I have gone into fastboot mode and used RSD to try and flash the stock rom but when it restarts the phone its unable to countiue becuse it is uable to get past the bootloop

If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app

Hydr0id said:
If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
OK, not able to take it to Rogers some issues with doing that but will try RSD lite 6.1.4 besides that no other ways?

I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.

xaneth said:
I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.
Click to expand...
Click to collapse
Thanks for the reply, I was thinking along the same lines as that but trying it on a freshly installed windows plus on different computer and just have RSD lite 6.0 and my Motorola drivers for my phone installed. I was thinking that it was my current motherboard that has a Intel usb 3.0 controller on it and my old motherboard did not as I manually updated my phone from 4.0.4 to 4.1.2 before on my old motherboard and had no issues and will fallow the instructions to the letter and will triple check as well. I will see how this goes and hope it works as its my last option to get it working.

OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?

osalot said:
OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?
Click to expand...
Click to collapse
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk

Hydr0id said:
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, The steps I take to flash my phone is to first put my phone in to fast boot mode then connect my phone to the back of my pc then start up RSD Lite and add the latest firmware for my XT925 in RSD then let it load the firmware and it restarts the phone. it starts up to the non animated red M icon then the android with the spinning blue object in its chest comes up but then shuts off and restarts and have left it for several hours until it died and had to recharge it up.If I can I will post a video of how I flash it and what the phone does.
also is it normal for RSD Lite not to show the imei number of the phone or any thing about it in the top left box (Device properties) when you click on the modal?, all I get is N/A in Device properties box.

Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app

Hydr0id said:
Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
thanks for the reply, I have just tried the the steps in the link you provided and I used RSD lite 6.1.4 and got the 4.0.4 Rogers firmware for my XT925 that it originally came with and waited an hour but just did the same thing, I don't get any errors when flashing although RSD displays to start the phone up manually and I have a locked boot loader (Device is LOCKED: Status Code: 0) I can how ever get it to go to the animated red M icon and then the rogers logo by selecting normal power up from the boot menu but doesn't boot in to android.

osalot said:
I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.
Click to expand...
Click to collapse
http://theunlockr.com/2012/01/24/how-to-restore-the-motorola-droid-razr-using-fastboot-files/

Ok, so I think I maybe doing something incorrectly so I will put all the steps I did to reflash my phone and will add some pics and a video if possible.It took me a few days to get another phone to use for vids and pics the phone I used to for video and pics Samsung Captivate, unbrickable ya can't kill it.
1. I have installed RSD Lite 6.1.4
2. Installed the latest Motorola drivers by down loading the Motorola Device Manager
3. Down loaded the firmware for my phone android 4.1.2 full file name ---> 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
4. Put my phone in fast boot mode then connected my phone to my netbook on the side or on the back usb 2.0 port on the PC with the original Motorola usb phone cable tried both to be sure
5. Started up RSD Lite 6.1.4 and load the firmware and selected Decompress only
6. Checked RSD Lite to make sure my phone is connected and showing up and RSD Lite shows (Fastboot VQUISH_U S USB N/A Connected)
7. I then selected start button on RSD Lite and it flashed the firmware with out issues or errors
8. phone restarts fine from fastboot left it for 1:30 RSD displays to reboot the phone manually but the phone does not do anything else but reboot constantly left the phone doing that until it ran out of battery
Pic of XT925 in fastboot mode not connected
Pic of RSD with phone connected in fastboot mode ready to be flashed
Video of phone restarting after being flashed and looping (click the link below)
http://s1295.photobucket.com/user/Osalot-Ruin/media/RSDandphonevideoCapture_zpsff85211b.mp4.html
Pic of RSD after leaving the phone for 1 hour and 30 minutes

In the steps I don't see the XML file editing, did you deleted the getvar line in the XML file?
Sent from my RAZR HD using XDA Free mobile app

{Solved} Pixel 2 Bricked, need help.

Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
EDIT:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!

Grab the latest Google platform tools and USB drivers. When your device is plugged in, do you see any unknown devices in your device manager? Or anything that looks like it could be your phone?

jascolli said:
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
Click to expand...
Click to collapse
I've seen that before.
When you select reboot bootloader does that message go away?
Try it without the cable plugged in does it go away then?
I just want to know if you can actually get that message to go away or not at this point.
Also can you link the tools you are downloading

jascolli said:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Click to expand...
Click to collapse
For future learning, I'd recommend you familiarize yourself with how to do this without toolkits. A toolkit is nice, but it really helps to understand what the toolkit is doing so that if you have an issue you know what to do next.

Telperion said:
For future learning, I'd recommend you familiarize yourself with how to do this without toolkits. A toolkit is nice, but it really helps to understand what the toolkit is doing so that if you have an issue you know what to do next.
Click to expand...
Click to collapse
Solid advice, thank you.

I did this same thing and solved it the same way. I think things just get funky and the tool you mentioned to fix it.

nolimit78 said:
I did this same thing and solved it the same way. I think things just get funky and the tool you mentioned to fix it.
Click to expand...
Click to collapse
Yeah I'm baffled. I could not for the life of me get fastboot to work. That Skipsoft tool is pretty impressive.

HELP!!!!
I have same problem, so which functions you use to fix it????
jascolli said:
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
EDIT:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Click to expand...
Click to collapse

Same thing happened to me. I need help. Please tell me how you unbricked your phone

same problem
i have the same problem already download skipsoft program but dont have results can you tell me the steps what you do please
---------- Post added at 07:48 AM ---------- Previous post was at 07:43 AM ----------
yuva_cool said:
Same thing happened to me. I need help. Please tell me how you unbricked your phone
Click to expand...
Click to collapse
do you already unbricked your phone?

my pixel still cant be detected by that toolkit, can u list the step by step procedure what u did to unbrick the device?

I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.

Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Click to expand...
Click to collapse
This is the correct resolution to this issue.
I had the same issue, no usb in bootloader. I drained the phone and rebooted into the Bootloader flash A and B side bootloader the Aug 2018 (previously working for me) and A and B side Radio, as well as the System image. After that everything booted fine.
Attempted to install the January update the same way and it worked as well.
Seems like they messed up A and B side flashing
My steps::: For Lurkers having this issue.
1. Drain battery DEAD!
2. Boot Bootloader (Vol Down + Power)
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
3. fastboot set_active b (opposite of the one on screen)
4. fastboot reboot-bootloader
5. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image) (Again)
6. fastboot reboot-bootloader
7. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
8. fastboot set_active a (opposite of the one on screen)
9. fastboot reboot-bootloader
10. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
11. fastboot reboot-bootloader
12. fastboot update image-walleye-pq1a.190105.004.zip (or whatever image)
Phone boots properly, and is updated.

thedude9821 said:
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
omg after months of figuring it out ,and almost opt for warranty,finally my pixel is aliveeeee, thanks alot for the fix im so glad.. and whats more important for me is the data is still intact! i cant thank you enough.. google messed up december update pretty bad.

I just received my 4th RMA and the bootloader wasn't able to unlock. So to my surprise Google is giving me a full refund? I purchased my Pixel 2 back in Nov 2017 ?

Dajax2 said:
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
Click to expand...
Click to collapse
@Dajax2 Super new to this and it may be a total waste since my bootloader screen says "Device State: locked" but in trying to flash or even sideload ota, the command returns "error: cannot load (file location/name): no such file or directory found". Again, total noob and I don't even know if I'm supposed to unzip the folder or not but have tried both ways with the same error.
It returns the serial number for fastboot devices but nothing for adb devices. I obviously didn't have OEM or USB debugging enabled prior. Hoping I can at least get in to retrieve data before giving up all hope :/

Solved. Enter barcode mode. In this screen, check for devices from adb or fastboot. It should be there. You are now able to switch slots and do all the fastboot things.

Great workaround that I would never have thought - good info here, thanks everyone!

dianea said:
Solved. Enter barcode mode. In this screen, check for devices from adb or fastboot. It should be there. You are now able to switch slots and do all the fastboot things.
Click to expand...
Click to collapse
Edit - My phone wasn't detected when on the barcode screen, just like from the main bootloader screen.
HOWEVER... to my surprise.. the above method of draining the battery completely to 0% actually worked. I'm a little dumbfounded why this allowed the bootloader to connect via fastboot again, but it did. I was able to flash the latest factory image (without wipe) and boot back up like nothing ever happened. Thank you so much for the tip. I passed this along to Google support and they also said they appreciate the troubleshooting and asked me to just send back the replacement phone with the RMA package/label.
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
thedude9821 said:
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
Did they accept the RMA phone back and remove the temp auth on your card?

thedude9821 said:
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
Dajax2 said:
This is the correct resolution to this issue.
I had the same issue, no usb in bootloader. I drained the phone and rebooted into the Bootloader flash A and B side bootloader the Aug 2018 (previously working for me) and A and B side Radio, as well as the System image. After that everything booted fine.
Attempted to install the January update the same way and it worked as well.
Seems like they messed up A and B side flashing
My steps::: For Lurkers having this issue.
1. Drain battery DEAD!
2. Boot Bootloader (Vol Down + Power)
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
3. fastboot set_active b (opposite of the one on screen)
4. fastboot reboot-bootloader
5. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image) (Again)
6. fastboot reboot-bootloader
7. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
8. fastboot set_active a (opposite of the one on screen)
9. fastboot reboot-bootloader
10. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
11. fastboot reboot-bootloader
12. fastboot update image-walleye-pq1a.190105.004.zip (or whatever image)
Phone boots properly, and is updated.
Click to expand...
Click to collapse
Gifted both of you Ad-Free for this.
You saved me $300 and the annoyance of having to wait for shipping for either RMA or another phone on Swappa.