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] Bricked my phone pretty bad

I managed to unlock my bootloader, rooted everything within 45mins, everything was running ok but I ended up encounter screen freeze and sudden shut downs. So I deceived to restore stock firmware follow this guide. http://forum.xda-developers.com/showthread.php?p=47820707#post47820707 when I started entering the codes, the first 3 returned as FAILED, the rest were either OKAY or ERROR, I decided to enter the last step even thought I encountered these mistakes. It was stuck on the Bootloader warning screen(the thing you always see after you unlocked your bootloader) for a good 4 hours before it shut down, and knowing that I did something wrong I decided to boot into fastboot mode first. Now heres where the problem lies, I used MOTOTOOL before hand to restore the recovery firmware to kitkat BEFORE I tried to restore stock, now I don't have access to a custom recovery, nor can I flash one because the battery is too low, but there is no way of getting it to charge either. I tried fastboot getvar battery-voltage and all it ended up saying is
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
idk why this is happening, it says on fastboot mode Battery Low (charging) but that has been going for a while and shows no sign of changing. I haven't touched barcode or QCOM yet, going to BP Tools and Normal Powerup shows the Bootloader warning that just stays like that. Since recovery wont do anything now, funny thing is I am able to access to fastboot mode through the "frozen Bootloader Warning".
The only way out I can think of is to somehow charge some battery, but BP Tool always leads to Bootloader warning which is always on full brightness and drains more than it gains. If I unplug my phone and enter the BP Tool is will show a battery gauge, I've yet to see the number go above 0% yet.

You"ve got company!!!!
TooMuchPhoneProblems said:
I managed to unlock my bootloader, rooted everything within 45mins, everything was running ok but I ended up encounter screen freeze and sudden shut downs. So I deceived to restore stock firmware follow this guide. http://forum.xda-developers.com/showthread.php?p=47820707#post47820707 when I started entering the codes, the first 3 returned as FAILED, the rest were either OKAY or ERROR, I decided to enter the last step even thought I encountered these mistakes. It was stuck on the Bootloader warning screen(the thing you always see after you unlocked your bootloader) for a good 4 hours before it shut down, and knowing that I did something wrong I decided to boot into fastboot mode first. Now heres where the problem lies, I used MOTOTOOL before hand to restore the recovery firmware to kitkat BEFORE I tried to restore stock, now I don't have access to a custom recovery, nor can I flash one because the battery is too low, but there is no way of getting it to charge either. I tried fastboot getvar battery-voltage and all it ended up saying is
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
idk why this is happening, it says on fastboot mode Battery Low (charging) but that has been going for a while and shows no sign of changing. I haven't touched barcode or QCOM yet, going to BP Tools and Normal Powerup shows the Bootloader warning that just stays like that. Since recovery wont do anything now, funny thing is I am able to access to fastboot mode through the "frozen Bootloader Warning".
The only way out I can think of is to somehow charge some battery, but BP Tool always leads to Bootloader warning which is always on full brightness and drains more than it gains. If I unplug my phone and enter the BP Tool is will show a battery gauge, I've yet to see the number go above 0% yet.
Click to expand...
Click to collapse
As mentioned above my phone is also stuck in boot loader unlock screen I am unable to flash anything due to low battery percentage and I have got a custom recovery installed (TWRP).In fastboot mode when connected to pc it says low battery (charging).After some time it loses all the charge and shuts down.i am then able to charge with a wall charger for min 2% and max 13%.Please someone help I have to flash stock rom back on and get the phone working.

Enter fastboot and charge there for 3hrs with a good charger 1Amp+.
See what happens and report back.

liveroy said:
Enter fastboot and charge there for 3hrs with a good charger 1Amp+.
See what happens and report back.
Click to expand...
Click to collapse
if I am not wrong its not possible to charge from fastboot.

TooMuchPhoneProblems said:
if I am not wrong its not possible to charge from fastboot.
Click to expand...
Click to collapse
You are wrong, it is possible.

TooMuchPhoneProblems said:
if I am not wrong its not possible to charge from fastboot.
Click to expand...
Click to collapse
it's possible, it even shows that it is charging when in fastboot

lifetimes said:
it's possible, it even shows that it is charging when in fastboot
Click to expand...
Click to collapse
I left it on fastboot for a very long period of time and it didn't seen to move from 0%. Anyway I somehow messed around and got the battery to 44% and got a TWRP built in. Now what?

wait, try to explain the problem with more details, and add more information about that(before and after trying to restore it)

RollVGE said:
wait, try to explain the problem with more details, and add more information about that(before and after trying to restore it)
Click to expand...
Click to collapse
Current state
I've managed to charge my battery to 38%
Installed CWM
Formatted /data /system /cache
frozen boot loader warning screen when I try to normal powerup
Click to expand...
Click to collapse
the goal
get out of bricked state:
Load a custom ROM/Restore stock firmware
Click to expand...
Click to collapse
what I am trying to do
adb sideload a rom.zip onto my storage
Click to expand...
Click to collapse
What I am unable to do
ROM WISE:
Theres no way of mounting USB storage on kitkat
mount /data /system /cache wont show up on pc
adb sideload cant detect any devices
unable to somehow put a rom inside my /sd card
RESTORING STOCK WISE:
preflash validation FAILED for the first 3 steps from the guide
Click to expand...
Click to collapse

the only thing I can think of for now is to try again with the guide you mention, but this time you download a 4.4.4 firmware update, be sure to be a .xml.zip file. that is compatible with your model, and good luck :fingers-crossed:

RollVGE said:
the only thing I can think of for now is to try again with the guide you mention, but this time you download a 4.4.4 firmware update, be sure to be a .xml.zip file. that is compatible with your model, and good luck :fingers-crossed:
Click to expand...
Click to collapse
I don't plan on downloading every single one until it works. And I have a feeling this one wont either.

Get a 4.4.4 or 4.4.2 stock and flash it. Don't skip "erase userdata", it's a vital step to unbrick.

RollVGE said:
the only thing I can think of for now is to try again with the guide you mention, but this time you download a 4.4.4 firmware update, be sure to be a .xml.zip file. that is compatible with your model, and good luck :fingers-crossed:
Click to expand...
Click to collapse
OMG you were RIGHT, I think. I downloaded the US 4.4.4 because it was the only one I could find at the link so I flash it just fine. But it turns out theres a 4.4.4 TESCO version that I missed. Now I am using US 4.4.4 stock firmware...

i had
TooMuchPhoneProblems said:
OMG you were RIGHT, I think. I downloaded the US 4.4.4 because it was the only one I could find at the link so I flash it just fine. But it turns out theres a 4.4.4 TESCO version that I missed. Now I am using US 4.4.4 stock firmware...
Click to expand...
Click to collapse
I had that same problem with my moto g (xt1039) but i downloaded xml.zip and extracted it and flashed with fastboot.

lordnakki said:
I had that same problem with my moto g (xt1039) but i downloaded xml.zip and extracted it and flashed with fastboot.
Click to expand...
Click to collapse
Now I am back to EU retail firmware by reflashing. A few important things I've learnt, always update the latest firmware and don't stop researching until you've found an answer. This took me a good 8 hours to unbrick.

TooMuchPhoneProblems said:
I left it on fastboot for a very long period of time and it didn't seen to move from 0%. Anyway I somehow messed around and got the battery to 44% and got a TWRP built in. Now what?
Click to expand...
Click to collapse
install stock os for your phone. Check Motorola Firmwares

TooMuchPhoneProblems said:
I left it on fastboot for a very long period of time and it didn't seen to move from 0%. Anyway I somehow messed around and got the battery to 44% and got a TWRP built in. Now what?
Click to expand...
Click to collapse
Hi im kind of the same issue here, i can't charge my phone more than 4% how do you manage to make it to 44% i've got all the files right here but cannot flash CWM because it says (bootloader) Battery Low!!writing 'recovery'... (bootloader) Battery Low!! FAILED (remote failure)
I´ve already try the battery script and also a full night on fastboot connected to my PC, it does not recognize my wall charger...
Any help would be apreciatted

Help me out too!
TooMuchPhoneProblems said:
I left it on fastboot for a very long period of time and it didn't seen to move from 0%. Anyway I somehow messed around and got the battery to 44% and got a TWRP built in. Now what?
Click to expand...
Click to collapse
I'm having the same problem here. My battery was not charging at all and entering into Android resulted in shutting down of the device immediately. So decided to flash the stock firmware. But Battery was low in the bootloader. Tried to charge the battery normally by switching off the phone. The battery symbol and percentage shows up. But never moves up. Tried charging the phone in fastboot, but only when connected to PC, it says that its charging(but never charges and remains in "battery Low", Duh!). If i plug it into Wall charger, it wont say its charging and wont charge too.
So, can you explain me how exactly you "messed around" to get 44% of battery?. Please help me out. I've been trying to charge it for a whole day and expecting the message to turn "Battery OK". Explain me the way to get it charged, atleast for a stock firmware flash and for how many hours and in which mode should i leave it charged?.
Thanks!
BTW, i have TWRP installed, still no use.

xt925 bricked - flashing stops at system step

Few weeks ago my phone started closing apps every now and then, sometimes even restarting itself when under "heavy" load like opening Snapchat filters with face recognition for example (maybe the processor is failing?).
The reboot sometimes took 5 minutes, sometimes more. One time it took the phone 1 hour to reboot.
A few days ago it rebooted itself and got stuck on the M logo for hours, I waited literally until battery drained.
Anyways, I tried to flash Android back on it on fastboot mode with RSD but it always stops at the system img step.
It says "PHONE returned FAIL" on RSD.
My Bootloader is Unlocked btw. Battery says OK. Status Code says 3. Fastboot reason says Sticky bit fastboot after the RSD restarts the phone.
I have tried with 3 different files and all stop at flashing system step. I had flashed 4.4 on it before. My phone is originally from Telcel (Mexico)

mauber said:
Few weeks ago my phone started closing apps every now and then, sometimes even restarting itself when under "heavy" load like opening Snapchat filters with face recognition for example (maybe the processor is failing?).
The reboot sometimes took 5 minutes, sometimes more. One time it took the phone 1 hour to reboot.
A few days ago it rebooted itself and got stuck on the M logo for hours, I waited literally until battery drained.
Anyways, I tried to flash Android back on it on fastboot mode with RSD but it always stops at the system img step.
It says "PHONE returned FAIL" on RSD.
My Bootloader is Unlocked btw. Battery says OK. Status Code says 3. Fastboot reason says Sticky bit fastboot after the RSD restarts the phone.
I have tried with 3 different files and all stop at flashing system step. I had flashed 4.4 on it before. My phone is originally from Telcel (Mexico)
Click to expand...
Click to collapse
Did you ever solve this issue?? I've got pretty much the same issue here, except mine is bricked... Won't even turn on, but if I connect to my pc the led turns green and after a few minutes it turns on, straight to fastboot. Same fastboot reason and everything. When I try to flash with rsd, it stays at step 2, trying to flash the sbl1 file... Then it fails and says PHONE returned FAIL... Any info from anyone is greatly appreciated!!

Luisit0 said:
Did you ever solve this issue?? I've got pretty much the same issue here, except mine is bricked... Won't even turn on, but if I connect to my pc the led turns green and after a few minutes it turns on, straight to fastboot. Same fastboot reason and everything. When I try to flash with rsd, it stays at step 2, trying to flash the sbl1 file... Then it fails and says PHONE returned FAIL... Any info from anyone is greatly appreciated!!
Click to expand...
Click to collapse
Nope Gave up and getting a Moto G 3rd gen

mauber said:
Nope Gave up and getting a Moto G 3rd gen
Click to expand...
Click to collapse
Ahh darn... Well, hopefully someone else sees this thread and is able to help out... Thanks anyways!

Hello, Luisit0 if your battery went bad then it could do that. Did you try hitting the power button when device is plugged into the home charger of the wall outlet? If you get to the M logo when you do that then its just the battery. If It does not do that and nothing happens you need a fastboot cable so you can flash the stock firmware. the fastboot cable will allow you to go to fatsboot mode without a battery.

OGdroidster said:
Hello, Luisit0 if your battery went bad then it could do that. Did you try hitting the power button when device is plugged into the home charger of the wall outlet? If you get to the M logo when you do that then its just the battery. If It does not do that and nothing happens you need a fastboot cable so you can flash the stock firmware. the fastboot cable will allow you to go to fatsboot mode without a battery.
Click to expand...
Click to collapse
HI, thanks for the reply. The thing is, the phone won't even get to the M logo. It charges and everything, but it powers up and goes straight to fastboot... It even said battery low, and after a while plugged in, it said battery ok, so I guess it's charging right. But like I said, no matter what combination I use, even the volume up + power button, it only goes straight to fastboot... I've tried numerous times to flash the Brazil and PR latam firmwares, and even after deleting the getvar and the md5 lines, it still gives me an error on step 2 when attempting to flash the sbl1 file and says FAIL on rsd lite 6.1.4...

Luisit0 said:
HI, thanks for the reply. The thing is, the phone won't even get to the M logo. It charges and everything, but it powers up and goes straight to fastboot... It even said battery low, and after a while plugged in, it said battery ok, so I guess it's charging right. But like I said, no matter what combination I use, even the volume up + power button, it only goes straight to fastboot... I've tried numerous times to flash the Brazil and PR latam firmwares, and even after deleting the getvar and the md5 lines, it still gives me an error on step 2 when attempting to flash the sbl1 file and says FAIL on rsd lite 6.1.4...
Click to expand...
Click to collapse
I am going to give you a two download links one to download proper drivers and another link for another version of rsd to try and flash your device back to life but first i need to know if your running 64bit system or 32bit system.

OGdroidster said:
I am going to give you a two download links one to download proper drivers and another link for another version of rsd to try and flash your device back to life but first i need to know if your running 64bit system or 32bit system.
Click to expand...
Click to collapse
That would be perfect!! I'm running 64bit windows 8

Luisit0 said:
That would be perfect!! I'm running 64bit windows 8
Click to expand...
Click to collapse
first install the drivers download link Here http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663 then install them on your windows 8 then install this rsd version after you uninstall the one you currently have and here is the link http://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 if this does not work hit me up after monday im in the middle of finals and working on a big programming project due monday after that I can help you figure this out if this does not work.

OGdroidster said:
first install the drivers download link Here http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663 then install them on your windows 8 then install this rsd version after you uninstall the one you currently have and here is the link http://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 if this does not work hit me up after monday im in the middle of finals and working on a big programming project due monday after that I can help you figure this out if this does not work.
Click to expand...
Click to collapse
Great!! Thanks so much!! I'll try this as soon as I get home in a few minutes, and hit you up after. Thanks again!!
EDIT: Okay so just a little update... I installed the drivers and it seems those were exactly the ones I had already installed, then I installed rsd lite 6.2.4 which you provided... Who wouldve known it was all in the version lol I was using 6.1.5 and, apparently, all I needed was to update... 6.2.4 did the trick!! However, not exactly... The firmware did finally flash completely and successfully, however it still boots directly to fastboot. The difference is, I can now actually access the boot menu holding volume down + volume up + power buttons, though every option I select only makes the bootloader unlocked warning come up and freeze there until I manually turn the phone off holding down the power button. If I select Normal Powerup, after a few seconds the warning goes away, but it never boots up. The other difference is, that now on fastboot, the reason now says "Sticky bit factory_fastboot". I'm going to attempt and flash the same firmware again, or my claropr latam firmware, or pretty much any other latam firmware and see if one of them works. Thanks again so much for your help so far!!!!
EDIT 2: IT LIVES!!!!!! Lol using rsd lite v6.2.4 did the trick. Apparently all I needed was to use the latest version of rsd lite... Man, I honestly cant thank you enough, you saved me a few 3 digit bucks on a new phone!! Lol, thanks so much for all your help!!

Luisit0 said:
Great!! Thanks so much!! I'll try this as soon as I get home in a few minutes, and hit you up after. Thanks again!!
EDIT: Okay so just a little update... I installed the drivers and it seems those were exactly the ones I had already installed, then I installed rsd lite 6.2.4 which you provided... Who wouldve known it was all in the version lol I was using 6.1.5 and, apparently, all I needed was to update... 6.2.4 did the trick!! However, not exactly... The firmware did finally flash completely and successfully, however it still boots directly to fastboot. The difference is, I can now actually access the boot menu holding volume down + volume up + power buttons, though every option I select only makes the bootloader unlocked warning come up and freeze there until I manually turn the phone off holding down the power button. If I select Normal Powerup, after a few seconds the warning goes away, but it never boots up. The other difference is, that now on fastboot, the reason now says "Sticky bit factory_fastboot". I'm going to attempt and flash the same firmware again, or my claropr latam firmware, or pretty much any other latam firmware and see if one of them works. Thanks again so much for your help so far!!!!
EDIT 2: IT LIVES!!!!!! Lol using rsd lite v6.2.4 did the trick. Apparently all I needed was to use the latest version of rsd lite... Man, I honestly cant thank you enough, you saved me a few 3 digit bucks on a new phone!! Lol, thanks so much for all your help!!
Click to expand...
Click to collapse
So you were able to boot into your ROM.

OGdroidster said:
So you were able to boot into your ROM.
Click to expand...
Click to collapse
Yeah, finally it's back to life and working again. Turns out all I needed was to use the 6.2.4 version. Thanks for the link! I would've never thought it was just that :highfive:

Luisit0 said:
Yeah, finally it's back to life and working again. Turns out all I needed was to use the 6.2.4 version. Thanks for the link! I would've never thought it was just that :highfive:
Click to expand...
Click to collapse
Your welcome, happy that it booted. Awsome! You ever need something or some help just hit me up.

xt 925 bricked?
Hi together...
need help...I wanted to reactivate my RAZR HD.....I flashed the Stock without any problem -> then ota dowload....and then only Fastboot mode...
gratis bilder

Stuck at bootloader, can't get into recovery, bricked

I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.

llong31 said:
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
Click to expand...
Click to collapse
If you can access bootloader, you're still OK. Take a breath, grab a recent adb/fastboot download. The Minimal ADB 1.41 copy isn't the latest but it'll work for this purpose. Redo your flash-all.bat. Be patient. May need to flash boota and bootb if you receive errors about boot slots. Search for CZ Eddie's flash-all instructions if unsure.

llong31 said:
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
Click to expand...
Click to collapse
Download the toolkit and choose option to download and install the latest factory build and when it asks if you want to erase data type n (no) so you will not lose anything. Just make sure you are on the slot that was active which i believe u said was b

quangtran1 said:
If you can access bootloader, you're still OK. Take a breath, grab a recent adb/fastboot download. The Minimal ADB 1.41 copy isn't the latest but it'll work for this purpose. Redo your flash-all.bat. Be patient. May need to flash boota and bootb if you receive errors about boot slots. Search for CZ Eddie's flash-all instructions if unsure.
Click to expand...
Click to collapse
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result. The below is the same for boot_a and boot_b
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...

llong31 said:
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
Click to expand...
Click to collapse
Well, you're always welcome to send it to me. I'll fix it at no charge one time, plus shipping. I have a team of testers whose only tasks are to break phones, tablets, laptops just so we can put them back together.

llong31 said:
C:\Program Files (x86)\Minimal ADB and Fastboot
Click to expand...
Click to collapse
Get off of minimal and on to Google's fastboot. May not help but there have been a far number of problems with this phone and minimal to not try.

Sounds like when I lost a recovery in one slot doing a sideload in TWRP. I did the temp TWRP load and then added TWRP properly from there. No issues after.

llong31 said:
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result. The below is the same for boot_a and boot_b
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
Click to expand...
Click to collapse
I had to do the flash all once because I wiped the whole OS. I just ran it without specifying _a or _b and it worked like a charm. I think where to flash it is in the bat file so it puts it in the right place on its on. I didn't take out the -w to save my data.

TonikJDK said:
Get off of minimal and on to Google's fastboot. May not help but there have been a far number of problems with this phone and minimal to not try.
Click to expand...
Click to collapse
This was going to be my suggestion. It's all I ever use when flashing through fastboot.
Also, as I believe the above poster stated, I don't specify_a or_b when flashing stuff. It usually just works for me.
Hope you get it all working again. If you can access the bootloader, I believe you will be able to.

GeekMcLeod said:
This was going to be my suggestion. It's all I ever use when flashing through fastboot.
Also, as I believe the above poster stated, I don't specify_a or_b when flashing stuff. It usually just works for me.
Hope you get it all working again. If you can access the bootloader, I believe you will be able to.
Click to expand...
Click to collapse
I am not so sure minimal even supports dual partitions. It's latest version is from April. Long before all of this. Might be why people are getting in trouble. It works if you don't specify partition sometimes it seems....We might be on to something here.

quangtran1 said:
Well, you're always welcome to send it to me. I'll fix it at no charge one time, plus shipping. I have a team of testers whose only tasks are to break phones, tablets, laptops just so we can put them back together.
Click to expand...
Click to collapse
Interest to know what you do? Can I have a job

aholeinthewor1d said:
Interest to know what you do? Can I have a job
Click to expand...
Click to collapse
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to drivers to incompatibilities to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.

quangtran1 said:
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
Click to expand...
Click to collapse
That sounds awesome. Here I am doing tech support from home talking to miserable people all day. But yea it's crazy how quiet it is here. I don't really mean the development side of things either I just mean on general any time I've had new phones at release the forums were filled with people. Hoping after the holidays and as back orders are shipping we get some more people here that can figure this out.
I know I won't have an issue rooting and installing TWRP but I'm a little nervous to flash Roms before this is figured out. Especially because I don't stay on any single ROM that long I like to experiment.

aholeinthewor1d said:
That sounds awesome. Here I am doing tech support from home talking to miserable people all day. But yea it's crazy how quiet it is here. I don't really mean the development side of things either I just mean on general any time I've had new phones at release the forums were filled with people. Hoping after the holidays and as back orders are shipping we get some more people here that can figure this out.
I know I won't have an issue rooting and installing TWRP but I'm a little nervous to flash Roms before this is figured out. Especially because I don't stay on any single ROM that long I like to experiment.
Click to expand...
Click to collapse
Understandable.

quangtran1 said:
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to drivers to incompatibilities to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
Click to expand...
Click to collapse
Im sure you didnt mean it this way, but I didnt do anything to brick the phone, I wasnt flashing twrp or a rom or tinkering in any way. I was just using the camera. The more I'm reading, the more I'm thinking its an issue with 7.1.1 with pixels and nexus 6p's. I RMA'd this, we'll see what happens.
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.

llong31 said:
Im sure you didnt mean it this way, but I didnt do anything to brick the phone, I wasnt flashing twrp or a rom or tinkering in any way. I was just using the camera. The more I'm reading, the more I'm thinking its an issue with 7.1.1 with pixels and nexus 6p's. I RMA'd this, we'll see what happens.
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
Click to expand...
Click to collapse
There was absolutely no negative connotation in my comment. I stand by my experience that it is improbable to brick a smart phone. I'm just flabbergasted that it happens at all to anyone these days.

llong31 said:
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
Click to expand...
Click to collapse
Thank you for trying, and letting us know how it went. We are all still gathering info, and it's much appreciated. And glad they rma'd it.

TonikJDK said:
Thank you for trying, and letting us know how it went. We are all still gathering info, and it's much appreciated. And glad they rma'd it.
Click to expand...
Click to collapse
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).

llong31 said:
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
Click to expand...
Click to collapse
Sure, a corrupt system would certainly cause the battery replenishment logic to misbehave. It won't know when to fast charge, when to maintain, when to trickle, etc.

llong31 said:
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
Click to expand...
Click to collapse
Did you have an outdated fastboot binary? If you can still get in bootloader, I'd try with the good fastboot from the Android SDK.

Question Unknown IMEI & Relocking the Bootloader Using ADB [SOLVED]

Hello there
I bought my SM-A125F\DS a few months ago and rooted it. It was working fine. A few weeks ago, I changed my SIM card, made a phone call and put my phone aside and didn't check it for a couple of hours. When I picked it up again, I saw no antenna bars. Turns out I have no IMEI on either SIM slots (says Unknown in About Phone tab). Since I kept no backups, I download the latest ROM from Samfrew and flashed it using Odin. I also ticked Nand Erase and PIT reset. Still no IMEI. And now Android OS is eating 99% of my memory and it just keeps restarting.
Now I am trying to relock the bootloader using ADB before taking it to a service center. Connecting my phone and entering either one of
fastboot flashing lock, fastboot oem lock, and fastboot oem relock
gives me
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any help on either step of the way is much appreciated.
P.S. I am no tech savvy. The more detailed your answer, the better.

Cactus1ne said:
Hello there
I bought my SM-A125F\DS a few months ago and rooted it. It was working fine. A few weeks ago, I changed my SIM card, made a phone call and put my phone aside and didn't check it for a couple of hours. When I picked it up again, I saw no antenna bars. Turns out I have no IMEI on either SIM slots (says Unknown in About Phone tab). Since I kept no backups, I download the latest ROM from Samfrew and flashed it using Odin. I also ticked Nand Erase and PIT reset. Still no IMEI. And now Android OS is eating 99% of my memory and it just keeps restarting.
Now I am trying to relock the bootloader using ADB before taking it to a service center. Connecting my phone and entering either one of
fastboot flashing lock, fastboot oem lock, and fastboot oem relock
gives me
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any help on either step of the way is much appreciated.
P.S. I am no tech savvy. The more detailed your answer, the better.
Click to expand...
Click to collapse
I believe the bootloader is locked in much the same way it is unlocked. Reboot to download mode, hold one of the Volume buttons until the bootloader screen appears, and select the option to relock your device.
Before you do that, though, I would suggest performing a complete flash with data wipe using Odin.

@Cactus1ne
This IMEI bug could be due to rooting.
Try this guide, it helped many people.
Try this guide https://forum.xda-developers.com/t/...y-no-imei-no-sim.4386753/page-2#post-86588571

V0latyle said:
I believe the bootloader is locked in much the same way it is unlocked. Reboot to download mode, hold one of the Volume buttons until the bootloader screen appears, and select the option to relock your device.
Before you do that, though, I would suggest performing a complete flash with data wipe using Odin.
Click to expand...
Click to collapse
Thanks for the quick reply, much appreciated.
I have already tried complete data wipe using Odin; didn't work. But I had totally forgotten about the bootloader screen (rookie mistake). I'll definitely do that after trying what @Jerffelly suggested.

Jerffelly said:
@Cactus1ne
This IMEI bug could be due to rooting.
Try this guide, it helped many people.
Try this guide https://forum.xda-developers.com/t/...y-no-imei-no-sim.4386753/page-2#post-86588571
Click to expand...
Click to collapse
Worked like a charm. Much love to you and @dronkit for the detailed and easy-to-follow guide. I struggled a bit with the stuck on file analysis from Odin and device unauthorized from adb; nothing an xda forum search won't fix though.