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] Xt925 fido problem

Hello all, this is my first real post here,
and I hate to say that I have a problem! First off let me say, I have trolled(and found MANY fixes here) and never had to sign up, because anything I needed was in the search menu!! which let me say is Awesome...
However i have a different problem this time, lol
I recieved my OTA of JB, I was rooted, after following a few steps, I unrooted and was able to update to JB, I rooted again, and somehow or another, I ended up back on ICS,(I found this VERY VERY weird) didn't think this was possible, but it happened after a few flashes.
Anyways today, I plug my phone into my pc,(after a few weeks of it working properly) to upload some pictures, it automatically started to flash, I unplug, reboot(which works most of the time) however NOT this time,
I have the following on my screen
AP Fastboot Flash Mode(S)
10.98(*)(sha-56608bc, 2012-11-23 and time)
eMMC Info:size 16gb
Device is LOCKED, Status Code:0
Battery Low
Transfer Mode: USB Connected
Partition(boot) Security Version Downgraded
Fastboot Reason : Boot Failure
usb connected
I have tried to load a 3rd party xml file aquired from this site, when loading I can get into the other screen which allows me to wipe data etc. but still nothing, Also tried to just let it run its course and nothing..
Officially I am a N00b and I would like some help
The third party file, gives me the error(rsd lite 6.1.4) flash fail
Now I cannot find much info on this, and am Kinda in a bind. Any help is appreciated and I will gladly take the n00b comments with it as I realize this is my own fault..lol
update: when I boot my phone OFF of usb cord, I get fastboot reason: sticky bit factory_fastboot at the bottom now, wtf is this? lol

waynold78 said:
Hello all, this is my first real post here,
and I hate to say that I have a problem! First off let me say, I have trolled(and found MANY fixes here) and never had to sign up, because anything I needed was in the search menu!! which let me say is Awesome...
However i have a different problem this time, lol
I recieved my OTA of JB, I was rooted, after following a few steps, I unrooted and was able to update to JB, I rooted again, and somehow or another, I ended up back on ICS,(I found this VERY VERY weird) didn't think this was possible, but it happened after a few flashes.
Anyways today, I plug my phone into my pc,(after a few weeks of it working properly) to upload some pictures, it automatically started to flash, I unplug, reboot(which works most of the time) however NOT this time,
I have the following on my screen
AP Fastboot Flash Mode(S)
10.98(*)(sha-56608bc, 2012-11-23 and time)
eMMC Info:size 16gb
Device is LOCKED, Status Code:0
Battery Low
Transfer Mode: USB Connected
Partition(boot) Security Version Downgraded
Fastboot Reason : Boot Failure
usb connected
I have tried to load a 3rd party xml file aquired from this site, when loading I can get into the other screen which allows me to wipe data etc. but still nothing, Also tried to just let it run its course and nothing..
Officially I am a N00b and I would like some help
The third party file, gives me the error(rsd lite 6.1.4) flash fail
Now I cannot find much info on this, and am Kinda in a bind. Any help is appreciated and I will gladly take the n00b comments with it as I realize this is my own fault..lol
update: when I boot my phone OFF of usb cord, I get fastboot reason: sticky bit factory_fastboot at the bottom now, wtf is this? lol
Click to expand...
Click to collapse
1) Don't use the fastboot files from here just yet... they are unofficial right now. I'm working on something better.
2) Your battery is low, you should get a factory cable or factory adapter. Look it up...

danifunker said:
1) Don't use the fastboot files from here just yet... they are unofficial right now. I'm working on something better.
2) Your battery is low, you should get a factory cable or factory adapter. Look it up...
Click to expand...
Click to collapse
I seen that it was low, switched back to my wall plug and I don't know if its charging or what, but now battery is OK, weird.
Ok, I will hold off, but from what you see , does this seem fixable? I love the phone, and if its a brick, then I may be a lil heart broken but lesson learned for sure. lol

Zopo ZP980t Need help Please

Good morning everyone,
I have a zopo zp980t 32gb 2gb ram model whihc from reading and checking mine does not have fcc or b logo under battery if that helps to know what rom i can use.
BUT i have a big problem.
Phone was working very well on latest firmware which it came with a month ago.
I changed boot animation once from someone on a site and all good as original was annoying.
He made me a custom animation and when i clicked on update as with other's, this time the screen went bright screen and went onto the blue adnroid icon with spinning circle going around it and now it just stays on this.
I am gutted as phone will not boot.
I can only get into recovery menu with usb cable conencted to pc and pressing vol up and power, this will not work without usb attached?
Anyway i am trying in vain to at least get it working again and flashing a rom original with flashtool 4.2, this now is into 2nd day and getting nowhere.
I am running windows 7 home edition and the driver is the issue as i get BROM error ...............port etc (1013) which i assume is driver not installed which i have tried way too often.
Is there a clear tut how to get this done as i feel once i get this corrected i will hopefully be able to get phone running again, maybe?
I don't like asking for much and always will work and learn myself by reading but their are so many models of this 980 it is not possible to know which rom i can use etc.
Any guidance is really much apprecaited.
Absolutley gutted what's happened not long after buying it.
Thank you so much for any advice given.

Fixed & how to
This is for other's that may have same problem or simply want to know how to reflash from fresh.
First of all i was having issues with the usb driver i.e port not installing.
So i used my wifes netbook and installed perfectly without issue.
I then went to zopo main original roms page and downloaded BOTH roms to save hassle.
As my phone is 32gb 1.5 quad core, Black under battery, no FC, no B and no replies to help me find out what model i have i went testing.
I started the flashtool 4.2, then i tried firstly the:-
ZP980/C2 4.2  ZP980_0610  341.4MB 2013/6/10 Normal Version (PHONE DOESN'T BOOT)
Secondly I then flashed:-
ZP980/C2 4.2 ZP980_0610 341.4MB 2013/6/10 B version (THIS WORKS FULLY)
So now completed flash and phone working.
Then i connected the phone to my wireless network, and in the phone i clicked on the WIRELESS UPDATE app.
This then provided me straight away with the latest update being:- BUILD NUMBER ZP980 20130818-173942.
I rebooted phone and now latest firmware.
I wanted to root it now and easiest way is simply using a program called EROOT.
Make sure USB DEBUGGING is ON, wait few seconds and hit ROOT.
Super user now in phone and fully rooted.
Job done

[Q] Android won't boot...

Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!

kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?

ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/

If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:

Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.

kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?

The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.

howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor

Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.

kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.

theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!

You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.

Help with apparently hard-bricked phone?

Tried 3 different versions of Odin, it always fails after boot.img ("complete write operation failed")
My phone model is G920I.
I'm stuck in the exclamation mark screen. Only thing I can do pressing buttons is reach the download screen. Can't access recovery.
Can I flash TWRP through odin and try installing a firmware stored in my ssd? Or that wouldn't even work seeing as I can't get pass the ! blue (green?) screen anyway?
Worst part is, I don't even know how this all started. I got a notification that a new update was released, but my battery was low, the phone died, I left ir charging and it wouldn't turn on the other day. I probably ****ed something up in the recovery screen (it was accessible in the beginning) and now I can only access the !/download screen.
Does anyone have any idea what I can do? Thanks in advance.

rifek4 said:
Charge you battery a bit anyway, to be sure there is minimum 30%. Then flash latest 7.0 firmware correctly for your model via Odin3 with latest drivers: https://forum.xda-developers.com/ga...official-stock-firmware-t3086387/post73935393 here you found all.
Click to expand...
Click to collapse
Made a new thread because my problem seems slightly different and I explain about it. Don't see how it could be prejudicial to the forum but thanks for the hint.
My phone is only on when connected with cable, either to the computer or charger, When I still had access to recovery mode, it said 99% battery. Now I don't even think I can check the battery? All I know is when the phone is not connected, it stays off.
I've tried using a couple of supposedly stock firmware from my model but the error is always the same. Gonna try downloading one from where you linked me to, but do you really thing it could make a difference, considering everything I've said?
Thanks in advance.