You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Writing seccfg on a device that has it empty by default
#442
I just had an Asus Zenpad (Z301 something) given to me, I've been trying to unlock the bootloader of. There's an XDA thread showing someone having success unlocking his on a 2.0 beta version of mtkclient, which is not on this repo anymore, but it doesn't seem to work on mine. After some digging, I found out I'm getting an exception because my seccfg partition is apparently empty, which is correctly detected as empty by the last release ot mtkclient, and that version offers to write it as well, while prompting it's dangerous. Is it just generic disclaimer, or is it known that writing the partition could brick the device? In theory I can always reflash it empty, I dumped all partitions, but I'm not experienced enough to say whether it's something that is likely to cause permanent damage, or likely reversible.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I just had an Asus Zenpad (Z301 something) given to me, I've been trying to unlock the bootloader of. There's an XDA thread showing someone having success unlocking his on a 2.0 beta version of mtkclient, which is not on this repo anymore, but it doesn't seem to work on mine. After some digging, I found out I'm getting an exception because my seccfg partition is apparently empty, which is correctly detected as empty by the last release ot mtkclient, and that version offers to write it as well, while prompting it's dangerous. Is it just generic disclaimer, or is it known that writing the partition could brick the device? In theory I can always reflash it empty, I dumped all partitions, but I'm not experienced enough to say whether it's something that is likely to cause permanent damage, or likely reversible.
All reactions