moto-penangf · progzone122 · Jan 17, 2025 · Jan 17, 2025 · Jan 17, 2025 · Jan 17, 2025
diff --git a/.gitignore b/.gitignore
@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
diff --git a/_sidebar.md b/_sidebar.md
diff --git a/blog/2019-05-28-first-blog-post.md b/blog/2019-05-28-first-blog-post.md
@@ -0,0 +1,12 @@
+---
+slug: first-blog-post
+title: First Blog Post
+authors: [slorber, yangshun]
+tags: [hola, docusaurus]
+---
+
+Lorem ipsum dolor sit amet...
+
+<!-- truncate -->
+
+...consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
diff --git a/blog/2019-05-29-long-blog-post.md b/blog/2019-05-29-long-blog-post.md
@@ -0,0 +1,44 @@
+---
+slug: long-blog-post
+title: Long Blog Post
+authors: yangshun
+tags: [hello, docusaurus]
+---
+
+This is the summary of a very long blog post,
+
+Use a `<!--` `truncate` `-->` comment to limit blog post size in the list view.
+
+<!-- truncate -->
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
diff --git a/blog/2021-08-01-mdx-blog-post.mdx b/blog/2021-08-01-mdx-blog-post.mdx
@@ -0,0 +1,24 @@
+---
+slug: mdx-blog-post
+title: MDX Blog Post
+authors: [slorber]
+tags: [docusaurus]
+---
+
+Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/).
+
+:::tip
+
+Use the power of React to create interactive blog posts.
+
+:::
+
+{/* truncate */}
+
+For example, use JSX to create an interactive button:
+
+```js
+<button onClick={() => alert('button clicked!')}>Click me!</button>
+```
+
+<button onClick={() => alert('button clicked!')}>Click me!</button>
diff --git a/blog/2021-08-26-welcome/docusaurus-plushie-banner.jpeg b/blog/2021-08-26-welcome/docusaurus-plushie-banner.jpeg
diff --git a/blog/2021-08-26-welcome/index.md b/blog/2021-08-26-welcome/index.md
@@ -0,0 +1,29 @@
+---
+slug: welcome
+title: Welcome
+authors: [slorber, yangshun]
+tags: [facebook, hello, docusaurus]
+---
+
+[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).
+
+Here are a few tips you might find useful.
+
+<!-- truncate -->
+
+Simply add Markdown files (or folders) to the `blog` directory.
+
+Regular blog authors can be added to `authors.yml`.
+
+The blog post date can be extracted from filenames, such as:
+
+- `2019-05-30-welcome.md`
+- `2019-05-30-welcome/index.md`
+
+A blog post folder can be convenient to co-locate blog post images:
+
+![Docusaurus Plushie](./docusaurus-plushie-banner.jpeg)
+
+The blog supports tags as well!
+
+**And if you don't want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config.
diff --git a/blog/authors.yml b/blog/authors.yml
@@ -0,0 +1,23 @@
+yangshun:
+  name: Yangshun Tay
+  title: Front End Engineer @ Facebook
+  url: https://github.com/yangshun
+  image_url: https://github.com/yangshun.png
+  page: true
+  socials:
+    x: yangshunz
+    github: yangshun
+
+slorber:
+  name: Sébastien Lorber
+  title: Docusaurus maintainer
+  url: https://sebastienlorber.com
+  image_url: https://github.com/slorber.png
+  page:
+    # customize the url of the author page at /blog/authors/<permalink>
+    permalink: '/all-sebastien-lorber-articles'
+  socials:
+    x: sebastienlorber
+    linkedin: sebastienlorber
+    github: slorber
+    newsletter: https://thisweekinreact.com
diff --git a/blog/tags.yml b/blog/tags.yml
@@ -0,0 +1,19 @@
+facebook:
+  label: Facebook
+  permalink: /facebook
+  description: Facebook tag description
+
+hello:
+  label: Hello
+  permalink: /hello
+  description: Hello tag description
+
+docusaurus:
+  label: Docusaurus
+  permalink: /docusaurus
+  description: Docusaurus tag description
+
+hola:
+  label: Hola
+  permalink: /hola
+  description: Hola tag description
diff --git a/dev/motherboard.md b/dev/motherboard.md
diff --git a/dev/testpoints.md b/dev/testpoints.md
diff --git a/docs/about.md b/docs/about.md
@@ -0,0 +1,29 @@
+---
+title: About
+---
+
+:::warning
+**MOTOROLA SHITTY FIRMWARE WARNING**
+
+Motorola really has shitty firmware.
+Carefully read all the warnings in the documentation, and if something doesn’t work - **DO NOT CONTINUE, THERE IS A RISK OF BRICKING YOUR DEVICE!**
+**Don't cry later and don't say we didn't warn you...**
+:::
+
+This documentation is dedicated to discoveries made by me and other people interested in unlocking the Moto G23 and Moto G13 bootloader.
+
+![Image](../static/assets/sticker2.png)
+
+## Contributing
+
+For any new discovery made that is still not on this documentation, please send a Pull Request or open an issue on [our documentation repo](https://github.com/moto-penangf/documentation) describing the discovery.<br/>
+For discoveries not yet assessed, consider starting a new discussion [here](https://github.com/orgs/moto-penangf/discussions) for further analysis.
+
+## Credits
+
+Documentation started by [Shomy](https://github.com/shomykohai), and then kept being expanded by them and [DiabloSat](https://github.com/progzone122).
+
+
+Special thanks goes to [DiabloSat](https://github.com/progzone122) and the [Helio G85 telegram group](https://t.me/motoheliog85) for providing crucial intel and testing hardware stuff.
+
+
diff --git a/dev/bootloader.md → docs/dev/bootloader.md b/dev/bootloader.md → docs/dev/bootloader.md
@@ -1,8 +1,13 @@
+---
+title: Bootloader
+---
+
 ## Unlock bootloader
 
-> [!NOTE] 
-> Currently there's no known way to unlock the bootloader.<br>
-> Investigations are going on to figure out how to unlock it, check the forum and updates in this documentation.
+:::note
+Currently there's no known way to unlock the bootloader.<br/>
+Investigations are going on to figure out how to unlock it, check the forum and updates in this documentation.
+:::
 
 ### Discoveries
 
@@ -51,9 +56,10 @@ fastboot: error: Command Failed
 
 It requires an unlock key, like all Motorola Devices.
 
-> [!NOTE]
-> The command to install and dump the key was discovered by [DiabloSat](https://github.com/progzone122) with support from [Shomy](https://github.com/shomykohai)
-In order to specify the key, we need to run the fastboot oem key <KEY> command.
+:::note
+The command to install and dump the key was discovered by [DiabloSat](https://github.com/progzone122) with support from [Shomy](https://github.com/shomykohai)
+In order to specify the key, we need to run the fastboot oem key \<KEY\> command.
+:::
 
 #### Dump of the current oem key 
 Just in case, make a dump of the current oem key
@@ -77,11 +83,13 @@ Finished. Total time: 0.000s
 
 **Now we can try to unlock the bootloader!**
 
-> [!NOTE]
-> As you can see, unlocking the bootloader with the default key didn't help.
-> We need to try bruteforce key and we'll update the info in the documentation and make a script if it works!
->
-> Update: brute forcing won't work because of fastboot timeout, but a keygen could be possible by decompiling lk and reversing the algorithm which checks the key.
+:::note
+As you can see, unlocking the bootloader with the default key didn't help.
+We need to try bruteforce key and we'll update the info in the documentation and make a script if it works!
+
+Update: brute forcing won't work because of fastboot timeout, but a keygen could be possible by decompiling lk and reversing the algorithm which checks the key.
+:::
+
 
 ```sh
 $ fastboot flashing unlock
@@ -108,7 +116,7 @@ We can only interact with the preloader.
 * Download Agent (Obtainable from RSA SP Flash tool, as it gets extracted during Rescue Mode, and now easy to get [from GitHub](https://github.com/moto-penangf/penangf-sp-flash-tool))
 
 
-<br><br >
+<br/><br/>
 ```bash
 # Read the SECCFG partition, which we want to edit to unlock bootloader
 $ mtk r seccfg seccfg.bin --loader DA_PL_NO_CERT_V6.bin --preloader preloader_penangf.bin > logs.txt
@@ -137,16 +145,16 @@ So unfortunately not even that works.
 
 Testpoints are [still being investigated](https://github.com/orgs/moto-penangf/discussions/1).
 
-**BROM:**<br>
-As for now, we're investigating the possibility of accessing brom through a combination of keys (read [decompilation](/dev/decompilation.md)).<br>
-The suspected TP for BROM is KPCOL0, located at the back of the board.<br>
+**BROM:**<br/>
+As for now, we're investigating the possibility of accessing brom through a combination of keys (read [decompilation](/dev/decompilation.md)).<br/>
+The suspected TP for BROM is KPCOL0, located at the back of the board.<br/>
 
 Though, we would need to use it in combination with two other keys: Power and Vol+.
 
 
-**UART:**<br>
+**UART:**<br/>
 [Almost bricked a device.](https://github.com/moto-penangf/penangf-schematics/issues/1)
-Further testing is needed.<br>
+Further testing is needed.<br/>
 I suspect to enable UART we need to run `fastboot oem p2u` first.
 
 

diff --git a/dev/decompilation.md → docs/dev/decompilation.md b/dev/decompilation.md → docs/dev/decompilation.md
@@ -1,14 +1,14 @@
-# Decompilation of LK and preloader
+---
+title: Decompilation
+---
 
+:::note
+The following information is yet to be verified.<br/>
+Some inaccuracy is possible.<br/>
+Act at your own risk.<br/>
+:::
 
-> [!NOTE]
->
-> The following information is yet to be verified.<br>
-> Some inaccuracy is possible.<br>
-> Act at your own risk.<br>
-
-
-## preloader
+## Preloader
 
 From the decompilation of the [preloader](https://github.com/moto-penangf/fuckyoumoto/raw/refs/heads/main/sources/preloader_penangf.bin), we get some really interesting information about brom.
 

diff --git a/dev/logs.md → docs/dev/logs.md b/dev/logs.md → docs/dev/logs.md
@@ -1,9 +1,14 @@
+---
+title: Logs
+---
+
 ## Get boot logs
 
 Clone the [workarounds script repo](https://github.com/moto-penangf/fuckyoumoto) and poweroff your phone.
 
 Run `get_logs.sh` and connect the phone to the pc.
 You'll find the dumped logs inside the `exported_logs` directory
 
-> [!NOTE]
-> Device specific information (IMEI, SERIAL NUMBER) are automatically removed from the logs
+:::note
+Device specific information (IMEI, SERIAL NUMBER) are automatically removed from the logs
+:::