yashsingh1/xdaforums huggingface dataset:
[Droid Ultra General] eurostylin:
I've followed the directions perfectly. Made a directory:

C;\\HouseOfMoto

It is trying to find a fastboot.exe that is not existent.

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: KEEP-DATA_xt1080.bat

1 file(s) copied.

1 file(s) copied.

1 file(s) copied.

1 file(s) copied.

C:\HouseOfMoto

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

'.\fastboot.exe' is not recognized as an internal or external command,

operable program or batch file.

Could Not Find C:\KEEP-DATA_xt1080.bat

Press any key to continue . . .
[Droid Ultra General] metalgear6:
those support files are in my directory
[Droid Ultra General] bigv5150:
i have all the screen shots how do you post a picture on this site.
[Droid Ultra General] metalgear6:
aha! got it! thank you all so much, i knew it was something simple
[Droid Ultra General] bigv5150:
Ok great glad you figured it out it really comes down to having it all in the right spot.
[Droid Ultra General] eurostylin:
All fixed! Thanks guys. This worked perfectly, no more root, and I'm downloading the update now.

I had fat fingered the directory name for the downloaded recovery files.
[Droid Ultra General] SamuriHL:
Flashmode is up to you. RSD or fastboot snapdragon for this phone. It's more personal preference than anything.
[Droid Ultra General] bigv5150:
Ok since I dont know how to post screen shots here are pics from my drop box just click the link and make sure each file of mine looks like yours.

https://www.dropbox.com/s/danswo93ax1tvvm/Screenshot (10).png

https://www.dropbox.com/s/3vwo7ibyf73z0y0/Screenshot (11).png

https://www.dropbox.com/s/qx571rcgq58xkel/Screenshot (12).png

https://www.dropbox.com/s/ns0op5ol6z3o52f/Screenshot (13).png

https://www.dropbox.com/s/fqn9y3ljnjxygh8/Screenshot (14).png

Dont worry about all the extra stuff for xt907 and xt875 I have a razr M and a bionic all you need obviously is xt1080 stuff.
[Droid Ultra General] SamuriHL:
It does the same as RSD only using the fastboot command line. The scripts (i.e. what it flashes) are identical to the RSD scripts, only converted to fastboot commands. The reason I included both is cause some people prefer one over the other and if one doesn't work I wanted to give the option to try the other. But it's strictly a matter of preference.

---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------

Quite correct. Security on the new update prevents going back.

---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------

Just some advice to make things easier. I posted a CreateLOG script last night. This spits out the devices attached to USB (both adb and fastboot so it should show if they're truly in AP Fastboot or not) and their entire folder structure so you can see if it's set up right. Makes our lives easier trying to troubleshoot. If people are having issues, have them run that. It'll open the log it creates in notepad and they can copy and paste it here.
[Droid Ultra General] hdmunger:
I went through the whole FXZ-keep data process, installed the update, then rooted with RockMyMoto and everything worked fine.

The question I have (in hindsight) based on people with the boot loop problem is can they just boot into fastboot and re-flash the stock recovery so that the update finds it and can complete installation?
[Droid Ultra General] bigv5150:
Damn brother you are always working you can't just leave it alone you have to make it better :)

That is genius it gives an account of my entire house of moto great work.
[Droid Ultra General] SamuriHL:
Possibly. But the best way is to flash recovery and wipe the cache and start over with a fresh ota download and install attempt.

---------- Post added at 03:01 PM ---------- Previous post was at 02:57 PM ----------

It comes from supporting quite a few xt1080 users who found themselves in a jam yesterday. A lot of times when the House doesn't work, it's usually due to an installation problem. I tried to make it fairly straight forward....Download the HoM zip, extract it to the C drive (I saw you say you have it on your desktop but some people have spaces in their path to the desktop and that WILL blow it up), download a support file, extract it to their C:\HouseOfMoto directory, create an FXZ_xt### directory to match their phone, and extract the contents of their FXZ into the new FXZ_xt### directory. That should be it for setup. But you know how it goes. A lot of times people wait until they soft brick the phone before they start searching for the right tool to fix it, and in a panic they try to rush things instead of taking the proper time to read. So this createlog tool will help us catch these little installation issues to better help people.
[Droid Ultra General] kevmosis:
I keep getting "Warning: Please check input file. Either XML format is wrong or image files associated with it are missing." and it's on the C drive. Everything seems to be in the right place. Any ideas? Could I have downloaded the wrong fxz of the 3 options available?
[Droid Ultra General] SamuriHL:
Ahhhh, a candidate for my new tool. :D

CreateLog

Download CreateLog.zip above, extract the CreateLOG.bat file to your c:\HouseOfMoto directory, run it, and post the results..
[Droid Ultra General] SamuriHL:
It looks good to me. Delete the KEEP_DATA*.* out of the fxz_xt1080 directory. It seems it didn't clean those up like it should. Try it again after doing that. If it still doesn't work, post the rsd\SWDL.txt file.
[Droid Ultra General] kevmosis:
Didn't work. Sorry, where do i find that file?
[Droid Ultra General] SamuriHL:
Well, that's why I said the rsd\SWDL.txt file. ;) Look at your post with the file listing. :D And you ARE connecting your phone in AP Fastboot mode BEFORE running this right?
[Droid Ultra General] kevmosis:
Ha... oops. Here it is, and yes i'm in AP Fastboot. If I don't use the RSD option it gets stuck on waiting for device. Kind of like it isn't connected right.

11/09/13 13:29:29 --------------------------------------------------------------------------------

11/09/13 13:29:29 New Log Started For Software Download.

11/09/13 13:31:32 --------------------------------------------------------------------------------

11/09/13 13:31:32 New Log Started For Software Download.

11/09/13 13:43:50 --------------------------------------------------------------------------------

11/09/13 13:43:50 New Log Started For Software Download.

11/09/13 13:45:56 --------------------------------------------------------------------------------

11/09/13 13:45:56 New Log Started For Software Download.

11/09/13 13:49:38 --------------------------------------------------------------------------------

11/09/13 13:49:38 New Log Started For Software Download.

11/09/13 13:55:54 --------------------------------------------------------------------------------

11/09/13 13:55:54 New Log Started For Software Download.

11/09/13 13:56:11 --------------------------------------------------------------------------------

11/09/13 13:56:11 New Log Started For Software Download.

11/09/13 13:56:26 --------------------------------------------------------------------------------

11/09/13 13:56:26 New Log Started For Software Download.

11/09/13 14:00:38 --------------------------------------------------------------------------------

11/09/13 14:00:38 New Log Started For Software Download.

11/09/13 14:13:23 --------------------------------------------------------------------------------

11/09/13 14:13:23 New Log Started For Software Download.

11/09/13 14:14:04 --------------------------------------------------------------------------------

11/09/13 14:14:04 New Log Started For Software Download.

11/09/13 14:27:47 --------------------------------------------------------------------------------

11/09/13 14:27:47 New Log Started For Software Download.

11/09/13 14:35:55 --------------------------------------------------------------------------------

11/09/13 14:35:55 New Log Started For Software Download.
[Droid Ultra General] SamuriHL:
Correct. It's not seeing it. When you ran the CreateLOG was it connected then? If so, your device isn't being seen by your PC at all. So, USB troubleshooting 101:

o) Ensure you have the LATEST motorola usb driver installed (google it)

o) Ensure you are using the OEM USB cable that came with your phone (yes, it matters)

o) Ensure you are NOT connected to a USB 3 port

o) Do not connect through a USB hub

o) Try changing the port if possible

o) Reboot the PC and plug it in again
[Droid Ultra General] kevmosis:
It is USB 3. Any way to make that work?
[Droid Ultra General] SamuriHL:
Sadly not to my knowledge, no.
[Droid Ultra General] kevmosis:
Ok, glad to know that's all it is. Thanks for the help.
[Droid Ultra General] SamuriHL:
You're welcome. Sorry I don't have better news for you.
[Droid Ultra General] SamuriHL:
If it's the "same problem" then it's the same reply. USB 3 doesn't work.
[Droid Ultra General] boosty06:
nevermind I got it! had to update my drivers! Guess I should read before I post lol! Thanks for the awesome work Samuri!

---------- Post added at 05:19 PM ---------- Previous post was at 05:14 PM ----------

sorry hit reply in the wrong part didnt mean to quote him but it wasnt the USB 3
[Droid Ultra General] SamuriHL:
Glad you got it sorted out.
[Droid Ultra General] spiral777:
fxz

worked like a charm! Thank you!
[Droid Ultra General] WaltA:
I guess I am looking for some advice though. Is one method is more fool proof, or idiot proof, than the others, for a beginner with no experience with any of them?
[Droid Ultra General] SamuriHL:
No. They are equally fine. Like I said, it's just a preference. If in doubt, I guess use RSD but really it doesn't matter.
[Droid Ultra General] imabigd:
Google Drive Promotion Post House of Moto

All,

Thanks for all the wonderful work (Samuri, much love). After using HOM to get back to stock and accepting the OTA, everything works fine, except the 50 GB Google Drive Promotion gives me the error "Failed retrieving offer from server" when I go through the product tour. Restarting, trying again later, doesn't help.

Anyone else having that problem? Google support says that if there server is working correctly, my device may not be eligible. I've got a Droid Maxx (xt1080m) which is listed in the promotion, so it should work.

I used the FXZ file "obake-maxx_verizon-user-4.2.2-12.9.0Q2.X-160-OBK_TA-14-7-7-release-keys-CFC.xml" when flashing back to stock. Was that not the correct file?

If the 50 GB promotion gets hosed with this method, it's a perfectly acceptable trade-off in my mind to be able to accept the OTA's so no worries on my end. I'm curios if others are experiencing this, though, or if I goofed and used the wrong FXZ or something else.

Thanks in advance.

ImaBigD
[Droid Ultra General] SamuriHL:
I haven't seen anything like that, no. I know others that have used the HoM have been able to get the 50gb drive space offer to work just fine. Something weird's going on there. Try wiping the cache and see if that works. If not, it may require an FDR to get it to work properly. Only you can decide if it's worth the trouble of doing that or not.
[Droid Ultra General] lioryte:
You have to uninstall the updated google drive app. You updated it/ kept your data, that's why you dont see it
[Droid Ultra General] imabigd:
Thanks Samuri and lioryte. Wiping the cache didn't seem to do the trick and also deleting the updated app didn't either. I can't seem to completely delete the drive app from the device all together, but deleted the updated version, and then downloaded it again from the app store - to no avail.

A FDR may fix the issue, but I'm not sure it's worth it since the amazing benefit of HOM is that I saved all my data.

Thanks for the quick replies.
[Droid Ultra General] IntenseImage:
How long should the HOM process take to run on the phone ... the "writing recovery" is showing DONE but nothing else came up after that.
[Droid Ultra General] oldmaiz0r:
Can't change settings?

First of all thanks to SamuriHL and bigv5150 for this guide.

I followed the instructions and was able to successfully flash my MAXX back to stock while preserving data. Took the OTA update and it looked like everything worked. Then I noticed I no longer saw my Active Notifications on the screen. Went to the settings and tried to change them but it didn't "take." Tried changing other settings and I'm seeing the same thing; the checkbox I click changes from/to checked/unchecked, but when I go to another screen and go back, the settings didn't actually change. It's like it's not able to write the changes to disk or something. Is anyone else having this issue?

EDIT: Disregard. Started messing around with other settings including checking for updates and it downloaded and ran the OTA update (again?). Changing settings seem to be working now.
[Droid Ultra General] SamuriHL:
It should be doing the next step. Recovery is small. System isn't and will be sent in pieces. But if it's not finishing you may have to try switching usb ports or the cable.
[Droid Ultra General] IntenseImage:
Ok well I rebooted it ... Showed no root ... Tried to install the OTA and it errored. Rebooted fine though and did the whole android is upgrading thing. How can I verify the ota didn't install before trying HOM again?

Edit ... And it just installed a camera update from the market. I am seeing the old "75" baseband. Looks like it partially took the ota. Safe to still run HOM again?
[Droid Ultra General] SamuriHL:
You can't really verify easily. What's the kernel show? It's not really all that safe to try to flash back with HoM unless you have the new FXZ which I don't think is posted yet.
[Droid Ultra General] SamuriHL:
I don't know your phone so I'm not sure if that's the new stuff or not.
[Droid Ultra General] IntenseImage:
From what I can tell the baseband should have been updated. Since its running I'll prob wait for someone who had the same issue or wait for the updated files
[Droid Ultra General] SamuriHL:
New FXZ will be posted any day now.
[Droid Ultra General] WaltA:
Camera update app?

Sorry for the tangent.... exactly what app is that? The only camera app I can find in the market from MOT, says it is incompatible with my phone.
[Droid Ultra General] xjack:
Weird you got the new system but kept the old baseband.
[Droid Ultra General] IntenseImage:
Just says Motorola camera
[Droid Ultra General] bigv5150:
Happens more than you think with a botched update.
[Droid Ultra General] IntenseImage:
What would be the best option -- wait for the new files to be posted and try the new ones to restore with data or run the one we have now?
[Droid Ultra General] SamuriHL:
If the phone is working, leave it for now. Once the new FXZ is posted, use the HoM with the keep data script to refresh your install, and then reroot it.
[Droid Ultra General] bigv5150:
The problem is if he runs the fxz we have now and security had been updated then he could be screwed and brick his phone. I say just wait for the new fxz and use house of moto save data option to be safe.
[Droid Ultra General] SamuriHL:
Slacker. :P
[Droid Ultra General] IntenseImage:
Ok so even if I didn't try the current fxz, using the new file (when available) wouldn't be a problem?
[Droid Ultra General] SamuriHL:
Yea, the new one will match the security. The old one does not and will fail to flash and cause you all kinds of problems. Stuff I could fix but it's better to not go down that path. Keep an eye on the FXZ site and wait for the new one to pop up. It'll be this week most likely. Skrilax is very good about getting them posted.
[Droid Ultra General] bigv5150:
I'm just trying to help you out because if he breaks his phone it's not going to be me helping him fix it is going to be you.;)
[Droid Ultra General] SamuriHL:
LMAO :) I'm just giving you a hard time because you were "samuri'd" :D LOL
[Droid Ultra General] cmarshack:
Do I need to download all three of these files?

Size	MD5	Carrier	File

717.8 MiB	9309C2963D70F08EA504E81FE7AF7445	Verizon US	XT1080_obake_verizon-user-4.2.2-12.9.0Q2.X-160-OBK_TA-14-4-4-release-keys_CFC.xml.zip

722.4 MiB	0BFADF800C7EFBBE09C863B4F285D653	Verizon US	obake-maxx_verizon-user-4.2.2-12.9.0Q2.X-160-OBK_TA-14-7-7-release-keys-CFC.xml.zip

722.4 MiB	89314EE4D2000AFF026356FADD56CD6D	Verizon US	obake_verizon-user-4.2.2-12.9.0Q2.X-160-OBK_TA-14-7-7-release-keys-CFC.xml.zip
[Droid Ultra General] SamuriHL:
Nope. Just the one for your phone.
[Droid Ultra General] cmarshack:
Thanks for the reply and for all of the info!

Just to clarify, if I have a Verizon Droid Maxx do I use the the one that has XT1080 or this one that has MAXX in the title:

722.4 MiB	0BFADF800C7EFBBE09C863B4F285D653	Verizon US obake-

maxx_verizon

-user-4.2.2-12.9.0Q2.X-160-OBK_TA-14-7-7-release-keys-CFC.xml.zip
[Droid Ultra General] IntenseImage:
Use the MAXX one
[Droid Ultra General] SamuriHL:
This. Thanks.
[Droid Ultra General] Nickrick2641:
Thank you so much!

SamuriHL , words cannot describe how happy I am to have used HouseofMoto, my soft Bootloop is fixed! ( I received a new droid mini in the mail :silly: so I guess I'll just back up this one and send it back, but Awesome work man!

Btw for anyone using a droid mini (XT1030 ), I tried RSD via HouseofMoto, only copied one file, and didn't do anything.

Attempted with Fastboot Snapdragon ( This will say failed several times, but it will correctly write to the necessary partitions in order to reset the phone without losing data.

Moto Droid Mini XT1030

Lastly, Drive C: is where HouseofMoto Zip should be extracted to (C:\HouseofMoto) otherwise both your laptop and phone will look at each other in utter confusion and sputter out error messages.

Most of it has been said before but , for those Droid Mini users, it may help somewhere?

Again, Thank you a million times SamuriHL!:D
[Droid Ultra General] ahjee:
so if i recently updated my phone to the latest ota (12.15.15) and then accidentally deleted both my back up of the rom and the OS on my phone, leaving me unable to boot up into anything but fastboot am i supposed to be able to still restore either files here http://sbf.droid-developers.org/obake/list.php to regain stock out of the box firmware and boot up regularly even though i've updated to the very latest OTA? Because...well, it's not working for me with RSD Lite or Houseofmoto unless i am Homering it and messing something up here

I am under the impression i need the latest 12.15.15 xml in order to return my phone into a phone and not a brick...
[Droid Ultra General] erishasnobattery:
You are under the correct impression.
[Droid Ultra General] kclantz:
Ahjee,

Hopefully the file we need will be posted soon, I found this post a few pages back:

So hopefully we will be able to our phones back up and running again soon.
[Droid Ultra General] SamuriHL:
Yea I'm actually surprised that they've not been posted yet. Just keep an eye on Skrilax's site....they'll show up eventually. But I had a conversation with someone yesterday about these new Droids. I'm NOT impressed with them. The morons security locked the system partition which means that the old tricks that we used to use to fix bricked phones without an FXZ won't work anymore. You guys and gals are literally stuck until a new FXZ can be found. Once you take the OTA, DON'T BRICK! :)
[Droid Ultra General] Skrilax_CZ:
I have Droid MAXX myself, still waiting for the new FXZs.
[Droid Ultra General] ahjee:
you'd think google owning moto now that they would have kept the system partition capable of being fixed without the FXZ...stupid F*****S!

O well, guess I am without a phone until the file is released, thanks for the replys guys cause i was getting frustrated trying the HouseofMoto method, thinking I was doing something wrong

---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------

I hope for all of our sake that you get your hands on them soon! haha.

I'll be patiently waiting until then.
[Droid Ultra General] Skrilax_CZ:
Will put it on ASAP when I get it. In the meantime, it's time to up some Moto G files :)
[Droid Ultra General] SamuriHL:
Thanks for the reply! Greatly appreciated.
[Droid Ultra General] xdraphael:
Bricked Phone Too

I bricked my phone as well (Droid Maxx), after I had successfully restored to stock (using RSDLite), re-rooting with RockMyMoto. Made a stupid fat-fingered mistake of restoring BOTH apps and system settings, instead of just apps using Titanium. Same as you I couldnt revert to the previous firmware.

Long story short - went to VZW store, said phone started bootlooping right after the OTA, and they sent me a new one. Old one is on its way back. Fingers crossed they dont figure out what caused it. Go to your store and try it if you're still stuck. Blame it on the OTA.
[Droid Ultra General] SamuriHL:
I'll let you re-read the directions which make it VERY clear about this issue and solve this problem.

---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------

Or you know, instead of lying to VZW and causing costs for legitimate problems to go up, you could just wait for the FXZ to appear.
[Droid Ultra General] Skrilax_CZ:
This abuse is the reason why the bootloaders are locked, you know? You're lucky they didn't check for "qe" status, because that marks when you boot phone with rooted system and means "goodbye warranty".
[Droid Ultra General] SamuriHL:
Sweet. Enjoy!
[Droid Ultra General] inkdaddy66:
It looks like the scripts aren't available right now due to mediafire. I'm looking for the save data script. Is there anywhere else I can find it?

Edit. Scripts downloaded. I'm still a little fuzzy about how this process/application works but I'm sure I'll find out.

53N7 FR0M M4 DMAXX V1A 7A9A7A7K
[Droid Ultra General] Archangel:
Thanks for this, I have a Droid Mini and am wondering do I extract the entire contents of the mini FXZ to the folder I created in the house of moto directory? When I extract it there are other folders in there,,,do they all go in the FXZ_xt1030 folder I created? I ask because another tutorial said not to extract the folders with the other contents?
[Droid Ultra General] bigv5150:
Unzip the fxz then move to the folder in the house of moto don't unzip any other files. All you are doing is unzipping the fxz and nothing else and movinf that entire file to the folder you created.
[Droid Ultra General] SamuriHL:
The simple test to know you got it right:

Does boot img exist directly under your FXZ directory?
[Droid Ultra General] inkdaddy66:
how long should I be waiting for device?

53N7 FR0M M4 DMAXX V1A 7A9A7A7K
[Droid Ultra General] SamuriHL:
Did you put your phone in AP Fastboot mode? Cause your PC isn't seeing it.