yashsingh1/xdaforums huggingface dataset:
[Droid Ultra General] tCizler:
Too late, I weighed my options, and decided I could live without root. Then I flashed the update.zip to kitkat. Not a huge deal though, if I absolutely can't live without root, I'm on the edge program with Verizon and am eligible for a new phone in February
[Droid Ultra General] SamuriHL:
Why are you using an old version?
[Droid Ultra General] livinitwarrior:
Has anyone confirmed it can downgrade from 4.4 back to 4.2.2? I tried, realized it was version 1.4, and I'm in the midst of downloading things so that it's up to 2.0... but I've heard a mixed back of responses and bricking...
[Droid Ultra General] SamuriHL:
Considering the root method says to downgrade, I'd say that's probably "confirmation" that it'll downgrade so long as people follow directions. Bricking generally occurs when people don't bother to read and just do stuff...expecting that if they screw it up, someone else will hand hold them through fixing it.
[Droid Ultra General] bigv5150:
The instructions were written for the moto x they can downgrade the maxx can't so if your on 4.4 and don't have root your out of luck unless someone comes up with a method to root 4.4. The house of moto version doesn't matter you can't downgrade do to security on the maxx build.
[Droid Ultra General] SamuriHL:
They locked the maxx? Wtf vzw/moto? If the X can downgrade then the droids, who are using the exact same build except for the security, should have been able to, as well. That's seriously wrong.
[Droid Ultra General] bigv5150:
It just goes to show that they monitor these boards it was all over the moto x boards how to downgrade and get root on 4.2.2. Moto/vrz had plenty of time to add the security to the maxx build to stop it. It sucks but I am not surprised thats why I froze my updater and waited till I found out if we could downgrade. You only get one shot at root unless a 4.4 work around pops up by jcase.
[Droid Ultra General] tlspatt:
Can Samuri or anyone else tell me, please, if this'll help fix my problem:

I bootlooped my phone.

I rooted my MAXX using JCase's first method. All was good.

I avoided taking even the very first 12.7.7 update. Until yesterday, that is, when I accidentally hit "install now" instead of "install later."

Now my Maxx reboots every two min or so.

I used SuperSU to "remove root completely" from the settings menu. Then I even tried to remove all the Xposed framework stuff so there was nothing non-stock going on (other than the obvious fact that I modded my phone). I was hoping the update would then just go through. Nope.​

Even if this works, I'd be RSDing back to a upgraded software version than I originally had. I don't think that should be a problem but I'm obviously not an expert on it or my phone wouldn't currently be borked.

Any help would be greatly appreciated!!! I'm okay with tinkering with my phone, but only ever used ADB (once to unlock my BL on the GNex) and haven't messed around with RSD for anything--so I'm a bit green.
[Droid Ultra General] SamuriHL:
Yes, the House of Moto will help. BUT, you need to understand this next point clearly. Whatever you flash *MUST* be at least the version that's on there now OR higher. So if you attempted to do an update and it failed and is now bootlooping, you can fix it using an FXZ (and the House of Moto's scripts can allow you to fix it without losing your data partition) but the FXZ must be at least the version you're currently on or higher (i.e. the update you were trying to install). Because of the way the root exploit works on the X and new DROIDs, simply using supersu to "remove root" is not nearly enough. The recovery partition is overwritten with a copy of the boot partition, which is why you're bootlooping. That has to be fixed before you can take any OTA updates.

[soapbox]

I REALLY wish you guys that are using this root exploit would freeze the OTA update checker until you're actually ready to update. Given how the root exploit works, you're better off just waiting for the new FXZ ANYWAY, and updating with that. Either that or one of you should create a "repair recovery" package for people to use when an OTA comes out so they can fix up their phone, protect root, unfreeze the OTA update checker, and take the update safely.

[/soapbox]
[Droid Ultra General] tlspatt:
Yeah I never even considered using TiBu to freeze the OTA update (until after the fact, of course). I just kept hitting "later" once a day and it really wasn't too much of a hassle. Stupid, stupid, stupid (kicking myself).

Thanks so much! Every version is newer than the one I'm on so I'll be good. I've never messed with any of this stuff so I'll follow the instructions step-by-step. However, if there's anything I need to add/omit then please let me know cause ignorance is dangerous (and what got me into this mess in the 1st place).

I waited this long cause I wanted to just jump straight to KK since that'll probably be the last major update for this phone (or 5.0, but we'll cross that bridge if/when it matters). Now I just want a functioning phone with root again.

But if you reckon that we'll get a root method + a new FXZ for KK then I'll heed your recommendation and wait. I only wanted the new bluetooth for my FitBit more than anything. I'm always open to suggestions :)
[Droid Ultra General] bigv5150:
The reason you bootlooped is because there was no stock recovery for the update to be installed. You can now run an exploit motowpnomo that takes the W/P off permanent and you can then have stock recovery back.
[Droid Ultra General] SamuriHL:
And just to be ultra clear here, unless I'm mistaken, for the DROIDS there is no KK root I believe. The X root exploit has you downgrade and protect and reupgrade. That's not possible on the DROIDS since the morons security locked the update. So if you want root you'll have to FXZ to the update just before the KK OTA, root it, protect root, and restore recovery before taking the OTA. However, that all being said, I believe the KK OTA was pulled due to bricking people's phones, so, I'd probably avoid that for now. LOL.
[Droid Ultra General] SamuriHL:
I updated my FXZ Script Generator prototype and uploaded a new version. It now creates House of Moto support files for any FXZ you have. So if there isn't a support file for your phone, you just run the script generator on the FXZ you have and it'll generate FULL and KEEP DATA scripts for you. This is step 1 to a much better plan to ultimately replace the House of Moto with something FAR better. ;)
[Droid Ultra General] ss12108:
Scripts

I've been searching for an hour now, but alas, I have not had any success. Where can I get the necessary scripts for my Droid Maxx? I've done everything else in the guide but can't seem to figure out where to obtain the scripts. Thank you all!

PS - Should the folder for my device be FXZ_xt1080 or FXZ_xt1080m? Its the second one, right?

Edit: Nevermind...found both answers.
[Droid Ultra General] IntenseImage:
If I used the fxz to update to the 12.15.15 file... What would prevent future OTAs from installing if I haven't rerooted?
[Droid Ultra General] SamuriHL:
Nothing.
[Droid Ultra General] IntenseImage:
Hmm the soak failed
[Droid Ultra General] SamuriHL:
Ok. Nothing anyone can do to help you with that given that "it failed" doesn't tell us anything about why it failed or what you've done to the phone to cause it to fail. You said you FXZ'd and didn't re-root. The FXZ restores all partitions to factory fresh. Given that's all the info we have, well, nothing to really go on to help you solve the problem.
[Droid Ultra General] IntenseImage:
After the fxz I have used the phone as is ... No other mods done (disabled some bloat apps thats it). Received the new soak, downloaded fine. Went to install, install started and went the the android with the red triangle and "!" and said Error. Thats all I know what to tell you.
[Droid Ultra General] SamuriHL:
And that's not enough info to tell you anything. Sorry, but, I'm not just going to make something up if I don't know.
[Droid Ultra General] IntenseImage:
Is there something I can do that could give you more info?
[Droid Ultra General] SamuriHL:
The only way is to sideload it and tell me what the FULL error 7 message is when it fails. It's failing an assertion. Meaning something on the system doesn't match what the update is expecting. I'm getting ready to head on vacation for a week, so, I don't have time to walk through sideloading it. Search for it and you'll find out how to do it.
[Droid Ultra General] bigv5150:
Do a full fxz and try again
[Droid Ultra General] evo2s197:
help!

I have tried to follow the instructions for house of moto, but I have not been successful, i keep getting "File not Found"

i have attached screen shots, I need this phone fixed to get it out of it's bootloop. I hit install now instead of install later :crying:

$20 bucks via paypal is on the table for anyone that can help me fix this.

here are the screen shots.
[Droid Ultra General] SamuriHL:
Didn't bother installing the support file huh? When you skip steps in the instructions it rarely works. ;)
[Droid Ultra General] evo2s197:
Like this?
[Droid Ultra General] SamuriHL:
No. The files are in the wrong folder.

---------- Post added at 09:25 PM ---------- Previous post was at 09:23 PM ----------

Reread the directions. Maybe even start over.
[Droid Ultra General] evo2s197:
did every thing else look good on the other screenshots?

Still no dice, i get the file not found error when i run houseofmoto windows batch file. How much $ do you want to help me if you have a minute?
[Droid Ultra General] SamuriHL:
I don't. I'm on vacation. I don't want money. I want you to read and follow the directions. Nothing more nothing less. It's not complicated... Unzip the house of moto zip file, unzip the support file into the house of moto directory, and unzip your FXZ into the new directory that the support file creates. Not to be rude but if you ant follow 3 fairly trivial unzipping directions, well, messing with a 650 dollar phone may not be wise.
[Droid Ultra General] evo2s197:
I put the device support files in the house of moto directory, and the fxz files in my FXZ_xt1080 file. i went full potato on this i must be tired or dumb ha! :eek:
[Droid Ultra General] SamuriHL:
Yea I saw where you put them. It was not correct. The scripts must end up in the Fxz dir for it to work.
[Droid Ultra General] evo2s197:
Ah post 272 worked, the problem was that I followed the instructions on this guide and thought they were the same, the creating FXZ_xtYYY instructions in this thread was causing the problems, i thought both instructions were the same, then missed the device support part. this thread needs to be updated to the 2.0 instructions, for those of us in panic mode, still my own fault though. Thanks for the help sir, just pm your paypal address and i'll shoot you the $20, i owe you that at least for bugging you on your vacation.

I know something wasn't right because I have done and flashed everything under the sun to my Epic 4G Touch I had before this Droid Maxx
[Droid Ultra General] SamuriHL:
I don't control this thread so can't update it. I only visit to help out those having issues.
[Droid Ultra General] imabigd:
Rooting Stock 4.2.2 12.7.7

SamuriHL et al.,

Thanks for all of your amazing work on this forum and in advance for helping me with my issue. In the midst of all of the 4.4 KitKat upgrade madness, I lost my Droid Maxx and had a replacement phone sent to me via insurance.

I was ready to upgarde to 4.4 until I started reading that it can't be rooted, it can't be downgraded, and the entitlement hacks no longer work for wi-fi. Given this, I have absolutely no interest in updating to 4.4.

That being said, I'd like to get my phone to 4.2. 12.15.15 with root (which is where my original Maxx was before it was lost) and the entitlement hack enabled.

So...

1.) Can someone confirm whether I need to install the 12..15.15 OTA BEFORE running House of Moto or can I do it on the stock, unrooted 12.7.7 that my replacement phone is running?

2.) Once I run House of Moto, can someone refresh my memory as to how I root the phone with this method?

3.) Once rooted, any pointers on how to disable thee OTA upgrade notification which is already trying to upgrade me to 4.4?

Thanks again,

ImaBigD
[Droid Ultra General] Caseyk621:
Yes you need to be on 12.15.15. Then follow the instructions here. They're quite clear.

http://xdaforums.com/showthread.php?t=2577029

[4.4 ROOT] SlapMyMoto 1.0 (Requires you to be on 4.2.2)

Once you achieve root you can use this method to gain hotspot

Sent from my KitKat Ultra

---------- Post added at 02:38 AM ---------- Previous post was at 02:34 AM ----------

Sent from my KitKat Ultra
[Droid Ultra General] imabigd:
Caseyk621,

Thanks for taking the time to read my question and post. I'm actually trying to avoid 4.4 for the time being. I've read through the thread that jcase started and even though the instructions seem straightforward, there are 37 pages of pain in that thread that I'm not sure I really want to get into. The instructions also involve steps I'm not really comfortable with at the moment and getting back to 12.15.15 4.22 with the entitlement hack is all I'm after.

Thanks again,

ImaBigD
[Droid Ultra General] imabigd:
So,

If I want to stay on 12.15.15 with root should I use House of Moto or RockMyMoto?
[Droid Ultra General] bigv5150:
Rock my moto roots are phone not house of moto
[Droid Ultra General] panicfreek:
I'm in the same boat...I am rooted on 4.2.2 & my phone is trying to get me to install the new OTA everyday. Is there a way to turn this off and stay where I am? If not, can anyone point me to the easiest way to go back to stock so I can SlapMyMoto. I have turned off write protection allready.. but i am stuck here as there seems to be several ways to do this.
[Droid Ultra General] Mustang02:
If you have titaniumbackup freeze the updater app.
[Droid Ultra General] panicfreek:
is that the MotorolaOTA 1.0?
[Droid Ultra General] Caseyk621:
Yes RockMyMoto for root. House of Moto is for flashing back to stock. And if you have success with that it means you have successfully set up ABD, Cydia impactor, and telnet. I know it seems like a lot but as I stated before the instructions are clear. I speak from experience as I had no experience with these programs. That being said I strongly recommend that you root 4.4 afterwards. Just a few steps and you already have it set up. Besides if you stay on 12.15.15 you'll be battling not to take the 4.4 OTA..

Sent from my KitKat Ultra
[Droid Ultra General] Topsnake:
Heres your answers

http://xdaforums.com/showthread.php?t=2616104
[Droid Ultra General] aviwdoowks:
HoM Script & more

http://ted.servepics.com/razrm/

Here are SamuriHL's threads at Rzr http://www.droidrzr.com/index.php/forum/138-samurihls-house-of-moto/

They are extensive, but if you are borked you need to climb them!
[Droid Ultra General] SamuriHL:
The House of Moto replacement project is moving along. I've nicknamed it the FXZ Flasher for now until I get all the bugs worked out and all the functionality I want added to it, but, essentially the latest version I posted today will allow you to drop the jar file (it's a java app) into an FXZ, run it (executable jar), select the FXZ's xml file, and then you can flash FULL or KEEP DATA options. It uses a hidden fastboot process to run each step from the FXZ's xml script. Once it's tested enough I'll add a custom option so you can select which steps to execute from the FXZ's xml file. The beauty of this solution is that as long as there's an FXZ for your device, this tool supports it automagically. No need for me to maintain support files. Plus it gives a UI to Linux and Mac users (in theory....untested at the moment as to whether it works) to flash FXZ files without custom scripts. It's my hope that it becomes more useful than the current batch file solutions we're all used to. Those who want to continue using RSD to flash can use my FXZ Script Generator to generate RSD scripts for your FXZ. That will also get a custom option at some point soon so you can select what to flash from the FXZ.
[Droid Ultra General] Akivaran:
Question about using HoM and stock

Hello all, I really appreciate all the work that Samurai HL has put into HoB/HoM. I used it in the past, and still I'm very grateful.

I have installed SafeStrap 3.5 on my Bionic, and I've successfully installed CM10 on the Slot 1. However, what I seem to have done is also installed CM10 in the Factory slot. When I boot using that slot, it just sits there and does not do anything. I've tried several times to install the stock roms, but all I get are Error Flashing Zip messages.

My question is about whether HoM will solve my problem or not. Am I able to flash the stock slot with HoM or do I remove SS and try flashing the slot another way? I've searched and searched, but I haven't seen an issue quite like this.

Thanks for all your help.
[Droid Ultra General] Teksu:
Cannot say if any of this would work for the bionic, this section of the forms is devoted to the 2013 droid line (Droid Mini, Droid ultra, Droid Maxx)

The bionic forum can be found here:

http://xdaforums.com/droid-bionic

Someone there would be more familiar with your device and needs to be done to fix it.
[Droid Ultra General] SamuriHL:
That'd be me. ;) Yes, you can use the House of Moto with the xt875 support file and the latest FXZ to restore stock. Use the KEEP DATA option. You will have to reinstall root and SS recovery once that's done. (No need to uninstall SS).
[Droid Ultra General] Akivaran:
Thank you to both Teksu and SamuriHL. I have reposted my question in the correct place.
[Droid Ultra General] matitor:
Hi, I have a kind of a rookie question, which one of the following http://sbf.droid-developers.org/phone.php?device=8 should I download?

I tried with the following and no success

VRZ_XT907_9.8.1Q-94-1_CFC.xml

VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml

Now I got stuck on fastboot mode, it says on fastboot reason: flash failure

Help please!!
[Droid Ultra General] SamuriHL:
See answer inline. "I tried with the following and no success" doesn't tell me anything I can use to help you, however.
[Droid Ultra General] matitor:
I meant, I was trying with those files, sorry. I tried with the one you suggested but I get the following message "Unknown fastboot command(get_var)" using Flash mode: RSD

When I try Flash mode: FASTBOOT I get the message : "File not found"
[Droid Ultra General] SamuriHL:
Sounds like your House of Moto install isn't setup properly. If you just want to flash it with RSD and skip the House of Moto, take the FXZ I pointed you to, extract it, drop this jar into the extracted folder, run it (it's executable), select the xml file in your FXZ, and then press the generate button. It will generate a couple scripts in your FXZ folder. Find the KEEP DATA script in RSD and flash that. It should get you up and running. If not, post the swdl.txt file contents (it's in your RSD installation folder) and we'll take a look.
[Droid Ultra General] matitor:
Here is the swdl.txt content:

01/31/14 13:57:18 --------------------------------------------------------------------------------

01/31/14 13:57:18 New Log Started For Software Download.

01/31/14 13:57:48 The FlashLog key is turned off.

01/31/14 13:57:52 Multi upgrade started for 1 phones

01/31/14 13:57:52 [Device ID: 0] 1/19 flash partition "gpt_main0.bin"

01/31/14 13:57:53 ERROR: 1/19 flash partition "gpt_main0.bin" -> Phone returned FAIL. - on device ID 0.

01/31/14 13:57:53 [Device ID: 0] 1/19 flash partition "gpt_main0.bin" -> Phone returned FAIL.

01/31/14 13:57:53 ERROR: Failed flashing process. - on device ID 0.

01/31/14 13:57:53 Multi upgrade finished.
[Droid Ultra General] SamuriHL:
That shows a flash that tried to downgrade. So that would be for the non-correct FXZ. If you use my FXZ Script Generator it'll create working scripts for the correct FXZ and allow you to flash and fix your phone. All the while keeping your data partition in tact.
[Droid Ultra General] aviwdoowks:
So any luck? Did it work?
[Droid Ultra General] matitor:
So basically you're saying that I should download al the files frome here http://sbf.droid-developers.org/phone.php?device=8 use your FXZ Script Generator and try it until one of them works?
[Droid Ultra General] bigv5150:
You have to use the fxz for the OS your on now if you use a earlier fxz then you get the error for trying to downgrade.
[Droid Ultra General] SamuriHL:
HUH? That's definitely NOT what I said to do. You will need to use the LATEST FXZ, not some random old one. Well, not unless you're trying to brick your phone, anyway. Just grab the very latest FXZ, run the script generator, and flash the keep data script.

So we're ABSOLUTELY clear here: Blur_Version.98.30.1.XT907.Verizon.en.US

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

This isn't specific enough. And I'll explain why. The RAZR HD and M both have 4 versions of "4.1.2". So when I ask people what version they're on, I invariably get "4.1.2" as an answer. I could say to use 9.18.94, which is the latest for both the HD and M, but, they seem to have no idea what I'm talking about. sigh. So I've gotten to the point of telling people to use the "latest". And yes, I get the irony that it's not specific enough, either, but, it's better than trying some random FXZ in hopes that it works. On security locked phones, all it'll do is brick it further, as you know.
[Droid Ultra General] matitor:
I knew there was a miss understanding...I've already done that (Blur_Version.98.30.1.XT907.Verizon.en.US name of file VRZ_XT907_9.8.1Q-94-1_CFC.xml.zip) .. and post the content of the swdl.txt file

Here is the swdl.txt content:

01/31/14 13:57:18 --------------------------------------------------------------------------------

01/31/14 13:57:18 New Log Started For Software Download.

01/31/14 13:57:48 The FlashLog key is turned off.

01/31/14 13:57:52 Multi upgrade started for 1 phones

01/31/14 13:57:52 [Device ID: 0] 1/19 flash partition "gpt_main0.bin"

01/31/14 13:57:53 ERROR: 1/19 flash partition "gpt_main0.bin" -> Phone returned FAIL. - on device ID 0.

01/31/14 13:57:53 [Device ID: 0] 1/19 flash partition "gpt_main0.bin" -> Phone returned FAIL.

01/31/14 13:57:53 ERROR: Failed flashing process. - on device ID 0.

01/31/14 13:57:53 Multi upgrade finished.
[Droid Ultra General] BladeRunner:
Silly, silly question here, but you DO have a Razr M, right?
[Droid Ultra General] matitor:
Hahaha, yes. It says model: XT 907 Motorola...
[Droid Ultra General] SamuriHL:
Um.....you have some serious issues there I'm afraid. The latest FXZ is basically telling you that you're trying to downgrade. I hate to ask uncomfortable questions, but, at any point during this process did you perhaps accidentally flash an FXZ for a different phone by mistake? If the latest FXZ is telling you to sod off, well, it's not really a good thing and nothing we're going to be able to fix until the next FXZ comes out with higher security. This is what I call "bad(tm)". :(
[Droid Ultra General] matitor:
So..I'm.... lost!!??
[Droid Ultra General] aviwdoowks:
Just to comment on a possible confusion.

Blur_Version.98.30.1.XT907.Verizon.en.US(.zip) could be an ota flash file.

While VRZ_XT907_9.8.1Q-94-1_CFC.xml.zip would be the fxz.

Just to be clear & maybe silly.

So the drama goes on...

---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------

He means the kk or 4.4 xml to come.
[Droid Ultra General] SamuriHL:
Correct. What I'm saying is if you're getting that error on the latest FXZ, generally that means you flashed something you shouldn't have and are stuck until an FXZ with newer security comes out. Likely to be KK or another maintenance release. People give me a hard time for saying that you should *KNOW* what you're flashing on your phone BEFORE flashing it and don't just indiscriminately flash things. This would be why...to avoid your exact situation.