3711 replies to this topic

[twinkyz1979]

verifying current system failed

 

 

wasn't there a way to make it think you were on something you were not?

[SamuriHL]

If you mean editing the boot.prop then not in your situation.  I don't know how to help you.

[twinkyz1979]

not sure how encryption failed when i didn't even start it but phone bricked now. won't reinstall the update and even though it states to do a factory wipe to gain access to the phone again it doesn't even work. I now have something to hold down papers on my desk when it is windy and my windows are open.

 

on a good note my battery wasn't holding a charge for crap anymore so something new was going to happen sooner than later. Although i hoped a little later than now.

[SamuriHL]

Once I can fix my own phone (lost root) I can probably help you unbrick it but you will lose root.

[twinkyz1979]

Once I can fix my own phone (lost root) I can probably help you unbrick it but you will lose root.

Trust me I will miss root but to be able to have my bionic back would make me happy all in it self. Only cause my other phone will probably be an OG Droid for now.

[SamuriHL]

Well I lost root permanently so that sucks.  What YOU need to do is worse.  Get into fastboot mode.  You can use the HoB reinstall option.  It should allow you to reapply the update and boot your phone again, but, root is history for both of us.

[twinkyz1979]

Well I lost root permanently so that sucks.  What YOU need to do is worse.  Get into fastboot mode.  You can use the HoB reinstall option.  It should allow you to reapply the update and boot your phone again, but, root is history for both of us.

tried that already didn't work. not sure why all it flashed was the cdt.bin then it copied some files told me somethings then quit. when i went into recovery afterwards it failed. i will try it again and tell you what it says.

 

it completes 2 0f 3 steps in rsd the 3rd step gives unknown command and rsd closes.

 

ok never mind had it on rsd changed mode now it may work.

[altspeed]

well i went to flash deodex through CWM and rebooted to it saying my encryption had failed and my phone needed to be wiped. I am now at a point where i think i am stuck going to try and run the update again through recovery will report back.

this. damn. you're hosed.  happened to me flashing xmas jelly on my maxx. I'm betting you told CWM to flash itself and then reboot? standalone bootstrap?

[altspeed]

damn sam, how'd you lose it?  backup just didn't recover?  did you try thru ADB?  (I'm sure you did, just trying to show other folks how damn serious this is)

[SamuriHL]

tried that already didn't work. not sure why all it flashed was the cdt.bin then it copied some files told me somethings then quit. when i went into recovery afterwards it failed. i will try it again and tell you what it says.

 

it completes 2 0f 3 steps in rsd the 3rd step gives unknown command and rsd closes.

 

Try flashing it with moto-fastboot.

[ns218]

was trying to fxz back to stock 246, the system was flashing preinstall.img then my battery went dead..  For some reason this was taking a heck of a long time, going on almost 7 hrs.  I just put a new battery in, and it moved on to flashing radio.img, not sure what state my phone is going to be in when rsd lite finishes.

[SamuriHL]

damn sam, how'd you lose it?  backup just didn't recover?  did you try thru ADB?  (I'm sure you did, just trying to show other folks how damn serious this is)

 

Cause I'm a fucking moron.  I rewrote OTA Rootkeeper and had my test version installed when I did a root backup.  FAIL.

[SamuriHL]

was trying to fxz back to stock 246, the system was flashing preinstall.img then my battery went dead..  For some reason this was taking a heck of a long time, going on almost 7 hrs.  I just put a new battery in, and it moved on to flashing radio.img, not sure what state my phone is going to be in when rsd lite finishes.

 

Um, that makes two of us...

[ns218]

Um, that makes two of us...

 

The last time I did this, I do not remember it taking so long,  is there a way I can just restart the thing where it died flashing preinstall.img, or am I most likely hosed?

[twinkyz1979]

nope that didn't work either fails at

 

verifying current system.....

assert failed:  apply_patch_check ("/system/bin/logwrapper")

 

 

Think i am now done with the Bionic at this point. Maybe VZW can help me in some manner. I mean it's not my fault the encryption messed up.

[SamuriHL]

nope that didn't work either fails at

 

verifying current system.....

assert failed:  apply_patch_check ("/system/bin/logwrapper")

 

 

Think i am now done with the Bionic at this point. Maybe VZW can help me in some manner. I mean it's not my fault the encryption messed up.

 

That means SS is causing it to fail.  It's not flashing properly.  

[SamuriHL]

The last time I did this, I do not remember it taking so long,  is there a way I can just restart the thing where it died flashing preinstall.img, or am I most likely hosed?

 

All you can do is try.  It won't boot so you'll have to start in fastboot mode.

[twinkyz1979]

That means SS is causing it to fail.  It's not flashing properly.  

never used SS didn't even have the app installed on my phone.

[SamuriHL]

never used SS didn't even have the app installed on my phone.

 

Then it's from bootstrap.  Either way, it shouldn't be there and fails the assert as a result.

[twinkyz1979]

Then it's from bootstrap.  Either way, it shouldn't be there and fails the assert as a result.

so if you had a stock recovery image i could flash would that solve it?