|
Post by gentzen01 on Mar 10, 2022 11:03:39 GMT
Thanks Vince. I have read around about how to use QFIL with a Firehose programmer file (mbn/elf). And, no, I hadn't used TWRP before, just found clear instructions about how to use it to get a boot.img off the device. I'm totally new to all this (although, I am not without IT background). In fact, DX300 was my first Android device! So, you are saying the file Steve provided contains the partitions (incl. boot) for the DX300 Max and those other DAPs? I'm only asking because normally you'd be directing QFIL to the Firehose file for the particular device you have got and then use QFIL's partition manager to track down the boot and recovery partitions to make img files of these. So, I am confused, as Steve's Firehose file seems to be the same for a number of different DAPs.
One last question, am I right in saying the DX300 Max flash (hynix) memory is emmc?
|
|
|
Post by NPAudio on Mar 10, 2022 15:23:40 GMT
Thanks Vince. I have read around about how to use QFIL with a Firehose programmer file (mbn/elf). And, no, I hadn't used TWRP before, just found clear instructions about how to use it to get a boot.img off the device. I'm totally new to all this (although, I am not without IT background). In fact, DX300 was my first Android device! So, you are saying the file Steve provided contains the partitions (incl. boot) for the DX300 Max and those other DAPs? I'm only asking because normally you'd be directing QFIL to the Firehose file for the particular device you have got and then use QFIL's partition manager to track down the boot and recovery partitions to make img files of these. So, I am confused, as Steve's Firehose file seems to be the same for a number of different DAPs.
One last question, am I right in saying the DX300 Max flash (hynix) memory is emmc?
Yes it's emmc 👍 All the daps covered share a very similar SDM660 soc module in order to read the partition layout.
|
|
|
Post by gentzen01 on Mar 10, 2022 20:12:46 GMT
Thanks Steve. Unfortunately, Sahara failed to upload the Firehose file you provided in QFIL (so Partition Manager did not open). Not sure why, there is a chance it's the USB3 that's at fault, as my laptop doesn't have any USB2 ports.
I tried an alternative route, which is to download the latest DX300 Max firmware (1.03.209) from iBasso's site to my laptop, get from it the payload.bin file and extract from it the boot.img file. I have checked and this is the same firmware version my DX300 Max is currently running. So I'm guessing the boot.img I derived from the encrypted payload.bin file must be the same as I would get from downloading the actual firmware from my device (or from using QFIL to read the partitions). However, there only one boot.img file I got this way (Vince said there were 2 for DX300), so can anyone confirm this is correct and I can proceed with Magisk-patching it and flashing?
Any help would be appreciated!
|
|
|
Post by NPAudio on Mar 12, 2022 12:53:56 GMT
Thanks Steve. Unfortunately, Sahara failed to upload the Firehose file you provided in QFIL (so Partition Manager did not open). Not sure why, there is a chance it's the USB3 that's at fault, as my laptop doesn't have any USB2 ports.
I tried an alternative route, which is to download the latest DX300 Max firmware (1.03.209) from iBasso's site to my laptop, get from it the payload.bin file and extract from it the boot.img file. I have checked and this is the same firmware version my DX300 Max is currently running. So I'm guessing the boot.img I derived from the encrypted payload.bin file must be the same as I would get from downloading the actual firmware from my device (or from using QFIL to read the partitions). However, there only one boot.img file I got this way (Vince said there were 2 for DX300), so can anyone confirm this is correct and I can proceed with Magisk-patching it and flashing?
Any help would be appreciated!
gentzen01, Android with A/B partitions was introduced for seemless updating and less chance of updates bricking android. Their are 2 copies of all the major partitions so if your currently running from partition A an OTA update will update partition B while you continue to use partition A, when it reboots it will be running from partition B. Then at the next OTA cycle back to partition A You can look for the currently active partition with adb shell getprop ro.boot.slot_suffix
or in fastboot with
fastboot getvar all look for (bootloader) current-slot it will say either current-slot:a or current-slot:b You can change your active slot, A or B with: fastboot --set-active=a
or fastboot --set-active=b
So you can be extra safe and flash only the active one with a magisk patched boot.img
If using fastboot to flash, it will default to the active partion unless you force flash the alternate one.
If you have extracted boot.img then sure try patching in magisk.
Although I don't own a 3MAX I should still have a magisk patched boot.img for it although i'm not 100% its from the latest firmware.
:note supported fastboot commands vary between devices. Always makes sure your using the latest fastboot etc also.
|
|
|
Post by gentzen01 on Mar 12, 2022 15:16:12 GMT
Many thanks, that was very helpful (I didn't know how the two partitions worked with updates).
A quick question for clarification (as I'm newbie): the reason for not flashing the boot.img to both partitions (e.g. using flash boot_a and flash boot_b commands in fastboot), is it to retain one of the partitions (the currently inactive) with the old firmware boot file, in case the patched img file bricks the other one? If so, do i ever need to flash the boot img to the other partition?
|
|
|
Post by gentzen01 on Mar 12, 2022 16:18:36 GMT
Done! (I think). Magisk now has access to a lot more data from the device and so does SmartPack
|
|
|
Post by NPAudio on Mar 12, 2022 17:31:19 GMT
Done! (I think). Magisk now has access to a lot more data from the device and so does SmartPack Excellent, well done buddy 😁👍 Also check with a root checker like this:
|
|
|
Post by gentzen01 on Mar 12, 2022 18:10:34 GMT
Thanks Steve, yep Root Checker confirmed. Quick question, CPUsets (in Misc as you said), has ranges for CPU cores for various apps, starting 0-digit. Why "0"? I want to increase cores for audio apps (Neutron) and reduce for others, so do I just reduce the end-value of the range (while keeping 0)?
|
|
|
Post by NPAudio on Mar 12, 2022 18:32:33 GMT
Thanks Steve, yep Root Checker confirmed. Quick question, CPUsets (in Misc as you said), has ranges for CPU cores for various apps, starting 0-digit. Why "0"? I want to increase cores for audio apps (Neutron) and reduce for others, so do I just reduce the end-value of the range (while keeping 0)? It just starts counting at 0 instead of 1 so: To use all 4 Little CPU cores 1 to 4 would be 0-3 To use all 4 Big CPU cores 5 to 8 would be 4-7 To use all 8 CPU cores 1 to 8 would be 0-7 Here's what I have set on a Hiby RS6
|
|
|
Post by gentzen01 on Mar 12, 2022 22:24:51 GMT
. Should have thought about it! Computer people (never quite fans of Natural numbers)...
|
|
|
Post by gentzen01 on Mar 13, 2022 13:42:54 GMT
Thanks Steve, yep Root Checker confirmed. Quick question, CPUsets (in Misc as you said), has ranges for CPU cores for various apps, starting 0-digit. Why "0"? I want to increase cores for audio apps (Neutron) and reduce for others, so do I just reduce the end-value of the range (while keeping 0)? It just starts counting at 0 instead of 1 so: To use all 4 Little CPU cores 1 to 4 would be 0-3 To use all 4 Big CPU cores 5 to 8 would be 4-7 To use all 8 CPU cores 1 to 8 would be 0-7 Here's what I have set on a Hiby RS6 <button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button>
That's what the CPUsets look like on my Dap from the outset (i.e. without any tweaking). Yet, PCM-->DSD256 stutters and clips when screen is off. Have you set Governor to Performance, is that how this is remedied (with increased heat generation being the flipside)? Any other tweaks to lower battery consumption and temperatures (I noticed you had a raft of adb commands to weed out bloatware in your original thread)? Also, that .json file, you posted earlier on, where is this installed and applied? Btw, a nice and easy way (if QFIL doesn't cooperate for whatever reason, e.g. USB 3.0 or cable issues) to get a boot.img for rooting is to use Payload Dumper Go on the encrypted payload.bin file one can find in the stock firmware which can be downloaded from iBasso's website. In case anyone might find it useful.
|
|
|
Post by NPAudio on Mar 13, 2022 14:56:48 GMT
It just starts counting at 0 instead of 1 so: To use all 4 Little CPU cores 1 to 4 would be 0-3 To use all 4 Big CPU cores 5 to 8 would be 4-7 To use all 8 CPU cores 1 to 8 would be 0-7 Here's what I have set on a Hiby RS6 <button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button>
That's what the CPUsets look like on my Dap from the outset (i.e. without any tweaking). Yet, PCM-->DSD256 stutters and clips when screen is off. Have you set Governor to Performance, is that how this is remedied (with increased heat generation being the flipside)? Any other tweaks to lower battery consumption and temperatures (I noticed you had a raft of adb commands to weed out bloatware in your original thread)? Also, that .json file, you posted earlier on, where is this installed and applied? Btw, a nice and easy way (if QFIL doesn't cooperate for whatever reason, e.g. USB 3.0 or cable issues) to get a boot.img for rooting is to use Payload Dumper Go on the encrypted payload.bin file one can find in the stock firmware which can be downloaded from iBasso's website. In case anyone might find it useful. Hiby had Audio apps CPU-sets set to 0-3 but performance set on the governor as stock so cpu was maxed all the time lol I've reduced cpu and gpu frequencies by a load and using interactive governor. I have a host of other kernel changes.
I think 3MAX uses powersave governor as default to reduce temperatures.
WARNING: Please DON'T set your 3MAX to performance without extra hardware cooling and reducing maximum cpu/gpu frequencies
You are likely to cause damage to the SDM660 SOC, AKM4499 DACs or just reduce the life of the components in general.
The json file is a profile to import into smart kernel. This wasn't created on a 3MAX however.
Thanks for posting the payload dumper tip 👍 its a shame Hiby don't supply full images as standard.
|
|
|
Post by gentzen01 on Mar 13, 2022 16:31:34 GMT
CPU governor on the Max Ti is (by default) set to "Interactive" in the kernel for both sets of cores (Big/Little). Thanks for your kind warning, no, I was aware (through Whitigir's post) of the effects of maxing out the governor, so wasn't going to do it before you return my DAP with extra cooling. Just trying to figure out how I can use Neutron's on-the-fly conversion to DSD256 with screen off. Is reducing core numbers on other apps (e.g. Foreground, Top) apps making any difference (btw, what's a "Top" app)? GPU is default-set on power level 4 (I guess I can reduce that and frequencies)?
|
|
|
Post by NPAudio on Mar 13, 2022 18:50:50 GMT
Yep, use lowest min and max gpu freq and power level 1
|
|
|
Post by NPAudio on Mar 13, 2022 18:56:12 GMT
That's interesting as if I remember rightly the 3max stainless governor was powersave 🤔
|
|