[EXPERIMENTAL] [AOSP] Phh-Treble for Tissot [8.0] [PORT]

[mahesh2040]

If Google was able to do it, why can't Xiaomi too? 1st Gen Pixel devices have treble support, even if they had Nougat out of the box. I think Xiaomi is too lazy to implement it.

Google already know ahead of android evolution so they probably implant things already in phones like they already have kept one partition for gen 1 so that if treble come out they can support it. But that's how Google policy and there concern towards there customer, while Xiaomi have some different policies, you may notice they never release kernel source code sooner ( they want people to adapt MIUI , Not custom roms, plus the kernel source they release is messy and they don't even bother to rectify it ).. they will release it when they are about to launch new handset so that they can empty there stock of that phone asap. Also they do support for older handset in terms of software updates but the catch is they won't give big update of major android release , they want you to throw old handset and buy new one for new features.. like I have Redmi note 3 they gave miui 9 but not nougat , it's still mm.. basically they are hiding the true face by giving long term support with update but only for MIUI they don't want custom ROM and it's development they want only miui

 

[methuselah]

Google already know ahead of android evolution so they probably implant things already in phones like they already have kept one partition for gen 1 so that if treble come out they can support it. But that's how Google policy and there concern towards there customer, while Xiaomi have some different policies, you may notice they never release kernel source code sooner ( they want people to adapt MIUI , Not custom roms, plus the kernel source they release is messy and they don't even bother to rectify it ).. they will release it when they are about to launch new handset so that they can empty there stock of that phone asap. Also they do support for older handset in terms of software updates but the catch is they won't give big update of major android release , they want you to throw old handset and buy new one for new features.. like I have Redmi note 3 they gave miui 9 but not nougat , it's still mm.. basically they are hiding the true face by giving long term support with update but only for MIUI they don't want custom ROM and it's development they want only miui

True. That's why Chinese companies except one plus are worst. They never respect gpl. Franco jumped into the fight it's only when they released the source. Now the thing is whether you should buy them or not ... Xiaomi is always worst when it comes to developer support. Sony on other hand do good things

 

[gougous3]

Google already know ahead of android evolution so they probably implant things already in phones like they already have kept one partition for gen 1 so that if treble come out they can support it. But that's how Google policy and there concern towards there customer, while Xiaomi have some different policies, you may notice they never release kernel source code sooner ( they want people to adapt MIUI , Not custom roms, plus the kernel source they release is messy and they don't even bother to rectify it ).. they will release it when they are about to launch new handset so that they can empty there stock of that phone asap. Also they do support for older handset in terms of software updates but the catch is they won't give big update of major android release , they want you to throw old handset and buy new one for new features.. like I have Redmi note 3 they gave miui 9 but not nougat , it's still mm.. basically they are hiding the true face by giving long term support with update but only for MIUI they don't want custom ROM and it's development they want only miui

That is indeed very right as shown here

We really need someone to help repartition system_b as vendor

 

[susheelkasab]

This could be possible

Let me be clear first, I am not an expert on this, but i read and search.

According to this thread of XDA News
Someone ported Project Treble support for Xiaomi Redmi 4.

This developer claims that Xiaomi already use a partition named "cust" of almost 840MB for their customization HALS (not sure if proper word) and the same developer reused this partition as /vendor to use vendor HALS as it is completely unused space for AOSP roms.

And more importantly Redmi 4 do not have a-b partitioning for seamless updates claimed by Android where Mi A1 have it!!
Considering this we may not have to request Xiaomi to re-partition,

For other device manufacture many developers claim that it can be done and very easy to achieve by just splitting the space of system partition,

This needed to be done only once in order to add minimum 5 Years of project treble support will be added to the device (considering Linux kernel is built for this time span of support)

Where some devices have too much unused space like OnePlus 5T, They can also use this space as /vendor partition

 

[CosmicDan]

Good to see this thread.

Sad to see that the GitHub branch has been deleted. Wat?

As I talked ranted about in my post here, what I think needs to be done is to do-away with Seamless A/B system and replace system_b with vendor. EDIT: Actually, with the knowledge I found, we could have system_a, system_b, vendor_a and vendor_b too, but the Seamless A/B is probably pointless for the custom ROM's we'll surely need to even use Treble anyway.

Here is my quick initial research on that matter.

From what I can see, the partition map is "soft" in this device - meaning it's defined by GPT binary files rather than embedded in the bootloader. So in theory we can try and edit this without risk of hard-brick.

We have the following files in full official fastboot ROM:

gpt_backup0.bin
gpt_both0.bin
gpt_main0.bin
partition.xml

Then I found this article, which mentions these files:

GUIDE -->> How To Create Partition.xml [GPT]

According to this guide, gpt_main0.bin is what's flashed to "partition" via Fastboot. This is also what appears in the flash_factory script in official fastboot ROM.

I think we can build a new gpt_main0.bin from partition.xml, patch0.xml and rawprogram0.xml but I'm really not sure. This is where I'm up to.

EDIT: It seems we can factory-flash the partition map in XML directly if we use Qualcomm QFIL tool (via MBN loader), which is part of QPST, but I am not sure if it will cause issues if we modify XML partition map since the gpt bin files will not match the XML. Also I don't know if QPST talk is allowed on XDA, it is probably some internal Qualcomm tool that's only for their partners...?

EDIT2: Best avoid the QPST and factory flash stuff, that can brick and wipe IMEI. I think all we need to do is edit the partition table via parted, and then the partition table data is actually stored in the "partition" partition, which can then be dumped to a new gpt_both0.bin. Will try this out.

 

[methuselah]

Good to see this thread.

Sad to see that the GitHub branch has been deleted. Wat?

As I talked ranted about in my post here, what I think needs to be done is to do-away with Seamless A/B system and replace system_b with vendor. EDIT: Actually, with the knowledge I found, we could have system_a, system_b, vendor_a and vendor_b too, but the Seamless A/B is probably pointless for the custom ROM's we'll surely need to even use Treble anyway.

Here is my quick initial research on that matter.

From what I can see, the partition map is "soft" in this device - meaning it's defined by GPT binary files rather than embedded in the bootloader. So in theory we can try and edit this without risk of hard-brick.

We have the following files in full official fastboot ROM:

gpt_backup0.bin
gpt_both0.bin
gpt_main0.bin
partition.xml

Then I found this article, which mentions these files:

GUIDE -->> How To Create Partition.xml [GPT]

According to this guide, gpt_main0.bin is what's flashed to "partition" via Fastboot. This is also what appears in the flash_factory script in official fastboot ROM.

I think we can build a new gpt_main0.bin from partition.xml, patch0.xml and rawprogram0.xml but I'm really not sure. This is where I'm up to.

EDIT: It seems we can factory-flash the partition map in XML directly if we use Qualcomm QFIL tool (via MBN loader), which is part of QPST, but I am not sure if it will cause issues if we modify XML partition map since the gpt bin files will not match the XML. Also I don't know if QPST talk is allowed on XDA, it is probably some internal Qualcomm tool that's only for their partners...?

EDIT2: Best avoid the QPST and factory flash stuff, that can brick and wipe IMEI. I think all we need to do is edit the partition table via parted, and then the partition table data is actually stored in the "partition" partition, which can then be dumped to a new gpt_both0.bin. Will try this out.

Whenever I see a post from you it's always there with so much information!.... Hope to see the something cool stuff at the end of the road

 

[CosmicDan]

So the GPT information is stored at the beginning of the eMMC block device, which I dumped, but for some reason is quite a bit different to the GPT bin that's included in official fastboot firmware packs.

I'd like some more data before I continue experimenting with my daily device I can't find a working "decoder" or "decompiler" for GPT binary yet either, all the existing scripts/tools I found error-out.

If a volunteer or two could share their GPT info dumps too (along with if you remember the last official stock firmware you flashed in fastboot; either Nougat or Oreo) I would appreciate it.

Run something like this via shell / command prompt...

adb shell dd if=/dev/block/mmcblk0 of=/tmp/gpt.bin bs=8 count=4352
adb pull /tmp/gpt.bin

...and share the gpt.bin file here (probably have to ZIP it for XDA to accept it).

Thanks!

 

[CosmicDan]

Sorry for triple post, but anyway...

Bricked my device, then broken the screen when trying to access test-point (deep flash cable didn't work). Will be a while before I can get a replacement screen

Managed to recover from brick at least. Well, I think so... when I boot to recovery I get "USB Device Not Recognized" which is scary.

But I'll get a new screen anyway and resume whenever that is.

Back to my garbage Redmi Note 4 MTK until then...

 

[methuselah]

Sorry for triple post, but anyway...

Bricked my device, then broken the screen when trying to access test-point (deep flash cable didn't work). Will be a while before I can get a replacement screen

Managed to recover from brick at least. Well, I think so... when I boot to recovery I get "USB Device Not Recognized" which is scary.

But I'll get a new screen anyway and resume whenever that is.

Back to my garbage Redmi Note 4 MTK until then...

ohhh so sorry to hear that. I hope you will have your device working normally.

 

[alkesh95]

Tried reading with a decoder only readable output i could see was modem_b. So i think it's the correct file.
Rename it back to gpt.bin from gpt.zip

 

[CosmicDan]

Tried reading with a decoder only readable output i could see was modem_b. So i think it's the correct file.
Rename it back to gpt.bin from gpt.zip

The strings for partition name are UTF encoded (or whatever it's called, 00 byte padding between letters). As long as the DD command was executed as I said, it should be fine.

Thanks!

 

[I1V1A1N]

Warning

The strings for partition name are UTF encoded (or whatever it's called, 00 byte padding between letters). As long as the DD command was executed as I said, it should be fine.

Thanks!

Warning droidlogic
Room
treble_arm64_agS-userdebug 8.1.0 OPM6.171019 180807 test-keys

 

[CosmicDan]

Warning droidlogic
Room
treble_arm64_agS-userdebug 8.1.0 OPM6.171019 180807 test-keys

What? Why are you replying to me?

@ghpranav you probably should request this thread be locked lol

 

[ghpranav]

What? Why are you replying to me?

@ghpranav you probably should request this thread be locked lol

Lol, true. I'll get this thread locked, before more users come here ? . We have come a long way from trying to port a GSI to actually having a Treble compatibility. This thread brought back all the good old memories of mine XD

 

[KennyG123]

Thread closed at OP's request