Database Develop

[REQUEST] Stock System Images for KFHD 2013 (soho)

There's a lot of people out there with bricked KFHD 2013 (the newest Fire HD), with a lot of them requesting for the stock system images for this device. Unfortunately, no one has done so yet. However, if you have this device, and are rooted, you can help. To create these images, connect to a PC via ADB and enter these commands:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/data/local/backup/stock-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/data/local/backup/stock-system.img"
adb pull "/data/local/backup/stock-recovery.img"
adb pull "/data/local/backup/stock-boot.img".
adb pull "/data/local/backup/stock-system.img""
If someone could upload these somewhere and provide the download link it would be greatly appreciated.

Ph0enix_216 said:
There's a lot of people out there with bricked KFHD 2013 (the newest Fire HD), with a lot of them requesting for the stock system images for this device. Unfortunately, no one has done so yet. However, if you have this device, and are rooted, you can help. To create these images, connect to a PC via ADB and enter these commands:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/data/local/backup/stock-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/data/local/backup/stock-system.img"
adb pull "/data/local/backup/stock-recovery.img"
adb pull "/data/local/backup/stock-boot.img".
adb pull "/data/local/backup/stock-system.img""
If someone could upload these somewhere and provide the download link it would be greatly appreciated.
Click to expand...
Click to collapse
*clapping*
About time someone posted this, i was thinking of doing it myself soon. Hopefully someone will pull their images and maybe, just maybe they will get added to kffa.

stunts513 said:
*clapping*
About time someone posted this, i was thinking of doing it myself soon. Hopefully someone will pull their images and maybe, just maybe they will get added to kffa.
Click to expand...
Click to collapse
There are so many threads for bricks posted in the Q&A section that it's seriously disorienting. My mom's got the Fire HD 2013, but I've been told that tinkering with it is a major no-no .
Assuming someone can pull the system images off the Fire HD 2013, then this script here should work on it as well.

Nobody wants to help?
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<

I'll do it, I have adb setup but am getting an error entering the first command in. Do I have to have the device rooted for this to work?
Error is "su: not found"
su makes me think I need to root it...

Lol, yeah it needs to be rooted.
Sent from my KFHD running CM11

Ok I've rooted, now getting different error. I'll see what I can do to work through it.
C:\android-sdk\platform-tools>adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/data/local/backup/stock-boot.img"
/data/local/backup/stock-boot.img: cannot open for write: No such file or directory
---------- Post added at 10:14 PM ---------- Previous post was at 10:10 PM ----------
Got past that error as well, just had to create the /data/local/backup directory
I've entered the first command in and I'm waiting... not sure if it locked up or if it should take a while to run.
---------- Post added at 10:16 PM ---------- Previous post was at 10:14 PM ----------
And of course right when I post it finishes. I'm running the second command, but are we missing on command to create the stock-recovery.img file?
---------- Post added at 10:39 PM ---------- Previous post was at 10:16 PM ----------
Ok I don't really know what I'm doing but I did some quick reading about partitions so that I could grab the recovery and I found the command that lists the data I think we want. So this is the layout on my kindle.
[email protected]:/dev/block/platform/omap_hsmmc.1/by-name # ll
ll
lrwxrwxrwx root root 2014-02-17 21:42 boot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-02-17 21:42 bootloader -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-02-17 21:42 cache -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-02-17 21:42 crypto -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-02-17 21:42 efs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-02-17 21:42 idme -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-02-17 21:42 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-02-17 21:42 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-02-17 21:42 system -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-02-17 21:42 userdata -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-02-17 21:42 xloader -> /dev/block/mmcblk0p1
So these are the commands that I ran.
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/data/local/backup/stock-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/data/local/backup/stock-recovery.img"
adb shell su -c "dd if=/dev/block/mmcblk0p9 of=/data/local/backup/stock-system.img"
-- I had to do a chmod 644 * on the /data/local/backup/ directory so that I could pull the files.
adb pull "/data/local/backup/stock-recovery.img"
adb pull "/data/local/backup/stock-boot.img"
adb pull "/data/local/backup/stock-system.img"
I should have the files posted soon. Do we need any of the others?
---------- Post added at 11:01 PM ---------- Previous post was at 10:39 PM ----------
Here are the files.
* Removed link
---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------
I'll check this thread tomorrow, hopefully I can help out with getting this device going.

Your sure your Kindle is the "KIndle Fire HD 7 2013 MODEL, right?'

davethebrave14 said:
Your sure your Kindle is the "KIndle Fire HD 7 2013 MODEL, right?'
Click to expand...
Click to collapse
I just got this as a warranty replacement from Amazon yesterday. Model on the back cover is P48WVB4. This is the add supported model, not sure if that matters.

bmasephol said:
I just got this as a warranty replacement from Amazon yesterday. Model on the back cover is P48WVB4. This is the add supported model, not sure if that matters.
Click to expand...
Click to collapse
Does it have a front mounted camera and HDMI output? Also, run the command "adb shell mount > /sdcard/mount.txt" Then pull it off your device and post it here.
Sent from my iPod touch using Tapatalk

Ph0enix_216 said:
Does it have a front mounted camera and HDMI output? Also, run the command "adb shell mount > /sdcard/mount.txt" Then pull it off your device and post it here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
No front camera. Only port is headphone and micro USB. I'll have to do the adb later tonight to check that.
---------- Post added at 02:50 PM ---------- Previous post was at 02:34 PM ----------
Maybe another important piece is that this is the 8gb version, not a 16gb.

bmasephol said:
No front camera. Only port is headphone and micro USB. I'll have to do the adb later tonight to check that.
---------- Post added at 02:50 PM ---------- Previous post was at 02:34 PM ----------
Maybe another important piece is that this is the 8gb version, not a 16gb.
Click to expand...
Click to collapse
You definitely have the 2013 version. If you have 8GB of storage on your SD card, try to keep in mind that the total space of all three images is about 1GB (the boot and recovery ones should be pretty small, whereas the system image is pretty massive).
Sent from my iPod touch using Tapatalk

Ph0enix_216 said:
There's a lot of people out there with bricked KFHD 2013 (the newest Fire HD), with a lot of them requesting for the stock system images for this device. Unfortunately, no one has done so yet. However, if you have this device, and are rooted, you can help. To create these images, connect to a PC via ADB and enter these commands:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/data/local/backup/stock-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/data/local/backup/stock-system.img"
adb pull "/data/local/backup/stock-recovery.img"
adb pull "/data/local/backup/stock-boot.img".
adb pull "/data/local/backup/stock-system.img""
If someone could upload these somewhere and provide the download link it would be greatly appreciated.
Click to expand...
Click to collapse
Kindle Fire HD 2013 Soho:
boot0block.img 4096 kb ~ 4 mb
stock-recovery.img 8192 kb ~ 8mb
stock-boot.img 8192 kb ~ 8 mb
stock-system.img 1277952 kb ~ 1.22 gb
Uploading to server. Will post links asap.

blambo said:
Kindle Fire HD 2013 Soho:
boot0block.img 4096 kb ~ 4 mb
stock-recovery.img 8192 kb ~ 8mb
stock-boot.img 8192 kb ~ 8 mb
stock-system.img 1277952 kb ~ 1.22 gb
Uploading to server. Will post links asap.
Click to expand...
Click to collapse
Those are the exact sizes of the files inside the zip I have posted... minus the boot0block.img. Didn't pull that one. But would probably be good to have more than one source.

bmasephol said:
Those are the exact sizes of the files inside the zip I have posted... minus the boot0block.img. Didn't pull that one. But would probably be good to have more than one source.
Click to expand...
Click to collapse
Sure, exactly.
Links:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
Please check your CRCs.
Good luck with it.

blambo said:
Sure, exactly.
Links:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
Please check your CRCs.
Good luck with it.
Click to expand...
Click to collapse
Thank you, kind sir!
Sent from my iPod touch using Tapatalk

blambo said:
Sure, exactly.
Links:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
Please check your CRCs.
Good luck with it.
Click to expand...
Click to collapse
how can I use the images on my kindle I get a red flash then it goes straight to fastboot im of the understanding that the images may fix my kindle can someone explain how I would go about using them thanks

Um just thought i'd add I wouldn't post your boot0block, it contains things like your serial number, device I'd to kindle market(used for blacklisting), mac address, etc), its kinda personal info, its like whenever someone dumps their nvram they always erase their imei out of it so no one can jack their imei.
Sent from my Amazon Kindle Fire HD using Tapatalk

blambo said:
Sure, exactly.
Links:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
Please check your CRCs.
Good luck with it.
Click to expand...
Click to collapse
stunts513 said:
Um just thought i'd add I wouldn't post your boot0block, it contains things like your serial number, device I'd to kindle market(used for blacklisting), mac address, etc), its kinda personal info, its like whenever someone dumps their nvram they always erase their imei out of it so no one can jack their imei.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
True. But it's always good to back it up, as there have been a few cases (according to @Hashcode) where the boot0block has been wiped. Always good to have a backup of it handy. You just can't use someone else's to restore yours, and vice versa.
My next question is: does fastboot work for the Fire HD 2013 (soho) in the same way as the Fire HD 2012 (tate)?

Dead upon arrival.
I would have sent you mine if it wasn't rooted by amazon this very afternoon by update 11.3.2.1... going past my hosts file... probably a new push server IP.

[Q] Wifi not working

My wiifi is not working, it's a XT1056 , software 4.4.2.
<6>[ 34.137372,1] wlan: loading driver v3.2.6.114.1220.3
<3>[ 34.137494,1] wlan: [960:F :HDD] hdd_driver_init: WLAN device not found!!
<3>[ 34.137616,1] wlan: driver load failure
Click to expand...
Click to collapse

bean1975 said:
My wiifi is not working, it's a XT1056 , software 4.4.2.
Click to expand...
Click to collapse
Please see the post I directed you to in the sim-unlock thread.

This is what I have in my persist directory:
ls /persist/*bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
Click to expand...
Click to collapse

bean1975 said:
Code:
ls /persist/*bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
Click to expand...
Click to collapse
Yep, you are missing the factory file: WCNSS_qcom_wlan_nv.bin
Download it! It's linked here: http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
Post # 7. Then put only the missing file in /persist, and change the permissions (they might be set correctly already). Reboot and wifi should be back up

No, it's right there, look at my post.
-rw-r--r-- root root 29776 2013-09-21 18:40 WCNSS_qcom_wlan_nv.bin

bean1975 said:
No, it's right there, look at my post.
-rw-r--r-- root root 29776 2013-09-21 18:40 WCNSS_qcom_wlan_nv.bin
Click to expand...
Click to collapse
Ohhhh my bad! So it looks like you are missing this one: .bt_nv.bin
Is that correct?

adb shell su -c 'ls -la' /persist
-rw-rw---- bluetooth bluetooth 9 2013-09-21 18:35 .bt_nv.bin
that's there too. I just didnt hunt for hidden files.

bean1975 said:
adb shell su -c 'ls -la' /persist
-rw-rw---- bluetooth bluetooth 9 2013-09-21 18:35 .bt_nv.bin
that's there too. I just didnt hunt for hidden files.
Click to expand...
Click to collapse
Bummer. Then based on your original post:
hdd_driver_init: WLAN device not found!!
I would have to assume an actual hardware failure. That's too bad....
I really don't have any further advice or suggestions for you -- except for to maybe consider trying to flash the entire 4.4.2 SBF and return to 100% stock and see if it might fix the issue (assuming you haven't tried this already). I'm wondering if the seller didn't sell you a bad unit...

Yeah, probably hw fail, oh well, not a big deal.

(WIP) all LTE bands enable (need some help)

i have found out what files to change/edit to enable all LTE bands in CN/WW ect versions
but need some help here
i cant find out were in the hell the file is located
so can u help please do so
RFSKUID_DETECT=$(cat /sys/module/intel_mid_sfi/parameters/rf_sku_id)needs to be changed but cant locate it
PROJID_DETECT=$(cat /sys/module/intel_mid_sfi/parameters/project_id)no problem changing
COUNTRY_CODE=$(cat /factory/PhoneInfodisk/country_code)no problem changing

-fluffy- said:
i have found out what files to change/edit to enable all LTE bands in CN/WW ect versions
but need some help here
i cant find out were in the hell the file is located
so can u help please do so
RFSKUID_DETECT=$(cat /sys/module/intel_mid_sfi/parameters/rf_sku_id)needs to be changed but cant locate it
PROJID_DETECT=$(cat /sys/module/intel_mid_sfi/parameters/project_id)no problem changing
COUNTRY_CODE=$(cat /factory/PhoneInfodisk/country_code)no problem changing
Click to expand...
Click to collapse
Not sure if this is the file u are asking for but still i am attaching it...I opened this file and found only "2" written in it

mhp1995 said:
Not sure if this is the file u are asking for but still i am attaching it...I opened this file and found only "2" written in it
Click to expand...
Click to collapse
didt u take it from ur data on the phone
because its locked so we cant put it on the phone again

-fluffy- said:
didt u take it from ur data on the phone
because its locked so we cant put it on the phone again
Click to expand...
Click to collapse
I opened root browser and extracted this file from sys/module/intel_mid_sfi.... Can't we push this file via adb? I am sorry i dont know anything about this... I am learning things

mhp1995 said:
I opened root browser and extracted this file from sys/module/intel_mid_sfi.... Can't we push this file via adb? I am sorry i dont know anything about this... I am learning things
Click to expand...
Click to collapse
no we cant
thats why i need to know from were this file comes frome

sysfs is pseudo filesystem. The content there is not stored on disk, and will be reset on reboot.

updateing said:
sysfs is pseudo filesystem. The content there is not stored on disk, and will be reset on reboot.
Click to expand...
Click to collapse
I know that's why I need to know we're it is hidden in boot.img

-fluffy- said:
I know that's why I need to know we're it is hidden in boot.img
Click to expand...
Click to collapse
They are not in the ramdisk. Instead, the device drivers populate these sysfs files/nodes. You may want to check the discussion thread about unlocking bands in general forum. The OP there is planning to add some hax into kernel, which I think more reasonable.

In boot.img somewere the band code is hidden just need to find out we're so I can change it so it's gets the same code on reboot

This would mean that the phone would require an unlocked bootloader in order to have all LTE bands enabled as the boot.img is signed...one changed byte and the checksum wouldn't match

bootloader unlock:
http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547

tachno said:
bootloader unlock:
http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547
Click to expand...
Click to collapse
Yeah, I know - the OP is mentioning my nickname along with shakalaca's :silly:
Problem is that not everyone wants to risk the unlock and have possible warranty issues, this is the point I am trying to refer to

TheSSJ said:
Yeah, I know - the OP is mentioning my nickname along with shakalaca's :silly:
Problem is that not everyone wants to risk the unlock and have possible warranty issues, this is the point I am trying to refer to
Click to expand...
Click to collapse
I'm trying the unlock later today. Don't give a rats u know about the warranty ?

LTE bands depends on RF_SKU_ID value.
In kernel sources RF_SKU_ID is defined based on "zenfone2.MR7.1-2.18.40\linux\kernel\arch\x86\platform\intel-mid\intel_mid_sfi.c" file.
Possibly, if we change it to static WW value "0", then LTE bands may become available.

Not sure if this helps, but thought I'd mention it.
My CN region ZF2 has unlocked bootloader and is rooted. I am very much interested in this thread. Using adb shell as su, I have poked around the phone and see that under /factory/PhoneInfodisk/PhoneInfo_inf contains 'CN' along with the the serial no, and other items.
Also, in the same directory /factory/PhoneInfodisk the file 'country_code' contains only CN.
Code:
127|[email protected]:/factory/PhoneInfodisk # ls -l
ls -l
-r----x--t root root 612 1999-12-31 22:36 PhoneInfo_inf
-rw-rw-rw- root root 18 1999-12-31 22:36 bd_addr.conf
-rw-rw-rw- root root 3 1999-12-31 22:36 color_id
-rw-rw-rw- root root 3 1999-12-31 22:36 country_code
-rw-rw-rw- root root 5 1999-12-31 22:36 customer_id
-rw-rw-rw- root root 13 1999-12-31 22:36 ssn
Also, the rf_sku_id is 2 on my phone. I looked under /factory/telephony and there is a directory called 2 and contains a file:
Code:
[email protected]:/factory # cd telephony
cd telephony
[email protected]:/factory/telephony # ls -l
ls -l
drwxrwx--- system radio 1999-12-31 16:01 2
-rw-rw---- system radio 131072 1999-12-31 22:36 calib.nvm
[email protected]:/factory/telephony # ls -l 2
ls -l 2
-rw-rw---- system radio 131072 1999-12-31 22:37 calib.nvm
Here's the Intel 726x radio datasheet - http://download.intel.com/newsroom/archive/mobile-xmm-7260-1-brief.pdf
And, just so you know, I modified one file which enabled my original ZF2 CN version (converted to WW) to get LTE Band 2.

hi-phile said:
Not sure if this helps, but thought I'd mention it.
My CN region ZF2 has unlocked bootloader and is rooted. I am very much interested in this thread. Using adb shell as su, I have poked around the phone and see that under /factory/PhoneInfodisk/PhoneInfo_inf contains 'CN' along with the the serial no, and other items.
Also, in the same directory /factory/PhoneInfodisk the file 'country_code' contains only CN.
Code:
127|[email protected]:/factory/PhoneInfodisk # ls -l
ls -l
-r----x--t root root 612 1999-12-31 22:36 PhoneInfo_inf
-rw-rw-rw- root root 18 1999-12-31 22:36 bd_addr.conf
-rw-rw-rw- root root 3 1999-12-31 22:36 color_id
-rw-rw-rw- root root 3 1999-12-31 22:36 country_code
-rw-rw-rw- root root 5 1999-12-31 22:36 customer_id
-rw-rw-rw- root root 13 1999-12-31 22:36 ssn
Also, the rf_sku_id is 2 on my phone. I looked under /factory/telephony and there is a directory called 2 and contains a file:
Code:
[email protected]:/factory # cd telephony
cd telephony
[email protected]:/factory/telephony # ls -l
ls -l
drwxrwx--- system radio 1999-12-31 16:01 2
-rw-rw---- system radio 131072 1999-12-31 22:36 calib.nvm
[email protected]:/factory/telephony # ls -l 2
ls -l 2
-rw-rw---- system radio 131072 1999-12-31 22:37 calib.nvm
Here's the Intel 726x radio datasheet - http://download.intel.com/newsroom/archive/mobile-xmm-7260-1-brief.pdf
And, just so you know, I modified one file which enabled my original ZF2 CN version (converted to WW) to get LTE Band 2.
Click to expand...
Click to collapse
As fore now we need to find out we're we change the country code an RF_sku file so it gets the right info on boot

How has the progress been on changing the RF_sku country code?

mrbubs3 said:
How has the progress been on changing the RF_sku country code?
Click to expand...
Click to collapse
Not yet
But they are working on it

-fluffy- said:
Not yet
But they are working on it
Click to expand...
Click to collapse
Fluffy, is this the best place to watch for update news on this WIP??
If not, where??
Boowho??

Hello! I'm having problems with my mobile connection. I can connect without any problems on LTE but if LTE signal is not available, my phone does not connect on HSDPA or 3G. Is that a problem on my network provider or with the my zf2? Sorry if this is the wrong place to ask question.

I need a file to unbrick my LG L70 d320n from Qualcomm HS-USB QDLOADER 9008

Hi everyone who has an LG l70 d320n!
I need your help to unbrick my device.
I need i file from a working lg l70 d320n the "loader.img" which you can create ang give to my following this steps:
1) You must have a rooted device and a terminal app installed
2) open the terminal on your lg and type this code:
su
dd if = / dev / block / mmcblk0 of = / sdcard / Loader.img bs = 1024 count = 168960
and wait until it finishes
3) then you just go into your sdcard and look for a file named "Loader.img" and upload it to dropbox or google drive or any other site that makes it possible to send it to me.
It would be very useful to me because thanks to this file i can unbrick my device. PLEASE HELP ME!!!

did you get the loader.img?

nope

VIKU said:
nope
Click to expand...
Click to collapse
dd: unknown operand if
1|[email protected]:/ #
---------- Post added at 09:28 AM ---------- Previous post was at 09:04 AM ----------
VIKU said:
Hi everyone who has an LG l70 d320n!
I need your help to unbrick my device.
I need i file from a working lg l70 d320n the "loader.img" which you can create ang give to my following this steps:
1) You must have a rooted device and a terminal app installed
2) open the terminal on your lg and type this code:
su
dd if = / dev / block / mmcblk0 of = / sdcard / Loader.img bs = 1024 count = 168960
and wait until it finishes
3) then you just go into your sdcard and look for a file named "Loader.img" and upload it to dropbox or google drive or any other site that makes it possible to send it to me.
It would be very useful to me because thanks to this file i can unbrick my device. PLEASE HELP ME!!!
Click to expand...
Click to collapse
dd: unknown operand if
1|[email protected]:/ #

[Module] ts-binds (Abandoned)

ts-binds
ts-binds basically make use of “bind” parameter of the “mount” available in your Android environment
Development Abandoned!
This project has been abandoned. This is because I personally do not require ts-binds anymore. Refer announcement post here: https://forum.xda-developers.com/showpost.php?p=79150883&postcount=237
What does it do
Essentially, this "binding" method is widely used to save space on internal storage!
Derived from a very long-living trick for users who are struggling with the internal storage space available on their phones, while at the same time has the benefit of inserting an SD card, ts-binds will make use of already available functions on your device, to mirror a path to another path, effectively making both paths indistinguishable.
For example, if you mirror the `Download` folder on Internal with the `Stuff from Internet` folder on your SD Card, the same list of cat pictures will be shown on both directories when navigated via a file manager, and any changes will take effect on both paths but only the folder in the external path is physically modified.
This saves space because the files physically reside on the external storage instead of internal storage.
Further read
To maintain a similar "Description" of the module, I had to trim down the OP of the thread. There are a total of 3 places where I host the module's description To read documentation, please go to my website
Alternative modules with the same purpose
Magic Folder Binder (really advanced compared to this module!)
Magisk Foldermount (may be abandoned)
Links
Documentation
→ DOWNLOAD ZIPs (Also available in Magisk Repo)
GitHub
Changelogs
Verbose changelog for Magisk releases

Nice work!

Module has been accepted into the repository. Now it is available for install and update via Magisk.
Since the creation of this thread, there has been 4 newer versions, the latest being 1.0.4.

Hi @TechnoSparks!
I have the following problem:
I had set folder list line like this:
folderbind ogi "$sd/Ogi" "$int/Ogi"
and after reboot my log file looks like this:
Log initialised at: Sat Aug 12 19:50:30 CEST 2017
2017-08-12 19:50:30:
Difference found between cached and original user list
2017-08-12 19:50:30:
Updated cached list
2017-08-12 19:50:30:
sdcard 7788-9789 mounted
2017-08-12 19:50:30:
Binding all entries
2017-08-12 19:50:31:
Bind aborted: Folder '/mnt/media_rw/7788-9789/Ogi' as source doesn't exist!
2017-08-12 19:50:31:
All entries were processed
2017-08-12 19:50:31:
Script execution completed
What could be wrong?
Thank you.
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
ogisha said:
Hi @TechnoSparks!
I have the following problem:
I had set folder list line like this:
folderbind ogi "$sd/Ogi" "$int/Ogi"
and after reboot my log file looks like this:
Log initialised at: Sat Aug 12 19:50:30 CEST 2017
2017-08-12 19:50:30:
Difference found between cached and original user list
2017-08-12 19:50:30:
Updated cached list
2017-08-12 19:50:30:
sdcard 7788-9789 mounted
2017-08-12 19:50:30:
Binding all entries
2017-08-12 19:50:31:
Bind aborted: Folder '/mnt/media_rw/7788-9789/Ogi' as source doesn't exist!
2017-08-12 19:50:31:
All entries were processed
2017-08-12 19:50:31:
Script execution completed
What could be wrong?
Thank you.
Click to expand...
Click to collapse
BTW, both folders exist.

ogisha said:
Hi @TechnoSparks!
I have the following problem:
I had set folder list line like this:
folderbind ogi "$sd/Ogi" "$int/Ogi"
and after reboot my log file looks like this:
Log initialised at: Sat Aug 12 19:50:30 CEST 2017
2017-08-12 19:50:30:
Difference found between cached and original user list
2017-08-12 19:50:30:
Updated cached list
2017-08-12 19:50:30:
sdcard 7788-9789 mounted
2017-08-12 19:50:30:
Binding all entries
2017-08-12 19:50:31:
Bind aborted: Folder '/mnt/media_rw/7788-9789/Ogi' as source doesn't exist!
2017-08-12 19:50:31:
All entries were processed
2017-08-12 19:50:31:
Script execution completed
What could be wrong?
Thank you.
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
BTW, both folders exist.
Click to expand...
Click to collapse
Hello
This seems to be a very odd issue, but it could be that ts-binds cannot access the folder via the hardcoded address of "/mnt/media_rw/". this is a perfect opportunity for me to troubleshoot this. Thank you for the report.
It would be great if you could run these commands (without the hashtags) on your terminal emulator and report back with the output (whether text or screenshots, your choice):
Code:
# if [ -d "/storage/7788-9789/Ogi" ]; then echo Exists; else echo Nope; fi
# ls -a1 /mnt
it would also be a great addition if you could copy the file "/proc/mounts" and attach it here.
And may I know what device are you using and the respective ROM version?

TechnoSparks said:
Hello
This seems to be a very odd issue, but it could be that ts-binds cannot access the folder via the hardcoded address of "/mnt/media_rw/". this is a perfect opportunity for me to troubleshoot this. Thank you for the report.
It would be great if you could run these commands (without the hashtags) on your terminal emulator and report back with the output (whether text or screenshots, your choice):
it would also be a great addition if you could copy the file "/proc/mounts" and attach it here.
And may I know what device are you using and the respective ROM version?
Click to expand...
Click to collapse
Commands' output:
HWEVA:/ $ su
HWEVA:/ # if [ -d "/storage/7788-9789/Ogi" ]; then echo Exisge/7788-9789/Ogi" ]; then echo Exists; else echo Nope ; fi <
Nope
HWEVA:/ # ls -a1 /mnt
.
..
appfuse
asec
expand
ext_sdcard
media_rw
obb
runtime
sdcard
secure
user
HWEVA:/ #
mounts file attached:
https://mega.nz/#!VF8wHIAb!hVPzmAVoBEWhLUehostkfb7kXOAELVA4iSsqMiooY3E
Device's information:
BOARD
EVA-L09
BOOTLOADER
unknown
BRAND
HUAWEI
CPU_ABI
arm64-v8a
DEVICE
HWEVA
DISPLAY
EVA-L09C432B386
FINGERPRINT
HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B386:user/release-keys
HARDWARE
hi3650
HOST
wuhjk0154cna
ID
HUAWEIEVA-L09
MANUFACTURER
HUAWEI
MODEL
EVA-L09
PRODUCT
EVA-L09
SERIAL
MWS7N17104001072
TAGS
release-keys
TYPE
user
UNKNOWN
unknown
USER
test
CODENAME
REL
INCREMENTAL
C432B386
RELEASE
7.0
SDK_INT
24
RADIO
21.258.05.00.030
Root Access:
Access Granted
SU:
su found
UID/GID:
uid=0(root)
gid=0(root)
groups=0(root)
context=u:r:su:s0
Utils:
busybox
toybox
toolbox
Path:
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin:/system/vendor/bin:/vendor/xbin:/system/vendor/xbin:/product/bin:/product/xbin
Path:
/sbin/
Version:
13.3:MAGISKSU (topjohnwu)
Permissions:
rwxrwxrwx
Owner:
root:root
SELinux:
Enforcing
Path:
[/system/xbin/]
Permissions:
r-xr-xr-x
Owner:
root:shell
Thank you!

ogisha said:
Commands' output:
HWEVA:/ $ su
HWEVA:/ # if [ -d "/storage/7788-9789/Ogi" ]; then echo Exisge/7788-9789/Ogi" ]; then echo Exists; else echo Nope ; fi <
Nope
HWEVA:/ # ls -a1 /mnt
.
..
appfuse
asec
expand
ext_sdcard
media_rw
obb
runtime
sdcard
secure
user
HWEVA:/ #
mounts file attached:
https://mega.nz/#!VF8wHIAb!hVPzmAVoBEWhLUehostkfb7kXOAELVA4iSsqMiooY3E
Device's information:
BOARD
EVA-L09
BOOTLOADER
unknown
BRAND
HUAWEI
CPU_ABI
arm64-v8a
DEVICE
HWEVA
DISPLAY
EVA-L09C432B386
FINGERPRINT
HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B386:user/release-keys
HARDWARE
hi3650
HOST
wuhjk0154cna
ID
HUAWEIEVA-L09
MANUFACTURER
HUAWEI
MODEL
EVA-L09
PRODUCT
EVA-L09
SERIAL
MWS7N17104001072
TAGS
release-keys
TYPE
user
UNKNOWN
unknown
USER
test
CODENAME
REL
INCREMENTAL
C432B386
RELEASE
7.0
SDK_INT
24
RADIO
21.258.05.00.030
Root Access:
Access Granted
SU:
su found
UID/GID:
uid=0(root)
gid=0(root)
groups=0(root)
context=u:r:su:s0
Utils:
busybox
toybox
toolbox
Path:
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin:/system/vendor/bin:/vendor/xbin:/system/vendor/xbin:/product/bin:/product/xbin
Path:
/sbin/
Version:
13.3:MAGISKSU (topjohnwu)
Permissions:
rwxrwxrwx
Owner:
root:root
SELinux:
Enforcing
Path:
[/system/xbin/]
Permissions:
r-xr-xr-x
Owner:
root:shell
Thank you!
Click to expand...
Click to collapse
EDIT: never mind, when i return from work today i will create an exclusive simple troubleshooting script for you! This is to ease the troubleshooting.
----
I have to say something weird is happening. The terminal should say the directory exists on the location i mentioned.
From the way you present your things, it seemed that you know what you are doing and is good with terminal. Could you report if you can "ls Ogi" when you changed the working directory to "/mnt/media_rw/7788-9789", "/storage/7788-9789" and "/mnt/ext_sdcard"?
Out of curiosity, I have seen issues in regards to sdcardfs with Magic Folder Binder module, and is wondering if your issue also has to do with it. Please run "grep sdcardfs /system/build.prop" and return me the output. Just some extra for fun note: My module isn't really ready to handle issues with sdcardfs and i may need to implement Magic Folder Binder's methods (persist off for build prop entry)
Also make sure the Ogi folder still exists tho lel ?
Sorry for having the commands not enclosed in the code tags. I am replying to this on the go

TechnoSparks said:
EDIT: never mind, when i return from work today i will create an exclusive simple troubleshooting script for you! This is to ease the troubleshooting.
Click to expand...
Click to collapse
Thanks. ?
--
I have to say something weird is happening. The terminal should say the directory exists on the location i mentioned. From the way you present your things, it seemed that you know what you are doing and is good with terminal. Could you report if you can "ls Ogi" when you changed the working directory to "/mnt/media_rw/7788-9789", "/storage/7788-9789" and "/mnt/ext_sdcard"?
--
Here comes the output:
HWEVA:/ $ su
HWEVA:/ # cd /mnt/media_rw/7788-9789
sh: cd: /mnt/media_rw/7788-9789: No such file or directory
2|HWEVA:/ # cd /storage/7788-9789
sh: cd: /storage/7788-9789: No such file or directory
2|HWEVA:/ # cd /mnt/ext_sdcard
HWEVA:/mnt/ext_sdcard # ls Ogi
HWEVA:/mnt/ext_sdcard #
BTW, both Ogi folders are empty.
--
Out of curiosity, I have seen issues in regards to sdcardfs with Magic Folder Binder module, and is wondering if your issue also has to do with it.
--
Magic Folder Binder did not work for me.
The developer was not interested in investigating the problem. ?
--
Please run "grep sdcardfs /system/build.prop" and return me the output. Just some extra for fun note: My module isn't really ready to handle issues with sdcardfs and i may need to implement Magic Folder Binder's methods (persist off for build prop entry)
--
Here comes the output:
HWEVA:/ $ su
HWEVA:/ # grep sdcardfs /system/build.prop
1|HWEVA:/ #
--
Also make sure the Ogi folder still exists tho lel ?
--
Yeah, both do and both are empty. ?
--
Sorry for having the commands not enclosed in the code tags. I am replying to this on the go
--
No problem at all. ?
Thank you. ?

ogisha said:
Thanks.
--
I have to say something weird is happening. The terminal should say the directory exists on the location i mentioned. From the way you present your things, it seemed that you know what you are doing and is good with terminal. Could you report if you can "ls Ogi" when you changed the working directory to "/mnt/media_rw/7788-9789", "/storage/7788-9789" and "/mnt/ext_sdcard"?
--
Here comes the output:
HWEVA:/ $ su
HWEVA:/ # cd /mnt/media_rw/7788-9789
sh: cd: /mnt/media_rw/7788-9789: No such file or directory
2|HWEVA:/ # cd /storage/7788-9789
sh: cd: /storage/7788-9789: No such file or directory
2|HWEVA:/ # cd /mnt/ext_sdcard
HWEVA:/mnt/ext_sdcard # ls Ogi
HWEVA:/mnt/ext_sdcard #
BTW, both Ogi folders are empty.
--
Out of curiosity, I have seen issues in regards to sdcardfs with Magic Folder Binder module, and is wondering if your issue also has to do with it.
--
Magic Folder Binder did not work for me.
The developer was not interested in investigating the problem.
--
Please run "grep sdcardfs /system/build.prop" and return me the output. Just some extra for fun note: My module isn't really ready to handle issues with sdcardfs and i may need to implement Magic Folder Binder's methods (persist off for build prop entry)
--
Here comes the output:
HWEVA:/ $ su
HWEVA:/ # grep sdcardfs /system/build.prop
1|HWEVA:/ #
--
Also make sure the Ogi folder still exists tho lel
--
Yeah, both do and both are empty.
--
Sorry for having the commands not enclosed in the code tags. I am replying to this on the go
--
No problem at all.
Thank you.
Click to expand...
Click to collapse
Thank you for the output. It seemed that I may have found the issue. My script unreliably pulled the wrong sdcard serial ID when the "grep"ing was run. In your mounts the line:
Code:
/dev/block/bootdevice/by-name/system /dev/magisk/dummy/system/bin/79b77788-9789-4a7a-a2be-b60155eef5f4.sec ext4 ro,seclabel,relatime,data=ordered 0 0
came first before the sdcard mounting line:
Code:
/dev/block/vold/public:179:193 /mnt/media_rw/7EB2-43FD vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
The first line contains sequences of which matches my regular expression here:
Code:
sdname=$(grep -m 1 -Eo "[0-9A-F]{4}-[0-9A-F]{4}" /proc/mounts)
Possible fix: Reliably get the whole "media_rw" line before extracting SD card's serial
Please test the following pre-release: https://drive.google.com/file/d/0ByQKilNkFEpAaW02RGJoRUZGcUU/view?usp=sharing

TechnoSparks said:
Thank you for the output. It seemed that I may have found the issue. My script unreliably pulled the wrong sdcard serial ID when the "grep"ing was run. In your mounts the line:
came first before the sdcard mounting line:
The first line contains sequences of which matches my regular expression here:
Possible fix: Reliably get the whole "media_rw" line before extracting SD card's serial
Please test the following pre-release: https://drive.google.com/file/d/0ByQKilNkFEpAaW02RGJoRUZGcUU/view?usp=sharing
Click to expand...
Click to collapse
Thank you. I have tested it. Log file now looks like this:
-----
Log initialised at: Tue Aug 15 19:30:54 CEST 2017
2017-08-15 19:30:55:
Cached the user list
-----
Anything I copy to internal Ogi folder does not show up in external Ogi folder. ?
Thank you again. ??

ogisha said:
Thank you. I have tested it. Log file now looks like this:
-----
Log initialised at: Tue Aug 15 19:30:54 CEST 2017
2017-08-15 19:30:55:
Cached the user list
-----
Anything I copy to internal Ogi folder does not show up in external Ogi folder.
Thank you again.
Click to expand...
Click to collapse
Thank you for the report again and apologies for the new issue. I have able to pinpoint the issue and it seems to be a grammar error for bash.
I have corrected the issue and this is another test package for you to test: https://drive.google.com/open?id=0ByQKilNkFEpAaW02RGJoRUZGcUU
The reason why the content didn't show up was because no binding process were made. As you can see in the log, there is no "Binding all entries". Hopefully this one will finally squash the issue!
As you may notice, the "beta" also contains some changes, mainly just some cleanup and a new description.

TechnoSparks said:
Thank you for the report again and apologies for the new issue. I have able to pinpoint the issue and it seems to be a grammar error for bash.
I have corrected the issue and this is another test package for you to test: https://drive.google.com/open?id=0ByQKilNkFEpAaW02RGJoRUZGcUU
The reason why the content didn't show up was because no binding process were made. As you can see in the log, there is no "Binding all entries". Hopefully this one will finally squash the issue!
As you may notice, the "beta" also contains some changes, mainly just some cleanup and a new description.
Click to expand...
Click to collapse
Everything went fine according to log file.
Now Ogi folder on internal sdcard has disappeared and file 0 bytes long named Ogi appeared.
Folder Ogi on external sdcard stayed untouched.
Thanks again. ?

ogisha said:
Everything went fine according to log file.
Now Ogi folder on internal sdcard has disappeared and file 0 bytes long named Ogi appeared.
Folder Ogi on external sdcard stayed untouched.
Thanks again.
Click to expand...
Click to collapse
This is abnormal. For the first patch, I could blame myself for not testing it myself before publishing it to you. The reason was because i did a simple test on the terminal on nested command substitution ( $() ) and it worked, so I called it a job done. However I didn't expect it to not work if the nested command substitution is placed as a conditional, hence the past issue. The second revision fixed this by well, not using nested command substitution. The second version is personally tested and my folders are now binded correctly and working as expected like 1.0.4
Also, please tell me what file manager are you using.
I think this must have to do with the ROM or the kernel, since the modifications that I did to try to fix your previous issues was just related to how SD card serial ID is pulled. Let's check if the system recognises the folder via terminal.
Code:
cd /storage/emulated/0
ls -al | grep Ogi
check if the output is similar to this:
Code:
drwxrwx--x 1 root sdcard_rw 131072 2017-08-17 04:25 Ogi
Emphasis on the "drwxr-xr-x". If yours is similar, then continue below. Otherwise please report that it didnt.
Great! It seems that most probably it has something to do with the ROM, but not with the kernel. Next, I'd like for you to "cd" into it, then create a text file by running this simple line:
Code:
echo date > text.txt
Now, check if the text file exists on SD Card folder, by using a file manager.

TechnoSparks said:
This is abnormal. For the first patch, I could blame myself for not testing it myself before publishing it to you. The reason was because i did a simple test on the terminal on nested command substitution ( $() ) and it worked, so I called it a job done. However I didn't expect it to not work if the nested command substitution is placed as a conditional, hence the past issue. The second revision fixed this by well, not using nested command substitution. The second version is personally tested and my folders are now binded correctly and working as expected like 1.0.4
Also, please tell me what file manager are you using.
I think this must have to do with the ROM or the kernel, since the modifications that I did to try to fix your previous issues was just related to how SD card serial ID is pulled. Let's check if the system recognises the folder via terminal.
check if the output is similar to this:
Emphasis on the "drwxr-xr-x". If yours is similar, then continue below. Otherwise please report that it didnt.
Click to expand...
Click to collapse
I am using MiXplorer file manager. I had tried Total Commander, but results are the same.
Here is the output:
HWEVA:/ $ cd /storage/emulated/0
HWEVA:/storage/emulated/0 $ ls -al | grep Ogi
ls: ./Ogi: Cross-device link
1|HWEVA:/storage/emulated/0 $
Obviously, there is no text file. ?
BTW, when I delete Ogi file on internal sdcard, put folderbind line in folder list under comment and reboot, Ogi folder on internal sdcard reappears.
Great! It seems that most probably it has something to do with the ROM, but not with the kernel. Next, I'd like for you to "cd" into it, then create a text file by running this simple line:
Now, check if the text file exists on SD Card folder, by using a file manager.
Click to expand...
Click to collapse
Output:
1|HWEVA:/storage/emulated/0 $ cd Ogi
/system/bin/sh: cd: /storage/emulated/0/Ogi: Cross-device link
2|HWEVA:/storage/emulated/0 $ cd ./Ogi
/system/bin/sh: cd: /storage/emulated/0/Ogi: Cross-device link
2|HWEVA:/storage/emulated/0 $
Thank you for your patience.

ogisha said:
I am using MiXplorer file manager. I had tried Total Commander, but results are the same.
Here is the output:
HWEVA:/ $ cd /storage/emulated/0
HWEVA:/storage/emulated/0 $ ls -al | grep Ogi
ls: ./Ogi: Cross-device link
1|HWEVA:/storage/emulated/0 $
Obviously, there is no text file.
BTW, when I delete Ogi file on internal sdcard, put folderbind line in folder list under comment and reboot, Ogi folder on internal sdcard reappears.
Output:
1|HWEVA:/storage/emulated/0 $ cd Ogi
/system/bin/sh: cd: /storage/emulated/0/Ogi: Cross-device link
2|HWEVA:/storage/emulated/0 $ cd ./Ogi
/system/bin/sh: cd: /storage/emulated/0/Ogi: Cross-device link
2|HWEVA:/storage/emulated/0 $
Thank you for your patience.
Click to expand...
Click to collapse
Sorry for the length of time i took to reply. I have been busy
Hmm.. This is not a bug, but rather an incompatibility. Huge chances that your kernel may contain modifications different from the norm. But let's see if I can workaround from the current method, since the terminal says it's a cross-device link. For this, I need a single file /proc/mounts to be inspected. Can you hand me that file, please?
I am also assuming that your kernel does support binding folders (default and expected behaviour across linux kernels).

TechnoSparks said:
Sorry for the length of time i took to reply. I have been busy
Hmm.. This is not a bug, but rather an incompatibility. Huge chances that your kernel may contain modifications different from the norm. But let's see if I can workaround from the current method, since the terminal says it's a cross-device link. For this, I need a single file /proc/mounts to be inspected. Can you hand me that file, please?
I am also assuming that your kernel does support binding folders (default and expected behaviour across linux kernels).
Click to expand...
Click to collapse
Please see what you can do.
Mounts attached.
Thank you.

ogisha said:
Please see what you can do.
Mounts attached.
Thank you.
Click to expand...
Click to collapse
After a closer look, it seems that your device really does have sdcardfs turned on!
Let's use a simple buildprop entry to turn it off, hopefully it will work (although i know this seems so simple). You may use this new beta: https://drive.google.com/open?id=0ByQKilNkFEpAcmVxbkhsaUhSRHM

TechnoSparks said:
After a closer look, it seems that your device really does have sdcardfs turned on!
Let's use a simple buildprop entry to turn it off, hopefully it will work (although i know this seems so simple). You may use this new beta: https://drive.google.com/open?id=0ByQKilNkFEpAcmVxbkhsaUhSRHM
Click to expand...
Click to collapse
It still the same like previous.
Thank you.

ogisha said:
It still the same like previous.
Thank you.
Click to expand...
Click to collapse
Please try again with a newer version: https://drive.google.com/uc?id=0ByQKilNkFEpAcmVxbkhsaUhSRHM&export=download

TechnoSparks said:
Please try again with a newer version: https://drive.google.com/uc?id=0ByQKilNkFEpAcmVxbkhsaUhSRHM&export=download
Click to expand...
Click to collapse
Still not working. :crying: