1296 replies to this topic

[johnthehillbilly]

Which one is showing zero?.......... typically, if you have a file with a zero length (file size) then something failed to copy properly or has gotten corrupted ... you should probably re download ....

HD tappin' .... hillbilly style!!

[SamuriHL]

The emstorage img. But it's only used to reformat the internal storage partition. Iow it should be 0 bytes as it should be empty when you init to factory defaults. No idea why it won't flash but that's a moto problem not a script problem.

Carved in blood by a wakizashi...

[Int_Rnd_Pooka]

I had that same thing happen with fastboot the other day. It couldn't read emsstorage, so it just skips that step. No big deal, since I meant to do it that way and accidentally used a full wipe xml/batch file. You could always just boot, format internal, and then factory reset. I know, it's longer that way. But it works the same in the end

[SamuriHL]

I had that same thing happen with fastboot the other day. It couldn't read emsstorage, so it just skips that step. No big deal, since I meant to do it that way and accidentally used a full wipe xml/batch file. You could always just boot, format internal, and then factory reset. I know, it's longer that way. But it works the same in the end

 

Yup.  That's exactly right.  Other than taking it out of the script there's nothing I can do to fix it.  Anyone who's troubled by it, go edit FULL_xt875.bat and remove the emstorage line.

[Int_Rnd_Pooka]

The emstorage img. But it's only used to reformat the internal storage partition. Iow it should be 0 bytes as it should be empty when you init to factory defaults. No idea why it won't flash but that's a moto problem not a script problem.

Carved in blood by a wakizashi...

Does the terminal shell in Safestrap 3.x support dd? I could wipe internal SD from ss, then dump the drive to a binary. Repackage that with the fxz and distribute it

[SamuriHL]

Wouldn't work.  All files in the FXZ are signed.  Even that stupid file.  It'd fail to flash.  Moral of the story, if you need to wipe internal storage by using emstorage, use RSD.  LOL

[shanewerner]

just a thanks again sam saved my phone for the third stupid mistake i did worked great except for the emstorage thing no biggy phone still works great thanks again for your time and instructions 

[cvhovey]

How to set up:

 

o) If root exists for your device, add the files to the root folder.  Make sure run.bat and/or run.sh exists.

 

I'm understanding that set up step to mean something to the effect of:

 

"If root [folder] exists [in the script support file] for your device, add the files to the root folder [in your HouseOfMoto directory].  Make sure run.bat and/or run.sh exists."

 

Since there is no root folder in HouseOfMoto-xt907.zip, that doesn't apply in my case ... or did I bang my head into the brick wall a bit too hard this time?   :

[SamuriHL]

Yes, head met wall with much velocity. We don't include root in the HoM. We only support it if the user provides it. For your device you'd use motochopper 1.3. However, if you don't have an empty root folder in your HouseOfMoto directory, then you skipped a couple steps. You need more than just the support file. Hopefully I'm misunderstanding. Anyway, the end user just needs to drop whatever root exists for their device into the root folder and as long as it has a run.bat it'll be added to the menu as an option. Hope that helps!

Sent from my Xoom using Tapatalk 4

[cvhovey]

Ah ha, now partly understand, but that raises another question to ask.

 

I have motochopper 1.1 so did a search for motochopper 1.3 per your post. Only thing that turned up was motochopper_1_3_xt907.zip .... and its mentioned this version should only be used on a b/l locked system version 98.18.78. The xt907 1.3 version includes a couple additional folders (boot_new, boot_old, and system).

 

I'm b/l unlocked on system 98.16.3 and that's what I have in my FXZ_xt907 folder. So assume I should stick with motochopper 1.1 since I'm not on 98.18.78?

[livinginkaos]

Ah ha, now partly understand, but that raises another question to ask.

 

I have motochopper 1.1 so did a search for motochopper 1.3 per your post. Only thing that turned up was motochopper_1_3_xt907.zip .... and its mentioned this version should only be used on a b/l locked system version 98.18.78. The xt907 1.3 version includes a couple additional folders (boot_new, boot_old, and system).

 

I'm b/l unlocked on system 98.16.3 and that's what I have in my FXZ_xt907 folder. So assume I should stick with motochopper 1.1 since I'm not on 98.18.78?

If you are unlocked, you should be rooting through your custom recovery

[SamuriHL]

Bootloader unlocked people need to learn to stop with root exploits.    Install your custom recovery (twrp most likely), grab the supersu zip file from chainfire, boot up recovery, and flash that bad boy.  Root DONE.    And if you want you could drop your custom recovery in the FXZ_xt907 directory and write a new script called RECOVERY_xt907.bat and drop that in the fastboot_scripts dir.  As long as you're using fastboot [snapdragon] as your flash methodology, you could then use that to reinstall custom recovery after any FXZ operations you perform.  The script would look like this (obviously replace the twrp_2.6.3.0.img with whatever your custom recovery filename happens to be):

Please Login or Register to see this Hidden Content

[SamuriHL]

If you are unlocked, you should be rooting through your custom recovery

 

Hey, knock it off!  No ninja'ing a samuri!  

[livinginkaos]

First time for everything.... just got lucky.... but in your defense, I did not expand...

[SamuriHL]

P.S. You can see the real power of using the House of Moto as a framework rather than an end product once you start writing custom scripts for it.  For example, if I was dealing with an unlocked Moto device, I'd create my own root script that basically installs custom recovery, boots into it, instructs the user to put recovery into sideload mode, and then sideload the super su zip for them.  DONE.  But that's just how I'd do it.  

[cvhovey]

^ I can see that makes a lot of sense about root and doing that all via script. When I recently got a gently used bootloader unlocked Droid M via Swappa .... that had been previously unrooted to use employer email ... I found motochopper to be no solution to re-root. By trial and error to regain root I made a stab in the dark by installing TWRP, boot into it, then flashed superuser.zip to get root.

 

Doing that all by script using the House of Moto would be a good way to go. Sadly, "writing custom scripts" translates in my brain to: "Your mother-in-law is coming to visit for a month." At that point my brain melts into a blob of warm jello .... and I find myself curled up in a fetal position.   :

[SamuriHL]

LMAO.  If I get some time later I'll put together a generic "root your unlocked moto" script that can be dropped into root.  But it will require end user action...providing their custom recovery image and the latest supersu binary.  And figuring out how to get the driver to work for sideload mode.  Mainly cause I don't have a moto device to be able to do that anymore.  But I can script it.  I have it written for the S4 GPE already.  I'll modify it.

[zombolt]

thanks a lot!!!!!

[MakeMeBAd420]

Hello I am in need of help bad.... i have been trying for months now to try and unbrick my bionic with no success. i believe i have prepared  and used the houseofmoto tool correctly with the directories looking as they should and the correct scripts for my device but after the tool runs i am left at the AP fastboot flash mode(s) screen on my phone and pretty much were i started off plz help.

P.S. well the houseofmoto tool was running it seemed to have a lot of failures:

 

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_xt875.bat

        1 file(s) copied.

        1 file(s) copied.

        1 file(s) copied.

        1 file(s) copied.

rebooting into bootloader...

OKAY [  0.001s]

finished. total time: 0.002s

sending 'mbm' (256 KB)...

OKAY [  0.014s]

writing 'mbm'...

OKAY [  0.456s]

finished. total time: 0.471s

rebooting into bootloader...

OKAY [  0.272s]

finished. total time: 0.273s

sending 'mbmloader' (40 KB)...

OKAY [  0.004s]

writing 'mbmloader'...

OKAY [  0.286s]

finished. total time: 0.290s

sending 'mbm' (256 KB)...

OKAY [  0.015s]

writing 'mbm'...

OKAY [  0.454s]

finished. total time: 0.470s

rebooting into bootloader...

OKAY [  0.270s]

finished. total time: 0.270s

sending 'cdt.bin' (16 KB)...

OKAY [  0.002s]

writing 'cdt.bin'...

Preflash validation failure

FAILED (remote: )

finished. total time: 0.211s

rebooting into bootloader...

OKAY [  0.269s]

finished. total time: 0.270s

erasing 'cache'...

OKAY [  0.007s]

finished. total time: 0.007s

erasing 'userdata'...

OKAY [  0.006s]

finished. total time: 0.006s

sending 'lbl' (16 KB)...

OKAY [  0.002s]

writing 'lbl'...

OKAY [  0.435s]

finished. total time: 0.438s

sending 'logo.bin' (854 KB)...

OKAY [  0.043s]

writing 'logo.bin'...

OKAY [  0.299s]

finished. total time: 0.344s

sending 'ebr' (16 KB)...

OKAY [  0.003s]

writing 'ebr'...

OKAY [  0.433s]

finished. total time: 0.438s

sending 'mbr' (16 KB)...

OKAY [  0.003s]

writing 'mbr'...

OKAY [  0.394s]

finished. total time: 0.397s

sending 'devtree' (512 KB)...

OKAY [  0.028s]

writing 'devtree'...

Preflash validation failure

FAILED (remote: )

finished. total time: 0.241s

sending 'system' (491264 KB)...

OKAY [ 23.997s]

writing 'system'...

Preflash validation failure

FAILED (remote: )

finished. total time: 24.211s

sending 'boot' (8192 KB)...

OKAY [  0.405s]

writing 'boot'...

Preflash validation failure

FAILED (remote: )

finished. total time: 0.619s

sending 'recovery' (9216 KB)...

OKAY [  0.457s]

writing 'recovery'...

Preflash validation failure

FAILED (remote: )

finished. total time: 0.672s

sending 'cdrom' (12032 KB)...

OKAY [  0.590s]

writing 'cdrom'...

Preflash validation failure

FAILED (remote: )

finished. total time: 0.803s

sending 'preinstall' (311296 KB)...

OKAY [ 15.182s]

writing 'preinstall'...

OKAY [ 26.496s]

finished. total time: 41.678s

sending 'emstorage' (8221 KB)...

OKAY [  0.399s]

writing 'emstorage'...

OKAY [  1.152s]

finished. total time: 1.553s

error: cannot load 'vendor.img'

 

sending 'radio' (21768 KB)...

OKAY [  1.063s]

writing 'radio'...

OKAY [  2.057s]

finished. total time: 3.120s

rebooting...

 

finished. total time: 0.267s

Press any key to continue . . .

 

 

what i know about my device:

 

It was running a rooted mod when it was working a while ago (not to sure of the specs of the mod so one click method for the droid3 i found on utube)

I'm trying to flash VRZ_XT875_5.7.893.XT875.Verizon.en.US_CFC_01.xml

 

my device model is xt875 and i have a factory cable because my battery is low

[soocold]

What was it on b4? The security's changed in ICS AND JB. You CANNOT go back to older versions once the phone upgraded to those. You need to grab the JB files and flash it

Sent from my Nexus 4 using Tapatalk 4