Jump to content


Photo
- - - - -

Green robot after using house of moto


  • Please log in to reply
10 replies to this topic

#1 Lebane0214

Lebane0214

    n00b

  • Members
  • Pip
  • 6 posts
  • Current Device(s):droid razr m

Posted 01 February 2014 - 09:17 PM

i used house of moto for my droid razr m (xt907) after getting stuck in a bootloop from trying to put cyanogen mod 11 for the mock 4.4 kit kat and now i have a green robot with a triangle that has an exclamation point in it. How do i get past it? my current version is 98.30.1.xt907.verizon.en.us. which is what i also used for house of moto.
 
This is what house of madness did using fastboot:
 
Please ensure your phone is:
o] Charged
o] Connected to USB using your OEM cable
o] USB drivers are installed
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
 
Ready to flash...
Press any key to continue . . .
 
Flashing: FULL_xt907.bat
rebooting into bootloader...
OKAY [  0.008s]
finished. total time: 0.008s
< waiting for device >
sending 'partition' (32 KB)...
OKAY [  0.014s]
writing 'partition'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.256s
sending 'sbl1' (100 KB)...
OKAY [  0.018s]
writing 'sbl1'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.270s
sending 'sbl2' (125 KB)...
OKAY [  0.020s]
writing 'sbl2'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.267s
sending 'sbl3' (512 KB)...
OKAY [  0.050s]
writing 'sbl3'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.299s
sending 'rpm' (140 KB)...
OKAY [  0.021s]
writing 'rpm'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.269s
sending 'tz' (192 KB)...
OKAY [  0.026s]
writing 'tz'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.273s
sending 'aboot' (256 KB)...
OKAY [  0.030s]
writing 'aboot'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.279s
sending 'modem' (30720 KB)...
OKAY [  2.369s]
writing 'modem'...
Battery Low!!
FAILED (remote failure)
finished. total time: 2.613s
sending 'fsg' (2794 KB)...
OKAY [  0.240s]
writing 'fsg'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.489s
erasing 'modemst1'...
OKAY [  0.624s]
finished. total time: 0.625s
erasing 'modemst2'...
OKAY [  0.607s]
finished. total time: 0.608s
sending 'logo' (1709 KB)...
OKAY [  0.141s]
writing 'logo'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.385s
sending 'devtree' (512 KB)...
OKAY [  0.050s]
writing 'devtree'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.294s
sending 'boot' (10240 KB)...
OKAY [  0.791s]
writing 'boot'...
Battery Low!!
FAILED (remote failure)
finished. total time: 1.034s
sending 'recovery' (10240 KB)...
OKAY [  0.791s]
writing 'recovery'...
Battery Low!!
FAILED (remote failure)
finished. total time: 1.038s
sending 'cdrom' (30720 KB)...
OKAY [  2.356s]
writing 'cdrom'...
OKAY [  2.854s]
sending 'cdrom' (22538 KB)...
OKAY [  3.677s]
writing 'cdrom'...
OKAY [  2.519s]
finished. total time: 11.413s
error: cannot load 'system.img.ext4'
 
erasing 'cache'...
OKAY [  1.011s]
finished. total time: 1.012s
erasing 'userdata'...
OKAY [  2.211s]
finished. total time: 2.211s
erasing 'tombstones'...
OKAY [  0.763s]
finished. total time: 0.763s
rebooting...
 
finished. total time: 0.011s
Press any key to continue . . .
 
 

i would gladly suply anymore information if needed.



#2 Lebane0214

Lebane0214

    n00b

  • Members
  • Pip
  • 6 posts
  • Current Device(s):droid razr m

Posted 01 February 2014 - 09:19 PM

well after looking at the fastboot text my battery was apparently low... :(



#3 Lebane0214

Lebane0214

    n00b

  • Members
  • Pip
  • 6 posts
  • Current Device(s):droid razr m

Posted 01 February 2014 - 10:01 PM

got this a different go around... what am i doing wrong?

 

Please ensure your phone is:
o] Charged
o] Connected to USB using your OEM cable
o] USB drivers are installed
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
 
Ready to flash...
Press any key to continue . . .
 
Flashing: FULL_xt907.bat
rebooting into bootloader...
OKAY [  0.009s]
finished. total time: 0.009s
< waiting for device >
sending 'partition' (32 KB)...
OKAY [  0.057s]
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
OKAY [  0.420s]
finished. total time: 0.478s
sending 'sbl1' (100 KB)...
OKAY [  0.018s]
writing 'sbl1'...
OKAY [  0.475s]
finished. total time: 0.496s
sending 'sbl2' (125 KB)...
OKAY [  0.028s]
writing 'sbl2'...
OKAY [  0.812s]
finished. total time: 0.843s
sending 'sbl3' (512 KB)...
OKAY [  0.064s]
writing 'sbl3'...
OKAY [  0.973s]
finished. total time: 1.039s
sending 'rpm' (140 KB)...
OKAY [  0.026s]
writing 'rpm'...
OKAY [  0.490s]
finished. total time: 0.519s
sending 'tz' (192 KB)...
OKAY [  0.026s]
writing 'tz'...
OKAY [  0.514s]
finished. total time: 0.544s
sending 'aboot' (256 KB)...
OKAY [  0.032s]
writing 'aboot'...
OKAY [  0.744s]
finished. total time: 0.777s
sending 'modem' (30720 KB)...
OKAY [  2.469s]
writing 'modem'...
OKAY [  1.047s]
sending 'modem' (17620 KB)...
OKAY [  3.356s]
writing 'modem'...
OKAY [  1.144s]
finished. total time: 8.019s
sending 'fsg' (2794 KB)...
OKAY [  0.226s]
writing 'fsg'...
OKAY [  1.155s]
finished. total time: 1.383s
erasing 'modemst1'...
OKAY [  0.611s]
finished. total time: 0.611s
erasing 'modemst2'...
OKAY [  0.605s]
finished. total time: 0.606s
sending 'logo' (1709 KB)...
OKAY [  0.143s]
writing 'logo'...
OKAY [  1.206s]
finished. total time: 1.351s
sending 'devtree' (512 KB)...
OKAY [  0.051s]
writing 'devtree'...
OKAY [  0.523s]
finished. total time: 0.575s
sending 'boot' (10240 KB)...
OKAY [  0.798s]
writing 'boot'...
OKAY [  3.386s]
finished. total time: 4.187s
sending 'recovery' (10240 KB)...
OKAY [  0.800s]
writing 'recovery'...
OKAY [  2.595s]
finished. total time: 3.396s
sending 'cdrom' (30720 KB)...
OKAY [  2.378s]
writing 'cdrom'...
OKAY [  2.992s]
sending 'cdrom' (22538 KB)...
OKAY [  3.754s]
writing 'cdrom'...
OKAY [  2.513s]
finished. total time: 11.641s
error: cannot load 'system.img.ext4'
 
erasing 'cache'...
OKAY [  1.016s]
finished. total time: 1.017s
erasing 'userdata'...
OKAY [  2.210s]
finished. total time: 2.211s
erasing 'tombstones'...
OKAY [  0.766s]
finished. total time: 0.767s
rebooting...
 
finished. total time: 0.010s
Press any key to continue . . .
 

 



#4 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 02 February 2014 - 07:14 AM

I see the problem.  You are not the only one to have this issue.  I'll post a solution in a minute.  I'm going to beotch slap moto.


Non potest esse nisi unus


#5 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 02 February 2014 - 07:22 AM

Follow these steps EXACTLY please:

 

o) Download: 

Please Login or Register to see this Hidden Content

o) Copy that to your HouseOfMoto\xt907 directory

o) Run the FXZ-ScriptGenerator.jar (it's an executable jar)

o) Press the ... button and select the VRZ_XT907_9.8.1Q-94-1_CFC.xml file

o) Enter xt907 for the model

o) Press the generate button

 

Then try running the House of Moto again with the KEEP DATA script.


Non potest esse nisi unus


#6 Lebane0214

Lebane0214

    n00b

  • Members
  • Pip
  • 6 posts
  • Current Device(s):droid razr m

Posted 02 February 2014 - 05:24 PM

after doing that i got this...

 

 
Ready to flash...
Press any key to continue . . .
 
Flashing: KEEP-DATA_xt907.bat
sending 'partition' (32 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
sending 'sbl1' (100 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
sending 'sbl2' (125 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
sending 'sbl3' (512 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
sending 'rpm' (140 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
sending 'tz' (192 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.005s
sending 'aboot' (256 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.005s
sending 'modem' (48340 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.007s
sending 'fsg' (2794 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.006s
erasing 'modemst1'...
FAILED (command write failed (Unknown error))
finished. total time: 0.614s
erasing 'modemst2'...
FAILED (command write failed (Unknown error))
finished. total time: 0.613s
sending 'logo' (1709 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.006s
sending 'devtree' (512 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
sending 'boot' (10240 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.005s
sending 'recovery' (10240 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
sending 'cdrom' (53258 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
sending 'system' (854969 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.007s
erasing 'tombstones'...
FAILED (command write failed (Unknown error))
finished. total time: 0.632s
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 0.591s
rebooting...
 
finished. total time: 0.551s
Press any key to continue . . .

 

Im not understanding what i did wrong.



#7 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 02 February 2014 - 05:26 PM

It's not finding your phone.  It has to be in AP Fastboot mode and plugged in.


Non potest esse nisi unus


#8 Lebane0214

Lebane0214

    n00b

  • Members
  • Pip
  • 6 posts
  • Current Device(s):droid razr m

Posted 02 February 2014 - 05:31 PM

it is plugged in and also in ap recovery... i am also even using my OEM usb cord



#9 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,372 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 02 February 2014 - 05:31 PM

Well, fastboot doesn't see it.  Don't know what to tell you.


Non potest esse nisi unus


#10 Lebane0214

Lebane0214

    n00b

  • Members
  • Pip
  • 6 posts
  • Current Device(s):droid razr m

Posted 02 February 2014 - 06:22 PM

thats fine i figured it out



#11 RikRong

RikRong

    Cap'n Slow

  • Superuser
  • 2,117 posts
  • LocationNoDak
  • Current Device(s):Pixel 7

Posted 03 February 2014 - 10:39 AM

thats fine i figured it out

What did you do to fix it? 


  • livinginkaos likes this

R. Long: Pixel 5

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users