I need help, please. My phone is stuck in AP fastboot flash mode (s)
At the bottom, it says:
load kernel (boot) failed
fastboot reason: boot failure
usb connected
phone was fine this morning, when i went to unplug it, it woke up and stated that my Nova launcher has forced closed. I rebooted the phone and this happened. I tried to reflash through rsd lite with oem 4.1.2 and it results in a failure. I had 4.4.2 but figured I'd go back to JB
I can get to the boot menu but every option takes me back to this screen, now it says 'invalid flash mode (s)'
Any thoughts on this? I'm lost.....
Thank you for your time.
davfed said:
I need help, please. My phone is stuck in AP fastboot flash mode (s)
At the bottom, it says:
load kernel (boot) failed
fastboot reason: boot failure
usb connected
phone was fine this morning, when i went to unplug it, it woke up and stated that my Nova launcher has forced closed. I rebooted the phone and this happened. I tried to reflash through rsd lite with oem 4.1.2 and it results in a failure. I had 4.4.2 but figured I'd go back to JB
I can get to the boot menu but every option takes me back to this screen, now it says 'invalid flash mode (s)'
Any thoughts on this? I'm lost.....
Thank you for your time.
Click to expand...
Click to collapse
some things we will need to know to help you:
- do you have a 926 or 925?
-what is your system version?
-if you dont know the above, when was the last time you took an update?
-what exactly did you try to flash to fix this? provide links please.
-what is the state of your phone now? can connect to pc? can boot? not boot? to what can you access if no boot?
-can you tell me what your fastboot screen says? power the phone off, hold the three vol and power buttons, release all 3 when you see the menu, and report the results.
respond with this info, and we will fix you right up
bweN diorD said:
some things we will need to know to help you:
- do you have a 926 or 925?
-what is your system version?
-if you dont know the above, when was the last time you took an update?
-what exactly did you try to flash to fix this? provide links please.
-what is the state of your phone now? can connect to pc? can boot? not boot? to what can you access if no boot?
-can you tell me what your fastboot screen says? power the phone off, hold the three vol and power buttons, release all 3 when you see the menu, and report the results.
respond with this info, and we will fix you right up
Click to expand...
Click to collapse
Thank you so much for offering to help!!!
I have the 926. I had trouble about 6 weeks ago and flashed 4.4.2 from this page http://sbf.droid-developers.org/phone.php?device=5
A few weeks later i took an OTA update to the .15 version, im sorry but I don't know the rest.
Today after my phone froze, i tried to flash first the 4.1.2 without success than the 4.4.2. both from the above link and both failed.
I can connect to the PC. i can get to the boot menu but all options take me to the fastboot screen.
now it says:
Invalid flash mode (s)
10.9b(*) (sha-61146a2, 2014-07-29 08:54:49)
eMMC info: size 16gb
device is unlocked status code 3
battery OK
transfer mode:
usb connected
load kernel (boot) failed
fastboot reason: boot failure
after i try to reboot it, the top line changes to 'AP fastboot flash mode (s)'
hope this is what you need
davfed said:
Thank you so much for offering to help!!!
I have the 926. I had trouble about 6 weeks ago and flashed 4.4.2 from this page http://sbf.droid-developers.org/phone.php?device=5
A few weeks later i took an OTA update to the .15 version, im sorry but I don't know the rest.
Today after my phone froze, i tried to flash first the 4.1.2 without success than the 4.4.2. both from the above link and both failed.
I can connect to the PC. i can get to the boot menu but all options take me to the fastboot screen.
now it says:
Invalid flash mode (s)
10.9b(*) (sha-61146a2, 2014-07-29 08:54:49)
eMMC info: size 16gb
device is unlocked status code 3
battery OK
transfer mode:
usb connected
load kernel (boot) failed
fastboot reason: boot failure
after i try to reboot it, the top line changes to 'AP fastboot flash mode (s)'
hope this is what you need
Click to expand...
Click to collapse
That's good,
Just a few more questions now that we have that info.
- how did you try to 're-flash? Rsd or fastboot method?
- if Rsd, did you edit the xml file first?
- do you remember what the script said when it failed?
- are you concerned with trying to save data? May not be possible, but we can try first if you are.
You phone indicates its unlocked, so you should be able to flash whatever you want as long as your doing it right. Hopefully the script is just failing because of some code that needs to be removed and not write errors, that would be bad.
bweN diorD said:
That's good,
Just a few more questions now that we have that info.
- how did you try to 're-flash? Rsd or fastboot method?
- if Rsd, did you edit the xml file first?
- do you remember what the script said when it failed?
- are you concerned with trying to save data? May not be possible, but we can try first if you are.
You phone indicates its unlocked, so you should be able to flash whatever you want as long as your doing it right. Hopefully the script is just failing because of some code that needs to be removed and not write errors, that would be bad.
Click to expand...
Click to collapse
I did use rsd lite
I have no idea why or how to edit the xml file
all i did was download the file, find it and decompress and flash. that is the way it worked for the the last time i had to do this when it was stuck in the boot animation. it worked the first time and that is the only experience i have with flashing.
I don't remember what it said other than a fail
I do not care about data at this point. most of what i need is backed up.
davfed said:
I did use rsd lite
I have no idea why or how to edit the xml file
all i did was download the file, find it and decompress and flash. that is the way it worked for the the last time i had to do this when it was stuck in the boot animation. it worked the first time and that is the only experience i have with flashing.
I don't remember what it said other than a fail
I do not care about data at this point. most of what i need is backed up.
Click to expand...
Click to collapse
This will be pretty easy to fix.
- extract the kk zip to a folder
- inside find the .xml file, right click and edit
- completely delete any lines containing "getvar", "tz", and "gpt"
- close the .xml file and choose save at the prompt
- flash with Rsd using the edited xml file as the target.
That should fix things good as new.
bweN diorD said:
This will be pretty easy to fix.
- extract the kk zip to a folder
- inside find the .xml file, right click and edit
- completely delete any lines containing "getvar", "tz", and "gpt"
- close the .xml file and choose save at the prompt
- flash with Rsd using the edited xml file as the target.
That should fix things good as new.
Click to expand...
Click to collapse
will this work for the JB file also, or only the KK?
Ive been very unhappy with KK
davfed said:
will this work for the JB file also, or only the KK?
Ive been very unhappy with KK
Click to expand...
Click to collapse
Sure, you can do the same to the jb file.
You will want to root afterwards and freeze the updater so it's not constantly annoying you.
I'm sorry to be so new at this. I'm not seeing getvar, tz, or gpt in the .xml file
here is the file
<?xml version="1.0" encoding="UTF-8"?>
-<flashing>
-<header>
<phone_model model="TARGA"/>
<software_version version="5.5.1_84_DBN-74"/>
-<interfaces>
<interface name="AP"/>
</interfaces>
</header>
-<steps interface="AP">
<step MD5="f6102e4b34c74cfefd5e80151a6913ff" filename="allow-mbmloader-flashing-mbm.bin" partition="mbm" operation="flash"/>
<step operation="reboot-bootloader"/>
<step MD5="b0c30799c8509c4d66599550e3fbdd82" filename="mbmloader.bin" partition="mbmloader" operation="flash"/>
<step MD5="da0b9ae7f38048a2987e0ae24593fb4b" filename="mbm.bin" partition="mbm" operation="flash"/>
<step operation="reboot-bootloader"/>
<step MD5="fd8c44b060415dfd963fa870ae7a4f35" filename="cdt.bin" partition="cdt.bin" operation="flash"/>
<step partition="cache" operation="erase"/>
<step partition="userdata" operation="erase"/>
<step partition="emstorage" operation="erase"/>
<step MD5="239bbc49a9cdb329577074ba60bbf1e5" filename="lbl" partition="lbl" operation="flash"/>
<step MD5="06c07c2970460a4e656a3206859a3617" filename="logo.bin" partition="logo.bin" operation="flash"/>
<step MD5="4c6df9afcd64661036a982e03eb1aa1a" filename="ebr" partition="ebr" operation="flash"/>
<step MD5="712e3e3757219ecfd925eb43be14f944" filename="mbr" partition="mbr" operation="flash"/>
<step MD5="2404a4f245f1da389d3422d0d59be24a" filename="device_tree.bin" partition="devtree" operation="flash"/>
<step MD5="8e306ac58dd4fcf01566c517eabc098d" filename="system.img" partition="system" operation="flash"/>
<step MD5="b64b38a48897c51fe229cf80a095d235" filename="boot.img" partition="boot" operation="flash"/>
<step MD5="ce9ee505c7fc708f7394617907ae5694" filename="recovery.img" partition="recovery" operation="flash"/>
<step MD5="6bdf130ecaa5183c0e463d2f3fa5d966" filename="cdrom" partition="cdrom" operation="flash"/>
<step MD5="f7f2ff434d2b0c819c1e28744d1b4d01" filename="preinstall.img" partition="preinstall" operation="flash"/>
<step MD5="953494fd0d356f25a58842f1a41b132d" filename="emstorage.img" partition="emstorage" operation="flash"/>
<step MD5="c9502cd8fd6fa7206c64e4dae3ed9b50" filename="grfs.img" partition="webtop" operation="flash"/>
<step MD5="683184cc2522ba00e6a0c38d321a8806" filename="radio.img" partition="radio" operation="flash"/>
</steps>
</flashing>
davfed said:
I'm sorry to be so new at this. I'm not seeing getvar, tz, or gpt in the .xml file
Click to expand...
Click to collapse
That doesn't look right. Targa came back as the bionic when I searched it.
Just go to the General forum here and look down the first page for my Guide.
The newest JB file is in there near the bottom of the OP. Its already edited, so you can flash as is.
I tried what you said and got another failure. I'm not sure if I'm doing something wrong. I will try again tho. I attached a pic of the end result.
davfed said:
I tried what you said and got another failure. I'm not sure if I'm doing something wrong. I will try again tho. I attached a pic of the end result.
Click to expand...
Click to collapse
i cant believe i forgot to delete the getvar line and with 600 downloads, no one mentioned it. im downloading now to verify.
---------- Post added at 07:46 PM ---------- Previous post was at 07:28 PM ----------
bweN diorD said:
i cant believe i forgot to delete the getvar line and with 600 downloads, no one mentioned it. im downloading now to verify.
Click to expand...
Click to collapse
nope, not my file, mine is clean and ready to roll.
http://www.mediafire.com/download/gia5kc742fodt53/VRZ_XT926_9.8.1Q-94-1_CFC.xml.rar
this is the link I used from your post that you described. You had it linked 'here' I copied the page url and posted at above.
davfed said:
http://www.mediafire.com/download/gia5kc742fodt53/VRZ_XT926_9.8.1Q-94-1_CFC.xml.rar
this is the link I used from your post that you described. You had it linked 'here' I copied the page url and posted at above.
Click to expand...
Click to collapse
here is the code directly from my file, you mut have something mixed up. i would delete all the other firmwares then re extract the file so there is no confusion.
BTW, the guide is in my sig
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="VANQUISH_CFC_IFLASH" />
<software_version version="vanquish_vzw-user 4.1.2 9.8.1Q-94-1 57 release-keysVANQUISH_BP_100730.151.64.17P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="BB624DBDA3BE7B433AFC4D0123B33491" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="68CB15F37E13BBD8277EB3429FCC871D" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="86C984B56AE4EE83AB0AE2B7525CCF1E" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="0C3F4FF07D3B5037E17B8EFE5F4C66EE" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="F9F828A07EFF5ACA78C51E60EC6A0391" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="BB624DBDA3BE7B433AFC4D0123B33491" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="68CB15F37E13BBD8277EB3429FCC871D" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="86C984B56AE4EE83AB0AE2B7525CCF1E" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="0C3F4FF07D3B5037E17B8EFE5F4C66EE" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="F9F828A07EFF5ACA78C51E60EC6A0391" />
<step operation="flash" partition="boot" filename="boot.img" MD5="70A4C7CC93E3C2CBC37B6DAA6BDA2E74" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="9D7F66A977550FF3496EBDAD79511CDE" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="0B2F9307E348E9CA0A0B11A29BCA28C1" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="82BE40595235096DCE6E20796DD39444" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="01CCD38F085EBEFE1080223FC62A5415" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="6463DC057ABF889F3B83A4D3DA4CDD1E" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="E01BB8745EE1529BD1DB7289EE38B2E1" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="9E38AECE800CB17548D62D4457100AF8" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="tombstones" />
</steps>
I did what you said and deleted everything redownloaded your file with the same result.
Then I thought I would upgrade from rsd lite v6.1.5 to 6.1.6 that you had. Different failure this time see attached
davfed said:
I did what you said and deleted everything redownloaded your file with the same result.
Then I thought I would upgrade from rsd lite v6.1.5 to 6.1.6 that you had. Different failure this time see attached
Click to expand...
Click to collapse
i dont know what to tell you, i and others have done it many times without issue.
the first error was "getvar" thats 100% not possible as the code is not in there.
the errors you are getting now.... no idea why...
il think about it and test some things and get back to you later.
davfed said:
I did what you said and deleted everything redownloaded your file with the same result.
Then I thought I would upgrade from rsd lite v6.1.5 to 6.1.6 that you had. Different failure this time see attached
Click to expand...
Click to collapse
ok, i just flashed mine from the latest kk to the jb file in my guide using rsd no problem.
ok so lets back up again. make a new folder where you keep all your downloads and put all the firmwares you have in there so there out of the way.
download this file, extract it, put your phone in fastboot, plug to pc, run the windows batch file then option 1 and if there are any errors, copy the entire output and post it here.
if the phone boots normally,
power off, put back into fastboot, download and extract this file and run it with rsd. if it fails, post the results.
if step 1 fails, you can try step 2 just for giggles, but it will likely fail.
bweN diorD said:
ok, i just flashed mine from the latest kk to the jb file in my guide using rsd no problem.
ok so lets back up again. make a new folder where you keep all your downloads and put all the firmwares you have in there so there out of the way.
download this file, extract it, put your phone in fastboot, plug to pc, run the windows batch file then option 1 and if there are any errors, copy the entire output and post it here.
if the phone boots normally,
power off, put back into fastboot, download and extract this file and run it with rsd. if it fails, post the results.
if step 1 fails, you can try step 2 just for giggles, but it will likely fail.
Click to expand...
Click to collapse
I tried with data wipe and without. Both failed. I also tried the file for rsd and it also failed.
here are the results.
[*] 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.350s
sending 'sbl1' (101 KB)...
OKAY [ 0.020s]
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.170s
sending 'sbl3' (512 KB)...
OKAY [ 0.050s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.510s
sending 'rpm' (140 KB)...
OKAY [ 0.040s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.470s
sending 'tz' (210 KB)...
OKAY [ 0.040s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.480s
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.480s
sending 'modem' (30720 KB)...
OKAY [ 2.390s]
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.170s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.070s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
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.100s
sending 'recovery' (10240 KB)...
OKAY [ 0.810s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.110s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.070s
sending 'system' (30720 KB)...
OKAY [ 2.392s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 2.622s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
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. 1
Here is the screen that the HD is stuck in. Just so we are clear. I can get to the boot menu where I can select recovery, factory reset, normal startup and a few others, but all options bring me back to this.
Related
Attempted to use the RAZR HD Utility to reset back to 4.1.2 and it failed in the process I think. I rebooted the phone and now it just gets stuck on the Welcome screen. After I press continue on the welcome screen it just goes into an infinite loading of "Please wait this may take a while...". I can access the settings page from it and I know my phone is on System Version 9.30.1.XT926 Verizon en US, I am on android version 4.1.2 but the baseband version is unknown. How do I factory reset this thing or get past the welcome screen? I can access the launcher when using the Volume UP+Down and Power button to get into fastboot and recovery but I am unsure of where to go from here!
To clear anything up, I am currently unable to boot to android. I am stuck in fastboot. I attempt to fastboot the boot.img or system.img and it just hangs on writing to the device. If I attempt to use the Razr HD Utility I get:
Preflash validation failed
FAILED (remote Failure)
When flashing the system.img
When I attempt to use RSD Lite 6.1.5 it hangs on flash boot "boot.img" 15/27
All my md5sums match.
re-download the utility and flash it again. something didnt flash properly, and no reset will will fix it.
bweN diorD said:
re-download the utility and flash it again. something didnt flash properly, and no reset will will fix it.
Click to expand...
Click to collapse
So I should delete the utility completely and run option 1 again?
ryudragoon said:
So I should delete the utility completely and run option 1 again?
Click to expand...
Click to collapse
Yes, delete the utility, re-download it, then run option 1 again.
Sent from my LG-VS980 using Tapatalk
bweN diorD said:
Yes, delete the utility, re-download it, then run option 1 again.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Attempted this and I got this output:
Code:
sending 'system' (30720 KB)...
OKAY [ 2.322s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.468s
sending 'boot' (10240 KB)...
OKAY [ 0.781s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.938s
The output on the phone:
Code:
Partition (system) Security Version Downgraded
PIV block Validation for system failed
Invalid PIV image: system
Partition (boot) Security Version Downgraded
Preflash validation failed for boot
try this utility instead, there is only one option.
https://www.dropbox.com/s/bpjghbbv0v6r4v5/DROID_RAZR_HD_Utility_1.3.gpt fix.rar
bweN diorD said:
try this utility instead, there is only one option.
https://www.dropbox.com/s/bpjghbbv0v6r4v5/DROID_RAZR_HD_Utility_1.3.gpt fix.rar
Click to expand...
Click to collapse
Not sure what happened here everything was going fine...
Code:
sending 'system' (30720 KB)...
OKAY [ 2.321s]
writing 'system'...
FAILED (status read failed (Unknown error))
finished. total time: 122.521s
< waiting for device >
sending 'boot' (10240 KB)...
OKAY [ 0.789s]
writing 'boot'...
ryudragoon said:
Attempted this and I got this output:
Code:
sending 'system' (30720 KB)...
OKAY [ 2.322s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.468s
sending 'boot' (10240 KB)...
OKAY [ 0.781s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.938s
The output on the phone:
Code:
Partition (system) Security Version Downgraded
PIV block Validation for system failed
Invalid PIV image: system
Partition (boot) Security Version Downgraded
Preflash validation failed for boot
Click to expand...
Click to collapse
Use rsd lite & delete the lines in the xml with getvar.
you have a 926 correct?
that tool re-wrote the partitions, i dont know why it would fail after they were clean. im not sure that else to tell you to try.
bweN diorD said:
you have a 926 correct?
that tool re-wrote the partitions, i dont know why it would fail after they were clean. im not sure that else to tell you to try.
Click to expand...
Click to collapse
I posted the wrong output please recheck my post.
aviwdoowks said:
Use rsd lite & delete the lines in the xml with getvar.
Click to expand...
Click to collapse
How would I go about doing this?
http://forum.xda-developers.com/showpost.php?p=49375230&postcount=7
ryudragoon said:
I posted the wrong output please recheck my post.
How would I go about doing this?
Click to expand...
Click to collapse
One uses the ...xml.zip unzipped btw.
Edit the xml with notepad or almost anything.
You then choose the modded xml from rsd lite(...) button.
bweN diorD said:
http://forum.xda-developers.com/showpost.php?p=49375230&postcount=7
Click to expand...
Click to collapse
I have the Razr Maxx HD. None of these are what I am looking for.
I think http://sbf.droid-developers.org/phone.php?device=5 is what I am looking for but I am unsure of which one to get.
it tells you to go to that ppage for the 926 if you read to the bottom.
you want the last file.
ryudragoon said:
I have the Razr Maxx HD. None of these are what I am looking for.
I think http://sbf.droid-developers.org/phone.php?device=5 is what I am looking for but I am unsure of which one to get.
Click to expand...
Click to collapse
The newest
http://sbf.droid-developers.org/download.php?device=5&file=75
aviwdoowks said:
The newest
http://sbf.droid-developers.org/download.php?device=5&file=75
Click to expand...
Click to collapse
which would be the last file on that page, like i said.
I have done everything correctly and when I use RSD lite v6.1.5 everything goes smoothly but it hangs or doesn't seem to progress past 15/27 flash boot "boot.img"
It seems that it doesn't want to write the boot.img to the phone.
I think I have narrowed it down to maybe a corrupt /system because it refuses to write or erase it from fastboot.
i wish i could help you but im not sure what else to tell you to try.
the only time i have seen the partition script i gave you not fix the problem is when twrp screwed up the partitions beyond repair.
ryudragoon said:
I have done everything correctly and when I use RSD lite v6.1.5 everything goes smoothly but it hangs or doesn't seem to progress past 15/27 flash boot "boot.img"
It seems that it doesn't want to write the boot.img to the phone.
I think I have narrowed it down to maybe a corrupt /system because it refuses to write or erase it from fastboot.
Click to expand...
Click to collapse
This guy will know what to do: @cellzealot !
He follows his mentions.
You could pm him.
aviwdoowks said:
This guy will know what to do: cellzealot !
He follows his mentions.
You could pm him.
Click to expand...
Click to collapse
I have the same issue, please HELP ME!
My phone is Stuck on Encryption Unsuccessful. I can log in to bootloader but I get partition Errors when I try to flash anything.
I have posted several times but to no response. Someone must be able to help?
http://forum.xda-developers.com/showthread.php?p=51115231
http://forum.xda-developers.com/showthread.php?t=2616191
aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2616191
Click to expand...
Click to collapse
The xt925 is not listed as being supported, but I am happy to try anything at this stage! Will report back.
is0lde said:
The xt925 is not listed as being supported, but I am happy to try anything at this stage! Will report back.
Click to expand...
Click to collapse
House of Moto can support just about Moto device that has a FXZ available, and FXZs are available for the 925.
is0lde said:
The xt925 is not listed as being supported, but I am happy to try anything at this stage! Will report back.
Click to expand...
Click to collapse
Well Tried House of Moto but get the same errors on RSD..
using RSD option either full or Keep data
"Failed flashing process. 2/22 Flash parition "partition signed" -> Phone returned FAIL."
When I used Fastboot - i just get a message saying specified path not found.
The Phone does show an AP fastboot message
"preflash validation failed for GPT
down graded security version
update gpt_main version failed"
is0lde said:
Well Tried House of Moto but get the same errors on RSD..
using RSD option either full or Keep data
"Failed flashing process. 2/22 Flash parition "partition signed" -> Phone returned FAIL."
When I used Fastboot - i just get a message saying specified path not found.
The Phone does show an AP fastboot message
"preflash validation failed for GPT
down graded security version
update gpt_main version failed"
Click to expand...
Click to collapse
you have to use Motorola fastboot to get the partition table to flash "mfastboot". do a search for it.
You can't downgrade your GPT.
When you want to flash (via RSD Light) a stock sbf ( http://sbf.droid-developers.org/ ) that contains older GPT than what is already present on your device, you have to edit the xml file and remove the lines containing the GPT reference.
bweN diorD said:
you have to use Motorola fastboot to get the partition table to flash "mfastboot". do a search for it.
Click to expand...
Click to collapse
I tested mfastboot to flash a recovery file and get the same results -
C:\Documents and Settings\Admin\Desktop\Fastbootxt925\Fastboot>mfastboot devices
TA240015YM fastboot
C:\Documents and Settings\Admin\Desktop\Fastbootxt925\Fastboot>mfastboot flash recovery twrp-hdrecovery.img
sending 'recovery' (6678 KB)...
OKAY [ 0.531s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.703s
C:\Documents and Settings\Admin\Desktop\Fastbootxt925\Fastboot>
Click to expand...
Click to collapse
What am I doing wrong?
kabaldan said:
You can't downgrade your GPT.
When you want to flash (via RSD Light) a stock sbf ( http://sbf.droid-developers.org/ ) that contains older GPT than what is already present on your device, you have to edit the xml file and remove the lines containing the GPT reference.
Click to expand...
Click to collapse
having downloaded 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml
I edited the xml file and tried to flash it using RSD but it stops at this point..
failed flashing process. step 1/20 flash sbl1 "sbl1_signed" -> Phone returned FAIL/QUOTE]
Here is a copy of the XML - Maybe I need to remove more lines?
<?xml version="1.0" encoding="UTF-8" ?>
- <flashing>
- <header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_rcica-user 4.1.2 9.8.2Q-8-XT925_VQL-12.2 1356031681 release-keysVANQUISH_U_BP_100700.220.65.33P" />
- <interfaces>
<interface name="AP" />
</interfaces>
</header>
- <steps interface="AP">
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="8840f90c9e80efc2e8deeb9baf3081f6" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="7fd9a42437e5b617b9a7724730a98d4e" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="9b50cb04d0f5d687632d8025f0ffc977" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="919d0b340cfdd5fc7c541803db65c2d6" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="ed1c505e36e769ccf0bb3c10e46dd62b" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="8d845fa3c79dc85962ce9989a8d21b05" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="b66d5afb5346bc959867723250e0630b" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="627f09f99ad62a7d201b33e6f8c3f4bc" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="52ed68c5943ca52f8db22ebdfeadbfa4" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="153c7f1e5ed1ad160b7038793c2ffaff" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="54b284c05362ea7595994a762365af8b" />
<step operation="flash" partition="system" filename="system_signed" MD5="7c0da284d9a5989d51263b80a4dc046d" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="f17376f4f570e5ae584d2afebf58de96" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step var="fb_mode_clear" operation="oem" />
</steps>
</flashing>
Click to expand...
Click to collapse
Click to expand...
Click to collapse
is0lde said:
I tested mfastboot to flash a recovery file and get the same results -
What am I doing wrong?
Click to expand...
Click to collapse
you missed the point. you dont need mfastboot to flash the recovery, you need it to flash the gpt file and fix your phone. im not sure why the previous poster would have told you to remove those lines. the partition table is the problem, it need to be flashed with mfastboot and removing those lines fixes nothing.
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
is0lde said:
I tested mfastboot to flash a recovery file and get the same results -
What am I doing wrong?
Click to expand...
Click to collapse
take a look at this file https://www.dropbox.com/s/bpjghbbv0v6r4v5/DROID_RAZR_HD_Utility_1.3.gpt fix.rar it is for fixing the partition table on a 926 only but you should be able to replace only the files i have used within with the files from your sbf. replace the lines in the xml with those from your sbf and replace the iso and other files in the main directory that they point to. dont change any other code.
bweN diorD said:
you missed the point. you dont need mfastboot to flash the recovery, you need it to flash the gpt file and fix your phone. im not sure why the previous poster would have told you to remove those lines. the partition table is the problem, it need to be flashed with mfastboot and removing those lines fixes nothing.
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
take a look at this file https://www.dropbox.com/s/bpjghbbv0v6r4v5/DROID_RAZR_HD_Utility_1.3.gpt fix.rar it is for fixing the partition table on a 926 only but you should be able to replace only the files i have used within with the files from your sbf. replace the lines in the xml with those from your sbf and replace the iso and other files in the main directory that they point to. dont change any other code.
Click to expand...
Click to collapse
I tried it and naturally it failed.
got this message
[*] Press any key to continue.
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.375s
error: cannot load 'system.img.ext4'
error: cannot load 'boot.img'
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.063s
sending 'modem' (30720 KB)...
OKAY [ 2.375s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.531s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.063s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.063s
sending 'fsg' (2704 KB)...
OKAY [ 0.219s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.375s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.000s
Click to expand...
Click to collapse
I look at your windows utility bat file and notice that its has the following lines..
mfastboot flash partition gpt_main0.bin
mfastboot flash system system.img.ext4
mfastboot flash boot boot.img
mfastboot -w
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
echo [*] Flash complete, Rebooting...
mfastboot reboot
Click to expand...
Click to collapse
My spf file names differ..as noted in the xml file ..
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_rcica-user 4.1.2 9.8.2Q-8-XT925_VQL-12.2 1356031681 release-keysVANQUISH_U_BP_100700.220.65.33P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step var="fb_mode_set" operation="oem"/>
<step operation="flash" partition="partition" filename="partition_signed" MD5="b512cbec4ea84740cddc55e2f5f29f04" />
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="8840f90c9e80efc2e8deeb9baf3081f6" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="7fd9a42437e5b617b9a7724730a98d4e" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="9b50cb04d0f5d687632d8025f0ffc977" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="919d0b340cfdd5fc7c541803db65c2d6" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="ed1c505e36e769ccf0bb3c10e46dd62b" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="8d845fa3c79dc85962ce9989a8d21b05" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="b66d5afb5346bc959867723250e0630b" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="627f09f99ad62a7d201b33e6f8c3f4bc" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="52ed68c5943ca52f8db22ebdfeadbfa4" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="153c7f1e5ed1ad160b7038793c2ffaff" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="54b284c05362ea7595994a762365af8b" />
<step operation="flash" partition="system" filename="system_signed" MD5="7c0da284d9a5989d51263b80a4dc046d" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="f17376f4f570e5ae584d2afebf58de96" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata"/>
<step var="fb_mode_clear" operation="oem"/>
</steps>
</flashing>
Click to expand...
Click to collapse
So My question is - what do I do now? where do i make the changes to match the file names?
is0lde said:
I tried it and naturally it failed.
got this message
I look at your windows utility bat file and notice that its has the following lines..
My spf file names differ..as noted in the xml file ..
So My question is - what do I do now? where do i make the changes to match the file names?
Click to expand...
Click to collapse
this is really easy to figure out. just replace the files in my utility with the files from your sbf. i see all the files there, although some have slightly different names. keep them aligned in the utility just as ihave them in the xml file.
also, go into the batch file and rename the 2 files to match yours, i think its just the modem and partition that have different names in your file.
when you copy and paste the xml file, just copy the hole line from yours and remove the one i have.
bweN diorD said:
this is really easy to figure out. just replace the files in my utility with the files from your sbf. i see all the files there, although some have slightly different names. keep them aligned in the utility just as ihave them in the xml file.
also, go into the batch file and rename the 2 files to match yours, i think its just the modem and partition that have different names in your file.
when you copy and paste the xml file, just copy the hole line from yours and remove the one i have.
Click to expand...
Click to collapse
I thought it may be simple but I just wanted to make there was not other hidden references to your original file names.
so I changed the windows utility bin file names..
mfastboot flash partition gpt_main0.bin
mfastboot flash system system_signed.img
mfastboot flash boot boot_signed.img
mfastboot -w
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
echo [*] Flash complete, Rebooting...
Click to expand...
Click to collapse
But I get the same familiar message..
[*] Press any key to continue.
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.344s
error: cannot load 'system_signed.img'
error: cannot load 'boot_signed.img'
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.063s
sending 'modem' (30720 KB)...
OKAY [ 2.375s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.516s
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.063s
sending 'fsg' (2704 KB)...
OKAY [ 0.219s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.359s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.016s
Click to expand...
Click to collapse
Do you think I have driver issues? or something more simple that I missed? (again)
I tried renaming the files with the img extensions but the results are the same.
Stuck!
is0lde said:
I thought it may be simple but I just wanted to make there was not other hidden references to your original file names.
so I changed the windows utility bin file names..
But I get the same familiar message..
Do you think I have driver issues? or something more simple that I missed? (again)
I tried renaming the files with the img extensions but the results are the same.
Stuck!
Click to expand...
Click to collapse
I tried to uninstall and reinstall the usb drivers and that did not change anything.
so i have run out of ideas.
Hi i'm having the exact same problems, i've got a stock xt925 running 4.1.2, i think the problems we're having might be because our phones aren't rooted, is there a way to root the phone if you cant get into the settings to enable debug/whatever?
TonyShaft said:
Hi i'm having the exact same problems, i've got a stock xt925 running 4.1.2, i think the problems we're having might be because our phones aren't rooted, is there a way to root the phone if you cant get into the settings to enable debug/whatever?
Click to expand...
Click to collapse
Mine is rooted.
then im pretty much boned. unless anyone knows of a way to fix this issue with a non rooted completely stock xt925?
I have failed when RSD sbf file to my M, but I think it may be the same. This method is used to install Verizon system to a Softbank M (XT902) with working network.
There's an xml file in the sbf file. To perform RSD, I have to delete this code: <step operation="getvar" var="max-download-size" />
Each code is deleted, the corresponding file will not be installed to phone. So I think you can delete the failed code (the risk is yours). Hope this work!
TonyShaft said:
then im pretty much boned. unless anyone knows of a way to fix this issue with a non rooted completely stock xt925?
Click to expand...
Click to collapse
I'm in the same boat trying to revive a bone-stock XT926 stuck at the EU screen. Seems as if there is nothing I can try without root or custom recovery already in place. Can someone please tell us we are wrong???
I deleted the line "<step operation="flash" partition="partition" filename="partition_signed" MD5="b512cbec4ea84740cddc55e2f5f29f04" />" and the operation worked like a charm!
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.
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.
I´m having a bad time trying to revive a Bricked XT925. I bought it bricked (for repairs only) but the device powers on! I can acces fastboot and recovery (stock). the bootloader is unlocked but every time i try to flash a firmware via RSD or Fastboot, and error returned.
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
I tryed some firmwares (last of Brazil) and some ones of Kitkat version, but none of them helped me.
Alredy tried to flash GPT and TZ only, the same errors. I can´t flash anything. there is something i can do in the stock recovery? The recovery says KDA20. 117-1
The fastboot says :
AP Fastboot Flash Mode (S)
10.9b(*) (sha-07671a2, 2014-10-02, 11:24:45)
eMMC Info: Size 16Gb
Device is UNLOCKED, Status Code : 3
Battery OK
Please enlight me
Thanks in advance
The thread is about the XT926 for Verizon, but since your issue is identical I guess the same solution works for your phone: http://forum.xda-developers.com/showthread.php?t=2177253
The only difference is that you have to use XT925 firmware.
1. Download the latest stock ROM for your device, then delete these lines in the ROM's xml-file:
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" />
2. Follow these steps:
mfastboot.exe flash partition gpt_main0.bin
mfastboot.exe flash logo logo.bin
mfastboot.exe flash system system.img.ext4
mfastboot.exe flash boot boot.img
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe reboot
Get yourself a "Motorola Factory Cable" if your battery is about to dry out.
http://www.ebay.com/itm/5-ft-Fastbo...403?pt=LH_DefaultDomain_0&hash=item3cd9dd0cf3