[CH23]

  Hold Power + Volume Up to go into recovery. Press Power for 30 secs to completely turn off and hold again to turn on. I'm so excited!
Try these settings if you haven't yet, maybe it's the configuration? MD5 size calculation mismatch? Who knows yet! I'll extract it myself as well and let you know how it goes!
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
This might tell you more. I'm scattering and multi tasking right now. Crossing my fingers and smiling like an idiot.
http://android.stackexchange.com/questions/28653/obtaining-root-by-modifying-default-propro-secure
and another. I was gonna keep them for me, but you seem to be doing the handywork as of now. I'll join you in a bit.
https://forum.xda-developers.com/showthread.php?t=2593581

just bricked my device. had to physically disconnect the battery to even get into rockchip recovery. be aware.
 

 

[Paulo Abreu]

 
it means you own your device, instead of your device owning you.
 

 

 
just bricked my device. had to physically disconnect the battery to even get into rockchip recovery. be aware.
 

 

 
But I think the device is owning you guys ... 

 he he ...

 

[RebeccaSugar]

 
just bricked my device. had to physically disconnect the battery to even get into rockchip recovery. be aware.
 

Been there actually! Like 3 times, I managed to get myself back into Flash Mode using Adb/Fastboot, then reflashed back to stock and tried again. Hang in there baby! You're a brave one.

 

[CH23]

 
Been there actually! Like 3 times, I managed to get myself back into Flash Mode using Adb/Fastboot, then reflashed back to stock and tried again. Hang in there baby! You're a brave one.

if you repack the boot.img, even if you "change nothing", a lot of stuff does change. i'm now trying to figure out what parts constitute ro.secure=1 and see if i can just use a hex editor to edit the original boot.img.

it sounds too easy to be true.

 

[Sound Eq]

  I'll check on it tomorrow and let you know what I did exactly, might have had something to do with moving around a few files from root. I'll see.

do u think we could flash a v4a zip file that are floating on xda forums

 

[CH23]

 
Been there actually! Like 3 times, I managed to get myself back into Flash Mode using Adb/Fastboot, then reflashed back to stock and tried again. Hang in there baby! You're a brave one.

somehow the values of the ramdisk get changed dramatically.

i think i found the issue.

the repackaged ramdisk is 2048 bits short.

i'll write later, no time anymore atm.
In short:This morning i found tools to unpack the boot.img, leaving a kernel file, and a ramdisk.cpio.gz file, containing the ramdisk.cpio file, which contains the ramdisk file.
After changing the default.prop file, packing it up, and building the boot.img, and update.img, flashing it, the following happens:

Device starts. partitiins are formatted. Device then 'reboots' but does nothing. Can't see it with rockchip tools, nor with adb. Can't reset.
Removed battery, holding volume up button on reconnect to usb, can reflash.

I compared the original ramdisk.cpio with the modified, and find 2048 bits (or bytes, more likely) missing.

After adding these 0 value bytes, rebuild the whole thing, and flashed.

Now on first boot, it shows the 'welcome' splash. It didn't do that with previous build, but after formatting of partitiins, same effect. Dead device.

 

[Dobrescu George]

 

 
Been there actually! Like 3 times, I managed to get myself back into Flash Mode using Adb/Fastboot, then reflashed back to stock and tried again. Hang in there baby! You're a brave one.

somehow the values of the ramdisk get changed dramatically.

i think i found the issue.

the repackaged ramdisk is 2048 bits short.

i'll write later, no time anymore atm.
In short:This morning i found tools to unpack the boot.img, leaving a kernel file, and a ramdisk.cpio.gz file, containing the ramdisk.cpio file, which contains the ramdisk file.
After changing the default.prop file, packing it up, and building the boot.img, and update.img, flashing it, the following happens:

Device starts. partitiins are formatted. Device then 'reboots' but does nothing. Can't see it with rockchip tools, nor with adb. Can't reset.
Removed battery, holding volume up button on reconnect to usb, can reflash.

I compared the original ramdisk.cpio with the modified, and find 2048 bits (or bytes, more likely) missing.

After adding these 0 value bytes, rebuild the whole thing, and flashed.

Now on first boot, it shows the 'welcome' splash. It didn't do that with previous build, but after formatting of partitiins, same effect. Dead device.

 
You're one courageous one for doing this though! 
 
Seems like it's a lot of tense work the first few times you brick a device. Can't imagine it being very fun having to remove the battery... 

 

[CH23]

You're one courageous one for doing this though! 

Seems like it's a lot of tense work the first few times you brick a device. Can't imagine it being very fun having to remove the battery... 

Knowing that you can't really brick it feels good

the device can quite easily be taken apart; unscrew amp module, unscrew the 2 black screws.
Remove the plastic antenna cover (BE AWARE! the double sided tape will need to be replaced.)
In the top corners unscrew 2 tiny black screws.
Now slide screen a bit, and hinge it up. Watch out for the battery wires.
Now unscrew battery thingie, and the battery is loose!

 

[Sarcasmo]

Knowing that you can't really brick it feels good

the device can quite easily be taken apart; unscrew amp module, unscrew the 2 black screws.
Remove the plastic antenna cover (BE AWARE! the double sided tape will need to be replaced.)
In the top corners unscrew 2 tiny black screws.
Now slide screen a bit, and hinge it up. Watch out for the battery wires.
Now unscrew battery thingie, and the battery is loose!

... and in case anyone from FiiO is reading this, naturally it's all completely theoretical...

 

[rusnak666]

Hi,
 
is it possible to conect to k5 a usb otg storage? Im using the k5 with fiio x7 (latest beta firmware), if i connect the usb otg storage to usb conector of x7 it works, but if i connect the usb otg storage to the back usb conectors of k5 it does not works, thanks

 

[kgs51]

Well after much research, I decided to go with the HD650 from Sennheiser. Will the K5 from Fiio be adequate enough to drive these headphones or should I buy a separate amp or amp module from Fiio.
 
Thanks for all of your help.

 

[FiiO]

  Hi,
 
is it possible to conect to k5 a usb otg storage? Im using the k5 with fiio x7 (latest beta firmware), if i connect the usb otg storage to usb conector of x7 it works, but if i connect the usb otg storage to the back usb conectors of k5 it does not works, thanks

Dear rusnak666,
 
Sorry, it is not available for the K5 to act like that.
 
Best regards

 

[CH23]

I have given up.
I can't figure out why it won't reboot.
 
These are the tools and steps I have taken to get to where I am, I hope that someone might find them useful. LINUX ONLY!
I'm sure it can be done on windows/macOS/BSD/toasterOS but I don't use those.

Start off with extracting boot.img from update.img. (see http://www.head-fi.org/t/713735/fiio-x7-dxd-dsd-384k-64b-ess9018-android-wifi-bluetooth-4-amp-modules-balanced-out/16575#post_13258757 on how to do this)

Now get the following things:
https://github.com/osm0sis/Android-Image-Kitchen/tree/AIK-Linux
 
once extracted, you'll need to make a directory ./bin/x86_64/ and add "bootimg-info", "mkbootfs", "mkbootimg" and "unpackbootimg" in there.
these are programs you can find at :
 
https://github.com/neo-technologies/rockchip-mkbootimg
https://github.com/huaixzk/unpackbootimg
https://github.com/osm0sis/mkbootfs
https://github.com/osm0sis/bootimg-info
 
BE AWARE! the mkbootimg from huaixzk does not work due to pagefile sizes. only get the unpackbootimg from them.

place the boot.img in the directory containing  "unpackimg.sh" and "repackimg.sh"

run "unpackimg.sh"

this creates ./ramdisk/ and ./split_img/

you can edit ./ramdisk/default.prop with a good editor (such as nano, vi(m), emacs)
 
now the annoying bit. ./repackimg.sh errors, so we can't use this. instead do the following:
 
go into ./ramdisk/ and open a command line
 
find . | cpio -o -H newc | gzip > ../ramdisk.cpio.gz
 
now ramdisk.cpio.gz is created one directory above.
 
then use ./bootimg-info on boot.img this info is required to rebuild boot.img
 
use ./mkbootimg , using the following command: (be sure to check if the values match YOUR output of bootimg-info)
 
./mkbootimg --kernel ../../split_img/boot.img-zImage --ramdisk ../../ramdisk.cpio.gz --base 0x60087f00 --pagesize 16384 --kernel_offset 0x00008000 --ramdisk_offset 0x01c00000 --second_offset 0x00b00000 --tags_offset 0xffc88000 --ramdiskaddr 0x62000000 -o ../../newboot.img

this 'newboot.img' should now be placed in the rockdev/image/ directory, rename to boot.img, and then run rockdev/mkupdate.sh
 
see if you can flash your X7.
 
I have not gotten it to reboot after it formats the partitions.

turns out though, you can reset the device to flash it again. no need to remove the battery.
 

 

[RebeccaSugar]

I found a kernel that is not from the X7, but works with it. I'll send it to you as a last resort.
I'll study the files by the way, to see if there is a way to prevent those commands.

 

[kgs51]

   
I got my balanced silver cables for my HD 650 from Headphone Lounge. Even the silver cables are cheaper than the Moon Audio cables.

I am new to this but how do you set up the balanced silver cables to combine with the hd650