84 replies to this topic

[reddevilz]

ok, I did it on the old machine too. The same problem. I have attached a picture from what was shown on the phone itself while flashing. It says "downgraded security version", is that normal? can be the cause of the problem?

Attached Files

•  FullSizeRender.jpg   30.06KB   5 downloads

[johnthehillbilly]

The downgraded security error means you're trying to flash an older version that what has been on the phone before.....

[johnthehillbilly]

What version did you try to flash?

[reddevilz]

here is he name of the file:

VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml

[johnthehillbilly]

Ok.... If you're getting the security downgraded error flashing that.... Then at some point the phone has "seen" the newer version (.15).....

[johnthehillbilly]

Possibly try to flash the newest FXZ.... If you are locked, then you will not be able to unlock.... But you can get root using the H2O2 method.......

[reddevilz]

I have this version too from somewhere I don't remember, but with this it will also give the same message!

VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml

 

This is the version I tried to flash with RSD Lite and it failed at the first or second step. After that I tried HouseofMoto with the 10. and it was giving error from the first time.

 

Any newer versions around?

[johnthehillbilly]

That one is the .15 version.... So yes the phone has seen it... Therefore you need to try to flash that one again...(now you're on a different PC)

[reddevilz]

Possibly try to flash the newest FXZ.... If you are locked, then you will not be able to unlock.... But you can get root using the H2O2 method.......

- where to find a newer one?

- it says lock now, lock to what? carrier?

- what is rooting? will it solve the problem? any ref to H2O2 in this site (don't know what it is)

[johnthehillbilly]

It said unlocked before?

Go ahead and flash that newest fxz and see what happens.....

We'll get into rooting and such once your phone is functional again

[johnthehillbilly]

The .15 one you have IS in-fact the newest

[johnthehillbilly]

If needed... You can grab a "fresh" copy of the fxz here

Please Login or Register to see this Hidden Content

[reddevilz]

ok, no downgrade message this time, but still the same failure, see the attachment please 

 

Is going to a different PC a solution? because this is the same one I tried to use RSD Lite with the newer version.

Attached Files

•  fail.PNG   26.09KB   4 downloads

[johnthehillbilly]

The older PC (without the "powered" USB ports ) is probably the answer.... I say that mainly because even tho you got the errors on the last flash.... It was on the old PC right? .... Getting those errors showed that it was in-fact flashing.... The current errors are telling me that it is only "half flashing" (if that makes sense )

So flash the newest fxz on the old PC ....:)

[johnthehillbilly]

I believe the extra power on the USB port is causing the failures

[reddevilz]

Tested on 2 different computers with USB 2 and OEM cable. The errors on the computer side are the same, just by using the 15. there is no error showing on the screen of the phone. The computer sides error were there from the beginning, no matter what version was used.

 

Any other method or action that can make this flashing working?

[spainter]

Tested on 2 different computers with USB 2 and OEM cable. The errors on the computer side are the same, just by using the 15. there is no error showing on the screen of the phone. The computer sides error were there from the beginning, no matter what version was used.

 

Any other method or action that can make this flashing working?

There are two things left that could cause this.  1st is a incorrect flash from a custom rom. 2nd is a hardware failure in the memory chip or a problem with the usb port.  Since the errors seem to be consistant I would guess that a hardware failure is to blame.

[reddevilz]

There are two things left that could cause this.  1st is a incorrect flash from a custom rom. 2nd is a hardware failure in the memory chip or a problem with the usb port.  Since the errors seem to be consistant I would guess that a hardware failure is to blame.

Considering that I was not trying to flash or do any change in the software when this issue suddenly happen, can you say that it can be more likely a hardware issue rather than software? Can the software just go wrong suddenly while the phone is locked sitting on the table?

 

Looking at the errors it will just fail in every step: fail to erase partition, then fail to flash partition, and at the end it will return Failed <remote failure>

[spainter]

Considering that I was not trying to flash or do any change in the software when this issue suddenly happen, can you say that it can be more likely a hardware issue rather than software? Can the software just go wrong suddenly while the phone is locked sitting on the table?

 

Looking at the errors it will just fail in every step: fail to erase partition, then fail to flash partition, and at the end it will return Failed <remote failure>

You can never tell when hardware will go bad.  A read error on boot or wake up, a hickup while trying to write to a temp file. Where you are getting the failure to erase partition and the error is consistant using different computers, that is what leads me to believe it is hardware related.  If the errors changed from one attempt to another then I would wonder but they don't change.

[spainter]

Considering that I was not trying to flash or do any change in the software when this issue suddenly happen, can you say that it can be more likely a hardware issue rather than software? Can the software just go wrong suddenly while the phone is locked sitting on the table?

 

Looking at the errors it will just fail in every step: fail to erase partition, then fail to flash partition, and at the end it will return Failed <remote failure>

You are getting the same errors with two different computers and using different flashing setups. You never know when a hardware failure will hit.  It can go out just sitting and waking up.  The consistant errors is what makes me believe that it is hardware. You could print out the bat or the xml file and try running the commands one at a time in fastboot so you can watch the results one at a time. If you have followed the steps John laid out (he is real good at bringing phones back from the dead) it should have gotten rid of the software side of things.  That would only leave hardware.