163 replies to this topic

[johnthehillbilly]

Try running sudo apt-get ia32-libs in terminal

sent from my spare phone tapadriving........

[newbdroyd]

I am running i386...

[johnthehillbilly]

I am running i386...

Well that wont do you any good then LOL .... We ran into that error with in the 1.82 utility.... I will check for you and try to find how we solved it...

sent from my spare phone tapadriving........

[johnthehillbilly]

Ok.... Did you get the newest version of the utility(1.10) ... Or do you have the older one (1.00)

sent from my spare phone tapadriving........

[newbdroyd]

Truth of the matter is I am trying to put together a utility for ATRIX HD owners running Linux based OS's...there is a utility already posted for the ahd, but its for use on windows. I was referred here basically for the shell script to use, but in trying to run it is when I got the syntax error...I know a few things need to be changed in the nutsnbolts folder for the ATRIX, but from everything I've looked at, it all looks like it should work....

[newbdroyd]

Ok.... Did you get the newest version of the utility(1.10) ... Or do you have the older one (1.00)

sent from my spare phone tapadriving........

Oh yes, its definitely 1.10, just downloaded it today...

[johnthehillbilly]

Ok..... so the only thing that would have to be changed in the "nuts and bolts" folder should be the specific files for the atrix hd....(and of course the script to match) The fastboot, adb files should stay the same...... With that error, we fixed it with 64bit by installing ia32 libs.... We still have not entirely come up with a 32bit solution..... I believe it may be machine specific because it is really hit or miss....(only some users see the error while others dont) ..... Maybe updating the computer is the answer?.....

sent from my spare phone tapadriving........

[newbdroyd]

Ok..... so the only thing that would have to be changed in the "nuts and bolts" folder should be the specific files for the atrix hd....(and of course the script to match) The fastboot, adb files should stay the same...... With that error, we fixed it with 64bit by installing ia32 libs.... We still have not entirely come up with a 32bit solution..... I believe it may be machine specific because it is really hit or miss....(only some users see the error while others dont) ..... Maybe updating the computer is the answer?.....

sent from my spare phone tapadriving........

ok so i have gone through and run updates, and have had the update manager check 3 times that all is updated, my knowledge is very limited and have run out of ideas, honestly i was out before i wrote my first post...
anyway this is exactly what is what i put in and the output...

michael@NV53:~/mb886dev$ sh LinuxMacDroidRazrHD.sh
32 bit Linux System
Resetting ADB and Launching Droid RAZR HD utility...
This Isn't A Windoze Tool.


LinuxMacDroidRazrHD.sh: 95: LinuxMacDroidRazrHD.sh: Syntax error: "(" unexpected
michael@NV53:~/mb886dev$

as you can see, i didn't get very far before this arose. any ideas would be a trmendous help...and thanks in advance

[johnthehillbilly]

Ok..... What i will do is i will look over the script to double check thst i have not made [another] typo.... ... Do have access to a 64bit machine to try it out on as well?

sent from my spare phone tapadriving........

[newbdroyd]

Ok..... What i will do is i will look over the script to double check thst i have not made [another] typo.... ... Do have access to a 64bit machine to try it out on as well?

sent from my spare phone tapadriving........

ironically enough, no...i say its ironic because it was originally a 64 bit windows system, but when installed my .nux system all i could get to go on was 32bit...oh n btw the distro is ubuntu 12.04... i have noticed that just every so often, for no reason i can figure, ubu has to have a slight difference to a typical linux distro. i don't know if that may be the case this time, but i just thought i should mention it in case someone else may have the same specific issue....

[johnthehillbilly]

I have a feeling that the ussue may be a difference in hardware..... i have checked it again on 3 different machines and 3 different ubuntu distros 12.04.1... 11.10... 10.04 and never saw the error.... all software updated etc etc so...IMO it has to be certain machines having a "bad additude "


sent from my DROID RAZR tapadriving ...

[newbdroyd]

I have a feeling that the ussue may be a difference in hardware..... i have checked it again on 3 different machines and 3 different ubuntu distros 12.04.1... 11.10... 10.04 and never saw the error.... all software updated etc etc so...IMO it has to be certain machines having a "bad additude "


sent from my DROID RAZR tapadriving ...

I don't doubt that...I'm going to try to force install 64 bit distro n see if I can get through that way...will update with results...thanks for all your help...

[johnthehillbilly]

I don't doubt that...I'm going to try to force install 64 bit distro n see if I can get through that way...will update with results...thanks for all your help...

NP anytime.... if you want.... PM me the windows script(.bat file) .... I'll help you any way i can with it....

sent from my DROID RAZR tapadriving ...

[newbdroyd]

NP anytime.... if you want.... PM me the windows script(.bat file) .... I'll help you any way i can with it....

sent from my DROID RAZR tapadriving ...

so after finally getting 64 bit linux mint on my ext hdd, i logged in to my 32 bit ubu and for some out of nowhere reason decided to chmod +x my shell script and got it running...
however when i tried to flash back to stock 4.0.4 i had a couple failures in the writing of partitions and long story short i have...

"No valid PIV block in SP for system
piv validation failed (system)
Fastboot Reason: Boot Failure
usb connected"

when i try to boot normally i go straight to fastboot mode with the previous quote


sending 'partition' (32 KB)...
OKAY [ 0.013s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.444s]
finished. total time: 0.457s
sending 'sbl1' (99 KB)...
OKAY [ 0.019s]
writing 'sbl1'...
OKAY [ 1.220s]
finished. total time: 1.239s
sending 'sbl2' (125 KB)...
OKAY [ 0.020s]
writing 'sbl2'...
OKAY [ 1.100s]
finished. total time: 1.121s
sending 'sbl3' (512 KB)...
OKAY [ 0.054s]
writing 'sbl3'...
OKAY [ 2.141s]
finished. total time: 2.195s
sending 'rpm' (140 KB)...
OKAY [ 0.023s]
writing 'rpm'...
OKAY [ 0.629s]
finished. total time: 0.652s
sending 'tz' (192 KB)...
OKAY [ 0.025s]
writing 'tz'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.309s
sending 'aboot' (256 KB)...
OKAY [ 0.031s]
writing 'aboot'...
OKAY [ 0.902s]
finished. total time: 0.933s
sending 'boot' (10240 KB)...
OKAY [ 0.811s]
writing 'boot'...
OKAY [ 7.032s]
finished. total time: 7.844s
sending 'system' (30720 KB)...
OKAY [ 2.412s]
writing 'system'...
OKAY [ 5.620s]
sending 'system' (30720 KB)...
OKAY [ 7.326s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.461s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.180s]
writing 'system'...
OKAY [ 2.089s]
sending 'system' (30720 KB)...
OKAY [ 6.973s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.990s]
writing 'system'...
OKAY [ 2.089s]
sending 'system' (30720 KB)...
OKAY [ 7.742s]
writing 'system'...
OKAY [ 2.089s]
sending 'system' (30720 KB)...
OKAY [ 7.229s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 6.554s]
writing 'system'...
OKAY [ 2.094s]
sending 'system' (30720 KB)...
OKAY [ 8.299s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 6.815s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.023s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.154s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.840s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.446s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.581s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 6.967s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.100s]
writing 'system'...
OKAY [ 2.090s]
sending 'system' (30720 KB)...
OKAY [ 7.079s]
writing 'system'...
^[[BUnkonwn chunk type
FAILED (remote failure)
finished. total time: 177.518s
sending 'recovery' (10240 KB)...
OKAY [ 1.099s]
writing 'recovery'...
OKAY [ 4.095s]
finished. total time: 5.194s
sending 'modem' (30720 KB)...
OKAY [ 2.413s]
writing 'modem'...
OKAY [ 2.658s]
sending 'modem' (17524 KB)...
OKAY [ 9.026s]
writing 'modem'...
OKAY [ 2.245s]
finished. total time: 16.342s
sending 'devtree' (512 KB)...
OKAY [ 0.051s]
writing 'devtree'...
OKAY [ 0.748s]
finished. total time: 0.799s
erasing 'modemst1'...
OKAY [ 1.799s]
finished. total time: 1.799s
erasing 'modemst2'...
OKAY [ 1.403s]
finished. total time: 1.404s
sending 'fsg' (2432 KB)...
OKAY [ 0.203s]
writing 'fsg'...
OKAY [ 1.502s]
finished. total time: 1.705s
erasing 'cache'...
OKAY [ 2.667s]
finished. total time: 2.667s
erasing 'tombstones'...
OKAY [ 2.847s]
finished. total time: 2.847s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
It is recommended that you wipe data......
IF you do not, you may get 'bootloop' ....
and be required to wipe data anyway.......
This will NOT wipe your sdcard(s).........
please exit the Utility......OR...........
Press 'ENTER' to wipe data................

erasing 'userdata'...
OKAY [ 3.391s]
finished. total time: 3.391s
sending 'modem' (30720 KB)...
OKAY [ 2.418s]
writing 'modem'...
OKAY [ 1.022s]
sending 'modem' (17524 KB)...
OKAY [ 5.653s]
writing 'modem'...
OKAY [ 2.242s]
finished. total time: 11.336s
erasing 'modemst1'...
OKAY [ 0.680s]
finished. total time: 0.680s
erasing 'modemst2'...
OKAY [ 1.206s]
finished. total time: 1.206s
That's It!
You should now be on stock ICS 4.0.4 (0.6.25) Please Boot Normally By Holding Down Power.
Press Enter To Continue

that was the output while running the script, im not sure what "tz" is but that was the only prevalidation failure i could find...
any help?

[johnthehillbilly]

Not sure why it's failing on tz.... that is a new one..... that may be why the last chunk of "system " fails as well ....

Just to make sure..... you are using OEM USB cable? You have plenty of charge? You rebooted computer prior to starting the utility? Did you change the script at all? (Even an inadvertent white space can change the script) . Possibly an incomplete or corrupt download?

Sorry for the delay in answering..... was a long night....

sent from my DROID RAZR tapadriving ...

[newbdroyd]

Not sure why it's failing on tz.... that is a new one..... that may be why the last chunk of "system " fails as well ....

Just to make sure..... you are using OEM USB cable? You have plenty of charge? You rebooted computer prior to starting the utility? Did you change the script at all? (Even an inadvertent white space can change the script) . Possibly an incomplete or corrupt download?

Sorry for the delay in answering..... was a long night....

sent from my DROID RAZR tapadriving ...

No worries...I just appreciate your continued assistance...OEM cable? Yes, well it is a moto cable, not sure it is the one that came with the phone...yes, over 80% charge...did not even open the script so no changes there...I did not reboot , was I supposed to? Also, I was able to get tz fixed, though I still got the failure on the last chunk of system...resulting in the same fastboot due to boot failure....

My exact process consisted of opening two file browser windows side by side, one with this utility and one with the windows atrix HD utility and basically removed the windows .exe files and replaced with the equivalent Linux and Mac scripts...insured remaining mbn files were titled the same as those in the razrHD util so that the sh could go unaltered...and no change to any app files....

I got the tz through by replacing the tz.mbn from another stock firmware zip download...I'm thinking maybe replace the system image with that from the same zip folder or do I need to replace all partition images? Any other thoughts or ideas?

[johnthehillbilly]

No worries...I just appreciate your continued assistance...OEM cable? Yes, well it is a moto cable, not sure it is the one that came with the phone...yes, over 80% charge...did not even open the script so no changes there...I did not reboot , was I supposed to? Also, I was able to get tz fixed, though I still got the failure on the last chunk of system...resulting in the same fastboot due to boot failure....

My exact process consisted of opening two file browser windows side by side, one with this utility and one with the windows atrix HD utility and basically removed the windows .exe files and replaced with the equivalent Linux and Mac scripts...insured remaining mbn files were titled the same as those in the razrHD util so that the sh could go unaltered...and no change to any app files....

I got the tz through by replacing the tz.mbn from another stock firmware zip download...I'm thinking maybe replace the system image with that from the same zip folder or do I need to replace all partition images? Any other thoughts or ideas?

You could try replacing system from your other zip..... maybe the current one is corrupted? (As long as they are the same images ( of course) )


sent from my DROID RAZR tapadriving ...

[newbdroyd]

why did you ask about rebooting my computer? is thAT something i need to do?

[johnthehillbilly]

why did you ask about rebooting my computer? is thAT something i need to do?

Its not a requirement.... But it can be a good practice to clear out any possible "crap" that might be hanging out and interfering with the script.... Not as big of an issue with linux as it is with windows.... But sometimes a good idea

sent from my spare phone tapadriving........

[jasonjw12]

So I've run through the utility using openSUSE 12.2 (64-bit) and everything seemed to be going perfectly until the data wipe. I used the script to do that, then the device rebooted and has been sitting at the Droid logo for ~10 mins. The script window hasn't updated since the press ENTER to wipe data.

Any assistance would be greatly appreciated.

EDIT: Okay, well I finally gave up on the boot and unplugged the phone. I went back into the bootloader and entered recovery where I wiped everything manually. After that it booted and I'm back on ICS.

Thanks for the great utility!