yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
People who say this usually have very good English! :)

That's a very strange issue. This might not be something that I can fix though. The packages.xml file is regenerated after the "installd" service starts and the Android framework communicates with it. However, "appsync" (the app sharing service) has to run before installd or else it won't be able to mount the data directories. It needs the packages.xml file before the system can regenerate it. I don't see a clean way to work around that.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You won't like it, but I will probably not implement this :( The OS environment during the Boot UI stage is extremely minimal and doesn't contain all the tools necessary for the more advanced functions. Notably, flashing, backup, and restore will never work because SELinux hasn't been loaded yet at this point.

(Also, as cool as it is, developing and debugging the Boot UI is a major pain in the butt. I honestly prefer dealing with MTK bugs than working on this.)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Can you give the test build here a try? https://github.com/chenxiaolong/DualBootPatcher/pull/267
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
No problem. I was just wondering. Yes, fixing bugs should be given the top priority.

And I have an issue now! I wiped my extsd-slot ROM from the app and now 2.5 GB used for the system.img is gone. Like last times. But now, I can't find the FOUND.000 folder! Is there any other way I can recover that space without formatting. I tried looking in LOST.DIR and lost+found, but no luck

Thanks

I don't know what changed it, maybe it was repairing error wizard in Windows. Anyways, it's gone!

Is this a bug or does this have something to do with Android?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Does it do the same thing if Boot UI is not installed? I know you have the Note 3, but the reason I didn't enable it for the Note 4 is because it sometimes crashes the GPU hardware with certain kernels. Maybe it's doing something similar on the Note 3 and thus, causing the black screen?
[Galaxy S 4 i9505 Original Android Development] csmarino90:
Hi [MENTION=4277844]chenxiaolong[/MENTION], first congratulations for your awesome work!! Second, could you add support for Huawei P9? What do you need? It would be very good that I can test new roms with your application. Thanks

EDIT: I have attached the logs. Thanks [MENTION=6275385]MisiekDP[/MENTION] :D

Enviado desde mi EVA-L09 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Flash it

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

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

EDIT: Ahh, yea. Sorry bro, late hour :D
[Galaxy S 4 i9505 Original Android Development] Galvarey:
It Works, now i have to try it complete,but that works :D

Sorry for the bad english
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I want to say "WTF", but at the same time, the weird stuff MTK does doesn't really surprise me anymore :)

It's trying to mount "/dev/block/mmcblk1", which is the SD card itself and not a partition. That could easily be caused by the latest changes.

Okay, now I've seen it all. This is probably the dumbest MTK thing I've seen yet. Like above, it's also trying to mount mmcblk1 (the card itself, not a partition), but the exFAT driver reports a success code (!!). So it successfully mounts something invalid and then complains about the "out of range" errors.

The test build here disables /system/bin/fsck_msdos_mtk and (hopefully) fixes the mounting issue: https://github.com/chenxiaolong/DualBootPatcher/pull/268
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unless you have a Samsung device, most of the time, the open-source fuse-exfat driver (https://github.com/relan/exfat) is used. That driver is made by reverse engineering the exFAT filesystem and thus, doesn't always work perfectly. This is probably one of the cases where it doesn't behave too well.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Without BootUI stuck on Note3 logo and nothing further :/ I think, logs are similar :/ Do you have any idea?
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
[MENTION=4277844]chenxiaolong[/MENTION] i removed Quantum GO 3G (you can see in my pull request) of supported devices. The problem is the following. There is a device called Infinix Zero 2, and Quantum GO 3G is a national version of it. There is another called Symphony ZV Pro which is also the same to another country. The original is who gets the custom roms, and other devices to install them and normal functioning is necessary to format the device with the same Infinix Zero 2 partitioning system (by SP FlashTool, with scatter and stock rom, if interested). So I want to know the following: I can add Infinix Zero 2 and put codenames of other three devices on it? So all three devices will be recognized by DualBootPatcher as Infinix Zero 2?

And I can make some suggestions? An option to "complete boot anyway" if the checksum does not match with the saved. Can install boot.img and system.img without the need to be in a zip on in-app flashing. And an in-app updater
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] We have a partial success bro, it now mounts the 2nd ext4 partition of the extsd, no more out of range errors. Now we just have to figure out why it's not trying to mount the 1st fat32 partition. Tried the new r63 test build on K3 Note, but still 5 vibrations at boot. Looking at the log it's not mounting the first partition of the card (mmcblk1p1) which is fat32 while the second ext4 partition (mmcblk1p2) is mounted.

<11>[ 1.156303]<0> (0)[1:init]mblog: Successfully mounted /dev/block/mmcblk1p2 (ext4) at /raw/extsd

It's even not attempting to mount the mmcblk1p1.

Also after reupdating the ramdisk from with the r63 build, the extsd slot roms are not booting anymore, reversing to the old boot.imgs temporary fixed that. Updating the ramdisk of the primary (AICP 11) went successfully and the rom booted. Seems that the mmcblk1p1 partition not being mounted at boot is also the reason the extsd slot roms are not booting anymore after reupdating the ramdisk.

EDIT: [MENTION=4277844]chenxiaolong[/MENTION] Added log for Oikitel K6000 Pro. Successfully booted a rom from the extsd slot on K6000 Pro with the r63 build, the card is configurated the same way as the one in K3 Note, so I don't know why it's not working there. Unfortunately sdcard corrupted on the extsd slot rom as you predicted.

Also in the latest build the patcher is not showing rom name and version for extsd slot roms. (see the shot)

The last issue is I can no more browse the system path of extsd roms in /raw/images/extsd-slot-xx/
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
Hi [MENTION=4277844]chenxiaolong[/MENTION], thanks for all that great work, I used this app in many devices, can you add support for Xiaomi Mi Max v32GB Hydrogen? Please, thanks ins advance.
[Galaxy S 4 i9505 Original Android Development] agueijo:
Sorry [MENTION=4277844]chenxiaolong[/MENTION]

I just realized that the problem is generated during the restart of my primary ROM and that has nothing to do with boot of CM or AppSync...

Usually when I reboot with app "Quick Reboot" (most violent) I do not usually have problems. But if I enter to Dual Boot Patch switch or not and after restart using ther reboot from menu or boton of my device my packages.xml menu is truncated...

I finish not tell if this has to do with Patch Dual Boot maybe this are working with packages.xml or if you only have to do with a bug in my primary rom....

Thank you

Agu
[Galaxy S 4 i9505 Original Android Development] robcore:
[MENTION=4277844]chenxiaolong[/MENTION]

FYI My kernel's dual patcher uci compatibility was fixed by changing the uci service to class late_start from class_main, and dropping the prefix "busybox" from my mount commands. Now to universalize this bad boy : ) thanks for your awesome attitude and cool project!
[Galaxy S 4 i9505 Original Android Development] schreda:
Same problem for me on my LG G4 running stock LG ROM as primary and cm13 as secondary (data-0)

Just that packages.xml doesn't get updated. Is there a way to update it manually?
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
It seems the network settings between systems are not independent. Changes made in on system will have impact to another system, sometimes renders the Settings to crash in the other system. Is this a known issue?

N910P PH4, Norma N7 V6, H-Vitamin Kernel
[Galaxy S 4 i9505 Original Android Development] Nagytoll:
Does the patcher supports android N builds? Just couse I couldn't flash any on OP3.

Also, the newest r60 snapshot works fine for me now except for one thing, it cannot fetch the background image when I click on the details of a selected rom
[Galaxy S 4 i9505 Original Android Development] agueijo:
If it is exactly the same as me, and packages.xml has been truncate

if my next boot is in Primary Rom LG based (Genisys with kernel simpleGX) the file packages.xml always regenerates ok if I were to restart again with app "Quick Reboot", this reboot usually never truncates the file.

If next boot is in CM Rom usually I find the correct file /raw/data/system/packages-backup.xml and overwrite the truncated file /raw/data/system/packages.xml reboot to primary all works ok. (boot on cm with the file truncated, only generates errors in appsync.log but mounts shared and all works well)

Regards,

Agu
[Galaxy S 4 i9505 Original Android Development] schreda:
CM always works well.

I tried to reboot the LG ROM (Genisys & Imperium Kernel) hot and cold, but the packages.xml never gets updated/regenerated

edit: wiping the cache partition helped, but this is not a real workaround. Takes too long if you switch more often
[Galaxy S 4 i9505 Original Android Development] buddhatrip:
CM14 flashed (patched with any version of dualboot patcher) in primary, data or any slot cannot access developer option. The screen turn black. Any solution?
[Galaxy S 4 i9505 Original Android Development] Odin Erbe:
I need a kernel for my GT- 19515 :( for Android 6.0.1 can help me one of you?

Gesendet von meinem GT-I9515 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] JohnSmith743:
Can you add support for the Thor S7 style Rom? Because I get this error message when I try to set the primary rom.
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

Still trying to use DBP with my Moto X Pure (clark). I'm currently trying to dual boot some Nougat ROMS (CM14, CM14.1, Tesla 7.0,etc.) and I keep coming up with the same error. They normally process all the way through except they never recognize my SIM.

The error that comes up is: mount: failed to mount /dev/block/bootdevice/by-name/modem at /firmware: No such file or directory.

I would send you a MB log but for some reason, when I'm on my MM stock (in Primary), I can never access, copy, or delete the log. It always states that I don't have permission. This was something I asked about before. Anyway, I'm guessing that the error is coming up because DBP doesn't have a pointer for /firmware like it does for /system, /cache, and /data. Do you have any suggestions since from what I can see, all of the MXP Nougat ROMS coming out reference /firmware as a target location for dumping modem files?

Thanks

Edit: Adding block of code in almost all Nougat ROMs for MXP where the issue occurs. As I mentioned earlier, the ROM still installs, but with no baseband, modem, etc.

mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");

mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/modem", "/firmware", "");

ui_print("Extracting modem firmware");

run_program("/sbin/sh", "/tmp/install/bin/extract_firmware.sh");

ui_print("Firmware extracted");

unmount("/firmware");
[Galaxy S 4 i9505 Original Android Development] Technical:
[MENTION=4277844]chenxiaolong[/MENTION],

I'm not being able to use DualBoot anymore in Asus Zenfone 2 ZE551ML since I've upgraded to MM boatloader of it.

I can do all things, but when I upgrade RAMdisk I reboot all the time in recovery (TWRP).

Only if I flash boot.img again I can reboot phone and use it.

Logs attached.
[Galaxy S 4 i9505 Original Android Development] kolmanb:
to build prop change from: ro.product.device=noblete

in : ro.product.device= jflte

then restart and try again.
[Galaxy S 4 i9505 Original Android Development] JohnSmith743:
OK. I will check it out. Thanks for the reply.

---------- Post added at 07:52 AM ---------- Previous post was at 07:14 AM ----------

Soooo um yeah...... is it possible to remove the secondary rom if something goes wrong?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yes it is. If it doesn't boot go to recovery and just switch to the primary rom. Then delete the secondary rom if you wish.
[Galaxy S 4 i9505 Original Android Development] Guroff1974:
Please add support Galaxy Note 7. I have phone Galaxy S6 Edge with an insertion Port Note 7. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You need to add:

ro.patcher.device=zerolte

to your build.prop so that the patcher knows that your real device is an S6 Edge.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you try the new test build at https://github.com/chenxiaolong/DualBootPatcher/pull/268? It should fix this issue by always mounting the first partition on the SD card. Previously, it was choosing a random partition based on how the list of partitions was stored in memory (which may not be sequential, oops).

There may not be an easy way for me to fix this since mbtool no longer mounts the external SD at boot. It won't be able to read the build.prop file in the system.img. I haven't thought of a good way to fix this yet.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Wow, I have no idea how that would fix the issue, but I'm glad that it does!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Right, it can't access /dev/block/bootdevice/by-name/modem since it's not explicitly allowed in the data file for your device (and also /firmware doesn't exist like you said). Can you try with this test build and let me know if it fixes the issue? https://github.com/chenxiaolong/DualBootPatcher/pull/272
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you flash the GetLogs zip from https://snapshots.noobdev.io and attach the file it creates in /sdcard/logs/? Most likely, the paths to the partitions changed with the bootloader update.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I'm glad to see you back mate! Will try the new test build and will report. No worries about the not accessible system images of the extsd roms, if all is working fine I won't need to mess with whatever is in the /system. I just want to clarify is the sdcard corrupted problem for extsd slot roms unfixable? Just want to know if I would need to reinstall my extsd roms to data slot.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Repost! Sorry.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] The extsd-slot ROM I just flashed failed. I'm attaching the log. Can you look into it and see if it is a bug with the ROM or Dualboot Patcher?
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

Gave it a try, but it still fails. Now the error message reads:

mount: failed to mount /dev/block/bootdevice/by-name/modem at /firmware: Device or resource busy
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Hello Chen,

is it possible to repair booting problem with this temasek's kernel (black screen)? :)

Greetings!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The CM14 developer settings crash is now fixed in 9.0.0.r61.g05501e3. A ramdisk update or reflash is

required

.

For those interested in what happened:

The issue was caused by NULL-pointer dereferencing bug in the vold service. When tapping the Developer Options item, the Settings app sends the "isConvertibleToFBE" command to vold to query some FBE (file-based encryption) information. Vold determines this information by looking at the /data entry in the /fstab.* file and checks if it contains the "forcefdeorfbe" flag. However, in a multiboot setup, the fstab file will not contain the /data entry and since vold is missing a NULL-check [1], the vold service crashes. The Settings app never gets a reply back from vold so it crashes too. This is fixed by [2], which adds a dummy /data entry to satisfy vold.

[1] https://github.com/CyanogenMod/andr...d9c4d526a359ef69f7f296c117170/cryptfs.c#L4225

[2] https://github.com/chenxiaolong/DualBootPatcher/commit/05501e32748587db05d53e774355b22bd06b4888
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It looks like the ROM tries to modifying things in /cache without mounting it first. If you add a line in META-INF/com/google/android/updater-script to mount /cache (around where it mounts /data), I think you should be good.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Are you using in-app flashing? The installer might not be able to mount the modem partition if Android already mounted it.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I didn't notice this before, but it looks like the exfat driver crashes around 3 seconds into the boot and nothing happens after that. For a quick test, could you try booting without the SD card inserted?

EDIT: And if it still fails, please grab a new kmsg.log. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure, but for the partitions, please don't include the /dev/block/mmcblk* paths in case the user forgets to format the device with the Infinix Zero 2 partitioning scheme. That way, we won't cause hard bricks. The normal /dev/block/platform/... paths are always correct.

I will be removing the checksums feature for 10.0.0 since it's more annoying than useful.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've already tried everything I can think of for resolving the SD card corruption notification, so unfortunately, I think your best bet is to use data-slots for now.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure! Please give the test build here a try: https://github.com/chenxiaolong/DualBootPatcher/pull/273
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Chen,

it IS WORKING without SD Card. :laugh: :laugh:

My card is formatted with Exfat but what can I do? :)

Thank you very much! :)

Btw. can you add HTC M7 and M8 devices if I upload logs? :)
[Galaxy S 4 i9505 Original Android Development] ewangw:
It failed using in-app flashing and in TWRP 3.0.2
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Can you give this test build a try? https://github.com/chenxiaolong/DualBootPatcher/pull/274
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Fantastic! If that's the case, you should be able to use the latest snapshot since it no longer mounts the SD card unless you're booting an extsd-slot. :)
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
So I can't boot ROMs via SD Card? This ROM with Temasek's kernel won't boot via SD Card?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Correct. At least with this kernel, you won't be able to boot from an SD card.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Ouh, why you want to delete extsd booting? :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm not sure I understand what you mean. I'm not removing support for anything. I'm just saying that the kernel you're using won't work for extsd-slots because the kernel crashes when the SD card is mounted by the patcher.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Aah, I thought that you wanted to delete external storage booting :laugh:

Can I do anything to repair booting this temasek's kernel from extsd card?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Hi chen, I used r63 to repatch and flash cm14 on N9005. This time the boot image is small enough and patching and flashing were successful, but I got 5 vibrations and enter recovery. Please see logs attached.

Edit: I'm not sure if this is related with the fix in r61 that you described above.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you attach the boot.img for the ROM you're trying to flash (or link to the download and I'll extract it myself)? Thanks!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
What ROM do you use on N9005 (cm14)?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
https://mega.nz/#!Hh8RQabZ

It's CM14 by trader418.

http://xdaforums.com/galaxy-note-3/...14-trader418-unofficial-t3459973/post68645440
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
So you need to know that this trader418 cm14 uses temasek's kernel and this kernel not working with DualBoot Patcher :( I have on cm13 with temasek's kernel and I have problems with patched kernel (errors with extsd card) :(
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Well, I tested before and it was a successful boot to system with DualBootPatcherAndroid-8.0.0.r2468.gad0b0d3-snapshot. The only problem is that I couldn't enter developer options.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
And now, is it working for you on version 9.0.0? On older version DBL temasek's kernel worked me too but now not.

Can you upload this old version of DBP for me?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Prior to r61, I always get stuck at boot animation, with r63 it was 5 vibrations and then enter recovery...

I'm happily running CM14 as my primary (unpatched) and a TW rom at data slot-1. So my purpose here is for testing only as I have encountered developer options thingy.. but please let me know if it's not useful/related at all :p
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Aah, you use cm14 as unpatched primary ROM :) But if you patch, ROM will not boot? Could you try to boot temasek cm13 ROM from sdcard? I get black screen on this ROM :/
[Galaxy S 4 i9505 Original Android Development] kopitalk:
I'm using christer12's cm14 right now, which has 'too big' a boot image to be patched.. so I leave it as unpatched primary. But for trader418's build, as I said I had a successful boot to system as patched slot-1 so I thought of testing that on.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I tested too traders418's cm14 but I have black screen after Note 3 logo. Temasek kernel worked with older versions of DBP.
[Galaxy S 4 i9505 Original Android Development] wingg:
Hi all.

Just to share: I've managed to make dual boot with g900f (s5) Nemesis Rom v 3.1(N7 port) and using data slot CM 14.1 ( 7.1) build 29.10.2016 +open gapps 30.10.2016_7.1 (micro) using Dual boot patcher snapshot 61.Everything works ok,developer options and CM root too. (Before I've tried secondary,extsd, multislot 1, but no success. Off course I've added in Nemesis build prop ro.patcher.device=klte, to switch between roms easily with Dualbootpatcher. )

Thanks [MENTION=4277844]chenxiaolong[/MENTION] for a great job.

-->>
[Galaxy S 4 i9505 Original Android Development] Technical:
I did as you've requested and attached the log files.

If it is necessary to run all the processes again just to generate other (or new) logs, please, just let me know.
[Galaxy S 4 i9505 Original Android Development] agueijo:
Hello [MENTION=4277844]chenxiaolong[/MENTION]

I cant never boot any CM 14.1 build (early) for my lg h815(int) for example, the last, this: https://www.androidfilehost.com/?fid=529152257862675135 but I could always boot and use the build cm 13 or 14.0.

When boot the device vibrate and then boot in recovery, I attach the logs from recovery in this moment...

Maybe this is util and you can fix them or say me if this an problem with the build cm 14.1

Thank you, Agu