I switched to RSD and like a red headed stepchild IM still having issues. Seriously I feel like a jerk why I can figure this out. It looks as simple as pie.
House of Moto [3.2]
#1281
Posted 16 December 2014 - 09:56 AM
....its never too late to learn
#1282
Posted 16 December 2014 - 10:19 AM
And I replied to your post. It's not flashing anything.
- bigjailerman likes this
Non potest esse nisi unus
#1284
Posted 01 January 2015 - 09:36 AM
Fair warning to all. The next version of the House of Moto will be dropping OMAP device support. It's going to be a complete rewrite based on the work I've done on the House of Nexus. The reason for the change is that Moto is not including xml files in some of the FXZ's anymore so I have to compensate by building the scripts from scratch. It'll make my life far easier to simply include support for snapdragon based devices going forward. I'm not sure when this rewrite will take place. I'm going to be gone for a few weeks soon, so, we'll see if I get it done before I go or after I get back.
- xKroniK13x likes this
Non potest esse nisi unus
#1285
Posted 01 January 2015 - 11:03 PM
What about
Root KDA20.62-15.1 Droid razer XT_926 ?#1286
Posted 01 January 2015 - 11:04 PM
What about
Root KDA20.62-15.1 Droid razer XT_926 ?#1287
Posted 02 January 2015 - 05:26 AM
What about
Root KDA20.62-15.1 Droid razer XT_926 ?
Not a chance to root if your not unlocked.
#1288
Posted 02 January 2015 - 01:56 PM
Sure flash it through TWRP... Oh that's right I forgotWhat about Root KDA20.62-15.1 Droid razer XT_926 ?
Sent from my LG-VS980
- spainter likes this
#1289
Posted 02 January 2015 - 01:58 PM
That's too bad... At lease I kept my copy of HOB in my Stash..Fair warning to all. The next version of the House of Moto will be dropping OMAP device support. It's going to be a complete rewrite based on the work I've done on the House of Nexus. The reason for the change is that Moto is not including xml files in some of the FXZ's anymore so I have to compensate by building the scripts from scratch. It'll make my life far easier to simply include support for snapdragon based devices going forward. I'm not sure when this rewrite will take place. I'm going to be gone for a few weeks soon, so, we'll see if I get it done before I go or after I get back.
Sent from my LG-VS980
#1290
Posted 02 January 2015 - 02:25 PM
That's too bad... At lease I kept my copy of HOB in my Stash..
Sent from my LG-VS980
The RSD Flasher will still support it. But this rewrite of the HoM is hard enough thanks to Moto's moronicy. I really do just want to them.
- spainter likes this
Non potest esse nisi unus
#1291
Posted 02 January 2015 - 02:52 PM
LMAO... But you can do it...The RSD Flasher will still support it. But this rewrite of the HoM is hard enough thanks to Moto's moronicy. I really do just want to them.
Sent from my LG-VS980
- spainter likes this
#1292
Posted 02 January 2015 - 08:24 PM
LMAO... But you can do it...
Sent from my LG-VS980
I have it mostly working already, but, Moto really screwed things up. There's no more guarantee of an XML file to tell you what the partitions are. So we have to know them ahead of time and be able to recognize them. Ok, fine, that's a pain in the ass but doable. Next up for the XT1095 (Moto X 2014 Pure Edition) 5.0 FXZ that they published up on their website, they split the system image into 8 sparse chunks. So you have to not only recognize all the files, but, you have to command the script to flash them in the proper order else you risk bricking the device. Like I said, I have it mostly working but I'm not yet happy with the robustness. I also added the ability for unlocked Moto users to add custom recovery so that it'll prompt them to flash custom recovery or stock and will walk them through using custom recovery to run the supersu install script built in to twrp to install root. But until I'm confident it can handle all the FXZ formats out there, I'm not considering it done.
- spainter likes this
Non potest esse nisi unus
#1293
Posted 03 January 2015 - 02:42 AM
keeps saying " waiting for device" after running the batch file... it's def connected to the usb 2.0 and it's the original cable. Tried 3 different cables just in case. the usb drivers are correctly installed. it's for a Verizon moto droid turbo xt1254
any suggestions?
#1294
Posted 03 January 2015 - 02:58 AM
Non potest esse nisi unus
#1295
Posted 03 January 2015 - 05:42 AM
keeps saying " waiting for device" after running the batch file... it's def connected to the usb 2.0 and it's the original cable. Tried 3 different cables just in case. the usb drivers are correctly installed. it's for a Verizon moto droid turbo xt1254
any suggestions?
Put it in ap fastboot mode.
Just FYI.. I see this issue all the time on Linux Mint. Have to open the HOM directory under root. Then launch the sh file. Strange how it works, but I guess that's just how it is.
Sent from my LG-VS980
#1296
Posted 03 January 2015 - 06:55 PM
Screw you, Moto. I'm tackling this problem in a completely different manner. I've so had enough of FXZ's.
Non potest esse nisi unus
#1297
Posted 03 January 2015 - 08:14 PM
It's time. I'm leaving this thread here for those that still want to use 3.2, but, I will no longer be providing any support for it. If you choose to continue using it, you do so without ANY expectation of support. Do NOT PM me with issues!
4.0 is now released:
And yes, it still has OMAP support.
Thread closed for further updates.
- johnlgalt and cmh714 like this
Non potest esse nisi unus
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users