<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>re on kitzman&#39;s place</title>
    <link>https://tilde.club/~kitzman/tags/re/</link>
    <description>Recent content in re on kitzman&#39;s place</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 26 Sep 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://tilde.club/~kitzman/tags/re/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reverse engineering &#39;nvdata&#39;</title>
      <link>https://tilde.club/~kitzman/posts/2021-09-26_reversing_nvdata_1/</link>
      <pubDate>Sun, 26 Sep 2021 00:00:00 +0000</pubDate>
      
      <guid>https://tilde.club/~kitzman/posts/2021-09-26_reversing_nvdata_1/</guid>
      <description>Introduction On mobile phone devices, there are different partitions/sections of data, which differs from vendor to vendor.
Samsung for example, keeps the partition information in a PIT file, and the partitions are various: radio (GSM/LTE/etc) firmware, bootloader, network vendor information, etc.
One of the most crucial ones, the EFS partition hold information which is never supposed to be overwritten, such as the IMEI, network vendor data, etc.
nvdata.bin You probably guessed that &amp;ldquo;nvdata&amp;rdquo; stands for &amp;ldquo;network vendor data&amp;rdquo;.</description>
    </item>
    
  </channel>
</rss>
