yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] hankching:
Missing partition below:

package_extract_file: can't open /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot for write: No such file or directory
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I too! :)

No, I don't use any TW 6.0 because I know that isn't working at the moment. But I believe it will be working in the future :D

Now I have 3 slots (no TW):

*primary - Temasek's ROM 6.0.1 cm13 - there is a problem with kernel (but I replace kernel from Purify cm13 6.0.1),

*second slot - Purify cm13 6.0.1 - working very well :p

*third slot - ResurrectionRemix M 6.0.1 - it didn't work so I deleted (black screen after Note3 logo, BootUI didn't show up if I remember correctly). If you want I can send to you logs of this situation.

Have a good day! Thanks! :)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Tried the build with the possible fsck fix on K3 Note also, but it didn't work either. :(
[Galaxy S 4 i9505 Original Android Development] santajulia.ego:
hi again [MENTION=4277844]chenxiaolong[/MENTION], a was wondering, and really if i look sooooooooooooooo lazy, but there is a posibility to use a TWRP backup to install a secondary rom?
[Galaxy S 4 i9505 Original Android Development] robcore:
[MENTION=4277844]chenxiaolong[/MENTION]

Hi! Very impressive project here man, kudos!

I'm a tw kernel "developer" (let's be honest, hacker at best) for the i9505, and my users have shown me some logs after your patches are applied.

Basically, I'm seeing none of my service-spawned startup scripts completing (I have them printing to /dev/kmsg upon completion for verification).

They are pretty crucial for the operation, as they launch init.d, su-daemon, set some boot defaults and create the json backend for the Synapse app I use to accompany the kernel (similiar to stweaks).

In total I have 3 start up services/scripts: one mid-boot for early init stuff, one post boot that has replaced com's post-init garbage, and one entitled uci which sets the json backend for Synapse in motion.

Is there something I can do on my end to account for the mbtool modifications to the boot/init process?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
You can't use twrp backups just like you're flashing a rom as for now. A huge amount of work is needed for this to happen. You can restore a backup which was previously made with the patcher.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is fixed in the test build here: https://github.com/chenxiaolong/DualBootPatcher/pull/261 (This also includes the fsck changes.)

It looks like the path to the boot partition is different when you used the in-app flashing (as [MENTION=7320148]hankching[/MENTION] noted).

Hmm, I guess that won't work on your ROM then. Could you grab a logcat immediately after boot? The old fsck test build or the new one a linked above are both fine.

Also, what happens when you run this?

su -c /system/bin/fsck_msdos
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks!

I'm really surprised any of that would be affected. Most of what mbtool does happens before /init is ever run and the only change that is made to the /init*.rc files is adding "import /init.multiboot.rc" to init.rc (/init.multiboot.rc contains a single service definition). I'll flash your kernel on my SGH-M919 and report back on my findings.
[Galaxy S 4 i9505 Original Android Development] robcore:
Thank you! Remember the uninstaller, it restores the stock binaries to their original state (mpdecision, thermald, etc). Andy, the user to bring it up, gave me a copy of the ramdisk post-patch and I didn't notice the multiboot.rc, maybe I should remove the commented lines in my imports?

Edit: Ps the Synapse backend relies on Busybox on rails from the play store, could that be conflicting with something?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
NOTE: Anyone running into boot issues where a freshly installed ROM hangs at the boot animation with 9.0.0.r31.g6046c0e or newer should upgrade to 9.0.0.r47.gd65a6fd.

There was a change I made to completely disable the app sharing process when app sharing is disabled and this caused an important patch to not be applied during boot.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I tested too but again black screen :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah, right, the changes won't show up in the patched boot.img because the modifications occur at runtime. You'd have to compare what's in the root directory after the device has booted.

It most likely wouldn't because the mbtool doesn't rely on any other binaries (not even a shell).

EDIT: Unfortunately, the kernel doesn't boot on the SGH-M919. It never gets to the ramdisk. Could it be because the T-Mobile S4 is stuck on the Kit Kat (M919UVUFOK3) bootloader?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
And there is a logs (oops very big file).
[Galaxy S 4 i9505 Original Android Development] robcore:
Ah it's a runtime change, that makes sense.

It could definitely be a bootloader issue. I think there is a patch for the old bootloader's compatibility that I will hunt down, and cm's variant-inclusive patch for good measure!
[Galaxy S 4 i9505 Original Android Development] Pcsx2006:
http://cloud.tapatalk.com/s/580d674a0589e/MultiBoot.jpg? [MENTION=4277844]chenxiaolong[/MENTION] failed to flash cm14 before it was flashing just fine now I don't know what happened it's not flashing anymore. Screenshot as well multiboot.jpg which is actually multiboot. log.

Can u plz look into it.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Try repatching with the latest version of the patcher. This bug was recently fixed.
[Galaxy S 4 i9505 Original Android Development] Pcsx2006:
Ok
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Same error with the latest v9.0.0.r49, CM14 installation failed on hlte. The only successful time patching, installing and booting of CM14 was with v8.0.0.r2468 (although entering developer options is not possible if the rom is installed on a non-primary slot).

Great work nonetheless!

Edit: I tried again repatching with v8.0.0.r2468 and flashing the rom was successful. Unfortunately it stuck at boot logo. Log attached. Could you please have a look?
[Galaxy S 4 i9505 Original Android Development] Nagytoll:
Is there a working version for oneplus 3? Only thing I would like is OOS 3.2.7 primary and RR as secondary and fb messenger shared between them. Is that version 8.somrthing good for this?
[Galaxy S 4 i9505 Original Android Development] Andycar:
About /sbin/uci script .... I wonder why the mount rootfs commands do not execute in the script?

Could it be that mbtool takes over syscall for chmod. Does mbtool modify contents of /sbin or /res dirs at runtime after boot with 'chmod' command?

Sorry - I may have wrote a mess type of post above! :) But...

I found dirty hack to launch Synapse! I've just commented out both "#mount -t rootfs bla bla bla " lines in the uci script, after that Synapse launches!

Still, I don't understand the root cause of it all...

Cheers!
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION]: The output of the above command on Oukitel K6000 Pro running stock Android 6.0:

The fsck_msdos options input by caller :
usage: fsck_msdosfs -p [-f] filesystem ...
fsck_msdosfs [-ny] filesystem ...

After I updated the ramdisk the command returned nothing. :(

And on K3 Note running CM12.1 like rom 5.1.1

fsck_msdos was disabled by mbtool because performing an online fsck while the
vfat partition is mounted is not possible. This is done to ensure that vold
does not fail the filesystem checks and make the external SD invisible to the OS.
If the filesystem checks must be completed, it will need to be done from a
computer or from recovery.

I guess the right output is from the K3 Note, is that means that it won't work on the Oukitel? Could be an issue with the Selinux policy?

The log will come soon. I still don't have the kernel.log file in the /Multiboot path.

Logcat and Getlogs attached.
[Galaxy S 4 i9505 Original Android Development] Nagytoll:
The newest r49 build is working for me, with oos 3.2.7 primary and official RR as secondary.

1 question : I already have fb messenger installed, if I share the data, it logs me out. How do I copy my existing messenger data to the shared one?
[Galaxy S 4 i9505 Original Android Development] hankching:
Error because of Unknown ROMID
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
Unfortunately tested with RR (redoing the patch and installing over) did not work. I decided to patch the CM 13 and install (one rom that was already installed in dualboot before) but this time stop on bootanimation. I saw you corrected it, but do not know which build to use, tested R49 but does not support my device
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Many thanks for trying to fix that nasty mtk problem! Sadly I'm now using the test build here on K6000 Pro

https://jenkins.noobdev.io/job/Dual...r-builder && fast,target=android-all-gcc/301/

I patched the rom and installed to extsd-sd2 slot in twrp. 5 vibrations at boot, just like before, looking at the kernel.log I'm getting the same error:

mblog: Failed to symlink /dev/block/mmcblk1p1 to /dev/block/platform/mtk-msdc.0/by-num/p1: File exists
mblog: Failed to symlink /dev/block/mmcblk1p2 to /dev/block/platform/mtk-msdc.0/by-num/p2: File exists

The ramdisk of the primary is not updated, because still "sdcard corrupted" but the data slot roms are working fine ie. they're booting and fully functional, but still "sdcard corrupted" on these roms also. It seems the kernel is VERY unfriendly on this device...will try to change the primary rom or to patch it first and then reinstall. Currently the primary was installed unpatched and now just trying to update the ramdisk which is giving me headache.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Not to worry I get used to this. For some strange reason, the ramdisk-update.log is not in that path. It seems that the patcher is not able to write in that directory. multiboot.log is succesfully on /sdcard/multiboot.log
[Galaxy S 4 i9505 Original Android Development] bvlgvr:
Manual installation of Boot UI ... "Not supported on this device"

Thanks.

I just tried to manually install Boot UI from DualBootPatcherAndroid-9.0.0.r14.g69ea40f-snapshot ... it's greyed out and it says "Not supported on this device". :(

The device is a GT-I9195 (serranoltexx)

Is there anything I can do?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] I tried the new 9.0.0.r50 build with the possible fsck fix on K3 Note and it didn't help to get rid of the message and can't access the extsd. Repatched the roms with the new patcher of course, also updated the ramdisk. The error is the same as on K6000 Pro I think. Interesting as the output of the command previously mentioned here was looking fine on K3 Note. GetLogs attached below.

I want to share my experience with this error. The first time I saw the "corrupted sdcard" false notification was when Android 6.0 roms rolled out back in time. I'm pretty sure I never saw this error on 5.1 or 5.1.1. There is something in MM that's causing that. Oh wait, I forgot...and these MTK devices causing a strange interference in the Android world, hate it or love it. :p There are MM that are working fine, but there are also a bunch of others which are having issues with the extsd on mtk devices. There is also a 3rd category of roms here, these are reading only one of the partitions of the extsd, mostly the ext4, the fat32 is "corrupted". AICP 11 is the opposite: readind the fat32, but corrupted for the ext4 and this is actually a working state of the rom as I'm able to mount the ext4 with Apps2SD app via script. Call me paranoid, but I think the MM roms which don't have extsd problem are zipaligned. :D

[MENTION=4277844]chenxiaolong[/MENTION] I think the only way for us to have a chance to determine what's causing this unusual behavior and to fix it is to send you 2 roms: the one is working and the other is showing "sdcard corrupted". It's not init.d, addon.d or other script, it's something in the fstab or vold files. You can check, compare and see.

I don't know what you did, but yes, you can manually edit the devices.json file in /data/data and then the option will be selectable, but it's not recommended. Got it to work on K6000 Pro as I just wanted to try it out, but I like the "old school" switching method. :p
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The big file is my fault. It always appends to the end of it instead of overwriting :)

This one is weird. Looking at the log, Android actually started booting, but at around 39 seconds, the log just stopped. I am confused...
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you grab MultiBoot.log after flashing CM14 with the latest snapshot? In the logs you sent me, it looks like the last thing you flashed was "open_gapps-arm-7.0-pico-20161020_data-slot-2.zip". Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
So far so good.

That is exactly what we want. We want to override fsck to do nothing so it can't fail. Weird that is works here, but not when the system (vold service) calls it.

Yep this is done in builds without the fsck "fix".

It's extremely likely that it's an SELinux policy issue. I just need to work out why.

Thanks! Looks like the fsck fix did nothing :( Can you grab a dmesg log and logcat when the SD card works properly (non-ramdisk updated)?

Btw, the "dmesg" command is just as good, if not better, than the kernel.log file.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Whoops, sorry. I'll merge the changes to support your device so you can use the normal releases.

EDIT: 9.0.0.r56.ga5fde5c
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Here is the MultiBoot.log taken after flashing CM14 failed. I hope I captured it correctly this time. Fyi, the snapshot of my storage.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, same error still :(

[ 10.603274] <5>.(5)[1:init]mblog: Failed to find block device corresponding to /devices/mtk-msdc.0/11240000.msdc1*
...
[ 10.616143] <3>.(3)[122:kworker/u16:2]mmc1: new ultra high speed SDR50 SDXC card at address 0001

External SD is detected 0.012869 seconds after the patcher looks for it. I'll see if I can fix this tonight. At least it'll be easier to fix than the fsck issue :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You'll need to ask the TWRP maintainer for the TWRP source code for your device. Boot UI uses the same graphics code as TWRP and thus, I need the source code in order to add support for serranoltexx.

Thanks!
[Galaxy S 4 i9505 Original Android Development] Galvarey:
Add UMI SUPER Suport

Can You add the UMI SUPER suport i see the elephone p9000 in the list and it is basicly the same
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Not recommended :p But at least this is a safe hack and won't cause any hard or soft bricks.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is the problem:

[E] Failed to write /dev/block/platform/msm_sdcc.1/by-name/boot: No space left on device

Unfortunately, that means once the multiboot components are added to the kernel, it's too large to fit on the boot partition. You won't be able to dual boot this ROM.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Mate, flash it

https://snapshots.noobdev.io/misc/getlogs/GetLogs-20161019-2.zip

and attach this file (/sdcard/logs/[Date&Time].tar) :)

---------- Post added at 11:51 PM ---------- Previous post was at 11:26 PM ----------

@chenxiaolong, did you deleted saving kmsg.log to /cache in version r56? I can't found logs on /cache partition :/
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This exists in your test build only (as it is a Note 3-specific hack). I've made a new test build based on 9.0.0.r56.ga5fde5c in case you want to try out the latest changes: https://jenkins.noobdev.io/job/Dual...tcher-builder && fast,target=android-all-gcc/
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Thanks, that explains well seeing that the boot image is pretty big.

Your work is revolutionary! (I was about to say that word yesterday but somehow it escaped my mind :p)
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
I just test the new build upgrading ramdisk of primary rom, and the same error already reported with RR. What intrigues me most is the external card is mounted on /raw/extsd / in a boot and not on next, continuing this cycle on how many reboots I do. Do you have any guesses to explain this?

And the option of skipping the sdcard0 is so that it is not confused with the external card? Because as you can see it is the internal memory on the Android booted, but the fstab is very confusing

ls -la /storage/
drwxr-xr-x 5 root root 140 Oct 24 21:56 .
drwxr-xr-x 22 root root 0 Oct 24 21:55 ..
drwxrwx--x 54 root sdcard_r 16384 Dec 31 1969 628B-5430
drwx--x--x 6 root sdcard_r 4096 Oct 13 22:23 emulated
lrwxrwxrwx 1 root root 7 Oct 24 21:55 sdcard0 -> /sdcard
lrwxrwxrwx 1 root root 18 Oct 24 21:56 sdcard1 -> /storage/628B-5430
drwxr-xr-x 2 root root 60 Oct 24 21:55 self

And as a suggestion to decrease our headache, you could not add the path of extsd as well as boot partition, recovery, system, cache and data on devices configs? Not needed to be mandatory on all devices, but only on devices with this value (those with this error) it will be used in place of the automatic identifier
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
[MENTION=4277844]chenxiaolong[/MENTION],

here is my last logs (a few minutes ago). Black screen, I waited 3 minutes.

BootUI didn't show up too. Only black screen after Note3 logo.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] I know you are busy fixing bugs and issues, and that it isn't the best time to ask for feature requests, but if this is easy, it will be of great use. So, here's the request: Is there you can embed the functions of DualBootUtilities.zip, like wiping the partitions of a ROM, into the BootUI? Then we won't have to go to recovery and flash the partly working aroma installer thing. Is this possible?

Thanks for your work! :)
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
There aren't impossible things for chenxiaolong :D
[Galaxy S 4 i9505 Original Android Development] Galvarey:
Theres my UMI SUPER log i'm running cm 13 rom
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=6450691]KaMyKaSii[/MENTION] [MENTION=5048731]911-Future_Maker[/MENTION]

Please give the test build here a try: https://github.com/chenxiaolong/DualBootPatcher/pull/266 This build changes a couple things:

For non-extsd-slot ROMs, mbtool will no longer mount (in /raw/extsd) or touch the external SD in any way. The fsck binaries will not be messed with either. This should prevent the corrupted SD card notification for non-extsd-slot ROMs.

For extsd-slot ROMs, mbtool will now wait until the SD card is detected. When booted into an extsd-slot, the corrupted SD card notification will probably still appear.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Can you believe? It's WORKING now man! I'm now happy as a little kid lol. :fingers-crossed:. Unbelievable! Installed a freshly patched with the r60 build rom to data-slot on K3 Note and voila, no more "sdcard corrupted" notification. After that installed that r60 build on K6000 Pro updated the ramdisk and bam, no more "corrupted sdcard" either! Beautiful! <3 You're awesome bro! So basically the issue on mtk is the kernel has some very relaxed values for mounting the extsd and the mbtool just don't wait for the kernel to mount the card. So far:

The r60 build fixed:

1)Updating the ramdisk on Android 6.0 stock (K6000 Pro)

2)Sdcard Corrupted false notification on Android 6.0 roms

Next I'll try the most desired action: to install a 6.0 rom to extsd slot and to see if the corrupted error is gone. Cheers :highfive:
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Does it mean that now r60 should work with TW 6.0.1 ?
[Galaxy S 4 i9505 Original Android Development] yfriday14:
What does this MR_bump.zip do?

Into which folder is dumping the kernel & ramdisk?

Who wrote it?
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Dear [MENTION=4277844]chenxiaolong[/MENTION]

Could you make test release based on latest r60 with Boot UI support for the Samsung S5 SM-G900F klte ?

• TWRP XDA Thread: [RECOVERY][klte] TWRP 3.0.2-0 touch recovery [2016-04-05]

• TWRP device tree: Github

• TWRP for klte: Download
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I don't know, I can't test TouchWiz as I don't have Samsung. The r60 build fixed the extsd wrongly marked as corrupted in 6.0 roms, before and after updating the ramdisk.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
As I replyed to [MENTION=4659955]nicesoni_ash[/MENTION] and explained to [MENTION=5048731]911-Future_Maker[/MENTION]:

MR_bump.zip is just toBump the kernel. Is just

signing

it. Actually is not Dumping anything.

The script comes from [MENTION=2174433]Skin1980[/MENTION] from his oversharpening mod.

Again this is

only

for LG G3 users, so if you have a Samsung phone or a mtk based phone or [Insert phone here] this is not for you. It's seems in the comments that nobody is understanding this excepting [MENTION=4277844]chenxiaolong[/MENTION].

Hopefully this is clear now :good:
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
I just updated ramdisk of primary rom, and as reported by 911-Future_Maker, is working perfectly. Now I will install an rom on data slot and finally be able to enjoy. Thank you very much :D
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Try to install to extsd slot also if you wish, that's what I'm going to do when I go home later today. I hope it will work.
[Galaxy S 4 i9505 Original Android Development] agueijo:
Hello [MENTION=4277844]chenxiaolong[/MENTION]

I have a LG G4 h815 (int) from version 9 I can update ramdisk and I'm using App Sharing! This is great!

But I think I found a bug, when switch from primary rom (lg based) to CM rom, at boot time my cyanogen rom truncate the file /raw/data/system/packages.xml

And In my appsync.log I found: [E] Failed to parse XML file: /raw/data/system/packages.xml: Start-end tags mismatch

If I keep using my CM rom App Sharing works perfect, but when I switch to Primary ROM I get the same error and my apps sharing don't mount your data share.

The packages.xml is re-created correctly after boot and if re-reboot again my primary rom my data share mount correctly.

I attach my log after booting CM rom and my packages.xml is truncated.

I have seen that I have one file backup and and if I overwrite packages-backup.xml on packages.xml before to switch primary everything works well.

I think in some cases when I wipe Dalvik-cache and cm boot takes longer my packages.xml was not truncated ...

Sorry for my English!

Regards!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Glad to hear it's working for you! The changes have been merged and are available in the latest snapshot (9.0.0.r60.g7294c90).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Nope, that's not quite done yet.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure! A new test build is available here: https://github.com/chenxiaolong/DualBootPatcher/pull/104
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Awesome! Glad it's working now! The changes have been merged and are available in the latest snapshot.