I was already on stock 4.4.2. Used RSD to flash it when the phone was on JB. My phone's suddenly not botting anymore though. Just stock on the boot animation screen. I tried flashing back the same firmware, but I get "Phone Returned Failed" error on RSD lite every time
What can I do? My phone was completely stock. Bootloader wasn't unlocked.
*edit*: Boot animation runs fine. Then it's just stuck at the orb thingy which just keeps going.
pyromaniac1 said:
I was already on stock 4.4.2. Used RSD to flash it when the phone was on JB. My phone's suddenly not botting anymore though. Just stock on the boot animation screen. I tried flashing back the same firmware, but I get "Phone Returned Failed" error on RSD lite every time
What can I do? My phone was completely stock. Bootloader wasn't unlocked.
*edit*: Boot animation runs fine. Then it's just stuck at the orb thingy which just keeps going.
Click to expand...
Click to collapse
Need more details on "fail." Just saying it failed won't narrow down anything.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Need more details on "fail." Just saying it failed won't narrow down anything.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Tried flashing VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml, get this error.
pyromaniac1 said:
Tried flashing VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml, get this error.
Click to expand...
Click to collapse
you have to edit the xml file and completely remove the line containing "gpt" in that error. the partition table cant be changed/downgraded once upgraded.
bweN diorD said:
you have to edit the xml file and completely remove the line containing "gpt" in that error. the partition table cant be changed/downgraded once upgraded.
Click to expand...
Click to collapse
I did
still luck. Whatever item it tries to flash it returns the same error. I even deleted everything in between that to system.img. Gives the same error trying to flash system.img
pyromaniac1 said:
I did
still luck. Whatever item it tries to flash it returns the same error. I even deleted everything in between that to system.img. Gives the same error trying to flash system.img
Click to expand...
Click to collapse
try this, its not the same as the utility in the dev forum, its a modified version.
bweN diorD said:
try this, its not the same as the utility in the dev forum, its a modified version.
Click to expand...
Click to collapse
Flashed the XML with RSD lite. still the same error. Removed the GPT line and tried again. Same thing.
pyromaniac1 said:
Flashed the XML with RSD lite. still the same error. Removed the GPT line and tried again. Same thing.
Click to expand...
Click to collapse
Mmk, do not use rsd, use the bat file at the bottom of the directory. You defeated the purpose of it by using rsd.
Sent from my G2 running SlimKat
bweN diorD said:
Mmk, do not use rsd, use the bat file at the bottom of the directory. You defeated the purpose of it by using rsd.
Sent from my G2 running SlimKat
Click to expand...
Click to collapse
Ran the script twice. Managed to copy this the second time :/. Phone reboots after flashing is done and like before still stuck at the end of the boot animation.
[*] Press any key to continue.
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.328s
sending 'sbl1' (101 KB)...
OKAY [ 0.028s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.156s
sending 'sbl2' (126 KB)...
OKAY [ 0.029s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.155s
sending 'sbl3' (512 KB)...
OKAY [ 0.058s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.323s
sending 'rpm' (140 KB)...
OKAY [ 0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.279s
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.286s
sending 'aboot' (256 KB)...
OKAY [ 0.038s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.292s
sending 'modem' (30720 KB)...
OKAY [ 2.262s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.385s
sending 'fsg' (165 KB)...
OKAY [ 0.032s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.144s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.045s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.043s
sending 'logo' (854 KB)...
OKAY [ 0.081s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.200s
sending 'boot' (10240 KB)...
OKAY [ 0.751s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.468s
sending 'recovery' (10240 KB)...
OKAY [ 0.779s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.503s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.044s
sending 'system' (30720 KB)...
OKAY [ 3.806s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 5.397s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.045s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.044s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.006s
pyromaniac1 said:
Ran the script twice. Managed to copy this the second time :/. Phone reboots after flashing is done and like before still stuck at the end of the boot animation.
Click to expand...
Click to collapse
hmm, not good!
it looks like the hole phone is r/o when in fastboot. i have seen this before several times and have yet to see any one fix it.
i thought a few of those may fail, although you weren't actually downgrading any of them, they shouldn't have, but every writing and erasing command has failed. i was hoping that didn't happen.
we didn't try a factory reset but that's pointless, as the script tried it and it failed.
i dont think there is a way to fix this. maybe @SamuriHL has an idea.
just so you know Sam, the "modified" script i gave him a few post down uses moto fastboot to flash everything.
figured that was the best shot, if there was one, given what he already tried.
thanks
Without having read everything cause I'm pressed for time, my gut instinct says this:
USB cable (make sure it's the oem cable that came with the phone...yes, it matters), USB port (usb 2.0 NOT 3.0), or USB driver issue.
SamuriHL said:
Without having read everything cause I'm pressed for time, my gut instinct says this:
USB cable (make sure it's the oem cable that came with the phone...yes, it matters), USB port (usb 2.0 NOT 3.0), or USB driver issue.
Click to expand...
Click to collapse
thanks!
i hope its something that simple. since the other instances were unlocked devices running custom recovery (with other mitigating factors), this seems rarely fixable as none of the other causes for a true r/o situation apply here.
im afraid to tell him to try a fdr in recovery, as i have seen quite a few cases go worse lately for no reason.
maybe a simple fix is what is needed.
thanks for your input either way.
I always try simple before moving on to the hard stuff. To me it feels like a communication issue with the phone but I don't know for sure. It's a guess. I'd start there at the very least.
SamuriHL said:
I always try simple before moving on to the hard stuff. To me it feels like a communication issue with the phone but I don't know for sure. It's a guess. I'd start there at the very least.
Click to expand...
Click to collapse
Well a factory reset was the first thing I tried anyway. So no luck there. I've tried it with the OEM cable on my laptop as well as a different cable on my PC. Not sure about the USB 3.0 or 2.0 though. I have a lenovo x230 laptop with 2 USB 3.0 ports so ill try again and see if using those ports with the OEM cable makes a difference.
You can not use a USB 3 port. It will fail.
Sent from my SM-P600 using Tapatalk
Nope. Tried it on my PC and laptop both on the usb 2.0 port with the oem cable. Still the same
pyromaniac1 said:
Nope. Tried it on my PC and laptop both on the usb 2.0 port with the oem cable. Still the same
Click to expand...
Click to collapse
I would go an uninstall all drivers, reboot, and then reinstall the drivers and then hook your phone up again to see if that helps. Could be either drivers are corrupted or something else is hosed up.
Since you've tried it on two different computers and it failed, I'm assuming you used the same drivers on both machines? What version of the drivers are you using?
You might want to go to the moto site and get the Motorola helper to bring down the drivers.
i assume you've tried both RSD Lite and motofastboot?
SamuriHL said:
i assume you've tried both RSD Lite and motofastboot?
Click to expand...
Click to collapse
he did, several times.
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
SamuriHL said:
i assume you've tried both RSD Lite and motofastboot?
Click to expand...
Click to collapse
results from mfastboot are in post 9.
failed writing and or erasing at every step. i made the script for him, he posted the results.
even if a couple would have failed as writing equal code, they all wouldn't have as it flashes each separately.
Yea, not a situation I've seen before. Almost like the partition table is screwed up somehow so it doesn't know the mount points to flash to. Just for fun, let's try something.
Boot her up in AP Fastboot mode, connect it to USB 2.0, then try this:
o) From a cmd prompt, type: fastboot oem fb_mode_clear
o) Then flash the FXZ again either with motofastboot or RSD.
I'm just curious.
Related
I need some help right here. I have flashed XT925 by mistake with stock veryzon 4.1.2 (XT926 firmware). I'm stuck in fastboot mode, my Bootloader is LOCKED, thats really weird because I was unlocked before I've tried to update via OTA (my phone was bricked after that OTA update fail). I tried to flash Retail Brasil JB and some other firmwares via fastboot and RSD Lite 6.1.5 with no results... this is what my fastboot screen shows up:
---------------------o---------------------------------
Device is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
----------------------o---------------------------------
Hope you can help me :S
Are you sure you were unlocked? Seems to me you may be screwed.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
Are you sure you were unlocked? Seems to me you may be screwed.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Yes I'm sure, my status code was 3 not 0. What do you think I can do now? Is there any solution?
I remember seeing something about the gpt while searching for a solution for a different fastboot error. But like you I'm to lazy to search for it. Since it is your problem you probably should.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
I remember seeing something about the gpt while searching for a solution for a different fastboot error. But like you I'm to lazy to search for it. Since it is your problem you probably should.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
I don't know what to do, i tried a lot of possible solutions out there but I can't flash a single file to my phone. I've tried via fastboot and RSD 6.1.5 with no results, and I can't start recovery, just fastboot mode showing this screen:
Code:
Device is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
chuYxP said:
I don't know what to do, i tried a lot of possible solutions out there but I can't flash a single file to my phone. I've tried via fastboot and RSD 6.1.5 with no results, and I can't start recovery, just fastboot mode showing this screen:
Code:
Device is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
Click to expand...
Click to collapse
Make sure your phone is mostly charged and you are trying to flash the correct firmware. http://forum.xda-developers.com/showthread.php?t=2032284
mentose457 said:
Make sure your phone is mostly charged and you are trying to flash the correct firmware. http://forum.xda-developers.com/showthread.php?t=2032284
Click to expand...
Click to collapse
I tried the newest Retail Br, Telcel Mexico and one from Veryzon for XT926 with no results.
I can't flash anything in fastboot or in RSD Lite, so maybe I will take it to Telcel, they will send it to Motorola and let's see what they say. Hope they don't notice that I unlocked the bootloader, although it says that is LOCKED and status = 0... let's see what happens
Any other ideas? Please, there must be something to do to fix this.
chuYxP said:
Any other ideas? Please, there must be something to do to fix this.
Click to expand...
Click to collapse
Make sure your phone is recognized in fastboot mode. While in fastboot mode type the following in the command prompt:
Code:
fastboot devices
You should see the devices serial number in the output.
If that works type the following in the command prompt while in fastboot mode:
Code:
fastboot oem fb_mode_clear
Then type the following:
Code:
fastboot reboot-bootloader
When it reboots back into the bootloader attempt to flash the stock firmware again.
---------- Post added at 04:27 PM ---------- Previous post was at 04:20 PM ----------
chuYxP said:
Code:
Device is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
Click to expand...
Click to collapse
If this is truly what you get when you try to flash then I can guarentee your phone is not connected correctly. It should say USB Connected where it currently says Connect USB.
---------- Post added at 04:31 PM ---------- Previous post was at 04:27 PM ----------
Make sure the correct drivers are installed. You can get them from HERE. Note that windows will remove your drivers at will. So even if you had them installed before, install them again.
mentose457 said:
Make sure your phone is recognized in fastboot mode. While in fastboot mode type the following in the command prompt:
Code:
fastboot devices
You should see the devices serial number in the output.
If that works type the following in the command prompt while in fastboot mode:
Code:
fastboot oem fb_mode_clear
Then type the following:
Code:
fastboot reboot-bootloader
When it reboots back into the bootloader attempt to flash the stock firmware again.
---------- Post added at 04:27 PM ---------- Previous post was at 04:20 PM ----------
If this is truly what you get when you try to flash then I can guarentee your phone is not connected correctly. It should say USB Connected where it currently says Connect USB.
---------- Post added at 04:31 PM ---------- Previous post was at 04:27 PM ----------
Make sure the correct drivers are installed. You can get them from HERE. Note that windows will remove your drivers at will. So even if you had them installed before, install them again.
Click to expand...
Click to collapse
It doesn't work. I've just tried that and I just can't flash a single Rom. The "fastboot oem fb_mode_clear" command doesn't work, I can't clear my fastboot screen on my device.
Sorry but my phone its connected properly, it says usb connected at the end of the screen. I reinstalled drivers too, but nothing changes, so maybe I'm screwed.
chuYxP said:
It doesn't work. I've just tried that and I just can't flash a single Rom. The "fastboot oem fb_mode_clear" command doesn't work, I can't clear my fastboot screen on my device.
Sorry but my phone its connected properly, it says usb connected at the end of the screen. I reinstalled drivers too, but nothing changes, so maybe I'm screwed.
Click to expand...
Click to collapse
Did
Code:
fastboot devices
show your serial number?
Yes, here is it:
Code:
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot de
vices
208f36d2 fastboot
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot oe
m fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot re
boot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>
But nothing happened, the fastboot screen on device still shows the same.
chuYxP said:
Yes, here is it:
Code:
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot de
vices
208f36d2 fastboot
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot oe
m fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot re
boot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
C:\Development\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>
Click to expand...
Click to collapse
Thats good. Now use this utility to flash the stock rom. http://forum.xda-developers.com/forumdisplay.php?f=1866
Download the 'lite' version.
mentose457 said:
Thats good. Now use this utility to flash the stock rom. http://forum.xda-developers.com/forumdisplay.php?f=1866
Download the 'lite' version.
Click to expand...
Click to collapse
Do you mean Mr.Parkinsons DroidHD Utility 2.0? Ok I will try it right now, hope it works, thanks.
chuYxP said:
Do you mean Mr.Parkinsons DroidHD Utility 2.0? Ok I will try it right now, hope it works, thanks.
Click to expand...
Click to collapse
You are correct. Sorry about the bad link.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
You are correct. Sorry about the bad link.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
It's ok don't worry, I'm downloading the Lite version now (about 637 MB)
It doesn't worked, and my battery is dying, it says "Battery: Low" now
chuYxP said:
It doesn't worked, and my battery is dying, it says "Battery: Low" now
Click to expand...
Click to collapse
Power it off and charge it with a wall charger. I believe you cannot fastboot if the charge is below 50%.
Where does it fail? What does the utility say?
mentose457 said:
Power it off and charge it with a wall charger. I believe you cannot fastboot if the charge is below 50%.
Where does it fail? What does the utility say?
Click to expand...
Click to collapse
I can't charge with wall charger, my phone thinks that is a USB data cable and fastboot shows up... here is what the utility say:
Code:
*****************
* 4.1.2 Restore *
* by *
* Mr. Parkinson *
*****************
This program will restore your phone to Verizon stock Android 4.1.2.
It will also replace your custom recovery with stock, if you have one.
WARNING: THIS PROGRAM IS ONLY GUARANTEED FOR XT925/926 DEVICES (Droid Razr/Razr
Maxx HD)!
USE AT YOUR OWN RISK, EVEN BETTER, IF YOUR PHONE IS NOT AN XT925/926, DO NOT USE
THIS PROGRAM AT ALL.
Presione una tecla para continuar . . .
This program will now install stock 4.1.2 firmware to your device.
Before launching the utility, put your phone into Fastboot mode!
Turn of the phone, then, hold the vol-up and vol-down buttons,
while holding the power button, until the boot menu comes up.
Scroll down to AP FASTBOOT, and select it.
Presione una tecla para continuar . . .
sending 'sbl1' (101 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.075s
sending 'sbl2' (126 KB)...
OKAY [ 0.017s]
writing 'sbl2'...
Invalid partition name sbl2
FAILED (remote failure)
finished. total time: 0.076s
sending 'sbl3' (512 KB)...
OKAY [ 0.047s]
writing 'sbl3'...
Invalid partition name sbl3
FAILED (remote failure)
finished. total time: 0.106s
sending 'rpm' (140 KB)...
OKAY [ 0.019s]
writing 'rpm'...
Invalid partition name rpm
FAILED (remote failure)
finished. total time: 0.078s
sending 'tz' (192 KB)...
OKAY [ 0.022s]
writing 'tz'...
Invalid partition name tz
FAILED (remote failure)
finished. total time: 0.080s
error: cannot load 'VZW_XT926_4.1.2/emmc_appboot.mbn'
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
When the screen bcomes back on, press any key to continue!
Presione una tecla para continuar . . .
sending 'partition' (32 KB)...
OKAY [ 0.010s]
writing 'partition'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.148s
sending 'sbl1' (101 KB)...
OKAY [ 0.019s]
writing 'sbl1'...
Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl2' (126 KB)...
OKAY [ 0.018s]
writing 'sbl2'...
Invalid partition name sbl2
FAILED (remote failure)
finished. total time: 0.076s
sending 'sbl3' (512 KB)...
OKAY [ 0.047s]
writing 'sbl3'...
Invalid partition name sbl3
FAILED (remote failure)
finished. total time: 0.105s
sending 'rpm' (140 KB)...
OKAY [ 0.019s]
writing 'rpm'...
Invalid partition name rpm
FAILED (remote failure)
finished. total time: 0.077s
sending 'tz' (192 KB)...
OKAY [ 0.023s]
writing 'tz'...
Invalid partition name tz
FAILED (remote failure)
finished. total time: 0.081s
error: cannot load 'VZW_XT926_4.1.2/emmc_appboot.mbn'
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.847s
sending 'system' (30720 KB)...
OKAY [ 2.351s]
writing 'system'...
Battery Low!!
FAILED (remote failure)
finished. total time: 2.495s
sending 'recovery' (10240 KB)...
OKAY [ 0.788s]
writing 'recovery'...
Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.847s
sending 'modem' (30720 KB)...
OKAY [ 2.352s]
writing 'modem'...
Unkown partition name modem
FAILED (remote failure)
finished. total time: 2.412s
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
Invalid partition name devtree
FAILED (remote failure)
finished. total time: 0.106s
sending 'logo' (1709 KB)...
OKAY [ 0.139s]
writing 'logo'...
Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.198s
sending 'cdrom' (30720 KB)...
OKAY [ 2.352s]
writing 'cdrom'...
Unkown partition name cdrom
FAILED (remote failure)
finished. total time: 2.411s
erasing 'modemst1'...
Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.054s
erasing 'modemst2'...
Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.054s
sending 'fsg' (2704 KB)...
OKAY [ 0.216s]
writing 'fsg'...
Invalid partition name fsg
FAILED (remote failure)
finished. total time: 0.274s
erasing 'cache'...
Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.054s
erasing 'tombstones'...
Invalid partition name tombstones
FAILED (remote failure)
finished. total time: 0.054s
After this point, the utility will erase userdata.
It is recommended you do this, but not required.
Would you like to erase userdata? (Y/N CASE SENSITIVE)Y
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.054s
error: cannot load 'VZW_XT926_4.1.2/NON-HLOS'
erasing 'modemst1'...
Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.054s
erasing 'modemst2'...
Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.054s
rebooting...
finished. total time: 0.006s
You are now on stock 4.1.2 for XT925/926 devices!
Pressing any key will return to the main menu.
Presione una tecla para continuar . . .
chuYxP said:
I can't charge with wall charger, my phone thinks that is a USB data cable and fastboot shows up... here is what the utility say:
snip...[/CODE]
Click to expand...
Click to collapse
What are the errors you get when flashing the stock firmware for your carrier?
I was given a droid razr hd (xt926). Guy said he took an update and when the phone rebooted, it wouldn't go past the M boot screen. I don't know what build he was on and I don't know the previous status of the phone (root, rom, unlock, etc)
I can access AP Fastboot but I can't access anything else (Recovery, BP Tools, Factory).
I am using a Team Black Hat Cable, the most recent Motorola_End_User_Driver_Installation_6.4.0_32bit Driver, and a Windows 7 computer (my best computer is at ASUS getting fixed).
AP Fastboot Reads:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 03:15:48)
eMMC Info: Size 16GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
usb connected
______________________________________________________________________________
I first tried RSD Lite (using both 6.1.4 and 6.2.4 to flash VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I got:
Code:
Failed flashing process. 1/17 flash partition "gpt.bin" -> phone return FAIL
Trying VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml I had to delete the "getvar" line for it to begin BUT I also get the "gpt.bin" failed message here. If I delete steps in XML (get.bin, sbl1, sbl2, sbl3, etc) the process just gets hung up and fails on the next step
______________________________________________________________________________
Trying the most recent Matt's Utility, Mr.Parkinson's Utility, and SamuriHL's House of Moto (trying each build listed above) I get significant failed messages which I will post below.
Code:
Ready to flash...
Press any key to continue . . .
Flashing: UNIVERSAL.bat
sending 'sbl1' (101 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl2' (127 KB)...
OKAY [ 0.031s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.250s
sending 'rpm' (140 KB)...
OKAY [ 0.031s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.218s
sending 'aboot' (256 KB)...
OKAY [ 0.031s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.218s
sending 'modem' (30720 KB)...
OKAY [ 2.371s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.434s
sending 'fsg' (165 KB)...
OKAY [ 0.031s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.094s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
sending 'logo' (854 KB)...
OKAY [ 0.078s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.140s
sending 'boot' (10240 KB)...
OKAY [ 0.796s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.451s
______________________________________________________________________________
Trying to manually mfastboot in cmd, I get similar errors. I tried boot.img first and got this error
Code:
mfastboot.exe flash boot boot.img
sending 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED <remote failure>
finished. total time: 1.451s
Flashing gpt.bin partition
Code:
mfastboot flash partition gpt.bin
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.250s
Is the phone FUBAR or does anyone have a suggestion how I could fix this?
Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.
eckdawg5 said:
Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.
Click to expand...
Click to collapse
Sorry to be the bearer of bad news, just by looking at your screen shots, I can tell you it's hard bricked.
Sent from my VS985 4G
device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
About a month ago (~dec 16, 2014 I believe) the phone was lagging and unresponsive so I powered down, restarted, and that is when the problem began. Upon restart the phone got to the red motorola logo and would hang there. holding the power button would power down for a second, then restart.. so I soft reset it to the boot menu where it atleast wasnt heating up drastically. I left it plugged in because there was no way to power down. From there I began researching the xt926 and seeing other people's problems about the phone hanging at boot logo.
I scoured these forums (and numerous others) for problems similar to mine. Since I was able to get into the boot options menu I've tried everything I could find.. rsd lite, rsd flasher, motorola device manager, house of motorola, droid razr utility...
I tried for about 5 days straight and gave up, took it to a local cell repair place and asked what they would do to repair it. They mentioned a few of the things I tried and said that I had went further than they would go. Out of pity (I believe) they gave me an old BB curve which I've been using the last month. I've been shopping around lately for new phones and wanted to give the razr hd one last crack before relenting and getting a new phone (either S5 or HTC one M8).
First question I guess is, is the phone unusable and beyond repair? upon power up, the phone gets to the red motorola logo for about 2 seconds then goes to this presumed fail boot screen.
it lists:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 03:17:13)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode: USB Connected
Load kernel (boot) failed
Fastboot Reason: Boot Failure
I can restart the phone from here by clicking the power button, it restarts, hits logo screen, then right back here.
I can get to the boot selection screen by holding the volume up button when its restarting.. it'll get to the boot menu and then restart after about 3 seconds of idle time if I dont pick something quickly.. the 5 options at the boot selection are:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools
Normal Powerup, Factory, and BP Tools do nothing.. the phone restarts and hits logo screen then boot failure.
AP Fastboot restarts phone and goes to the same boot screen, but instead of the load kernel boot failure stuff it says: Fastboot Reason: Key Pressed. This is the same result as during powerup/restart holding the volume down key.
Recovery restarts, gets to logo screen, then after about 5 seconds gets to the droid dude with the red exclamation triangle over his open chest. From here I can get it into the recovery mode with 5 selections..
reboot system now
apply update from sdcard
apply update from ADB
wipe data/factory reset
wipe cache partition
All of that being said.. do I have any options to get this phone functional?
Your time and effort is greatly appreciated.
Cheers
I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?
i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
---------- Post added at 10:21 PM ---------- Previous post was at 10:14 PM ----------
randymancanstand said:
device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
Cheers
Click to expand...
Click to collapse
__
I appreciate the input, sorry for the delay in my response.
I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?
Click to expand...
Click to collapse
yes, I factory wiped and using rsd lite, droid razr utility, rsd flasher I tried many different images.. through different iterations and combinations. When rsd lite had no effect installing the different images I had, I moved onto a different program. I wasnt exactly sure which image the system required.. I went through the following:
VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
VZW_XT926_4.4.2-KDA20.62-10_1FF.xml
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I am unsure if they are 'factory' images
i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droi...46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
Click to expand...
Click to collapse
I am glad to hear that the phone may have a chance yet. I will look into the latest image. I have RSD Lite v6.2.4.. could someone remind me of the basic flash process?
connect the phone to my pc
put the phone into fastboot,
load up rsd lite
load up image in rsd lite
????
profit?
Again, thank you for your time.
edit: I also have motorola mobile driver 6.4.0 installed
RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..
randymancanstand said:
RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..
Click to expand...
Click to collapse
this may sound to simple but are you unziping the sbf/fxz?
billycar11 said:
this may sound to simple but are you unziping the sbf/fxz?
Click to expand...
Click to collapse
yes definitely
okay maybe your partitions are messed up then i have seen @bweN diorD help people with that before so he may be able to help.
randymancanstand said:
yes definitely
Click to expand...
Click to collapse
flash this in fastboot. use the data wipe batch file.
if the phone doesnt boot fully to the setup screen within 10min after flashing, its likely toast.
edit,
on second thought, dont close the prompt until you see if it boots up or not. if not, copy all the text from inside the prompt and post it here for me to look at.
thanks
The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction
randymancanstand said:
The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction
Click to expand...
Click to collapse
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time
randymancanstand said:
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time
Click to expand...
Click to collapse
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.
bweN diorD said:
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.
Click to expand...
Click to collapse
no dice...
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] Be VERY aware! This WILL wipe your userdata, including contacts, apps, etc.
[*] I am not responsible if this wipes your internal sdcard, and you should
[*] backup anything worth it to you to your external sdcard and computer before
[*] you choose to continue. You can exit now with the X button on this window.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] This script will also wipe your data (did i mention this will wipe your data
?).
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.340s
sending 'sbl1' (101 KB)...
OKAY [ 0.030s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl2' (127 KB)...
OKAY [ 0.030s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl3' (512 KB)...
OKAY [ 0.060s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.350s
sending 'rpm' (140 KB)...
OKAY [ 0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.300s
sending 'tz' (210 KB)...
OKAY [ 0.030s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.300s
sending 'aboot' (256 KB)...
OKAY [ 0.040s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.310s
sending 'modem' (30720 KB)...
OKAY [ 2.400s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.540s
sending 'fsg' (165 KB)...
OKAY [ 0.030s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.160s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.050s
sending 'logo' (854 KB)...
OKAY [ 0.090s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.220s
sending 'boot' (10240 KB)...
OKAY [ 0.810s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.550s
sending 'recovery' (10240 KB)...
OKAY [ 0.822s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.556s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
sending 'system' (30720 KB)...
OKAY [ 2.400s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 4.010s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.053s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.010s
Hit ENTER to return.
Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.
bweN diorD said:
Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.
Click to expand...
Click to collapse
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers
randymancanstand said:
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers
Click to expand...
Click to collapse
no one seems to know whats causing it. some have mods, some dont. the hole device just seems to become write protected for no reason.
stuck on logo boot
I can enter recovery mod, but I cant do nothing from there
it says 0 internal storage
here a pictures:
i58.tinypic.com/11al3xi.jpg
i59.tinypic.com/whz5v4.jpg
someone? any help
VanKS said:
someone? any help
Click to expand...
Click to collapse
Maybe help you
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
jordirpz said:
Maybe help you
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
Click to expand...
Click to collapse
Thank you for the respond!!
im getting this when im tryin to do it
and after it my nexus goes to boot loop
Code:
0606de650060d85d fastboot
erasing 'system'...
OKAY [ 0.117s]
sending 'system' (721400 KB)...
OKAY [ 22.793s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 23.093s
sending 'recovery' (9284 KB)...
OKAY [ 0.505s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.685s
sending 'boot' (8700 KB)...
OKAY [ 0.485s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.667s
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.288s
your Nexus 5 hammerhead 4.4 Restore Installer is now restored! :)
rebooting...
finished. total time: 0.086s
Press any key to continue . . .
VanKS said:
Thank you for the respond!!
im getting this when im tryin to do it
and after it my nexus goes to boot loop
Code:
0606de650060d85d fastboot
erasing 'system'...
OKAY [ 0.117s]
sending 'system' (721400 KB)...
OKAY [ 22.793s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 23.093s
sending 'recovery' (9284 KB)...
OKAY [ 0.505s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.685s
sending 'boot' (8700 KB)...
OKAY [ 0.485s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.667s
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.288s
your Nexus 5 hammerhead 4.4 Restore Installer is now restored! :)
rebooting...
finished. total time: 0.086s
Press any key to continue . . .
Click to expand...
Click to collapse
Use dead method
jordirpz said:
Use dead method
Click to expand...
Click to collapse
can you explain or give me a link?
VanKS said:
can you explain or give me a link?
Click to expand...
Click to collapse
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
---------- Post added at 12:06 AM ---------- Previous post was at 12:05 AM ----------
INSTRUCTIONS:
1) If for whatever reason you don't already have your drivers installed on your PC, download and*install*DRIVERS*(Win 8 Driver instructions included).
2) Download and extract*Restore_Nexus_5_KTU84P.zip*
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the phone)
4) Open up folder where you extracted theRestore_Nexus_5_KTU84P.zip*
5) Double Click on the "Recovery_Nexus5.bat" and follow the instructions,,,,it really is that easy!*(watch video and follow along)
6)*If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power), connect phone to PC, and click the "Dead_Nexus5.bat" file found in the folder.
jordirpz said:
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
---------- Post added at 12:06 AM ---------- Previous post was at 12:05 AM ----------
INSTRUCTIONS:
1) If for whatever reason you don't already have your drivers installed on your PC, download and*install*DRIVERS*(Win 8 Driver instructions included).
2) Download and extract*Restore_Nexus_5_KTU84P.zip*
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the phone)
4) Open up folder where you extracted theRestore_Nexus_5_KTU84P.zip*
5) Double Click on the "Recovery_Nexus5.bat" and follow the instructions,,,,it really is that easy!*(watch video and follow along)
6)*If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power), connect phone to PC, and click the "Dead_Nexus5.bat" file found in the folder.
Click to expand...
Click to collapse
I tried it already, thought you mean to something else :<
Any suggestions ?
VanKS said:
Any suggestions ?
Click to expand...
Click to collapse
bump
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
FkReMy said:
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
Click to expand...
Click to collapse
From what I found on the internet, I guess you didn't turn on the setting `oem allow unlock' in developer settings.
But isn't there `rescue party' (a subsystem of androids recovery which shows two options: 1) Try again 2) Factory data reset)?
If it is, just press that Try again button, wait until it boots into rescue party again and then press the Try again button again. Do that 5-7 times in a row (depending on the phone). Your phone should detect that your current slot is unbootable and should boot into the unupdated slot.
You could also try to find the stock image (or whatever image you have currently installed) and flash it within recovery (there should be a button labeled like `update...' or `sideload...' or something). That should also work.
If nothing helps, you could also factory data reset and hope that it works now...
If that also doesn't work, you could research abit about edl (emergency donwload mode) and how to use it to reflash your device.