From cae96348f38de8b3730309a5f333eb27c61ef0b5 Mon Sep 17 00:00:00 2001
From: mathew-dennis <78794223+mathew-dennis@users.noreply.github.com>
Date: Fri, 8 Sep 2023 21:12:59 +0530
Subject: [PATCH] initial draft porting to non-treable device

---
 porting-to-non-treble-device.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 porting-to-non-treble-device.md

diff --git a/porting-to-non-treble-device.md b/porting-to-non-treble-device.md
new file mode 100644
index 0000000..7f17377
--- /dev/null
+++ b/porting-to-non-treble-device.md
@@ -0,0 +1,19 @@
+
+### introduction
+Porting to a non treble device is going to be simular but will have a lot of additional steps 
+### step 1
+first part which is kernal compilation is common to both types of devices
+
+### step 2 
+As we cannot use the halium gsi image we need to create a device specific image for that we can follow the halium porting guide or the ubports porting guide (which is more up-to-date) 
+if the device already have a ubports port then that system image can be used.
+
+### step 3 
+The third step is to flash the flash it to the device
+for that download the rootfs appropriate for the device
+flash it using twrp
+remove the android-roofs.img located in /data and put the device specific system image that we created in step 2 and rename it to android-rootfs.img
+and reboot to system
+
+### non-treble specific errors 
+non-treble specific errors will come here.
\ No newline at end of file