docs: Improve Troubleshoot guide
Signed-off-by: Jackeagle <jackeagle102@gmail.com>
diff --git a/getting-started/troubleshoot.md b/getting-started/troubleshoot.md
index 21a2f4f..21d0fef 100644
--- a/getting-started/troubleshoot.md
+++ b/getting-started/troubleshoot.md
@@ -1,13 +1,25 @@
### Troubleshooting
-If your build failed, there are a couple things you can try.
+If your build fails, there are several steps you can take to troubleshoot the issue:
-* Try a fresh `repo sync` to make your repository up to date. Sometimes, the Internet connection between you and GitHub can be flaky. In rare cases a commit merge might be ongoing, and you might've grabbed an incomplete merge. Mostly, this should fix the issue 70% of the time.
-* Make sure your dependencies are installed correctly. Error messages help out a lot here! Often it will say `shared/linked library not found` or something along those lines.
-* Make sure you sourced `build/envsetup.sh`. This is especially common and worth suspecting if none of the build commands like `breakfast` and `lunch` work. If you have `repo sync`ed do this again.
-* Make sure you’re at the root of the build tree. Again, to quickly jump there, use `croot`.
-* Make sure you ran `breakfast` correctly and it did not error out. Missing device files will prevent successful builds.
-* Make sure your computer meets minimum requirements to compile AOSP. Chances are, you need more memory/CPU power to complete a build.
-* Make sure your computer isn't faulty. This is unlikely, but to check, use a stress-test program like Prime95.
+1. **Perform a fresh `repo sync`:** Sometimes, your local repository may not be up to date or there could be issues with the internet connection between you and GitHub. Running `repo sync` again can resolve these issues in most cases.
-If something goes wrong and you've tried everything above, first use Google to look up your error! Most of the errors you encounter is due to misconfiguration and wrong commands entered. More often than not, Google will have the answer you are looking for. If you're still stuck and nothing fixes the problem, then ask us via [our Telegram Build Support chat.](https://t.me/Team_Bliss_Build_Support) \(Please only ask issues about BlissRoms, not other custom ROMs as we are unable to assist with those!\)
+2. **Check your dependencies:** Error messages can provide valuable information about missing shared or linked libraries. Make sure all the necessary dependencies are installed correctly.
+
+3. **Ensure you sourced `build/envsetup.sh`:** Sourcing the `build/envsetup.sh` script is essential for setting up the build environment. If commands like `breakfast` and `lunch` are not working, it's possible that you missed this step. Source `build/envsetup.sh` again, especially if you have performed a `repo sync`.
+
+4. **Verify your location in the build tree:** Make sure you are in the root directory of the build tree. You can quickly navigate to the root directory by using the command `croot`.
+
+5. **Check if `breakfast` ran successfully:** Running `breakfast` is crucial to ensure that device-specific files are properly configured. If there are any errors during this step, it may prevent successful builds.
+
+6. **Ensure your computer meets the minimum requirements:** Compiling AOSP requires a certain amount of memory and CPU power. Verify that your computer meets the minimum system requirements to complete the build successfully.
+
+7. **Check for hardware issues:** While rare, it's possible that your computer may have hardware issues that can affect the build process. To rule out this possibility, you can use stress-test programs like Prime95 to check the stability of your computer.
+
+If you have exhausted all the above troubleshooting steps and are still facing issues, follow these additional steps:
+
+1. **Search for solutions online:** Use search engines like Google to look up the specific error message you encountered. Many common errors have been encountered and resolved by the development community. You may find helpful insights or solutions to your problem.
+
+2. **Seek assistance from the BlissROMs community:** If you are unable to resolve the issue on your own, you can seek help from the [BlissROMs Telegram Build Support chat](https://t.me/Team_Bliss_Build_Support). However, please note that the support provided is specific to BlissROMs and not other custom ROMs.
+
+By following these troubleshooting steps and reaching out for assistance when needed, you can overcome challenges and successfully build your custom ROM using BlissROMs.
\ No newline at end of file