624 replies to this topic

[satman80]

Where is the failsafe folder? It took me FOREVER to download this file and now it is dead

Here I will PM with a personal link

[vman411gamer]

Are you saying the links are down?

no I downloaded it but it force closes at the batman symbol and the .txt file says to use the .bat from the "failsafe" folder. But I cannot find it and I have 52 min of redownloading left and I leave for vaca tomorrow D:

I still haven't packed!!

[johnthehillbilly]

just a note:... if you are looking for the failsafe folder that was included with the 1.81 utility, ... it was not included in 1.82.... but im sure between satman and myself we can get you the failsafe

[satman80]

just a note:... if you are looking for the failsafe folder that was included with the 1.81 utility, ... it was not included in 1.82.... but im sure between satman and myself we can get you the failsafe

I have 1.81 if anyone want's it, I believe I posted those links.. I think??? If not just PM me..

[vman411gamer]

Ok I am trying to get my phone back to .211 and I get this error:

INFOPreflash validation failure FAILED (remote: )


when it tries to write 'boot'

[johnthehillbilly]

I'm extracting and uploading the 1.81 failsafe files as well..... just so we have all the bases covered

[johnthehillbilly]

Ok I am trying to get my phone back to .211 and I get this error:

INFOPreflash validation failure FAILED (remote: )


when it tries to write 'boot'

first question.... was your battery fully charged fully when you started?

second.... did you do a wipe to all the usual places (cache, dalvik cache).... then factory reset before running the utility?

is that the only error you get? ..... is it booting back into AP Fastboot?

[satman80]

Ok I am trying to get my phone back to .211 and I get this error:

INFOPreflash validation failure FAILED (remote: )


when it tries to write 'boot'

I am also uploading 1,82 to my Dropbox, this will take a few, I will have 1.81 available for download as well.. Just let me know if you need the link, things may be slow for a bit as I am using all the bandwidth at the moment for about an hour

[vman411gamer]

first question.... was your battery fully charged fully when you started?

second.... did you do a wipe to all the usual places (cache, dalvik cache).... then factory reset before running the utility?

is that the only error you get? ..... is it booting back into AP Fastboot?

yes, yes, yes, and yes

[satman80]

Until the links are fixed you may use this as well, My link may be a little slower at this time, but it works, johnthehillbilly has also offered a link as well..


Link 1 - Matt's

Please Login or Register to see this Hidden Content

Link 2 - johnthehillbilly's

Please Login or Register to see this Hidden Content

Link 3 - Satman80's

Please Login or Register to see this Hidden Content

Thank You,
Satman

Bump!

[satman80]

My other link "bump" is from another server, that one is not being used at the moment.. it should be fast..

[johnthehillbilly]

yes, yes, yes, and yes

BTW here are the failsafe files (just in case you still need them)

Please Login or Register to see this Hidden Content

....
even tho the failsafe files are from the 1.81 utility... the fastboot restore and root should still work if you are using the 1.82 utility


another question.... are your drivers up to date.... if not here are the latest motorola drivers....

Please Login or Register to see this Hidden Content

...

[vman411gamer]

BTW here are the failsafe files (just in case you still need them)

Please Login or Register to see this Hidden Content

....
even tho the failsafe files are from the 1.81 utility... the fastboot restore and root should still work if you are using the 1.82 utility


another question.... are your drivers up to date.... if not here are the latest motorola drivers....

Please Login or Register to see this Hidden Content

...

ya I even deleted and re installed them.

[geodroid]

Okay folks, now what do I do? I tried (twice) to drop back to .211 from .215 using 1.82. The utility never gets past "writing 'system' ...": either time. Now it is out of power and I'm re-charging.

I tried to restart (while its on the charger) to no avail. It is stuck on the AP Fastboot Flash screen. I cannot do anything with it now.

Suggestions??

[vman411gamer]

ya I even deleted and re installed them.

I think my boot211.img is corrupt. Could someone please upload a version of that?

[satman80]

Okay folks, now what do I do? I tried (twice) to drop back to .211 from .215 using 1.82. The utility never gets past "writing 'system' ...": either time. Now it is out of power and I'm re-charging.

I tried to restart (while its on the charger) to no avail. It is stuck on the AP Fastboot Flash screen. I cannot do anything with it now.

Suggestions??

I am not sure you can charge in AP mode.. If you can power off and charge the phone please do so.. otherwise you will need this

Please Login or Register to see this Hidden Content

[geodroid]

I am not sure you can charge in AP mode.. If you can power off and charge the phone please do so.. otherwise you will need this

Please Login or Register to see this Hidden Content

assuming i get it powered.

what do I do???

[johnthehillbilly]

I think my boot211.img is corrupt. Could someone please upload a version of that?

what is on the screen while in AP Fastboot....

and no, you cannot charge while in AP Fastboot .....

there a couple of low battery workarounds outlined here

Please Login or Register to see this Hidden Content

they sometimes work (assuming that your battery is not totally dead), in which case you WILL need a TBH Factory cable or adapter that was linked to above

i can PM you a link to a fresh copy of boot211.img ... but i dont think it is corrupt since the failure is a remote failure.....

[satman80]

assuming i get it powered.

what do I do???

I have not seen this as an issue before, either retry downloading the Utility and unzipping it from winrar to the desktop again or try, 1.81 utility, reinstall drivers, reboot, and try that?

[vman411gamer]

i can PM you a link to a fresh copy of boot211.img ... but i dont think it is corrupt since the failure is a remote failure.....

With the failsafe it said it just couldn't load boot211.img