1296 replies to this topic

[SamuriHL]

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

 

Can't boot right now.  So no.  It's in an ugly state that I have no fix for.  Better minds than mine need to work on it.

[livinginkaos]

Well, he was on the -94 build, so he was on jelly. I am wondering, if maybe, your device was in the process of updating and it got interrupted? sent from my G3

[markjurado]

Well, he was on the -94 build, do he was on jelly. I am wondering, if maybe, your device was in the process off updating and it got interrupted?

sent from my G3

yes it was interrupted while updating

[markjurado]

my bad, it was on jellybean not ics

[SamuriHL]

Yea, when you said 94 I knew what build it was.  But this is bad.  I don't have a fix for you.  I really don't.

[cmh714]

Sam in the other thread he posted that hes using the Blur files which is the OTA not the FXZ...not sure if that changes things....

[markjurado]

Sam in the other thread he posted that hes using the Blur files which is the OTA not the FXZ...not sure if that changes things....

im using this

Attached Files

•  blur.jpg   104.16KB   22 downloads

[johnthehillbilly]

Strange that rsdlite is showing "xt926".... Mine always shows "fastboot" .....

Probably a moot question, but are you in-fact putting your phone in AP Fastboot mode prior to plugging it in or booting "normally" ?

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

[markjurado]

Strange that rsdlite is showing "xt926".... Mine always shows "fastboot" .....

Probably a moot question, but are you in-fact putting your phone in AP Fastboot mode prior to plugging it in or booting "normally" ?

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

 

the scrshot shows the phone that has just been plugged in the computer, and is not in fastboot mode. i just showed the details of phone coz i dont know how to get the version

 

and yes, im on fastboot mode when flashing(tried it before plugging in and after i plugged it in the computer)

[nobe1976]

Clearly you have something going wrong with the way you are setting up both HOM and RSD in order to have this issue

Attached are some screenshots of how I have mine setup...

Check and make sure that your PC is recoginizing as a ADB Interface as seen in the Device Manager screenshot.

RSD should recognize it as fastboot not xt926

and if you use HOM your FXZ_xt926 Needs to be as so for it to work.

 

Best of luck..

Attached Files

•  Capture.PNG   60.63KB   20 downloads
•  Capture2.PNG   45.29KB   21 downloads
•  Capture3.PNG   70.31KB   19 downloads

[markjurado]

Clearly you have something going wrong with the way you are setting up both HOM and RSD in order to have this issue

Attached are some screenshots of how I have mine setup...

Check and make sure that your PC is recoginizing as a ADB Interface as seen in the Device Manager screenshot.

RSD should recognize it as fastboot not xt926

and if you use HOM your FXZ_xt926 Needs to be as so for it to work.

 

Best of luck..

 

as i said, my scrsht was only used in checking the version, it is on NORMAL MODE ( i just plugged in the cable, and the phone was NOT on AP Fastboot mode )

ofcourse i will SWITCH to fastboot mode when i do the flashing and "fastboot" WILL SHOW  in the RSD

everything is setup correctly and i'm 99.99% sure about it

(drivers, oem cable, fxz... etc)

 

 

-just clearing up your doubts-

 

Mr. Sam already told me that he has no fix for my issue.. yet? so i think i will have to wait if ever there will be one

[SamuriHL]

I'm not hopeful. I'll dig up the link to the xda thread for you tomorrow. If I forget remind me as I have 4 hours of meeting in the morning. There's nothing in the thread that will give you any hope. I have a theory but it sucks and no one believes me anyway. But I surmise that the flash memory they used is complete crap.

Sent from my SM-P600 using Tapatalk

[markjurado]

I'm not hopeful. I'll dig up the link to the xda thread for you tomorrow. If I forget remind me as I have 4 hours of meeting in the morning. There's nothing in the thread that will give you any hope. I have a theory but it sucks and no one believes me anyway. But I surmise that the flash memory they used is complete crap.

Sent from my SM-P600 using Tapatalk

 

i think it is a hardware failure, coz this phone boots up a little slow than normal xt926 boot. it takes about 5 minutes to boot up

 

thank you for your help anyways

[SamuriHL]

That's my opinion of the phones that have this problem too but others don't share my opinion. Not that it matters since no one has a working solution. The flash memory seems to go into some kind of read only state. It's really messed up. Sorry I couldn't help fix it.

Sent from my SM-P600 using Tapatalk

[markjurado]

That's my opinion of the phones that have this problem too but others don't share my opinion. Not that it matters since no one has a working solution. The flash memory seems to go into some kind of read only state. It's really messed up. Sorry I couldn't help fix it.

Sent from my SM-P600 using Tapatalk

well the others are not as lucky as i am to have this defective droid i think so too that this phone has a read only flash memory. but i wonder how did it go corrupted when i updated it to KK ota..
well i have read on the xda forum that the only fix *probably* is to solder another chip in the unit (that sucks!!)

well there's nothing we could do if it's a hardware failure, so no worries, and thank you for trying to help

keep up the good work

[jcarter3729]

hi i tried to upgrade my droid bionic to 4.1.2 and i tried to do it through the house of moto method and it didn't work. it get past the motorola logo but but it never boots up to its home screen. actually it never shows the red eye that loads up when you power it on but the buttons on the bottom of the screen lights up though.

here is my log by the way

POST THE CONTENTS OF THIS FILE IN THE HoM THREAD

FASTBOOT DEVICES:

FILE STRUCTURE:
Volume in drive C is Windows
Volume Serial Number is 5012-A7B2

Directory of C:\HouseOfMoto_3.2

09/09/2014 04:50 PM .
09/09/2014 04:50 PM ..
11/24/2013 03:02 PM 281 CreateLOG.bat
09/09/2014 08:05 AM 0 flash.log
09/09/2014 04:43 PM FXZ_XT875
09/09/2014 04:50 PM 95 house.log
08/28/2014 08:11 PM 14,957 HouseOfMoto-ScriptGenerator.jar
08/28/2014 08:17 PM 3,537 HouseOfMoto.bat
08/28/2014 08:11 PM 3,012 HouseOfMoto.sh
11/23/2013 07:07 PM root
08/12/2014 08:52 AM 56,832 wtee.exe
7 File(s) 78,714 bytes

Directory of C:\HouseOfMoto_3.2\FXZ_XT875

09/09/2014 04:43 PM .
09/09/2014 04:43 PM ..
03/22/2013 03:46 PM 262,144 allow-mbmloader-flashing-mbm.bin
03/08/2013 04:50 PM 8,388,608 boot.img
03/22/2013 05:11 PM 2,484 cdma_targa_9.8.2O-72_VZW-22_cfc.xml
03/08/2013 04:51 PM 12,320,768 cdrom
03/08/2013 04:51 PM 16,384 cdt.bin
09/09/2014 07:58 AM Darwin
03/08/2013 04:51 PM 524,288 device_tree.bin
03/08/2013 04:51 PM 16,384 ebr
03/22/2013 03:56 PM 0 emstorage.img
09/09/2014 04:43 PM 878 FULL.bat
09/09/2014 04:43 PM 851 KEEPDATA.bat
03/22/2013 04:43 PM 16,384 lbl
09/09/2014 07:58 AM Linux
03/08/2013 04:50 PM 874,800 logo.bin
03/22/2013 03:46 PM 262,144 mbm.bin
03/22/2013 03:46 PM 42,060 mbmloader.bin
03/08/2013 04:51 PM 16,384 mbr
03/08/2013 04:50 PM 318,767,104 preinstall.img
09/09/2014 04:43 PM 102 RADIO.bat
03/08/2013 04:50 PM 22,458,368 radio.img
03/08/2013 04:50 PM 9,437,184 recovery.img
03/08/2013 04:50 PM 503,054,336 system.img
03/08/2013 04:51 PM 1,397,489,664 vendor.img
09/09/2014 07:58 AM Windows
21 File(s) 2,273,951,319 bytes

Directory of C:\HouseOfMoto_3.2\FXZ_XT875\Darwin

09/09/2014 07:58 AM .
09/09/2014 07:58 AM ..
08/06/2013 09:22 PM 225,100 fastboot
1 File(s) 225,100 bytes

Directory of C:\HouseOfMoto_3.2\FXZ_XT875\Linux

09/09/2014 07:58 AM .
09/09/2014 07:58 AM ..
08/06/2013 09:22 PM 541,322 fastboot
1 File(s) 541,322 bytes

Directory of C:\HouseOfMoto_3.2\FXZ_XT875\Windows

09/09/2014 07:58 AM .
09/09/2014 07:58 AM ..
08/06/2013 09:22 PM 96,256 AdbWinApi.dll
06/24/2011 05:35 AM 90,523 fastboot.exe
2 File(s) 186,779 bytes

Directory of C:\HouseOfMoto_3.2\root

11/23/2013 07:07 PM .
11/23/2013 07:07 PM ..
0 File(s) 0 bytes

Total Files Listed:
32 File(s) 2,274,983,234 bytes
17 Dir(s) 402,068,983,808 bytes free

[jcarter3729]

HERE IS THE RESULTS OF MY FLASH LOG

Ready to flash...
Press any key to continue . . .

Flashing: FULL.bat
        sending 'mbm' (256 KB)... OKAY [  0.020s]
                 writing 'mbm'... OKAY [  0.870s]
     rebooting into bootloader... OKAY [  0.254s]
   sending 'mbmloader' (41 KB)... OKAY [  0.008s]
           writing 'mbmloader'... OKAY [  0.368s]
        sending 'mbm' (256 KB)... OKAY [  0.315s]
                 writing 'mbm'... OKAY [  0.636s]
     rebooting into bootloader... OKAY [  0.273s]
     sending 'cdt.bin' (16 KB)... OKAY [  0.008s]
             writing 'cdt.bin'... OKAY [  0.609s]
     rebooting into bootloader... OKAY [  0.463s]
               erasing 'cache'... OKAY [  0.013s]
            erasing 'userdata'... OKAY [  1.585s]
         sending 'lbl' (16 KB)... OKAY [  0.009s]
                 writing 'lbl'... OKAY [  7.884s]
   sending 'logo.bin' (854 KB)... OKAY [  0.286s]
            writing 'logo.bin'... OKAY [  0.407s]
         sending 'ebr' (16 KB)... OKAY [  0.288s]
                 writing 'ebr'... OKAY [  0.572s]
         sending 'mbr' (16 KB)... OKAY [  0.264s]
                 writing 'mbr'... OKAY [  0.450s]
    sending 'devtree' (512 KB)... OKAY [  0.326s]
             writing 'devtree'... OKAY [  0.578s]
  sending 'system' (262144 KB)... OKAY [ 14.593s]
              writing 'system'... OKAY [ 14.883s]
  sending 'system' (229120 KB)... OKAY [ 13.060s]
              writing 'system'... OKAY [ 11.847s]
      sending 'boot' (8192 KB)... OKAY [  0.447s]
                writing 'boot'... OKAY [  0.873s]
  sending 'recovery' (9216 KB)... OKAY [  0.904s]
            writing 'recovery'... OKAY [  1.180s]
    sending 'cdrom' (12032 KB)... OKAY [  1.195s]
               writing 'cdrom'... OKAY [  1.877s]
sending 'preinstall' (262144 KB)... OKAY [ 14.576s]
          writing 'preinstall'... OKAY [ 14.634s]
sending 'preinstall' (49152 KB)... OKAY [  2.758s]
          writing 'preinstall'... OKAY [  2.577s]
load_file: could not allocate 1397489664 bytes
error: cannot load 'vendor.img'

    sending 'radio' (21932 KB)... OKAY [  1.179s]
               writing 'radio'... OKAY [  3.347s]
                     rebooting...
Press any key to continue . . .

[SamuriHL]

error: cannot load 'vendor.img'

 

That seems a likely cause of said issue.  Check your FXZ.

[jcarter3729]

the FXZ is FXZ_XT875

[SamuriHL]

Ummmmm, I don't even know what to do with that.