Jump to content


Photo

validation of cryptographic module failed razr maxx

My razr maxx says validation

Best Answer aktrazer , 10 April 2013 - 04:03 AM

Try Matt's utility 1.9 and fastboot back to stock. Usually a crypto error indicates that you're flashing something like the Xmas leak (.8) onto the OTA (.16) and there is a kernel mismatch.

Utility can be found here: http://www.droidrzr....nux-all-in-one/ Go to the full post


  • Please log in to reply
8 replies to this topic

#1 wilsonb116

wilsonb116

    n00b

  • Members
  • Pip
  • 2 posts
  • Location72947

Posted 05 April 2013 - 05:39 PM

I took OTA jb update. rooted with razr utility jb xt912 then installed safestrap 3.11 and tried to flash a custom rom and could not flash any roms so I tried to rsd lite and start over. I could not restore with rsd lite or razr utility. I uninstalled safestrap and installed razr bootstrap. I booted to cwr and made backup then when i booted my phone i got message (encryption unsuccesful). I tried fastboot with rom compatibility flasher and now when I boot phone (RAZR MAXX XT912) it says (validation of cryptographic module failed). Please Help. Thank You.



P.S What am I doing wrong with rsd lite?

#2 aktrazer

aktrazer

    SMod/News Team Leader

  • Smod
  • 537 posts
  • LocationGreensboro, NC
  • Current Device(s):Smasung Galaxy Note 2, ASUS TF700T

Posted 10 April 2013 - 04:03 AM   Best Answer

Try Matt's utility 1.9 and fastboot back to stock. Usually a crypto error indicates that you're flashing something like the Xmas leak (.8) onto the OTA (.16) and there is a kernel mismatch.

Utility can be found here:

Please Login or Register to see this Hidden Content


  • cmh714 likes this

Posted Image


#3 wabmorgan

wabmorgan

    Member

  • Members
  • PipPip
  • 236 posts

Posted 10 April 2013 - 09:06 AM

Sounds like he took the OTA upgrade and then tried to install .08 kernel roms. :-(

Kernel update is not backwards compatible. :-(

After taking OTA update... you have 2 choices. Either use the kernel swap program.

Please Login or Register to see this Hidden Content



(if you use the program... you must swap kernels to .08 or .16 kernels according to what rom you are running.)

Or run .16 OTA based roms.

#4 aktrazer

aktrazer

    SMod/News Team Leader

  • Smod
  • 537 posts
  • LocationGreensboro, NC
  • Current Device(s):Smasung Galaxy Note 2, ASUS TF700T

Posted 10 April 2013 - 09:17 AM

^ what HE said. :)

Posted Image


#5 ajras4444

ajras4444

    n00b

  • Members
  • Pip
  • 1 posts
  • Current Device(s):RAZR MAXX, Droid 3, Droid 1

Posted 15 April 2013 - 06:44 AM

So I have this issue too And I would like to not have to loose all my data and what not. I was running the .08 build and then I got the ota to .16 build and it was running fine. I rooted like 2 weeks ago and installed safestrap 3.11 i went on a rom flashing spree. I'm running CM10.1 (nightlies) as my daily driver but. The only thing I can think of that would affect this would be a flashable zip I used from xda That allowed me to run a touch wiz based ROM which was based on the .08 build. Should that have anything to do with it? I want to stay away from restoring if possible.

#6 wilsonb116

wilsonb116

    n00b

  • Members
  • Pip
  • 2 posts
  • Location72947

Posted 15 April 2013 - 05:23 PM

Thanks for the help I used matts utility to restore phone to stock after I got the right drivers for my phone. worked like a charm.



#7 jasaobeneri

jasaobeneri

    n00b

  • Members
  • Pip
  • 1 posts

Posted 17 April 2013 - 08:01 PM

Please help me out.
I was using version 4.1 without the CID and tried to restore a backup of the original version 4.0.4 and went back to CID.
Now I can no longer access my phone it is always with the message invalid flash mode.


#8 aktrazer

aktrazer

    SMod/News Team Leader

  • Smod
  • 537 posts
  • LocationGreensboro, NC
  • Current Device(s):Smasung Galaxy Note 2, ASUS TF700T

Posted 18 April 2013 - 04:52 AM

 

Please help me out.
I was using version 4.1 without the CID and tried to restore a backup of the original version 4.0.4 and went back to CID.
Now I can no longer access my phone it is always with the message invalid flash mode.

 

 

Moving this thread to Help, other users may have this issue.

 

jasao, once you're on JB you CANNOT go back to ICS, this is due to the bootloader version being upgraded.  Once you're on JB, you can't go back.

 

I'd use Matt's utility, listed above, to fastboot back to stock 4.1


Posted Image


#9 aktrazer

aktrazer

    SMod/News Team Leader

  • Smod
  • 537 posts
  • LocationGreensboro, NC
  • Current Device(s):Smasung Galaxy Note 2, ASUS TF700T

Posted 18 April 2013 - 04:53 AM

So I have this issue too And I would like to not have to loose all my data and what not. I was running the .08 build and then I got the ota to .16 build and it was running fine. I rooted like 2 weeks ago and installed safestrap 3.11 i went on a rom flashing spree. I'm running CM10.1 (nightlies) as my daily driver but. The only thing I can think of that would affect this would be a flashable zip I used from xda That allowed me to run a touch wiz based ROM which was based on the .08 build. Should that have anything to do with it? I want to stay away from restoring if possible.

I'm sure that's the issue.  When you went to .16, you can no longer flash .08 build ROMs.  


Posted Image





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users