yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] todivefor:
Attached is the logcat and the 3 files you requested.

EDIT: I keep seeing this in the logcat. Last lines looks bad:

01-01 00:00:57.790 D/SubscriptionManager( 4487): [getPhoneId]- fail
01-01 00:00:57.790 D/TelephonyManager( 4487): INVALID_PHONE_INDEX ==> DEFAULT_PHONE_INDEX
01-01 00:00:57.790 D/TelephonyManager( 4487): getTelephonyProperty: return propVal='null' phoneId=0 property='gsm.operator.iso-country' defaultVal='' prop=
01-01 00:00:57.790 D/SubscriptionController( 5423): [getSubId]- mSlotIdToSubIdMap.size == 0, return DummySubIds slotIdx=0
01-01 00:00:57.790 D/SubscriptionController( 5423): getDummySubIds: slotIdx=0 return 1 DummySubIds with each subId=2147483643
01-01 00:00:57.790 D/SubscriptionManager( 4487): [getPhoneId]- fail
01-01 00:00:57.790 D/TelephonyManager( 4487): INVALID_PHONE_INDEX ==> DEFAULT_PHONE_INDEX
01-01 00:00:57.790 D/TelephonyManager( 4487): getTelephonyProperty: return propVal='null' phoneId=0 property='gsm.operator.iso-country' defaultVal='' prop=
01-01 00:00:57.800 D/SubscriptionController( 5423): getPhoneId, received dummy subId 2147483643
01-01 00:00:57.810 D/CDMAPhone( 5423): Event EVENT_RADIO_OFF_OR_NOT_AVAILABLE Received
01-01 00:00:57.810 D/CdmaSST ( 5423): [CdmaLteSST] SubscriptionListener.onSubscriptionInfoChanged
01-01 00:00:57.810 D/SubscriptionController( 5423): [getSubId]- mSlotIdToSubIdMap.size == 0, return DummySubIds slotIdx=0
01-01 00:00:57.810 D/SubscriptionController( 5423): getDummySubIds: slotIdx=0 return 1 DummySubIds with each subId=2147483643
01-01 00:00:57.810 E/PhoneBase( 5423): Error! This function should never be executed, inactive CDMAPhone.

EDIT1: Some observations and another logcat. I just noticed that ro.build.type=eng does something different. Just before it fails I get a notification "Run dump state, press to create dump." I press, then I get "Get modem log success, please copy to sdcard at next menu, OK" There is a menu behind dialog box, but when I press ok, it just reboots to recovery. I caught the last logcat at the dialog and it looks different. Attached logcatNEW.zip. There is nothing captured on sdcard other than check_chameleon.txt which is empty.

Here are some further observations: If I boot after being on primary, date and time is correct. I get a message "no service", then "searching for service", and then "Sprint." Time goes to 12:00, then dump message. If I reboot, from recovery after failure, time comes up as 12:01 and about a minute later, the rest occurs.

Flashing unikernel and SU has no affect.
[Galaxy S 4 i9505 Original Android Development] sronweb:
@ chenxiaolong,

Hello' Chen, I'm just using a Snapdragon Note 4 and I tried to flash a secondary image based on CM13 (TW on primary)

After flash the rom I install manually the patcher and if I try to switch to primary I get an error of SHA512 mismatch for boot.img as I understood.

The problem is that after this message if I reboot I get boot loop.

Please, do you have any suggestion for this issue?

Thank you
[Galaxy S 4 i9505 Original Android Development] Steven1962:
Hi, is there a way to patch arter's kernel?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Lol dude..a six roms?? I only can flash up to 4 roms because I'm limited by the running out internal storage. How much free internal do you have right now?
[Galaxy S 4 i9505 Original Android Development] jroq8400:
:) same here the limit is the data partition. I try to use only web apps but still have to keep clearing apps cache regularly. Tinkering with new roms is my hobby so this app is great for that :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Are you using a build you compiled yourself? That comes from the LeakCanary library I use (https://github.com/square/leakcanary) and is indeed used for finding memory leaks in the app. It should not exist in builds from https://snapshot.noobdev.io/ unless it was included by accident.
[Galaxy S 4 i9505 Original Android Development] stiw47:
Aha, understand now. Thank you.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi [MENTION=4277844]chenxiaolong[/MENTION]. You know that if you "adopt" the extsd in Marshmallow it's going to be formatted as 128-bit AES encrypted EXT4 filesystem. This is my biggest concern of migrating from LP to MM. I think it will kill the dualboot possibility because the card is encrypted. Am I right? If yes is there any way to use extsd as internal on MM, that's not preventing us from dualbooting?
[Galaxy S 4 i9505 Original Android Development] haimann95:
CM13 not working with Dualbootpatcher

Hello,

I'm using the dualbootpatcher app on my klimtlte and I really love it.

All roms I ever patched worked, but cm13 does not. I can patch and install it without any problems, but it does not boot. It reboots to recovery and that's it. I know that the build I'm using is working, because I already tested it in normal installation.

I attached my logs and I hope someone can help me.

Thanks
[Galaxy S 4 i9505 Original Android Development] sronweb:
The error I got was "The SHA512 checksum for this ROM's boot.img or other *.img files in /sdcard/Multiboot/primary/ are missing. This is likely caused by upgrading from older version of this app. Proceed with switching the ROM?" and if I switch it I get bootloop of primary rom.

PS: I have patched and reflashed the primary rom using latest patcher version and now switching between roms it's working fine.
[Galaxy S 4 i9505 Original Android Development] nutpants:
Tried updating mbtool on my s4 (with the wamanlite rom) with 2255. Still have a hang for more than 15 minutes.

(I flashed boot img back on after 20mins)

If mbtpool is just for app info sharing then it's not an issue as I don't app data share between roms...

Got a log however in case it's an easy fix from here.

Thank you for all your hard work.

You have brought life and excitement to all my old devices
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for all the testing! I just pushed out 8.0.0.r2259.g0f037b0, which should make the same Multi-CSC changes that happen when you flash the tar.md5 via Odin. I think the "ro.build.type=eng" issues probably came from trying to forcefully enable engineering mode for a non-engineering build of the ROM.

Anyway, I'm fingers cross my fingers... really hoping this works :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! It actually looks like you ran out of space on /cache. You might want to install to a different slot, like data-slot (installs to /data) or extsd-slot (installs to external SD).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! The awesome community is what keeps me here :)

This is indeed a very odd issue. If I had to guess, I'd say it's probably a kernel bug. If you're willing to debug this further, I'd suggest opening a separate terminal window and running:

adb shell su
cat /proc/kmsg

and then try the same "ls" command again. I don't know if it will be able to catch the error fast enough, but it might.

Another option is immediately booting to recovery when it instant reboots (without shutting down or rebooting in between). Then from recovery, grab the /proc/last_kmsg file. I'm definitely interested in figuring out why this happens since I've never seen anything like it before.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Did you happen to boot into another ROM before capturing the logs? I'm looking at /sdcard/MultiBoot/appsync.log and it seems like it's for another ROM. Could you try deleting that log, booting to wanamlite (just wait around ~2 minutes), reboot straight to recovery, and grabbing the logs again? Thanks!

---

mbtool actually handles much more than app sharing. It handles 100% of all multiboot operations that happen behind the scenes (hence, "multiboot tool"). For example, mbtool is responsible for:

Flashing ROMs from recovery

In app flashing

Mounting partitions before Android boots

Behind the scenes work for switching ROMs and setting the kernel

Getting ROM information (ROM version, thumbnail, wallpaper, ROM size, etc.) for the app

Wiping ROMs

Prevent primary ROM from replacing SELinux labels of other ROMs' files

App data sharing

Most people associate it with the app data sharing feature because it requires a ramdisk update, which integrates mbtool into the current ROM. This allows the app sharing code to run while Android is booting.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Great! Is there any possibility you might have forgotten to set the kernel from the primary ROM earlier? That error usually happens if the boot.img files in /sdcard/MultiBoot/primary/ are out of date.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If you choose you "adopt" the external SD as internal storage, then the extst-slots will no longer work because of the encryption. As far as I know, in this mode, the original /data partition is untouched so you can still install ROMs there. I would recommend against using this new mode though. Every ROM will use it's own encryption key, so only one ROM (the one with the correct key) will be able to access the SD card.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The kernel is using some ugly hacks to support F2FS partitions, causing it to try to mount the partitions a second time after the multiboot code already mounted them. I'll have to add some hacks to work around this.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This issue is now fixed in the minizip library: https://github.com/nmoinvaz/minizip/issues/44

The fix has been included in 8.0.0.r2260.g09ac4a5 :)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Well okay then I'll avoid using the extsd as internal on MM.
[Galaxy S 4 i9505 Original Android Development] todivefor:
No! Thank you. I'll keep doing what ever you need. I have learned a lot from testing with you over the last 1-2 years.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Patched with 2260.

I am not sure what you did in 2259 (Multi-CSC changes?). Is this for debugging or was this a shot at a fix? It did not fix the problem same result. I got a logcat (attached). I haven't looked at it. Some new information. When I flashed, I got an error (don't remember what exactly). I captured logs, but forgot about the error when it booted. I might have to recreate. Anyway it booted, I got logcat, and it rebooted to recovery as before. When it got to TWRP, there was a swipe to run, and I did without thinking. Unfortunately, it was on factory reset :crying: I am restoring my system. The factory reset did not format my sdcard for whatever reason, so I have attached the logs.

EDIT: I see a failed to flash CSC in multiboot.log? See several problems:

[D] Running command: [ mount, /cache ]
mount: mounting /dev/block/sda19 on /cache failed: Device or resource busy
[D] Running command: [ mount, /data ]
mount: mounting /dev/block/sda21 on /data failed: Device or resource busy
[D] Running command: [ mount, -o, ro, /efs ]
mount: can't find /efs in /etc/fstab

Extracting system/csc/XAS/system/etc/csc_user_apks_list.tSales code is empty
Failed to apply Multi-CSC
xt

eFaild to flash CSC
[UI] Failed to flash CSC
[D] Child exited: 1
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION], I ended up doing that after I saw the spacing error in the logs. The major problem I have right now is that while I can now add new ROMS, my SD card is always coming up as being corrupt (which I know it isn't). All is good in the primary slot, just not in the others. App data sharing is also a challenge.
[Galaxy S 4 i9505 Original Android Development] vykintazo:
Is it possible to get the bigger size of img file? In my dual ROM I haven't got enough space.
[Galaxy S 4 i9505 Original Android Development] nutpants:
No, that should have been the log right after failing to boot,I went strait to recovery and got the logs then flashed boot.img to get back up and running.

But strangely, once in a while I get the error "kernal has changed set new kernal?" every now and then from your app.

Ill get new logs for you and post them tomorrow.

Thank you again for your efforts for the Android and open source community.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oh man, that was a close one. Good thing we have backups, right? :)

That build was indeed an attempt at a fix (and I believe it should work if the installation didn't fail). The "Sales code is empty" error is definitely an issue. It is caused by this:

[D] Running command: [ mount, -o, ro, /efs ]
mount: can't find /efs in /etc/fstab

The installer needs to mount /efs so it can to read /efs/imei/mps_code.dat to determine the sales code. The sales code is used to figure out which files it needs to copy in /system/csc. However, the fstab file in the Galaxy S6's TWRP has a typo: "emmc" should be "ext4", which prevents /efs from being mounted properly. I've added a workaround for this in 8.0.0.r2265.ga8a1e6f. This new version will also fail at the beginning if a similar error occurs so you don't have to wait for the long flashing operation.
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], you are the man! I am running stock on data-slot. It was a little scary at first. I flashed and got the same result. Looked at the multiboot.log and it looked the same. I hadn't deleted the prior patched zip and the new was named .zip(1). So I had just flashed the prior. I'll play with it some more tomorrow. Can I install DB app on stock and use it to switch?

Let me know if there is anything you want me to test, now or anytime. This has been fun. :D

Thank you very much!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Awesome!! Thanks again for testing! There's no way I would have fixed it without your help :D

You should be able install the app and switch ROMs without rooting. You might have trouble updating to the new versions of the app without rooting though, since it currently requires root to stop the existing mbtool process and start the new one, but eventually this requirement will go away.

Unfortunately, there's no way for me to change the ".zip(1)" behavior. The app can recommend a certain filename to the Android framework, but in the end, the framework is free to choose a different name.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Is the typo in twrp fstab a twrp problem that I need to report to them?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, that would probably be a good idea. In the /etc/recovery.fstab file, the bolded field should be changed to "ext4" or else the partition can't be mounted with "mount /efs":

/efs [b]emmc[/b] /dev/block/platform/15570000.ufs/by-name/EFS flags=display="EFS";backup=1
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], Playing with my custom rom primary and stock rom data-slot, I no longer is /RAW in free space from app or root explorer. What is that all about?

EDIT: One other question. When we were doing our testing, I was trying to flash another ROM to make sure it would work. It flashed, but ended up with no DATA. It is an aroma flash. I thought aroma was supported?
[Galaxy S 4 i9505 Original Android Development] Mehul.S:
I've downloaded the latest version of the app..

I wanted to patch some zip files.. But I'm not able to select the zip file.. Once I click on zip file.. It opens and shows what's into it.. And I'm only able to select the img files.. Can someone help with this??
[Galaxy S 4 i9505 Original Android Development] empat:
Hi, chenxiaolong!

Sorry to bother you again!

I have a ported Note 5 rom (Sixperience) on my note 4, and tried to follow your instructions. After that, I have been able to set the kernel correctly, but the ramdisk update still fails. Is there some specific place to paste the line on build.prop?

I will try to attach the log.

Thank you very much!

Regards!
[Galaxy S 4 i9505 Original Android Development] mephisto20:
Is it possible to restore a nandroid backup as secondary rom ? I have Seen this Option in multirom and l like it a lot.

Thanks
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Hello [MENTION=4277844]chenxiaolong[/MENTION] , can you plz add this device to tree , lt03xxxx ,note 10.1 2014 lte....

https://www.dropbox.com/s/c3t24veoqdopzpo/20160221.181922.tar?dl=0

Thank you!
[Galaxy S 4 i9505 Original Android Development] nutpants:
Here are fresh logs

Installed latest patcher on both roms, updated mbtool in primary,rebooted as directed.hung at boot for 3 mins, used buttons to reboot into recovery.flashed get logs. Restored backup of boot.img from nandroid.

I just had a feeling I might have done the logs wrong, so I did them again.lol.
[Galaxy S 4 i9505 Original Android Development] NoFrown:
I have exactly the same problem. In an earlier version I was able to select third party apps to open the zip, like Es file Explorer. Is it possible to add this again?
[Galaxy S 4 i9505 Original Android Development] sam.crowther:
Hello [MENTION=4277844]chenxiaolong[/MENTION] , can you please add Tab S 10.5 LTE to device tree?

'chagalllte' is identical to chagallwifi, which is in the tree.

Have tested by changing my build prop, and is fine with LP roms, but i'm having some difficulty with MM roms

Thanks in advance :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the log! The ramdisk update log is saying that the last 4MB (at least) of the boot.img is getting chopped off, which is very weird. Could you send me your /sdcard/MultiBoot/boot.img file so I can take a closer look?
[Galaxy S 4 i9505 Original Android Development] empat:
Thank you very much for your attention! I will attach the file!

Regards!
[Galaxy S 4 i9505 Original Android Development] danon.brown:
[MENTION=4277844]chenxiaolong[/MENTION] any plans of making this work with the s7/edge? I see you constantly adding support for devices.
[Galaxy S 4 i9505 Original Android Development] xdadevelopersrocks:
Can I use this with the Nexus 5x bullhead?
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Thanks for the zip fix!!

Another idea:

What about of importing the wallpaper from the other rom to the current rom?

Sometimes I delete the pictures forgetting that are wallpapers... :'(
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=4277844]chenxiaolong[/MENTION]: Thanks for the great work! Your dual boot concept is really one of a kind!

I am currently experiencing difficulties in updating the ram disk on my Galaxy S5 G900F TouchWiz Lollipop. ROM is installed as primary and no other rom is present. The patcher says ramdisk update is successful but after reboot it fails to boot and goes directly to recovery. I then have to restore the original ketnel before patching to get the ROM booting again. I am attaching a couple of logs, hope you find the time to have a look. Thanks again for the nice work!

Ramdisk log:

https://www.dropbox.com/s/epo83b4q8h28tit/ramdisk-update.log?dl=0

Multiboot

https://www.dropbox.com/s/83ytile5y69as21/MultiBoot.log?dl=0
[Galaxy S 4 i9505 Original Android Development] todivefor:
Hope you make the workaround permanent. Response from TWRP maintainer for Galaxy S6 Sprint.
[Galaxy S 4 i9505 Original Android Development] physwizz:
Backup & restore

[MENTION=4277844]chenxiaolong[/MENTION]

Hi Chen

How are you going with the integration of backup & restore into the app?
[Galaxy S 4 i9505 Original Android Development] C52:
Thanks for the app. Unfortunately getting a can't connect to mbtool error when checking ROMs. I added the patcher line in build.prop (zeroflte for S6) with no luck
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
On that subject, I do not know if it is possible, but it would be great to be able to create the backup on external sdcard.

By the way, have you any ideas about large external SD's detection issue when booting on external SD ? If I can provide additional information, I will gladly do it.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
[MENTION=1160716]bilbonotry[/MENTION], In order to save your backed up roms to external sd follow the instruction given by [MENTION=4277844]chenxiaolong[/MENTION] in post #7920 Here
[Galaxy S 4 i9505 Original Android Development] NewsTimes:
Cellular Network signal is losted in sim1 when switch rom. Please fix that issue. Thank Devs

Sent from my Surface Pro 4 using ChromeOS!​
[Galaxy S 4 i9505 Original Android Development] C52:
Tried again on stock. Is it possible flash a kernel through TWRP for the second ROM? I attached the log of when I tried Hacker Kernel.

Thanks for all the work you've done on the app!
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Yes, you can, just make sure to patch kernel for the appropriate slot.
[Galaxy S 4 i9505 Original Android Development] george stamatos:
VRTOXIN it doesn't boot, http://xdaforums.com/showthread.php?t=3321267
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
I have it booting on my s4 on my extsd slot.
[Galaxy S 4 i9505 Original Android Development] C52:
When I tried that I got "Ramdisk image exceeds boot image size by 365568 bytes" unfortunately.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
[MENTION=4277844]chenxiaolong[/MENTION] posted about this type of situation a while back. He will have to explain and perhaps help you out with this issue.
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Ι ll give it a try again
[Galaxy S 4 i9505 Original Android Development] eyeless95:
Can you add Samsung Galaxy Grand Prime VE G531H to a list? It is codename is grandprimeve3g
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry I haven't had a chance do much yet. I've been really busy with school and have also worked on some core parts of the patcher.

8.0.0.r2298.g5c35a23 should finally fix the flashing of systemless SuperSU. I had to work around some things because SuperSU hardcoded /dev/block/loop0 into its installer. This hardcoded path almost guarantees that using in-app-flashing with SuperSU will fail. Therefore, I always recommend flashing SuperSU from recovery.

For developers, DualBootPatcher now completely CMake for compiling. No more ugly ndk-build hacks! This means ccache actually works properly now (cutting build times on my server from 25-40 minutes down to ~6 minutes). Those of you who are building from source will probably have to remove the build directory and rebuild.
[Galaxy S 4 i9505 Original Android Development] GabryP97:
Terrible Problem

:crying: Primary Rom: Imperium LL 5.0.1 Secondary Rom (dual): CyanogenMod 13 (Nightly) Both ROMs have Dual Boot Patcher app, in Secondary I Switch to Primary, reboot and Secondary ROM boots. Can anyone help me??
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
My guess would be that you never " Set Kernel" in Primary Rom before installing Secondary Rom.
[Galaxy S 4 i9505 Original Android Development] irfanbd94:
I want to turn on app sharing options......in secondary rom it is ok....but in primary rom it is sowing unable need to update mbtool/ramdisk....i am using latest version of patcher app and latest xxuhpa1 official firmware as primary.
[Galaxy S 4 i9505 Original Android Development] GabryP97:
That was my problem! Thank you ;)
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
[MENTION=4667339]irfanbd94[/MENTION], Patcher app goto "Roms" and click on "3-dot menu" of rom that needs mbtool update choose "Update ramdisk". that should update mbtool status.