Jump to content


Photo

House of Moto [4.3]


  • Please log in to reply
421 replies to this topic

#1 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 29,477 posts
  • Current Device(s):Pixel XL

Posted 03 January 2015 - 08:11 PM

Please do yourself a favor and read, read again, and read one more time™ before installing and using this tool.  If it's set up correctly, it's very easy to use.  But if you don't follow directions, it'll either not work or not do what you expect.  Failure to read and follow the directions is NOT a defect of the tool!
 
Mission statement for tool:
 
This tool facilitates the flashing of so-called factory images (FXZ's) to restore your device's partitions to a minty factory fresh state.  
 
 
WARNING: You MUST do ALL of these steps for this to work!  This is VERY different from previous House of Moto versions.  PAY ATTENTION!
 
Downloads:
o) 

Please Login or Register to see this Hidden Content

o)

Please Login or Register to see this Hidden Content

o) The correct factory image (FXZ) for your device from here: 

Please Login or Register to see this Hidden Content

 (For now....stay tuned)
 
NOTE: You MUST have Java 7 or higher installed and correctly set up to allow it to run executable jars!
 

Install:

o) You MUST install the Motorola USB driver

o) Extract the House Of Moto zip to a folder on your hard drive.  IMPORTANT: Make sure no spaces are in the path. (Windows users should extract it to C:\)
 
Setup (Needs to be completed each time you acquire a new factory image):
o) Copy the compressed factory image (the FXZ that's a zip or tar.gz) to the HouseOfMoto/IMAGES folder
o) Run the HouseOfMoto.jar
o) Select the compressed factory image you copied to your HouseOfMoto/IMAGES folder
o) When the extraction and script generation is complete, click finish

 

 
NOTE:
 
If you have an OMAP device (xt875, xt912, etc), you MUST extract 

Please Login or Register to see this Hidden Content

 to the HouseOfMoto/TOOLS folder and overwrite the existing files
If you have a 2012 era SNAPDRAGON device (xt926, xt907, etc), you MUST extract

Please Login or Register to see this Hidden Content

 to the HouseOfMoto/TOOLS folder and overwrite the existing files
 

USAGE:

 

Warning: Do NOT run the script until you are ready to start flashing.  It will start flashing IMMEDIATELY when you run the script!

 

o) Your phone MUST be in AP Fastboot mode.  Try holding volume down and pressing the power button when the phone is off.

o) Your phone MUST be connected to a USB 2 port via the original OEM USB cable that came with your phone.

o) In the new HouseOfMoto/MOTO folder, run flashme.bat or flashme.sh (see Linux/Mac notes below)

o) Depending on your factory image and device, you may be asked a series of questions during flashing.  READ THEM CAREFULLY.  Failure to do so will result in your data being ERASED!

 

(Linux/Mac Users):
o) You may need to chmod +x flashme.sh
o) You will need to run it in a terminal as sudo ./flashme.sh
 
Custom Recovery:
 
Warning: This only applies to UNLOCKED USERS.  If you "try" this on a locked bootloader, you will brick, and I will NOT be sympathetic to you.
 
o) Download your custom recovery image file from

Please Login or Register to see this Hidden Content

.  ONLY TWRP is supported.
o) Copy it to the HouseOfMoto/RECOVERY folder
 
NOTE: Some Moto devices do not allow booting recovery from memory, which this script will attempt to do when installing SuperSU.  If you're one of the unlucky ones where booting recovery from memory does not work, you will have to flash custom recovery, boot it, and allow it to run the SuperSU script when you reboot to system.
 
ALSO: If you add custom recovery AFTER you generate your scripts, it will not work.  You will need to regenerate the script!
 
DA FAQ:
 
Q: My RAZR HD or M is stuck in AP Fastboot mode with a sticky bit failure.  Help?
A: 

Please Login or Register to see this Hidden Content

  Follow that.
 
Q: I attempted the SuperSU install from the script and now boot to AP Fastboot with a failed flash message every time I restart the phone.
A: You're either on a locked bootloader or your phone doesn't support booting recovery from memory.  Rerun the flashme script and do not use the SuperSU option this time.
 
SUPPORT:
 
Something went wrong...now what?
 
Flash issue:
 
o) Provide the following information:
 
-Model of phone
-Exact system version the phone was on before flashing (4.1.2 is NOT a version)
-Exact filename of the FXZ you are attempting to flash
-The text of the AP Fastboot mode
-The contents of the flashme.bat/sh file from the HouseOfMoto/MOTO folder
-The text copied from the flashme.bat/sh run (select all the text, copy it, and paste it into your post)
-The text copied from the HouseOfMoto/Generate.log file
-Details of everything you've "tried"
-Any other pertinent information that will help us diagnose and fix your problem.

  • perfoliate, johnthehillbilly, spainter and 12 others like this

R6bmQQ4.jpg

PIxel XL


#2 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 29,477 posts
  • Current Device(s):Pixel XL

Posted 03 January 2015 - 08:11 PM

VERSION HISTORY:

 

7/10/2015: 4.3 released

:Fixed a bug with extracting FXZ's where they use the xml filename as the root directory (morons)

 

7/9/2015: 4.2 released

:Fixed bug causing optional partitions in Linux/Mac to always be flashed.  Sometimes twice depending on what you selected.  FFS, seriously?  UGH

 

1/4/2015: 4.1 released

:Fixed bug causing Linux/Mac script to not be written

:Added custom recovery *FOR UNLOCKED USERS ONLY* option

:Fixed extraction code

:Added Generate.log file creation

:Misc fixes to generated scripts

 

1/3/2015: 4.0 rewrite released


  • Platy87, johnthehillbilly, bdazzg1 and 2 others like this

R6bmQQ4.jpg

PIxel XL


#3 cmh714

cmh714

    Tech Service & Beyond

  • Smod
  • 3,271 posts
  • LocationSoCal
  • Current Device(s):Nexus 6

Posted 03 January 2015 - 08:22 PM

1/9 ??? planning for the future :) :)



#4 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 29,477 posts
  • Current Device(s):Pixel XL

Posted 03 January 2015 - 08:27 PM

So I wanted to talk about the changes I've made.  The previous version of House of Moto was written to be more of a framework for users to customize scripts for flashing.  No one ever took advantage of it and instead it became a tool for simply fixing devices.  This version has embraced that.  I've modeled this after my new House of Nexus tool.  It will generate a script (bat for Windows sh for Linux/Mac) for your factory image (FXZ).  My long time House of Moto users are probably freaking out a little bit seeing only one script getting generated.  "But I need KEEP DATA!  I need UNIVERSAL!  WTF, Samuri?!?!?"  Calm down.   :D  If you fully read the OP, which you did.....RIGHT? :D you will see the part that says "the script will ask you questions during flashing."  Let's talk about that for a minute cause this is where the power of the new HoM comes from.  When the script generator detects certain partitions, it'll add special code to the script to prompt you with an option.  So, let's say you're unlocked and are looking to downgrade.  Typically you'd have generated a UNIVERSAL script and gone to town, right?  Ok, but, the magic there is that it simply skips certain partitions.  GPT and TZ, specifically.  Additionally motoboot on some devices.  So this new script that gets generated will ask you:

 

Flash GPT partition?  [y/n]

Flash TZ partitoin?  [y/n]

 

If you're looking to downgrade (again, ONLY for unlocked users), you select N to those questions.

 

Now, what about FULL vs KEEP DATA?  Same concept as UNIVERSAL.  The difference between the two is that FULL erases the userdata partition whereas KEEP DATA does not.  Soooooo, the script will now ask you if you want to erase the userdata partition.  Use that option carefully.

 

What does this all mean for the future?  Well, like with the House of Nexus, I have some stuff I'm going to add soon for unlocked users that'll truly rock.  Things like flashing custom recovery (TWRP only) in place of stock recovery and then prompting the user to install SuperSU using TWRP.  That'll be in 4.1 most likely tomorrow.

 

This is all new code so please report any issues you encounter.


  • johnthehillbilly, bdazzg1, spainter and 2 others like this

R6bmQQ4.jpg

PIxel XL


#5 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 29,477 posts
  • Current Device(s):Pixel XL

Posted 03 January 2015 - 08:27 PM

1/9 ??? planning for the future :) :)

 

Whatttt?  No idea what you're talking about.  :D


  • cmh714 likes this

R6bmQQ4.jpg

PIxel XL


#6 Android_michael

Android_michael

    n00b

  • Members
  • Pip
  • 1 posts

Posted 04 January 2015 - 01:37 AM

Hey Samuri, thank you for this tool and your time and effort you put into this! I have a brand new Imac running osx 10.10.1 so everything is a clean install.  I did the following, installed Java 8.25.  

 

The drivers linked in the post are windows drivers with an .msi so I googled moto drivers for mac and downloaded the MDM installer 2.2.9 from this page

Please Login or Register to see this Hidden Content

and installed that.

 

 I downloaded the FXZ for my Droid Maxx xt1080 from the motofirmware site which is called CFC-fastboot-obake-maxx_verizon-user-4.4-SU2-3-15-release-keys.xml.zip.  

 

Downloaded House of moto 4.0 extracted it to the root of my Hard drive which would be Macintosh HD/Houseofmoto

 

Put the FXZ into the house of moto/images folder 

 

Ran the houseofmoto.jar which extracts this set of commands

 

Warning: Multiple files found in RECOVERY.  Selecting first match!
Custom recovery not found.
Extracting: boot.img
...CRC32 checksum: 2648339372
Extracting: CFC-fastboot-obake-maxx_verizon-user-4.4-SU2-3-15-release-keys.xml
...CRC32 checksum: 2581368508
Extracting: fsg.mbn
...CRC32 checksum: 1572675346
Extracting: gpt.bin
...CRC32 checksum: 2475493426
Extracting: logo.bin
...CRC32 checksum: 2935950521
Extracting: emmc_appsboot.mbn
...CRC32 checksum: 3757131677
Extracting: motoboot.img
...CRC32 checksum: 679820494
Extracting: rpm.mbn
...CRC32 checksum: 3624665795
Extracting: sbl1.mbn
...CRC32 checksum: 1733016163
Extracting: sbl2.mbn
...CRC32 checksum: 3694223678
Extracting: sbl3.mbn
...CRC32 checksum: 3599702739
Extracting: tz.mbn
...CRC32 checksum: 2423004816
Extracting: emmc_appsboot.mbn
...CRC32 checksum: 2989107917
Extracting: motoboot.img
...CRC32 checksum: 2812753877
Extracting: rpm.mbn
...CRC32 checksum: 2552887963
Extracting: sbl1.mbn
...CRC32 checksum: 2446756449
Extracting: sbl2.mbn
...CRC32 checksum: 2431107373
Extracting: sbl3.mbn
...CRC32 checksum: 2897925626
Extracting: tz.mbn
...CRC32 checksum: 3657100232
Extracting: motoboot.img
...CRC32 checksum: 3317427560
Extracting: NON-HLOS.bin
...CRC32 checksum: 1020908380
Extracting: recovery.img
...CRC32 checksum: 3010878486
Extracting: system.img
...CRC32 checksum: 2874281561
Found CFC-fastboot-obake-maxx_verizon-user-4.4-SU2-3-15-release-keys.xml
 
clicked finish
 
 
Then I go into houseofmoto/moto to look for the Flashme.bat or Flashme.sh and I cannot find that file.  I've searched the computer using the key words flashme.bat and flashme.sh  to see if I have missed something and it is not there.  I only have usb 3 ports on this mac but I am using the original usb cable in fastboot mode.  
 
is there something I am missing?  
 
Thank you again for all your hardwork!

  • bigjailerman likes this

#7 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 29,477 posts
  • Current Device(s):Pixel XL

Posted 04 January 2015 - 04:30 AM

I'll look into it. Looks like a bug of some kind.
  • bigjailerman likes this

R6bmQQ4.jpg

PIxel XL


#8 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 29,477 posts
  • Current Device(s):Pixel XL

Posted 04 January 2015 - 06:54 AM

Found and squashed your bug, but, I found another one that's more concerning to me.  It's taking a bit longer to fix than I'd like.  Should be done soon, though.  Watch for 4.1 shortly.


  • johnthehillbilly, transmissiontech, spainter and 1 other like this

R6bmQQ4.jpg

PIxel XL


#9 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 29,477 posts
  • Current Device(s):Pixel XL

Posted 04 January 2015 - 07:45 AM

4.1 is out now.  Reread the OP.


  • transmissiontech, spainter and bigjailerman like this

R6bmQQ4.jpg

PIxel XL


#10 bigjailerman

bigjailerman

    Member

  • Members
  • PipPip
  • 31 posts
  • Twitter:Dave L
  • Locationon the hop
  • Current Device(s):razr M, S4 I545

Posted 04 January 2015 - 09:41 AM

damn you waste no time...thank you


  • SamuriHL, johnthehillbilly, livinginkaos and 2 others like this

....its never too late to learn :google


#11 transmissiontech

transmissiontech

    Your Tranny Specialist

  • Dedicated Supporter
  • PipPipPipPipPip
  • 7,080 posts
  • LocationMissouri...Show Me State
  • Current Device(s):Google Pixel 32 gig

Posted 04 January 2015 - 12:29 PM

Sam the bug squasher ...lol


  • rickw likes this

Thanks Droidrzr for the continued support of my family and a special thank you to Kaos and Kelly....

Google pixel 32 gig....


#12 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 29,477 posts
  • Current Device(s):Pixel XL

Posted 04 January 2015 - 01:41 PM

I use a katana.  :D


  • johnthehillbilly and bigjailerman like this

R6bmQQ4.jpg

PIxel XL


#13 derber

derber

    n00b

  • Members
  • Pip
  • 3 posts

Posted 06 January 2015 - 10:22 PM

I have a Droid Razr M

Sometimes the phone doesn't initialize the camera, and when that happens, I restart the phone.

Yesterday this happened and I was restarting the phone, but it never came alive. It's stock in the loading part (the red eye thing).

 

I can access my AP FastBoot, it says "Device is locked"

 

So I reached your topic, and tried to do what you said, but there were 2 problems:
First, it seems like the script doesn't get extracted for me. It keeps giving me an error saying "ERROR: XML script not found in this factory image.  This is not yet supported." (there are two more lines before this, but didn't seem much relevant)

(I did the parts exactly as mentioned in the first post. I extracted HouseOfMoto in C:\, copied the image file in image folder, and then imported the file in HouseOfMoto.jar

2. There is no TWRP file for my phone model.

 

Does anyone have any idea what I should do?! I'd reeeeeaaaaally appreciate it if some one could help me

 

Thanks in advance

 

P.S: Details in the order mentioned in the first post:

 

- Droid Razr M
- I believe my android version is 4.1.2 and I've never tried rooting, unlocking, flashing or anything else, the phone was running on a raw Android
- There is no FXZ file that I can see. If there's a location that I can check that, please let me know
- AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-09 02:30:05)
eMMC Info: Size 8 GB
 
Device is LOCKED, Status Code: 0
 
Battery OK
 
Transfer Mode:
USB Connected
 
Fastboot Reason: Boot menu selected
usb connected
 
- The HouseOfMoto/MOTO folder is empty
- There is no such file (flashme.bat/sh)
- Custom recovery not found.
Using factory image: Blur_Version.21.21.15.quark_verizon.verizon.en.US.zip
ERROR: XML script not found in this factory image.  This is not yet supported.
-  People posted one more solution to this problem which was going to recovery mode, and then pressing VOL down and VOL up and releasing VOL up which would lead to a "factory reset", but when I try that, the broken android guy keeps saying "no command" 


#14 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 29,477 posts
  • Current Device(s):Pixel XL

Posted 07 January 2015 - 05:38 PM

You're lucky that didn't work or you'd have bricked that phone. What made you think that was the right FXZ for your device? The factory image (which is the fxz) you are using is not for the razr m. Period.

Sent from my Nexus 6 using Tapatalk


  • rickw, johnthehillbilly and cmh714 like this

R6bmQQ4.jpg

PIxel XL


#15 derber

derber

    n00b

  • Members
  • Pip
  • 3 posts

Posted 07 January 2015 - 11:41 PM

Well, perfect then!

I'm basically left with no solutions. Sounds pretty much like having a bricked device!

 

Any ideas for a solution maybe?!

 

Thanks



#16 RikRong

RikRong

    Cap'n Slow

  • Superuser
  • 2,115 posts
  • Twitter:@rlongjr80
  • LocationSoCal
  • Current Device(s):Moto X Pure 2015 / N7 2013 / RazrM

Posted 08 January 2015 - 03:51 AM

Well, perfect then!

I'm basically left with no solutions. Sounds pretty much like having a bricked device!

Any ideas for a solution maybe?!

Thanks

Hopefully, the solution is flashing the correct FXZ. If you're not bricked from flashing the incorrect FW, you should be able to flash the correct FW.

Sent from my HTC6525LVW using Tapatalk


  • derber likes this

R. Long: Nexus 5 on Carbon / Slimmed N7 2013 / RazrM stock KK

 


#17 johnthehillbilly

johnthehillbilly

    Gear jammin' S-Mod

  • Smod
  • 6,470 posts
  • Twitter:@johnhillbilly
  • Google+:http://goo.gl/ColUJ .. johnthehillbilly@gmail.com
  • LocationSomewhere between here, and there...
  • Current Device(s):unlocked RAZR HD (xt926)... RAZR (xt912)

Posted 08 January 2015 - 03:59 AM

Well, perfect then!

I'm basically left with no solutions. Sounds pretty much like having a bricked device!

Any ideas for a solution maybe?!

Thanks


You NEED to download and flash the PROPER firmware for the M ..... You CAN find it via the motofirmware link in the OP.... :):)
  • rickw and derber like this

Feeding my android addiction......... one phone at a time.....

jhf.png

If you are feeling generous and would like to buy me a drink.... coffee :)


#18 livinginkaos

livinginkaos

    I don't know what I'm doing anymore.....

  • Administrator
  • 13,867 posts
  • Google+:Hangouts - livinginkaos@gmail.com
  • LocationOregon
  • Current Device(s):Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7

Posted 08 January 2015 - 04:57 AM

They can also be found here for the xt907 RAZR M -

Please Login or Register to see this Hidden Content



sent from my N6


  • rickw, johnthehillbilly and derber like this

b2wvCBn.png

Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7


#19 derber

derber

    n00b

  • Members
  • Pip
  • 3 posts

Posted 09 January 2015 - 01:00 PM

Thanks guys.

 

I haven't done anything to the phone, so it's not hard bricked, yet!

 

How can I know the right FXZ?! (regarding that I'm not sure about my Android version. As long as I can remember, it was up-to-date and the version was 4.1.2)

 

And once that I get the right FXZ, can I flash the device using the solution provided in this topic?!



#20 rcmitch

rcmitch

    n00b

  • Members
  • Pip
  • 9 posts
  • Current Device(s):Bionic

Posted 15 January 2015 - 09:47 AM

Trying to FXZ my Bionic. Below is the message I get. I had planned on just using the old HoB files to FXZ but apparently I don't have them anymore. What'd I do wrong here? Seems really straightforward. Double checked the process.
 
Custom recovery not found.
Using factory image: VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip
ERROR: XML script not found in this factory image.  This is not yet supported.

  • jdax likes this




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users