[Q] Razr HD XT926 Kit Kat VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip

Search This thread

stras1234

Senior Member
May 14, 2014
80
38
Hi all, still a newbie here - so i cannot post this in Development forum

i would like to share the following file:
'VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip'

@SamuraiHL i'm sure youve been waiting for this.

special thanks to @zachariahpope for asking me for it. otherwise i wouldve completely forgotten i had it.

link is here: be sure to remove the 4 spaces (still a noob; someone can repost below with a proper link)
https: //drive. google. com /file/d/0Byyu7DY1fJ31YjJ4bWpjQ2x0Yk0/edit?usp=sharing
 
Last edited:

SamuriHL

Senior Member
Aug 5, 2010
3,418
2,200
Hi all, still a newbie here - so i cannot post this in Development forum

i would like to share the following file:
'VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip'

@SamuraiHL i'm sure youve been waiting for this.

special thanks to @zachariahpope for asking me for it. otherwise i wouldve completely forgotten i had it.

link is here: be sure to remove the 4 spaces (still a noob; someone can repost below with a proper link)
https: //drive. google. com /file/d/0Byyu7DY1fJ31YjJ4bWpjQ2x0Yk0/edit?usp=sharing

OMG yes we needed this so bad. I wish you had spelled my username correctly so I'd have seen this sooner. LMAO! :D THANK YOU!
 

SamuriHL

Senior Member
Aug 5, 2010
3,418
2,200
Thanks stras1234!

The above is the FXZ for the 182.46.10 version. At least it is something, but I will be watching for the 183.46.10 FXZ.


BBB
Crack for Crackers

What is the difference?

The version number and release signing keys used. That's IT. I don't much care as those who are bricked now (and I have a bunch of people who attempted to downgrade to JB cause they "didn't like KK" :rolleyes:) can fix their phones. if they want the "official" FXZ later, it's a matter of using my RSD Script Generator and flashing it. They won't even lose data in the process.
 

jldr

Senior Member
Aug 21, 2012
344
50
Oh awesome. So I'll be able to flash from rooted, unlocked CM11 straight to stock KitKat now?
 

jldr

Senior Member
Aug 21, 2012
344
50
Outstanding. Eagerly awaiting your awesome instructions!

I know I asked that same damn question 5 times, I think I'm done now!
 

SamuriHL

Senior Member
Aug 5, 2010
3,418
2,200
LOL I know, right? :D Hopefully someone will be able to provide that. Am curious if the idea will work.
 

SamuriHL

Senior Member
Aug 5, 2010
3,418
2,200
You need to post the exact error you're getting if you want me to help. It definitely works, so, it's something in your environment preventing it.
 

qqjjz

Member
Jul 11, 2013
16
0
You need to post the exact error you're getting if you want me to help. It definitely works, so, it's something in your environment preventing it.

Where can I find the info you need? I was rooted and unlocked when OTA forced hit me. In the AP Fastboot menu I am showing locked now with status code 0.
 

SamuriHL

Senior Member
Aug 5, 2010
3,418
2,200
Where can I find the info you need? I was rooted and unlocked when OTA forced hit me. In the AP Fastboot menu I am showing locked now with status code 0.

In your RSD folder, look for an SWDL txt file and post it here so I can look at it. Do not worry about the locked status. It's only a temporary thing until we fix the failed flash. Don't panic. This can be fixed.
 

killrhythm09

Senior Member
May 3, 2011
254
94
35
California
I think it's because you used the universal script which doesn't update the GPT partitioning. If you're going from JB to KK for the first time, you probably need it to do that.

Basically your partitions are hosed now and you need to find a way to fix them.

EDIT: Never mind, SamuraiHL knows what he's talking about, ignore me. :)
 

SamuriHL

Senior Member
Aug 5, 2010
3,418
2,200
I think it's because you used the universal script which doesn't update the GPT partitioning. If you're going from JB to KK for the first time, you probably need it to do that.

Basically your partitions are hosed now and you need to find a way to fix them.

Naw, you don't have to flash gpt. I've had others not flash it and it worked fine for them.
 

qqjjz

Member
Jul 11, 2013
16
0
In your RSD folder, look for an SWDL txt file and post it here so I can look at it. Do not worry about the locked status. It's only a temporary thing until we fix the failed flash. Don't panic. This can be fixed.

Oh no man I am good. I've been poking around my phones and rooting for a few years but I've never encountered anything like this. I am glad I did though because I need to know all this stuff. I'm running on my backup phone right now so what we're repairing here is just to let me have a dev phone and another backup phone :)

If there is one thing I know about Motorola, they're very sneaky with backdoors and tools when it comes to software. I've worked with them for several years in software testing.

I really appreciate all you guys help btw. Here is the data.

05/22/14 19:11:02 --------------------------------------------------------------------------------
05/22/14 19:11:02 New Log Started For Software Download.
05/22/14 19:11:39 The FlashLog key is turned off.
05/22/14 19:12:49 Multi upgrade started for 1 phones
05/22/14 19:12:49 [Device ID: 0] 1/15 flash sbl1 "sbl1.mbn"
05/22/14 19:12:50 [Device ID: 0] 2/15 flash sbl2 "sbl2.mbn"
05/22/14 19:12:51 [Device ID: 0] 3/15 flash sbl3 "sbl3.mbn"
05/22/14 19:12:52 [Device ID: 0] 4/15 flash rpm "rpm.mbn"
05/22/14 19:12:53 [Device ID: 0] 5/15 flash aboot "emmc_appsboot.mbn"
05/22/14 19:12:54 [Device ID: 0] 6/15 flash modem "NON-HLOS.bin"
05/22/14 19:13:09 [Device ID: 0] 7/15 flash fsg "fsg.mbn"
05/22/14 19:13:10 [Device ID: 0] 8/15 erase modemst1
05/22/14 19:13:11 [Device ID: 0] 9/15 erase modemst2
05/22/14 19:13:12 [Device ID: 0] 10/15 flash logo "logo.bin"
05/22/14 19:13:14 [Device ID: 0] 11/15 flash boot "boot.img"
05/22/14 19:13:21 [Device ID: 0] 12/15 flash recovery "recovery.img"
05/22/14 19:13:27 [Device ID: 0] 13/15 flash system "system.img"
05/22/14 19:14:04 ERROR: 13/15 flash system "system.img" -> Phone returned FAIL. - on device ID 0.
05/22/14 19:14:04 [Device ID: 0] 13/15 flash system "system.img" -> Phone returned FAIL.
05/22/14 19:14:04 ERROR: Failed flashing process. - on device ID 0.
05/22/14 19:14:04 Multi upgrade finished.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
 

SamuriHL

Senior Member
Aug 5, 2010
3,418
2,200
I'm guessing you have one of the following problems that you need to resolve:

o) Latest Moto USB driver must be installed
o) Must be a USB 2 port, *NOT* a USB 3 port
o) Must be original OEM cable that came with the phone (yes, it matters)

Basically it failed to send system to your phone...and it's a large freaking file so the transfer failed.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Hi all, still a newbie here - so i cannot post this in Development forum

    i would like to share the following file:
    'VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip'

    @SamuraiHL i'm sure youve been waiting for this.

    special thanks to @zachariahpope for asking me for it. otherwise i wouldve completely forgotten i had it.

    link is here: be sure to remove the 4 spaces (still a noob; someone can repost below with a proper link)
    https: //drive. google. com /file/d/0Byyu7DY1fJ31YjJ4bWpjQ2x0Yk0/edit?usp=sharing
    5
    Just FYI the FXZ in OP is a bit outdated (final version is on http://sbf.droid-developers.org/phone.php?device=5, Blur_Version.183.46.10.XT926.Verizon.en.US)
    2
    Hi all, still a newbie here - so i cannot post this in Development forum

    i would like to share the following file:
    'VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip'

    @SamuraiHL i'm sure youve been waiting for this.

    special thanks to @zachariahpope for asking me for it. otherwise i wouldve completely forgotten i had it.

    link is here: be sure to remove the 4 spaces (still a noob; someone can repost below with a proper link)
    https: //drive. google. com /file/d/0Byyu7DY1fJ31YjJ4bWpjQ2x0Yk0/edit?usp=sharing

    OMG yes we needed this so bad. I wish you had spelled my username correctly so I'd have seen this sooner. LMAO! :D THANK YOU!
    1
    Thanks stras1234!

    The above is the FXZ for the 182.46.10 version. At least it is something, but I will be watching for the 183.46.10 FXZ.


    BBB
    Crack for Crackers
    1
    Might be a little late, but this happened to me. Plugged in phone to charge and it was dead after a few hours. All I did was unplug the charger and plugged it back in and it started to charge. No problem since.

    If I plug it in, the green light will come on for a few minutes, but that's it. I suspect it's entering emergency charge mode, charges enough, leaves emergency mode, but won't charge anymore. I've left it plugged in for hours on end and I've tried to get fastboot to recognize it, but I haven't had any luck yet. My only theories are that it's been raining and high humidity lately and maybe some form of moisture shorted something or that when I was welding the other day I had a few currents pass through me, nothing painful or serious (felt like a weak 9v on my tongue), and maybe that did something...my dog was wanting to play frisbee so I just plugged it into the charger and walked away...didn't actually look at it when I plugged it in...

    I might have to solder up a Moto Factory cable...surprised I haven't done that yet considering I have 3 Motorola phones...

    ---------- Post added at 08:48 AM ---------- Previous post was at 08:47 AM ----------

    If he's already applied the OTA update, then using RSD is fine. He'll just need to download the FXZ and unzip it and then go from there. He will lose all data (internal storage plus internal SD card) unless he modifies the XML file in there.

    Samuri's tool, using the universal script, will keep all data. But, I've found that this sometimes causes issues as well and it's usually best to just wipe data anyways to ensure there isn't anything left to chance.

    @demonshouter

    That.

    And FWIW, my Mother took the Atrix HD OTA a week ago (just a heartbleed fix) and her phone randomly shut off a few times. A factory reset was the only thing that fixed it.