yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Exynos or Snapdragon?

No one has sent me the logs for the Exynos variant yet. The Snapdragon variant will never be supported since it has a locked bootloader. (And I bought the darn thing :()
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you send me /sdcard/MultiBoot/daemon.log after you tried switching a couple times (but don't reboot)? It sounds like the kernel is probably not being flashed correctly when you try to switch ROMs.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
I solved it by deleting the kernels from data-slot-* and primary multiboot folders and replaced with the ones from my earlier backups, then the switching was okay again!

Thanks though!

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Galaxy s7 edge g935w8
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Just in case.

Galaxy s7 edge G935w8. Canadian variant. Should be exynos because I am currently rooted and have custom recovery.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Maybe this will help lol.

Galaxy s7 edge G935w8 Canadian variant. Exynos if I am not mistaken as I am rooted and have custom recovery. Let me know if you need anything else.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
From DualBoot patcher itself. Same variant of the phone.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Wow, if you guys have custom recovery already, could you flash the GetLogs zip from https://snapshots.noobdev.io/ and send me the file it creates in /sdcard/logs/?
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
I have 3 Roms on my T800, and I'd like to back them up. However, I can't get adb (on PC) to connect to the device while in Recovery (TWRP). It (adb) connects OK when the tablet is booted into a ROM. I've tried TWRP 3.0.0.0-1 and 2.8.7.

What's the trick?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Switch to Linux or Mac :) Just kidding! I don't use Windows myself, but if I remember correctly, there's a different driver you have to install for adb to recognize the device when it's booted to recovery. Maybe somebody here can help you with that.
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
I tried Linux Mint, it did the same thing. :D

Then I discovered in TWRP, Mount, Disable MTP........ then it worked!
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Here is what you asked for.

https://mega.nz/#!2dJEELpL!hKHEZfRlf93l_FDZa6jMiA5m0DS2lSkXBVTvA3Q5kSc
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Try heading to device manager under your PC, then look if the drivers are properly installed, or just click your device and update drivers, this will prompt the PC to install drivers for your tablet...this should work!

Select the second option when updating the drivers! (do not use online option, use browse my PC for driver software and then let me pick from a list of device drivers on my PC option, and click any of the compatible drivers and install...at this stage you should see a notification showing driver installation, this worked on my 2 tablets)

Edit:

Only noticed Later that you've got that solved!

Lol

---------------------------------------------------------------------

[New World Order (NWO)

Telegram it's better than Whatsapp In every way!]

---------------------------------------------------------------------
[Galaxy S 4 i9505 Original Android Development] Gerxp:
[MENTION=4277844]chenxiaolong[/MENTION]

I have a JDCTeam CM13 installed as dual Rom.

Some apps cannot run and stop with an error message telling that they need root access. For example "Root Checker" and "Busybox on Rails" from Playstore.

Please can you look into it?
[Galaxy S 4 i9505 Original Android Development] Help The Peace:
I'll try! I actually thought to have caught the log from the failed gaps flash. But never mind! I am new to this log grabbing [emoji28] Sooorry :D
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=4277844]chenxiaolong[/MENTION]: After fixing the /cache mess on my device I played with the multi boot magic?. I am currently experiencing two major problems.

1. Boot from Ext_sd does not work. I tried a couple of different ROMs, even one that is starting fine from data slot 1 but always get thrown to recovery after the initial reboot. What trace do you want me to provide me for this issu? GetLogs?

2. App Sharing Problems: I enabled individual app sharing on the primary, also data sharing for some apps, but I cannot see the apps in the data slot 1 rom and I find no option to enable APK share. All that happed was that I lost the data of the shared apps.

Any idea what is/am I doing wrong?
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Hi [MENTION=4277844]chenxiaolong[/MENTION]

I am getting status 1 as an error while flashing a marshmallow rom on marshmallow rom as secondary rom. Happens with any marshmallow rom.

Device is op2, trying to flash on data partition. Have Temasek marshmallow rom flashed.

Here is the log.

pastebin.com/t7iMWGAg
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! Added in 8.0.0.r2351.gf2192a5 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could somebody please try patching OpenGapps (any version and architecture) for the Qualcomm S7 Edge with 8.0.0.r2351.gf2192a5 and let me know if it completes successfully? For some reason my downloads keep getting interrupted halfway through. Thanks!
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Give me some time I'm doing some testing now
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
GetLogs dump would be perfect! I'll know for sure when I see the logs, but it might be this bug: https://github.com/chenxiaolong/DualBootPatcher/issues/36. The patcher currently doesn't wait for the SD card on boot so if the device takes a few seconds longer to detect the SD card, then it will fail to boot.

APK sharing used to exist, but I removed it because Marshmallow made quite a few changes that make the feature near impossible to implement reliably. If you want to share the data, you have to install the app in both ROMs, then enable the shared data option. When you do that, the app will use a fresh data folder in /data/multiboot/_appsharing instead of the normal /data/data. That's why it appears you have lost the app data. If you uncheck the shared option, you'll be able to use the old data again.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Looks like the path to the recovery partition changed in the Marshmallow ROMs. Could you send me the boot.img from any Marshmallow ROM for the OnePlus 2?
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
All good so far ☺️
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the log! From what I can see, it looks like the SD card was successfully mount at /storage/3703-C670. Are you unable to access that directory?

D/StorageNotification( 4955): Notifying about public volume: VolumeInfo{public:179,65}:
D/StorageNotification( 4955): type=PUBLIC diskId=disk:179,64 partGuid=null mountFlags=VISIBLE
D/StorageNotification( 4955): mountUserId=0 state=MOUNTED
D/StorageNotification( 4955): fsType=exfat fsUuid=3703-C670 fsLabel=
D/StorageNotification( 4955): path=/storage/3703-C670 internalPath=/mnt/media_rw/3703-C670
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Got an error when trying to install custom rom on data slot

https://drive.google.com/file/d/0B5S8tu4Ke9anRG50M2dQcG5ySlk/view?usp=docslist_api
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Awesome, thanks!

Note that The S7 devices are encrypted by default and encryption is not supported by the patcher right now. You'll need to use a ROM (or kernel) that disables encryption for dual booting to work. I plan to fix this if I can buy an Exynos S7 Edge that's not region locked.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oh crap. I totally forgot about that. In-app flashing and dual booting is going to be totally broken on TouchWiz 6.0 right now :( Samsung made some very dev unfriendly SELinux changes that severely impact the patcher's functionality. For now, the only way to dual boot is to use a kernel with SELinux set to permissive.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Encryption can be disabled using twrp.

You have to format data within the recovery.

Then all should be good. TWRP can then see internal data, external SD all that good stuff

---------- Post added at 03:33 AM ---------- Previous post was at 03:28 AM ----------

If I install the patched Rom for data slot then using twrp recovery to install I think I may be good. Correct me if i am wrong or give me your thoughts.

Also my other thing is dual boot patcher will work for switching between roms right? Just to be safe if I install this custom rom for data slot in twrp I just want to know dual boot patcher will function with the ability of switching between roms.

We are close to making this happen I think
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

Storage/3703-C670 shows up as an empty directory in all slots. In primary, I can see the contents of the external card if I go to /raw/extsd. In any other slot, it's a mixed bag as to whether I can see or even access the contents of /raw/extsd or not. In all cases /storage/3703-C670 is always empty. I just had to do a complete reset of my phone because I tried setting up a ROM to a data set location and when I switched to it, my phone would shutdown. When I rebooted it, it would load and then go back to shutdown. When I went to TWRP, everything I had in the internal SD card was gone. My nandroid backup on my external sd worked, but when the system loaded up, everything google would not work. After several tries, I just had to reload from scratch. Not sure what happened there, but I think it may have had something to do with the February security patch that Google put out. When I reloaded my phone, I did not install the patch.

Currently, I'm using v.2348 of DBP. I created to data slots: 1 for crdroid and another for Resurrection Remix. I can't see my internal or external sdcards in crdroid. As far as its concerned, everything is gone, even though I know it's not. I can only see and access my internal sd on Resurrection, /raw/extsd is not accessible and storage/3703-C670 is empty according to the ROM.

I appreciate you taking the time to look into this one!

crdroid: http://xdaforums.com/moto-x-style/development/rom-crdroid-android-t3313112

Resurrection Remix: http://xdaforums.com/moto-x-style/development/rom-resurrectionremix-v5-6-2-t3301393

Edit: In all slots except Primary, I see a notification that the sdcard is corrupted.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
This is how far I got. It installed.

It recognizes.

I am just not able to boot into the custom rom itself. I try switching roms with dual boot patcher but when I restart it kicks me back in to the stock touchwiz Rom.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Picture attached.

So close
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Yeah, the logs look the same to me as well. I tried looking at the SELinux policy on my computer to see if I could spot something in there. Then, I found out none of the SELinux tools could load the policy. (Lightbulb appears on top of my head...) If that's the case, mbtool will also run into the same issue when it tries to modify the policy (and therefore, autoreboot to recovery). It looks like Google made some backwards incompatible changes to the SELinux policy file format that I'll need to add support for: https://android-review.googlesource.com/#/c/179568/ I'll see if I can get that done tomorrow.

With that said, I still don't know why nothing is being logged to the kernel log. It doesn't make any sense to me. It should at least log the mbtool version number and a few other things before SELinux has a chance of blocking that. Could you send me the boot.img for that ROM in /sdcard/MultiBoot?

That's the /data folder for the ROM. It should be populated when the ROM boots (successfully). /data/multiboot/data-slot-mm/system is the one that holds the /system files after flashing.

That's very interesting. I've seen that happen before when installd (system service responsible for clearing app data, creating /data/data folders, etc.) crashes, which can happen if the app sharing code acts up. When the /sdcard symlink is missing, does /mnt/sdcard/MultiBoot/appsync.log show any signs of crashes? You'd see a lot of "Retrying ..." messages if there were.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks, I'll keep looking into this. Do you have a primary ROM right now (unpatched with no ramdisk update, so no /raw/* paths at all)? If so, could you paste the output of "adb shell mount" here? mbtool is currently trying to mount the card using the fuse-exfat driver and if the ROM uses a different driver (like Samsung's exfat kernel module), then that could easily cause the SD card issues you're seeing.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahh, yeah SELinux will prevent switching ROMs (and just about anything besides patching a file). Flashing a permissive kernel for your primary ROM should fix that.

You can also switch ROMs from TWRP by flashing the appropriate /sdcard/MultiBoot/[ROM ID]/boot.img file.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
I tried switching roms in twrp using boot.img still no luck ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Yep, it's definitely using a kernel module for exfat:

/dev/block/vold/public:179,65 /mnt/media_rw/3703-C670 [B]exfat[/B] rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,namecase=0,errors=remount-ro 0 0

That is likely to be what's causing the issues. I'll download the two ROMs you linked to earlier and see if there's a good way to detect which driver mbtool should use.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Darn :(

EDIT: The SELinux policy file format issue I mentioned to [MENTION=2688336]todivefor[/MENTION] most likely applies to your device as well. Could you upload any boot.img file for your device? That'll help me fix at least that bug. Thanks!
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Uploaded the primary boot.img found in MultiBoot folder. Let me know if that is good for you.

https://drive.google.com/file/d/0B5S8tu4Ke9anUlVEVHZBNDZmT1U/view?usp=docslist_api
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Here u go.

https://www.dropbox.com/s/2coe3gaqmx701fh/boot.img?dl=0

I appreciate if a fix version would have that mentioned in change log.

Thanks.
[Galaxy S 4 i9505 Original Android Development] chavdar:
Hi [MENTION=427477]chenxialong[/MENTION]. Here are the logs from the failed boot from ext_sd. Thank for the clarification on the apps. I hoped to spare some space on the internal flash. I guess I have to wait untill ext_sd works to shave off a GB ?

https://www.dropbox.com/s/k8p8g7i0jlkhgcp/G900F.20160318.095916.tar.gz?dl=0
[Galaxy S 4 i9505 Original Android Development] todivefor:
Here you go. I am currently on the road. This appsync.log is from a couple days ago, about time I was testing. I am not sure it is the one you want. I will get whatever you need once I get home.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The problem should hopefully be fixed in 8.0.0.r2358.gc44e5a3 :)
[Galaxy S 4 i9505 Original Android Development] Gerxp:
delete
[Galaxy S 4 i9505 Original Android Development] MBariya:
I am also having same problem on Snapdragon Note 4.

Flashing kernel gives bootloop and then Dual boot Utility also not detecting primary rom.

I am on r2333 duel boot version. Need to test this on older version and confirm.
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Newer version fixed some of the problems for me (can update kernel ramdisk but can't flash kernel in recovery, cm13 now boots, can't flash kernels/ROM's from dual boot patcher-bootloop) but I get empty logs from the remaining problems, that's why I didn't post any logs.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Anybody else seeing this on the download website?

Really weird
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
His SSL certificate expired today.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Me too, first time seeing this!

---------------------------------------------------------------------

[New World Order (NWO)

Telegram it's better than Whatsapp In every way!]

---------------------------------------------------------------------
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Oh ok I was concerned and wondering if I had done something with all the testing with dual booting.

Thanks for the bit of clarification.
[Galaxy S 4 i9505 Original Android Development] ewangw:
Yes, the encryption certificate for the website expired today. The site owner would need to renew it before it goes away. You can still get you can still get to the site, but have to accept/Ok the warning message regarding the encryption.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
He is probably hard at work fixing the issues we have brought to his attention.

Will be amazing to see this working on the Galaxy S7 edge fully.

Only issue is switching roms and booting between the two
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Well shoot. Damn StartSSL for emailing me today telling me that it would expire next Wednesday. I'll fix this today.

I'm switching away from that company to Lets Encrypt.

EDIT: Fixed! https://*.noobdev.io now use Lets Encrypt and will auto renew when the certs are about to expire. Also took to time to update the SSL configuration to disable weak ciphers: https://www.ssllabs.com/ssltest/analyze.html?d=snapshots.noobdev.io
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I just pushed out 8.0.0.r2360.gf25a72d. This should fix the issue where mbtool could not read the SELinux policy file format in TouchWiz 6.0. It will not fix the other SELinux issues, but hopefully, it'll get further in the boot process now.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
r2360 fixed my issue. Thank you.
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi, that thread is specifically for the Transformer, yes. But you can apply the concept around it to any device where the Rom's kernel (or linux for ARM, Firefox OS, etc) can be patched to be "kexecbooted" from another kernel or from some boot mechanism via the recovery, or some other strategies.

The Multiboot project for the Nexus family is a good example of this concept. You can search and read about it here at XDA, there is a lot of information but I don't know if any or part of that is made for running in your device. Search, read and try .. but be carefull to not fry :)

Regards.
[Galaxy S 4 i9505 Original Android Development] todivefor:
I don't know if this was supposed to do anything for my issues, but I installed patch with windows (successfully), and flashed. It appears to me to be the same.

Unfortunately, I have to send my S6 back to Samsung for a warranty claim on Monday at which time I will no longer be able to test. Keep up the great work. I'll be happy to pick up again on its return.
[Galaxy S 4 i9505 Original Android Development] Help The Peace:
[MENTION=4277844]chenxiaolong[/MENTION]: How to backup and restore both builds of the Dualboot system? ?

PS: I got it running!!! Didn't install on the exact same slot![emoji14]
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
I guess that feature hasn't been developed yet and WIP. Would be nice to have when it's available in future though. [emoji4]
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2361.g4e0ba6c should hopefully fix this. A ramdisk update isn't enough to apply the changes. You'll have to reflash the ROMs that have trouble with the SD card.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'm getting the feeling that Samsung disabled logging to the kernel log just like how they disabled a lot of SELinux logging to make it harder for us. Would you mind testing this debug build for me? The app installs alongside the snapshot builds and should say version "8.99.13-DEBUG" when you open it.

https://snapshots.noobdev.io/misc/X...0.0.r2361.g4e0ba6c_DEBUG_Test1_Vibrations.apk

If the S6's vibration motor doesn't need a driver to work (i.e. vibration works in TWRP), then this should cause the device to vibrate between 0 and 13 times depending on how far it gets in the boot process. Hopefully, that'll help me figure out which part of the code is going wrong. If no vibrations happen, this bug will probably have to wait until I can get my hands on an international S7 Edge (or my Note 4 if T-Mobile ever manages to push the TouchWiz 6.0 update).
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=4277844]chenxiaolong[/MENTION]: Here are the logs from the failed boot. Thanks!
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], that did not work. I have no vibrations in TWRP and the new patcher did not produce any. I am in no hurry on this problem as I am sending my phone back to Samsung. I will pickup when I get it back. I am back to my GS4. I might be bugging you there. Thanks for all your help.
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

Gave it a try and one of the ROMS was able to show the contents of raw/extsd, but the other one couldn't. The location of storage/***** still couldn't be opened in any of the slots and I still got the corrupted sdcard notification in all ROMS except for primary.

EDIT: Got caught being a dumba**. Forgot to repatch the files using the new version. Just did it and the crdroid ROM in dual slot is able to see my sdcard in /storage/**** and I didn't get the corrupt sdcard notification. Now to try Resurrection Remix!

Thanks [MENTION=4277844]chenxiaolong[/MENTION]!
[Galaxy S 4 i9505 Original Android Development] gaww:
I would like to get one also. Also have US version and would gladly trade for an intentional one. Would miss WiFi calling at times, but would hang on to S4 with TMo TW based primary ROM for that.
[Galaxy S 4 i9505 Original Android Development] rabby38:
bro where is the download link? i need dual patcher utilities but the web site show get logs. getlogs and dual boot patcher is same? or other