57 replies to this topic

[dlw]

My apologies, all email from here goes to spam folder for some reason.
Did not see any until just now.
Again, my apologies.

dlw

[SamuriHL]

Not a problem at all. Don't worry about it. I'll see what we can do a bit later. But I'm not sure how to fix that issue since it happens on some people's machines and not others. It happens on the RAZR Linux tool, as well, and it's always due to something missing on the Linux install.

[dlw]

I'll see if I can find out anything on the Ubuntu forum.

[SamuriHL]

I'll do some digging, as well, when I can get a chance. Probably another hour or two before I can even consider looking into it.

[SamuriHL]

I'm probably not going to get to look into this tonight. I just wanted to let you know so you aren't waiting for me. I've just gotten back from vacation and have so much to catch up on that I just don't have the time at the moment. If you're still struggling with this when I get a free moment let me know. Also, one piece of advice is to post the error you're getting in the Linux RAZR utility thread and see if those guys have any ideas. The issue is with the code they developed that I use in the Linux HoB. Maybe they know a solution.

[tmyinc]

Running Linux could you use a windows emulator or would the syntax errors persist through it?

Sent from my XT907 using Tapatalk 2

[SamuriHL]

You'd run into driver issues. It's a real pain. When it works it's awesome. When it doesn't, it can be a freaking nightmare. The real basic issue comes down to getting fastboot to work on that machine so that you can flash everything from the FXZ. The XML file in the FXZ folder shows what to flash and what order to do it in. So if you can get fastboot working on a command line you'd not even really need the HoB. You could just follow the XML file and flash each one using fastboot.

[johnlgalt]

I'm wondering - does the OP have a 64bit Linux OS?

from the readme:

o) 64 bit Linux systems may need to run: sudo apt-get install ia32-libs

[dlw]

Might be making progress here.
When running 'HouseOfBionic.sh' now I get:

sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found

Is this the fastboot in /HouseOfBionic/utils or the phone?

[SamuriHL]

utils.

[dlw]

No, it is 32 bit.

[SamuriHL]

Oh god. 32 bit has been massively problematic. I don't have a 32 bit system to test on.

[dlw]

That is where the error is or was.
It seems to be past that now.
The previous error concerned a misplaced "(" in fastboot.linux.

[SamuriHL]

Wait a minute. What type of shell are you running this from? Bash I hope?

[dlw]

Yes, bash as root

[SamuriHL]

Then I'm afraid I don't know. Command not found, btw, is not "getting past" anything. That's bad. Something is configured very wrong on your machine.

[dlw]

My thought that I can not set debugging mode has nothing to do with the problem.

[dlw]

Also, running adb in a terminal does not find the phone either.
Where as it did before.

[SamuriHL]

Debugging mode must be set for the usb interface to work. However, no, your problem is deeper than that and is something on your machine not your phone.

[SamuriHL]

Let me be clear....IF the phone is in AP Fastboot mode, adb won't see it and that's fine. Fastboot should, however.