1296 replies to this topic

[johnthehillbilly]

For some reason it thinks that file is not there .... I've had that happen before as well..... (On Windows)...... If you have access to a Linux installation run it thru again on Linux ...... You can download a Linux live DVD or CD and use it......

HD tapadriving..... hillbilly style!!!

[joeysicily]

Guys.  Im on a windows 7 and installed the latest House of moto.   I ran executed the house of moto and chose the zip file and flash the moto razr maxx hd phone with (no eye popping errors).   I started to get into a boot loop and it seemed to NOT get passed the M logo screen.

 

RESOLUTION:    It turned out that during the extraction of the zip file the "boot.img" did not get extracted for some ODD reason.  The zip file had the boot.img file and had the correct md5. I happened to catch the error that boot.img file was missing during the flash.  The flash.log file was empty and didn't show anything.  So once I "manually" extracted the boot.img  everything finally worked as expected.   So the extraction process needs to be fixed.  the flash part needs to BOLDY break on MAJOR errors like that and display the ERROR.

 

Hopefully this will help others with similar problems. 

[SamuriHL]

So get to work writing a tool that does all that.  Your post takes on a very demanding tone which is not even remotely appreciated.  If the extraction was "broken" for everyone, it'd be reported by more than one person.  So while I appreciate you had a unique situation on your machine, I'm certainly not jumping to go "fix" everything just because you happen to demand it.

[ac7ss]

Thank you for this, I borked my RAZR M trying to use an alternate rom. kept getting the dead droid. This did the trick.

[SamuriHL]

House of Moto 3.2 released

 

o) Minor bug fixes.  You should upgrade.

[markjurado]

hello, i tried but i got some errors

, help please

model: XT926
system version: 9.8.1Q-94 (not sure if this is the system version)
FXZ: i downloaded Android 4.4.2 Blur_Version.183.46.10.XT926.Verizon.en.US / VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF
=========================
AP Fastboot Mode (S)
10.9B(*) (sha-1e9f557, 2013-09-25 16:26:59)
eMMC Info: Size 32GB

Device is LOCKED. Status Code: 0

Battery OK

Transfer Mode:
USB Connected

Fastboot Reason: Boot menu Selected
usb Connected
=======================
i opened the flash log but it doesnt contain anything


i followed the steps exactly but i dont know what went wrong
- downloaded and installed moto usb drivers
- downloaded and set up the house of moto
- included the snapdragon support

i am also using the cable that was found in the box together with the phone
 

Attached Files

•  error.jpg   284.15KB   17 downloads

[johnthehillbilly]

What errors did you get.....

HD tapadriving..... hillbilly style!!!

[markjurado]

What errors did you get.....

HD tapadriving..... hillbilly style!!!

oh sorry i forgot to attach this

Attached Files

•  error.jpg   284.15KB   23 downloads

[SamuriHL]

Yea I need the errors.  I don't know why the hell the flash log isn't working for people.  Every time I run it I get the log.  I've been trying to figure that issue out but apparently my last fix didn't seem to work.  Copy and paste the flash window for us so I can see what failed.

[SamuriHL]

Ok, just saw your screenshots.  Uhhhh, yea.  There's some bad juju going on there.  Make sure it's a USB 2 port, latest moto USB drivers.  You said it's the oem cable so that's good, but, maybe try another port.  If it's still failing, switch to my RSD Flasher tool and run that.  If it still fails after that, we got a problem. Basically it's not writing the partitions which i've seen a few times on another forum. I was pulled into a conversation about it and we've seen it on a few phones.  And there is NO known solution if it's the same issue.  

[markjurado]

Ok, just saw your screenshots.  Uhhhh, yea.  There's some bad juju going on there.  Make sure it's a USB 2 port, latest moto USB drivers.  You said it's the oem cable so that's good, but, maybe try another port.  If it's still failing, switch to my RSD Flasher tool and run that.  If it still fails after that, we got a problem. Basically it's not writing the partitions which i've seen a few times on another forum. I was pulled into a conversation about it and we've seen it on a few phones.  And there is NO known solution if it's the same issue.  

im on usb 2.0, and i just installed the latest drivers,

im gonna try it on other ports and the rsd flasher tool

hope i can fix this

thanks for the reply

[SamuriHL]

Yea I hope so, too.  If not, it means it's like the one I was pulled into the conversation about and we have not found ANY solutions for it.  We don't know why it happens and have NO idea how to fix it.  

[markjurado]

Ok, just saw your screenshots.  Uhhhh, yea.  There's some bad juju going on there.  Make sure it's a USB 2 port, latest moto USB drivers.  You said it's the oem cable so that's good, but, maybe try another port.  If it's still failing, switch to my RSD Flasher tool and run that.  If it still fails after that, we got a problem. Basically it's not writing the partitions which i've seen a few times on another forum. I was pulled into a conversation about it and we've seen it on a few phones.  And there is NO known solution if it's the same issue.  

 

tried other ports but still the same

tried the rsd flasher

 

swdl log shows this

==============================

09/01/14 09:34:15  New Log Started For Software Download.
09/01/14 09:36:38  00000ffc    PhoneFactory.cpp    878    -1    ERROR    CPhoneFactory::NotifyPhoneArrival - Failed to wait for QC ready in 10s
09/01/14 09:36:38  ERROR: PSTSendCommand failed: Error Code 136 on device ID 0
09/01/14 09:36:38  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:38  ERROR: PSTSendCommand failed: Error Code 41 on device ID 0
09/01/14 09:36:38  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:38  00000ffc    Phone.cpp    1683    0    ERROR    GetPhoneID failed: ERROR.
09/01/14 09:36:38  ERROR: PSTSendCommand failed: Error Code 136 on device ID 0
09/01/14 09:36:38  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:38  ERROR: PSTSendCommand failed: Error Code 41 on device ID 0
09/01/14 09:36:38  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:38  00000ffc    Phone.cpp    1683    0    ERROR    GetPhoneID failed: ERROR.
09/01/14 09:36:45  ERROR: PSTSendCommand failed: Error Code 136 on device ID 0
09/01/14 09:36:45  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:45  ERROR: PSTSendCommand failed: Error Code 41 on device ID 0
09/01/14 09:36:45  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:45  00000ffc    Phone.cpp    1683    0    ERROR    GetPhoneID failed: ERROR.
09/01/14 09:36:45  ERROR: PSTSendCommand failed: Error Code 136 on device ID 0
09/01/14 09:36:45  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:46  ERROR: PSTSendCommand failed: Error Code 41 on device ID 0
09/01/14 09:36:46  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:46  00000ffc    Phone.cpp    1683    0    ERROR    GetPhoneID failed: ERROR.
09/01/14 09:36:46  ERROR: PSTSendCommand failed: Error Code 136 on device ID 0
09/01/14 09:36:46  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:46  ERROR: PSTSendCommand failed: Error Code 41 on device ID 0
09/01/14 09:36:46  00000ffc    Phone.cpp    593    -1    ERROR    Sending the Test Command RDELEM to the phone failed 1 times. (retry interval: 1000 milliseconds)
09/01/14 09:36:49  1 devices switching to 56 mod.
09/01/14 09:36:49  1 devices are being switched.
09/01/14 09:36:49  enter LaunchSwitchThread
09/01/14 09:36:49  [Device ID: 0] Switching phone mode,Target Mode is 56.
09/01/14 09:36:54  The FlashLog key is turned off.
09/01/14 09:36:54  FlashLog file is turned off.
09/01/14 09:36:54  Multi upgrade finished.
09/01/14 09:36:54  00000ffc    Phone.cpp    531    0    ERROR    Generic failure when sending command.
09/01/14 09:36:54  00000ffc    Phone.cpp    1683    0    ERROR    GetPhoneID failed: ERROR.
09/01/14 09:36:54  00000ffc    Phone.cpp    531    0    ERROR    Generic failure when sending command.
09/01/14 09:36:54  00000ffc    Phone.cpp    1683    0    ERROR    GetPhoneID failed: ERROR.
09/01/14 09:37:00  --------------------------------------------------------------------------------
09/01/14 09:37:00  New Log Started For Software Download.
09/01/14 09:37:00  The FlashLog key is turned off.
09/01/14 09:37:03  00001568    Phone.cpp    531    0    ERROR    Generic failure when sending command.
09/01/14 09:37:03  00001568    Phone.cpp    1778    0    ERROR    GetTechnology failed: ERROR.
09/01/14 09:37:03  00001568    Phone.cpp    531    0    ERROR    Generic failure when sending command.
09/01/14 09:37:03  00001568    Phone.cpp    1778    0    ERROR    GetTechnology failed: ERROR.
09/01/14 09:37:03  00001568    Phone.cpp    531    0    ERROR    Generic failure when sending command.
09/01/14 09:37:03  00001568    Phone.cpp    1778    0    ERROR    GetTechnology failed: ERROR.
09/01/14 09:37:03  00001568    Phone.cpp    531    0    ERROR    Generic failure when sending command.
09/01/14 09:37:03  00001568    Phone.cpp    1847    0    ERROR    GetSoftwareVersion failed: SendTC failed: ERROR.
09/01/14 09:37:03  00001568    Phone.cpp    531    0    ERROR    Generic failure when sending command.
09/01/14 09:37:03  00001568    Phone.cpp    2005    0    ERROR    GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
09/01/14 09:37:03  00001568    Phone.cpp    531    0    ERROR    Generic failure when sending command.
09/01/14 09:37:03  00001568    Phone.cpp    1975    0    ERROR    GetBootVerFlashMode failed: SendTC failed: ERROR.
09/01/14 09:37:03  00001568    Phone.cpp    531    0    ERROR    Generic failure when sending command.
09/01/14 09:37:03  00001568    Phone.cpp    1894    0    ERROR    GetDRMVersion failed: SendTC failed: ERROR.
09/01/14 09:37:03  Multi upgrade started for 1 phones
09/01/14 09:37:03  [Device ID: 0] 1/18 flash partition "gpt.bin"
09/01/14 09:37:03  ERROR: 1/18 flash partition "gpt.bin" -> Phone returned FAIL. - on device ID 0.
09/01/14 09:37:03  [Device ID: 0] 1/18 flash partition "gpt.bin" -> Phone returned FAIL.
09/01/14 09:37:03  ERROR: Failed flashing process. - on device ID 0.
09/01/14 09:37:03  Multi upgrade finished.
==========================================================

what seems to be the problem?

[SamuriHL]

Thank you for posting that without me having to ask.  I really appreciate that.

 

As for the problem, may I ask two question...what version were you on and what fxz are you flashing?

[markjurado]

Thank you for posting that without me having to ask.  I really appreciate that.

 

As for the problem, may I ask two question...what version were you on and what fxz are you flashing?

 

for the version, hmm i honestly dont know, but rsdlite show this 9.8.1Q-94 so i guess it's the one you're looking for..

 

i am flashing VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF

[SamuriHL]

Woa woa.  Hold on.  RSD Lite shows the version you're flashing.  So, that doesn't mesh with what you're telling me you're flashing.  Please re-extract the 4.4.2 FXZ zip file and flash again.  Delete what you currently have for an FXZ first.

[markjurado]

Woa woa.  Hold on.  RSD Lite shows the version you're flashing.  So, that doesn't mesh with what you're telling me you're flashing.  Please re-extract the 4.4.2 FXZ zip file and flash again.  Delete what you currently have for an FXZ first.

rsdlite shows this..

 

sorry but i dont know how to find the version

i was on stock running on ics

unrooted and lock bootloader

Attached Files

•  version.jpg   92.35KB   16 downloads

[SamuriHL]

Interesting.  Yea, still try what I was saying to do.  Essentially extract the 4.4.2 FXZ clean and then flash it with RSD using either my tool or just RSD Lite directly.  If that fails, I hate to say it, but, things aren't looking good.  

[markjurado]

Interesting.  Yea, still try what I was saying to do.  Essentially extract the 4.4.2 FXZ clean and then flash it with RSD using either my tool or just RSD Lite directly.  If that fails, I hate to say it, but, things aren't looking good.  

 

awww man no luck, it still fails

 

i guess i have to wait for some fix

[transmissiontech]

If he is on ICS, should not the ota's update him, also will can you go from ICS to KK in one jump.