Database Info

[Q] Stuck on Moto Logo

Hey there,
Was on Dexter's Froyo 1.2b. Phone froze up, had to pull battery.
After pulling the battery, it won't reboot. Just stays on the Moto logo forever.
Will not go into recovery mode, but will go into bootloader.
Tried flashing a few different ROMs onto it with RSD, no luck.
Any thoughts?
Thanks!

Charles Angus said:
Hey there,
Was on Dexter's Froyo 1.2b. Phone froze up, had to pull battery.
After pulling the battery, it won't reboot. Just stays on the Moto logo forever.
Will not go into recovery mode, but will go into bootloader.
Tried flashing a few different ROMs onto it with RSD, no luck.
Any thoughts?
Thanks!
Click to expand...
Click to collapse
try this
remove your sdcard and just leave sim card in our phone and boot..wait for it ..if after 10 minutes moto logo still there..pull out your battery and put it back into phone
press power button , press the Vol + button for 30 seconds as soon as the Moto Logo shows up
if you see the recovery option select the wipe data/ factory reset option and then reboot..

I had exactly the same problem (and a few people too)
sorry...but you can't do anything!
I tried to flash my phone numerous time, and can't get into recovery!
only solution is to send phone to motorola service
PS. this is 100% connected with dexter's froyo...so it would be nice that we collect some info why is this happening on some phones......

pajo985 said:
I had exactly the same problem (and a few people too)
sorry...but you can't do anything!
I tried to flash my phone numerous time, and can't get into recovery!
only solution is to send phone to motorola service
PS. this is 100% connected with dexter's froyo...so it would be nice that we collect some info why is this happening on some phones......
Click to expand...
Click to collapse
Did you end up sending yours out to motorola service? Were they able to fix your phone? I think resar also had a similar problem. http://forum.xda-developers.com/showthread.php?t=821210 (before Dexter's ROM)

It is wrong that there is no way to deal with that problem. I also had it a few weeks ago.
Method 1: http://forum.xda-developers.com/showthread.php?t=892026
Method 2: Get a second battery that is charged up ( at least 40 % or so..) and then get into the bootloader and reflash your custom ROM.
Method 3: Charge up your phone ( do not connect it to PC ) with the wall charger. When the phone wants to boot automatically, pull out the battery and set it in again. When the phone tries again to boot, pull the battery out and set it in again. My XT720 wanted to boot after 5-10 minutes or so when it was charging up. You should do that until your phone has enough battery to get into the bootloader.
In my opinion the problem is that the battery does not charge up anyway?
It worked for me with a second battery that was charged up for 50 % and then I reflashed custom ROM with RSD Lite.
Just ask if you don't understand anything
Did you get into RSD Lite & bootloader mode?

Knoedelkopf said:
It is wrong that there is no way to deal with that problem. I also had it a few weeks ago.
Method 1: http://forum.xda-developers.com/showthread.php?t=892026
Method 2: Get a second battery that is charged ( at least 40 % or so..) and then get into the bootloader and reflash your custom ROM.
Method 3: Charge your phone ( do not connect it to PC ) with the wall charger. When the phone wants to boot automatically, pull out the battery and set it in again. When the phone tries again to boot, pull the battery out and set it in again. My XT720 wanted to boot after 5-10 minutes or so when it was charged up. You should do that until your phone has enough battery to get into the bootloader.
In my opinion the problem is that the phone does not charge anyway?
It worked for me with a second battery that was charged up for 50 % and then I reflashed custom ROM with RSD Lite.
Just keep asking questions if you don't understand anything
Did you get into RSD Lite & bootloader mode?
Click to expand...
Click to collapse
Interesting! So, the idea is that when battery power is too low the flash is either ineffective or perhaps disabled by some low-level hardware check? It does seem plausible. I hope I don't ever have to try this.

battery is not a problem (at least in my case)
I have original milestone which have the same battery as xt, so I always charged battery at 100%...
motorola did repair my phone, but now I am afraid of flashing 2.2 back, because it will surely stuck at M logo again (I tried it two times already )
PS. tried flashing ALL available flashes (even original korean 2.2), and nothing happened..
I just couldn't boot into recovery

So when you got into the bootloader mode, was there shown something like "battery low cannot program"?
Or what do you mean exactly with "I just couldn't boot into recovery "?

Knoedelkopf said:
So when you got into the bootloader mode, was there shown something like "battery low cannot program"?
Or what do you mean exactly with "I just couldn't boot into recovery "?
Click to expand...
Click to collapse
We tried everything we could to save pajo's phone but nothing worked. resar is also extremely knowledgeable and had to send the phone to Motorola for repair. Pajo's thread has been merged into this mega thread, unfortunately:
http://forum.xda-developers.com/showthread.php?t=962744&page=1

Mine bricked today also using Dexter 1.3. This was my replacement phone (other one had audio jack issue, hardware not software). My battery died and couldn't get it to reboot, would just cycle the moto logo then sometime the dex froyo logo. I'm flashing back to stock right now,then reverting ti 1.2b was a more stable build.

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

Stuck In a boot loop after trying to downgrade from latest OTA.

So I started the journey of getting on the KKBL today, I sort of did it the long way, using the Droid HD Utility 2.0 I went all the way back to 4.1.2. That went smoothly, then I installed all the OTA's. I didn't realize that the latest OTA broke the ability to use towel root, and I couldn't find any way to root from the latest OTA, so I figured I'd just reflash back to 4.1.2 and start over...........
I guess that was the wrong answer, It is failing to flash, it's giving me an error on the fastboot screen that reads:
Fastboot reason: Flash Failure
Usb connected
Downgraded security version
update gpt_main version failed
preflash validation failed for GPT
invalid image size partition tz
Now when I try to turn it on I just get the unlocked bootloader warning, and it loops from there, never even starting a boot animation.
Please help?

captainlovesac said:
So I started the journey of getting on the KKBL today, I sort of did it the long way, using the Droid HD Utility 2.0 I went all the way back to 4.1.2. That went smoothly, then I installed all the OTA's. I didn't realize that the latest OTA broke the ability to use towel root, and I couldn't find any way to root from the latest OTA, so I figured I'd just reflash back to 4.1.2 and start over...........
I guess that was the wrong answer, It is failing to flash, it's giving me an error on the fastboot screen that reads:
Fastboot reason: Flash Failure
Usb connected
Downgraded security version
update gpt_main version failed
preflash validation failed for GPT
invalid image size partition tz
Now when I try to turn it on I just get the unlocked bootloader warning, and it loops from there, never even starting a boot animation.
Please help?
Click to expand...
Click to collapse
this should fix it.
after fixed, before downgrading again, you need to edit the xml on your stock file and remove the lines containing "gpt" and tz" or it will do the same thing again.

bweN diorD said:
this should fix it.
after fixed, before downgrading again, you need to edit the xml on your stock file and remove the lines containing "gpt" and tz" or it will do the same thing again.
Click to expand...
Click to collapse
First off thanks for reading and taking the time to try and help.
When it starts flashing, the first several lines in ADB fail.
sending 'partition' ...
OKAY [0.013s]
writing 'partition' ...
Battery Low!!
FAILED (remote failure)
It fails in that manner for: partition, sbl1, sbl2, sbl3, rpm, tz, modem, fsg, modemst1, modemst2, logo, and revovery.
Once it gets to "erasing user data" everything works from that point on, but the phone still won't boot.
Also i Can't turn it off. It automatically tries to boot constantly. Even if I hold power + volume down.
It had a full battery when i started yesterday, but it looks like it's not charging at this point.

captainlovesac said:
First off thanks for reading and taking the time to try and help.
When it starts flashing, the first several lines in ADB fail.
sending 'partition' ...
OKAY [0.013s]
writing 'partition' ...
Battery Low!!
FAILED (remote failure)
It fails in that manner for: partition, sbl1, sbl2, sbl3, rpm, tz, modem, fsg, modemst1, modemst2, logo, and revovery.
Once it gets to "erasing user data" everything works from that point on, but the phone still won't boot.
Also i Can't turn it off. It automatically tries to boot constantly. Even if I hold power + volume down.
It had a full battery when i started yesterday, but it looks like it's not charging at this point.
Click to expand...
Click to collapse
with a low battery, we dont know if it would flash or not. your going to have to somehow charge the battery, or make or buy a factory adapter to bypass the battery. https://www.youtube.com/watch?v=awYRazTmaXc

bweN diorD said:
with a low battery, we dont know if it would flash or not. your going to have to somehow charge the battery, or make or buy a factory adapter to bypass the battery. https://www.youtube.com/watch?v=awYRazTmaXc
Click to expand...
Click to collapse
Well I finally got my hands on a Factory Motorola cable, And I have the exact same issues. I left it plugged in on the fast boot screen all night, and it still says "battery low" . I'm assuming that the cable doesn't charge the battery, it just powers the phone?
I tried flashing again and got the exact same results as above. I think it's dead.

captainlovesac said:
Well I finally got my hands on a Factory Motorola cable, And I have the exact same issues. I left it plugged in on the fast boot screen all night, and it still says "battery low" . I'm assuming that the cable doesn't charge the battery, it just powers the phone?
I tried flashing again and got the exact same results as above. I think it's dead.
Click to expand...
Click to collapse
The factory cable won't charge.
Sent from my HTC6525LVW using Tapatalk

captainlovesac said:
Well I finally got my hands on a Factory Motorola cable, And I have the exact same issues. I left it plugged in on the fast boot screen all night, and it still says "battery low" . I'm assuming that the cable doesn't charge the battery, it just powers the phone?
I tried flashing again and got the exact same results as above. I think it's dead.
Click to expand...
Click to collapse
maybe try rsd with the latest firmware.
not sure what else to suggest.

bweN diorD said:
maybe try rsd with the latest firmware.
not sure what else to suggest.
Click to expand...
Click to collapse
I've got RSD set up but I'm having a hard time finding the latest firmware, do you have a link?

captainlovesac said:
I've got RSD set up but I'm having a hard time finding the latest firmware, do you have a link?
Click to expand...
Click to collapse
http://www.drdevs.com/devs/FXZ-files/XT926 (Droid RAZR HD)/
Sent from my HTC6525LVW using Tapatalk

RikRong said:
http://www.drdevs.com/devs/FXZ-files/XT926 (Droid RAZR HD)/
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks again for all your help.
RSD fails every time. As soon as I click start it just says "Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone Returned Fail.
I'm pretty convinced at this point that it's totally screwed.

captainlovesac said:
Thanks again for all your help.
RSD fails every time. As soon as I click start it just says "Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone Returned Fail.
I'm pretty convinced at this point that it's totally screwed.
Click to expand...
Click to collapse
edit that line out of the xml then try again. if other lines fail, edit them out too. after removing a few lines through trial and error, if its still failing right away, its probably done.

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

Battery not recognize Although when it is full

its fix now
SO... I did make some terrible mistake here and PLEASE stop saying it
I was dump .... to RELOCK bootloader
After that I put a RUU into sdcard and update AND THEN my screen just turn off after 5 seconds.
I wait for awhile but its not turn on So I force reboot into Download mode BUT its not work the icon battery with thunder symbol loading (battery die icon) I am sure battery was full before it.
Then I find out I may used wrong RUU (dump ep 2 -.-0)
I tried figure out and bring back download mode by flash hosd image but the battery problem cause I cannot used any command
All I needed is get out this battery issue to flash Stock RUU
So I can used flash command in Bootloader mode only
Please do not tell me to send to retail its not easy here and I buy this second hand device so I have nothing to gave them and I wanna know anyone can show me how to get away from this issue?
Thanks
Please stop "I don't know why RELOCK" I see a lot after I doing that T_T
Click to expand...
Click to collapse