yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] shantam3108:
Hi anyone here dual boring android n are mm roms on their phone. If so when booting to android n and going in developer options does settings crash for you.

Tried every n based rom. Dual boot works fine but developer options crash in everyones ROm

Thanx in advance
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
Hi Chenxialong, please add support for mtk6735 devices, HomTom HT6, thanks
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you post your "/fstab.*" file here? You might need to use a root file browser to access it. Encryption support is still in beta, but since it uses the same code as TWRP, if TWRP can access your encrypted data partition, then the patcher should be able to as well.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
From your secondary (or any other ROM), you can access the primary ROM's files in /raw. So, in the case of AdAway, you're probably looking for /raw/system/etc/hosts.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Encryption can be considered "supported", but there are a few caveats:

The device must be encrypted with an AOSP ROM. I'm using TWRP's cryptfs code, which currently only supports AOSP-style encryption.

The device must be encrypted before installing any dual boot components. mbtool (which is responsible for mounting partitions during boot) will bypass Android's own mounting procedure (vold) and thus, the built-in encrypt option will no longer work.

This sounds like an awesome setup, but unfortunately isn't possible with DualBootPatcher yet. During boot, the encrypted /data partition is always mounted and thus, its files are accessible from any ROM with root access. If this were to be disabled, a large amount of functionality would be broken (any thing requiring access to /sdcard/MultiBoot) and the sandbox ROM would need an alternative location to store its data.

The next major release (10.0.0) will allow the user to create custom slots to install ROMs, allowing the entire data for a ROM to be contained in an ext4 image, if desired. Perhaps I could also implement support for encrypting these images.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Just got my G935F! I'll finally be able to work on TouchWiz 6.0 support.
[Galaxy S 4 i9505 Original Android Development] lexxx84:
Thank you for this. I had to install a non-rooted ROM just to play Pokemon Go and I thought I couldn't modify the hosts file.. till now. I have just tried it and there is no problem switching between both ROMs after copying the file over. Thanks again.
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
I am waiting for your reply.
[Galaxy S 4 i9505 Original Android Development] monkteo:
My friend I am waiting this for a loooooong time , and THX for that !

THX 5B404140WA812243D
[Galaxy S 4 i9505 Original Android Development] SerJo87:
chenxiaolong,

What can you say about the support Xiaomi Redmi Note 3 Pro(kenzo)?
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
So I have 40 gb free memory.I an trying to dual boot dirty unicorns.I patched the zip to install to data slot "1".I rebooted to recovery , mounted system (just in case) flashed the DU zip.It installed successfully,I rebooted,phone vibrated a few times then rebooted to twrp.I tried using dual boot utility to switch to primary from,but the zip failed to do so.I rebooted and the phone vibrated and went back to twrp.I was using ElementalX kernel.I have a backup of my stock kernel.I entered the utility,deleted DU rom from data slot 1 and restored stock boot IMG.( by the way the utility could not find the boot img of the stock rom .why? perhaps it cannot access data ?).The phone booted up fine on my primary rom.Like I mentioned my one plus 3 is encrypted and a few weeks back when I tried to decrypt I had a lot of trouble and gave up.P lease look into it, check the logs and thank you.(TWRP can decrypt and access my internal storage easily.)
[Galaxy S 4 i9505 Original Android Development] navcar:
Oh... guess you're not a warranty person? :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Given that Samsung does not provide warranty for non-US models in the US, nope, I don't really care :D
[Galaxy S 4 i9505 Original Android Development] corsicanu:
[MENTION=4277844]chenxiaolong[/MENTION] Could you please add support for A5 2015? Here you have the required logs.

My device is A500F (a5lte - lte, duos) and the twrp is made for A500FU (a5ulte - lte, single sim). They are the same as specs and things, even the roms work from one to another.

Anyway, if you can, it will be nice to have also BootUI.

Unofficial TWRP thread and source.

Edit: If you need anything else, i will try to provide :D.

Many thanks for your awesome work! Cheers!
[Galaxy S 4 i9505 Original Android Development] traumatism:
Wrong thread admin please delete
[Galaxy S 4 i9505 Original Android Development] bvlgvr:
Encryption

Well, this sounds like it would solve my problem, so it would sure be nice to have.

I just wonder why the kind of setup with a "sandbox" ROM isn't discussed much if at all. Does everyone think features like Privacy Guard are sufficient ... or has everyone given up on keeping their data from being collected in big companies pockets with smarthpones?
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
Chen please look in my post and see whats the problem.Thank You.
[Galaxy S 4 i9505 Original Android Development] Sr_psycho:
Chenxialong, please add support for Xiaomi Note 3 pro.
[Galaxy S 4 i9505 Original Android Development] Daviteusz:
Please add support for Xiaomi Redmi Note 3 Snapdragon :)

• Tapatalk • Redmi Note 3 Pro •
[Galaxy S 4 i9505 Original Android Development] lokicm14:
Please support Pantech Sky a900

Chenxialong, please support for Pantech Sky A900. Thanks!
[Galaxy S 4 i9505 Original Android Development] -MaD-:
It seems to be true: I'll be back to Dualboot with my good old note 4 (snapdragon) on Marshmallow?!

Gesendet von meinem SM-N910F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Pcsx2006:
Chen plz add support for Oneplus 3.
[Galaxy S 4 i9505 Original Android Development] ttydy:
+1
[Galaxy S 4 i9505 Original Android Development] Deic:
Use PHH's SeSuperUser & rename /sbin/su to /sbin/sudo & you can play Pokémon GO w/o problem.

You can use my script instead of manual renaming su:

https://gist.github.com/DeicPro/4dc0971be5a775067aa83d11c16b0af9

To install my script run this & close the terminal after:

su
sh /sdcard/nosu

*notice what now su is sudo*

Usage

Restore root:

sudo
nosu

Hide root:

su
nosu

I hope this can help you.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi [MENTION=4277844]chenxiaolong[/MENTION] can you add support for Oukitel K6000 Pro please. Log attached.
[Galaxy S 4 i9505 Original Android Development] gaww:
This may be the deciding factor in moving over there myself.

I would think it would be possible to use a 935T based ROM (not the firmware of course) on it to preserve WiFi calling, as on my US S4 I have an international ROM that was based on a US s4 touchwis ROM (the reverse of this situation), and also an international TW and ASOP ROMs as my duel boots.

Question of the LTE bands - wouldn't the installation of the US modem allow access to the TMo bands - even on other ROMs? My international S4 ROM, which I assume was based on Enos, works OK here and it of course has a US TMo modem.

In any case, with you heaving a 935F I feel some good things are coming down the road soon.
[Galaxy S 4 i9505 Original Android Development] physwizz:
Has anyone been able to run a TW ROM on extSD?
[Galaxy S 4 i9505 Original Android Development] gaww:
Good question - would free up a lot of space - am currently short on that due to 2 TW ROMs (international and US TW stock for WiFi calling).
[Galaxy S 4 i9505 Original Android Development] virulentt:
[MENTION=4277844]chenxiaolong[/MENTION] , I don't if you remember me, i'm the guy that made the tutorial for the s6. I recently changed to a nexus 6p and i couldn't run it on my device. Is it supported? I'm on Nougat.
[Galaxy S 4 i9505 Original Android Development] eilex17:
Please enable a Backup Rom feature... ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! Please try out the test build at https://github.com/chenxiaolong/DualBootPatcher/pull/219 and let me know if it works.

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

Please give the test build at https://github.com/chenxiaolong/DualBootPatcher/pull/220 a try. Thanks!

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

Thanks! A test build is available here: https://github.com/chenxiaolong/DualBootPatcher/pull/221

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

Thanks for providing a complete set of logs and links! A link to a test build is available at this pull request: https://github.com/chenxiaolong/DualBootPatcher/pull/222

Note that TouchWiz 6.0 kernels with SELinux set to enforcing currently do not work properly. Everything else should be fine though.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I personally care about this a lot, but at the same time, I don't like losing the convenience of having Google's features. I try to prevent data collection as much as possible through ad and script blockers, but of course, those doesn't really help with anything outside the browser. I'd like see some sort of application-level sandbox that:

jails the Google processes to an empty or clean chroot

supplies fake data through the APIs that are used to collect non-file data (eg. GPS location, sensor readings, etc.)

blocks access to the TEE, modem, and other closed-source super-privileged systems that ARM devices have

With that said, if open-source software on Android gets good enough, I might stop using the Google services. Heck, on my Laptop, I run Linux fully encrypted (including /boot partition) with no closed-source software besides the Intel WIFI firmware and the NVIDIA driver.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure. Can you link to the recovery for your device and also upload boot.img and a few files from /system/bin (any files)?

The reason I need that is because the build.prop file says the device is 32-bit, but the default.prop file says it's 64-bit.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
VoLTE, WiFi calling, RCS, and EVS are actually what I've been working on for the past week. I've gotten VoLTE working already, but not WiFi calling (haven't tried RCS or EVS). I don't know if band 12 works since my school is the only place I got a band 12 signal and I've graduated already.

The biggest problem with WiFi-calling is that the international model uses what Samsung refers to as IMS 5.0, while the US models use IMS 6.0. When the IMS 6.0 binaries and framework are ported to the international ROM, the IMS service crashes trying to communicate with the modem, leading to the whole framework crashing. I have not figured out a way around this yet. It's not possible to flash the G935T modem on the G935F since they have different modem hardware.

Now, with the Note 7, every variant uses IMS 6.0, which should hopefully make porting the feature easier. Maybe a ported Note 7 ROM will be the first to have WiFi calling on T-Mobile. Or maybe if TouchWiz 7.0 uses IMS 6.0 everywhere...
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
[MENTION=4277844]chenxiaolong[/MENTION] I have a MT6753 device and could do DualBoot using the Jiayu S3 Plus settings. As the mtk 64-bit are very similar you could not create a universal support for mtk 64-bit? If you can take a look at the link (and maybe add on your build)

https://github.com/Nonta72/DualBootPatcher/blob/master/libmbp/devices/mtk64.cpp

If you do not want make a mess adding so many devices from different manufacturers in the same file, I will attach only mine. And there are two problems that I hope you can help me: I can't boot any boot ROM with encrypted data, then you could add support for my device? What you need to know is in the attached fstabs. And also to update the ramdisk of primary rom (MM) in order to use the boot ui, on next boot the notification "sd card corrupted" appears and can only access the internal memory, not the external card. In CM (data slot) updating the ramdisk brings no problem. On MM the internal memory is mounted on "/storage/emulated/0/" and "/storage/sdcard0/". The external card is mounted on "/storage/628B-5430/" and "/storage/sdcard1/". I was seeing in your code that both "sdcard0" and "sdcard1" are considered the external card and as I said each one represents a different storage on my device. Both are giving conflict? Can you help me?
[Galaxy S 4 i9505 Original Android Development] corsicanu:
I'm having some problems. Fails when mounting some partitions. Same thing happens with any patched zip, that normally work. Don't know if it matters but TWRP is made from CM 12.1 branch and has SELinux enforcing. You have Multiboot.log here. Cheers and thanks for your promptitude!
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Sure, the thing is that the cpu itself is x64, but the rom I'm using is x86. Currently there are x64 roms for this device, I guess I need to flash one of them. Meanwhile I'll upload the files you need.

Edit. Actually I managed to dump the boot.img with the dd command in Terminal. Zipped with some files from /system/bin and attached below. ;)

Yeah, I'll really appreciate the backup option to be finished. Thank bro.
[Galaxy S 4 i9505 Original Android Development] dikime:
Hey,

I've used this multiboot solution a long time ago and I'm happy to see it progressed so much and is well maintained. I recently needed to do dualbooting again since the geniuses at Niantic decided blocking root/Xposed is the way to deal with cheaters in Pokemon GO (judging by what I see - it doesn't work).

So I decided to have my main ROM with every trick like root, xposed etc. and a secondary ROM that is completely clean. However, I still need root for AdBlock, changing the resolution (so games play much smoother) and restoring some of the most often used apps' data like Chrome and Messenger. I found this solution: phh's hidesu. It also modifies the boot image, and that's where the problem starts.

If I just patch it (works as expected) and then try to install it, the script fails because of the ramdisk modifications done by the patcher. If I first apply the hidesu patch, then extract the boot.img and patch it, it becomes too big and gives an error.

So... is there a way that I'm missing to have a "hidden root" secondary ROM. Hope I was clear enough, even though I didn't provide logs (can't right now :( ).

Thanks a lot.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Have you checked microg project ? http://xdaforums.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616/page203
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the files! I've set it up so that the 32-bit multiboot binaries will be used. This will work everywhere and only breaks encryption support on 64-bit ROMs (if you care about that).

Can you give the test build linked here a try? https://github.com/chenxiaolong/DualBootPatcher/pull/224

I know, I know. The GUI code is mostly done, just need to find the time to finish it :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's a very interesting issue. The patcher mounts the EFS partition in order to apply CSC changes when flashing a patched Odin tarball. It finds the EFS partition by looking at /etc/recovery.fstab. Your device's recovery image has the following in the fstab file:

/efs1 emmc /dev/block/bootdevice/by-name/modemst1 flags=backup=1;display=EFS
/efs2 emmc /dev/block/bootdevice/by-name/modemst2 flags=backup=1;subpartitionof=/efs1

which, as far as I can tell, aren't the actual EFS partition (am I wrong?). The reason I say that is because /dev/block/platform/7824900.sdhci/by-name/efs exists.

I've added an ugly workaround for finding the EFS partition without /etc/recovery.fstab until I have some time to implement a better solution: https://github.com/chenxiaolong/Dua...mits/2f26f4d22e7df8f95e2d86edadc3b3a5121d9e0b

A new test build is available at the pull request page for you to try: https://github.com/chenxiaolong/DualBootPatcher/pull/222
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
When it vibrates and reboots to recovery (and only then), can you flash the GetLogs zip from https://snapshot.noobdev.io/ and send me the file it creates in /sdcard/logs/? That will include the kernel log, which should show what's failing in the multiboot process. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I personally prefer to keep the devices grouped by manufacturer since it's easier to locate the device from the app. Regarding mtk64.cpp, I've noticed it's based on the version 8.0.0 code. This has changed significantly with version 9.0.0 that will be released soon. You can see some examples on the 9.0.0-staging branch here: https://github.com/chenxiaolong/DualBootPatcher/tree/9.0.0-staging/data/devices

This requires the following section in the new 9.0.0-style YML file:

- name: Quantum GO 4G
...
crypto:
supported: true
header_path: /dev/block/platform/mtk-msdc.0/by-name/metadata

The header_path field is the value of "encryptable=/dev/..." in the fstab file.

This is a known problem. Unfortunately, the patcher currently does not have support for devices where the internal storage is separate from the /data partition. It currently that every device has a large /data partition with the internal storage located at /data/media. This is something I hope to work on for 10.0.0 as it requires more changes to the code than just the path detection.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If you don't need the ability to boot off an exFAT-formatted external SD, you should be able to delete the /sbin/*.exfat* files in ramdisk to free up some space in the boot image :)

I'm curious to know what hidesu doesn't like about the patched boot image though. The changes the patcher makes are actually very minimal. Most of the modifications happen at runtime right before Android boots.
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
Hey.I flashed , zips are below.I throught systemless SuperSU was the culprit.I removed it from the rom,wiped everything and flashed again but same story.Check the logs, I hope you find them useful.Thank you.
[Galaxy S 4 i9505 Original Android Development] corsicanu:
From what i see those partitions are actually modem partitions. For now flashing works. Don't know if a full rom will patch and boot as should. I will try in few days with some 5.0.1 for better compatibility. Also i want to try to recompile twrp with some changes (+fstab fixes). Tried also BootUI and it works and not.. Meaning i see the boot ui and the options but ramdisk changes make the phone reboot back to recovery every time. 6.0.1 stock kernel, only patched for systemless root. That's why i said i'll try 5.0.1 android. Many many thanks for everything!!! Will provide feedback when i'll have. Cheers!
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Many thanks bro! I really don't care about the encryption. ;)

I want to ask you about something that's happening on my other phone Lenovo K3 Note. Most roms I've tried work flawlessly patched for dualboot, but small amount of the roms are getting installed just fine, but when I reboot the phone produces 5 vibrations and goes to recovery. When I look into the rom details the data partition is 0 B. For some reason the rom installs fine, but then can't find the mount points for storage or something and can't boot. I know you'll need logs to be able to answer, but do you have any idea why this is happening? Thanks.
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
Attached is the file following the new model. I believe that the path "/dev/block/platform/mtk-msdc.0/by-name" is accessible only on MTK Marshmallow roms, and as I also want to run Lollipop roms, i changed to "/dev/block/mmcblk0p19" . I hope you have no problem. And I added two more devices from my manufacturer's, but I am in doubt if the last modified correctly, especially if your app will consider "/" as a base dir. I hope you make the changes if needed and merge in your repository. Thank you!

- name: Quantum GO 3G
id: Q1
codenames:
- Q1
architecture: armeabi-v7a

block_devs:
base_dirs:
- /
- /dev/
- /dev/block/
system:
- /emmc@android
- /dev/block/mmcblk0p6
cache:
- /emmc@cache
- /dev/block/mmcblk0p7
data:
- emmc@usrdata
- /dev/block/mmcblk0p8
boot:
- /dev/bootimg
recovery:
- /dev/recovery
extra:
- /dev/block/mmcblk0boot0
- /dev/block/mmcblk0p2
- /emmc@protect_f
- /dev/block/mmcblk0p3
- /emmc@protect_s
- /dev/nvram
- /dev/pro_info
- /dev/seccfg
- /dev/uboot
- /dev/block/mmcblk0p4
- /dev/sec_ro
- /dev/misc
- /dev/logo
- /dev/expdb

And here there was a misunderstanding, I'm sorry if I was not very clear. The actual path of my internal memory is "/data/media/0/," which I cited are symlinks that applications to recognize, as you can see in screenshots. I will cause the problem again and I record with Liveboot, hopefully it will be enough to unravel the problem

Looking at the log found the following:

D/NetlinkEvent( 248): NL action '1'
11,1658,9106587,-; (2)[1:init]mblog: Successfully mounted /dev/block/mmcblk0p21 (ext4) at /raw/extsd

What is very strange, since the mmcblk0p21 block is the cache on my device. Would not it be better to use "/dev/block/mmcblk1p1/" block since it is pretty much standard among all devices?

In the log of CM13 I did not find anything related to mount of the external card, which is stranger still. But as you can see something is mounted as the external card, but that size "963.5MB" is the size of my "/" filesystem, which I believe to be temporary. "extsd" I manually mounted
[Galaxy S 4 i9505 Original Android Development] eilex17:
chenxiaolong, backup for cache partition on primary rom

Its a backup for multislot-1?????
[Galaxy S 4 i9505 Original Android Development] physwizz:
I found that I only had this problem with patchers after 2616.

2616 was good. Everything after that gave me the recovery at boot.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Did you experience the emergency "5 vibrations" code and reboot to recovery at boot with patchers after 2616?

Just tried myself using 2616 over the 2709 and yes suddenly the problem the rom is not booting dissapeared. Now it's just showing my sdcard as corrupted when it's not, it just has 2 partitions (fat32+ext4). I usually have problems MM roms reading my partitioned sdcard, that's why I ditched most of them and still my main rom is 51.1

Interesting enough there are other MM roms where the card works just fine, but most of them display a false "SD Corrupted" notification. Sometimes only one of the partitions is recognized, usually the Ext4 which is strange, because the first partition of the card is Fat32 and it's proven to be the most compatible sdcard FS. So ext4 is showed, but the fat32 is displayed as corrupted.
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
Problem is that older versions do not have one plus 3 encrypted support(or do they?)Do you have a Oneplus 3?If you do, give me a link to the apk.Thank you.
[Galaxy S 4 i9505 Original Android Development] physwizz:
The sd corrupted notification is rom related.

I sometimes get it on my nexus 5 using multirom with an external usb.

---------- Post added at 10:56 AM ---------- Previous post was at 10:49 AM ----------

No. I don't have a one plus 3.

Chen might be able to fix this.
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
Well I just tested 2616 and I get same error as before.I am waiting for Chen s answer...
[Galaxy S 4 i9505 Original Android Development] eminem5055:
Is there support for the T-Mobile LG g5 (h830)?
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
https://github.com/chenxiaolong/DualBootPatcher/issues/188