|
|
Post by rlw6534 on Mar 12, 2022 1:31:23 GMT
Here is an emmc firehose for the Hiby R5 (and likely R5S). The root is simple, use QFIL to save the boot.bin, patch with Magisk and reflash with QFIL. Tested and working on my personal R5 (for Magisk root - version 24.3). It also works on R6Pro (tested). It may work on other Snapdragon 425 devices as well (Cayin N6ii - untested) and the new R5ii. prog_emmc_firehose_8917_ddr_xiaomi.mbn (368.66 KB) |
|
|
|
Post by NPAudio on Mar 12, 2022 3:39:15 GMT
Here is an emmc firehose for the Hiby R5 (and likely R5S). The root is simple, use QFIL to save the boot.bin, patch with Magisk and reflash with QFIL. Tested and working on my personal R5 (for Magisk root - version 24.3). It may work on other Snapdragon 425 devices as well (Hiby R6Pro, Cayin N6ii - both untested). <button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button> Awesome mate! I'll be able to try it out on an N6II 👍 if it works on that it will definitely work on the R6Pro too. |
|
|
|
Post by NPAudio on Mar 12, 2022 5:47:22 GMT
p.s. come to think of it, I rooted (sort of) the N6ii not long after release by extracting the boot.img from a downloaded rom and magjsk patching / flashing with fastboot. Only thing was I could never unlock the bootloader so it would freeze when trying to write to the system partition. Was the R5 bootloader locked ? rlw6534, |
|
|
|
Post by rlw6534 on Mar 12, 2022 11:48:10 GMT
I assume the bootloader was not locked. I did switch the "oem unlock" option in developer options. Not sure if it matters. Fastboot mode did not work for me - "waiting for device", so I used QFIL to write the patched image.
|
|
|
|
Post by NPAudio on Mar 12, 2022 12:09:38 GMT
I assume the bootloader was not locked. I did switch the "oem unlock" option in developer options. Not sure if it matters. Fastboot mode did not work for me - "waiting for device", so I used QFIL to write the patched image. Yeah had thet off, maybe it's a bit different, magisk was happy it was rooted and working but not so. I'll give it a go with QFIL at some point next week cheers. |
|
|
|
Post by rlw6534 on Mar 12, 2022 12:21:04 GMT
I'll try to root my neglected R6Pro later today and report back. I have installed JamesDSP on my R5 and it's working, although a bit fussy with high resolution streaming. I'm not that experienced with it, so maybe that can be improved. I'm never quite sure about all of the audio patches (narsil, acp, aml, etc...). Viper did not work on the first try, installed OK but not processing. Not a big deal for me as I know Viper does not support high resolution anyway. My objective is system-wide EQ that also works with high resolution streaming.
Edit:
Confirmed to work on Hiby R6Pro.
|
|
|
|
Post by NPAudio on Mar 12, 2022 17:27:21 GMT
rlw6534 , Nice I'll let you you know on the N6ii
Can you confirm editing something like build prop works ok ?
I'll make some R5 and R6Pro threads. I used to like my R6Pro.
|
|
|
|
Post by rlw6534 on Mar 12, 2022 20:26:11 GMT
rlw6534 , Nice I'll let you you know on the N6ii
Can you confirm editing something like build prop works ok ?
I'll make some R5 and R6Pro threads. I used to like my R6Pro.
Actually I cannot edit build.prop (causes lockup). I'm having no problem installing Magisk modules or editing vendor. I did leave "preserve encryption" when patching with Magisk (selected by default). This is a new one for me; Google search shows it's not uncommon. I did get fastboot working (driver issues) but none of the "oem" commands seem to work. |
|
|
|
Post by NPAudio on Mar 12, 2022 20:48:19 GMT
rlw6534 , Nice I'll let you you know on the N6ii
Can you confirm editing something like build prop works ok ?
I'll make some R5 and R6Pro threads. I used to like my R6Pro.
Actually I cannot edit build.prop (causes lockup). I'm having no problem installing Magisk modules or editing vendor. I did leave "preserve encryption" when patching with Magisk (selected by default). This is a new one for me; Google search shows it's not uncommon. I did get fastboot working (driver issues) but none of the "oem" commands seem to work. Thanks buddy, sounds the same issue then but I never botherered to try magisk modules 👍 |
|
|
|
Post by rlw6534 on Mar 15, 2022 13:04:56 GMT
Yeah, the same issue with the R6Pro as well. Magisk modules install and work fine but no write access to the system folder. If you have any ideas to improve things let me know and I will try. Not sure if it's bootloader lock or perhaps verity issues. I did leave it disabled (the default) when patching for Magisk root. It's not a big deal for me as I can install JamesDSP which was my goal. Unfortunately it only works at 44.1 kHz (so far). You can, of course, change props with the Magisk props module if needed.
|
|
|
|
Post by NPAudio on Mar 15, 2022 13:19:16 GMT
Yeah, the same issue with the R6Pro as well. Magisk modules install and work fine but no write access to the system folder. If you have any ideas to improve things let me know and I will try. Not sure if it's bootloader lock or perhaps verity issues. I did leave it disabled (the default) when patching for Magisk root. It's not a big deal for me as I can install JamesDSP which was my goal. Unfortunately it only works at 44.1 kHz (so far). You can, of course, change props with the Magisk props module if needed. it will be one of those 2 (or both 🤔) I've not used JamesDSP much before, I was a die hard V4A user but obviously it doesn't go over 48khz. I wonder how it determines what khz to use. I just rooted a Shanling M9 and JamesDSP changes everything to 192khz |
|
|
|
Post by rlw6534 on Mar 15, 2022 14:49:49 GMT
JamesDSP works on my Fiio M11Pro and M11Plus at all streaming sample rates (at least to 192 kHz). My Hiby R5, R6Pro and R6 2020 don't work for high res. High resolution plays but JamesDSP does not process the audio. Probably some difference in SRC bypass method?
|
|
|
|
Post by leo5122 on Apr 19, 2022 20:51:42 GMT
how do i use this? i have qfil tool but have never used it before i have also file in first post
|
|
|
|
Post by rlw6534 on Apr 20, 2022 18:35:07 GMT
|
|
|
|
Post by whitigir on Apr 21, 2022 17:25:28 GMT
I am trying out on Shanling M30 and N8ii, neither devices are identified by ABD  So sad!! Is there anyway to force identifications of such ? Or to make it self identify ? LOL |
|
