View Single Post
Old 05-21-2012, 10:02 PM   #232
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by ixtab View Post
The problem seems not to be with the jailbreak, but with the Kindle not honoring the ENABLE_DIAGS file to get into diags mode, for whichever reason. Your setup does look correct to me. But since there have been at least two versions of the diagnostics partition seen in the wild (But the devices labeled with the exact same FW version), maybe this is a similar "situation".

Please try to get into diags one way or another, and be sure to help us find out the exact reason afterwards.
Perhaps they have yet ANOTHER patched firmware version that does not honor ENABLE_DIAGS?

At least if the idme bootmode var still works, you should be able to get into diags with MfgTool (read the Select Boot first post, linked from the simple debricking thread).

You can also set the bootmode var to diags with fastboot. MfgTool boots without saving a different bootmode so it might be safer for you to use MfgTool.
geekmaster is offline   Reply With Quote