yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I have not rooted my S6 Edge+ yet because I actually use Samsung Pay a lot (grr.. expensive school parking lol). I've been wanting to dissect the Samsung Pay app to see if it's possible to make it skip the KNOX check using Xposed, but I haven't gotten around to doing that yet. Not having root reminded me how bad the experience is without an ad blocker :laugh:
[Galaxy S 4 i9505 Original Android Development] mismamente:
Great!!! Thank you very much. All works fine.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It creates an ext4 image file with the exact same size as your system partition. Some AOSP ROMs expect or require this and may not boot if the size is changed. Is there something you want to flash that doesn't fit?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Haha! :laugh: It's getting close, but I didn't want to hold back all the other changes until the backup/restore feature was complete.
[Galaxy S 4 i9505 Original Android Development] Eliminater:
same reboots in recovery with build 8.0.0.r2007.gfa298ab and system ext4 :eek:
[Galaxy S 4 i9505 Original Android Development] Johan1976:
Asked a while back about placing /data on sdcard as well if using extsd option. The reason I use extsd is because internal is kind of out of space. What do you think? Or maybe an option?

Skickat från min GT-I9505 via Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes, if there are no further errors, what you suggested will work :) If you open the zip file and take a look, you will see that:

/system/vendor/operator/app/Baidu_Location/Baidu_Location.[COLOR="Red"]apk[/COLOR]

exists, but

/system/vendor/operator/app/Baidu_Location/[COLOR="Red"]arm64[/COLOR]/Baidu_Location.[COLOR="red"]odex[/COLOR]

does not. That's why it's failing to install. The ROM develop tried to change permissions on a file that doesn't exist.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahh, okay, you're using the arter97 kernel. He has a basic dual boot implementation built into his kernel that interferes with DualBootPatcher. It may take me a while to work around this.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I currently do not plan to implement this feature as it does not work with app sharing and would need quite a bit of extra code to handle both extsd w/internal data and extsd w/external data. It might be a possibility for a future version, but I really don't know yet.
[Galaxy S 4 i9505 Original Android Development] mismamente:
[MENTION=4277844]chenxiaolong[/MENTION] I have talked too fast. I wiped my external rom, and when I've tried to install a new rom an error happens. It says rom is patched for jfltexx but device is jflterefreshspr

Failed to run real updated-binary
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you flash the GetLogs zip from https://snapshots.noobdev.io/ immediately after flashing the new ROM and then send me the log file it creates in /sdcard/logs/? Thanks!
[Galaxy S 4 i9505 Original Android Development] Eliminater:
than you very much for your excellent support :o

I hope it work with arters kernel in the future.
[Galaxy S 4 i9505 Original Android Development] mismamente:
Doing it at this moment through TWRP. But the error I'm telling you about it's from android app. I'll post the logs when flash finish.

Thank you for you great and extremely fast support..
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
That makes sense, I thought I could have a larger image to also store the apps,but if that does not work then I will work with that. By the way this method works great for more roms on your s4.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Ok. I'll try.

What about the other edits I said?? Will they be needed? Boot.img, etc.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I don't know, the flashing failed before it got to that point :) Try without changing the additional stuff (i.e. remove Baidu_Location.odex only).
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
So that's why is doesn't work on my S6.
[Galaxy S 4 i9505 Original Android Development] karkasss:
Perfect working for my S4 (jaltektt)

BTW, if you don’t mind, could you add more operators like below?

Then, Any Korean user can apply Dual boot patcher without modifying build.prop.

Thank you so much.

(i9500)

From

device->setCodenames({ "ja3g", "jalte", "jaltektt" });

To

device->setCodenames({ "ja3g", "jalte", "jaltektt" , "jalteskt" });

(ks01lte)

From

device->setCodenames({ "ks01lte" });

To

device->setCodenames({ "ks01lte" , "ks01ltektt" , "ks01lteskt" });
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] been meaning on asking you this for awhile, would I be able to use flash fire inside, say my secondary, for whatever reason it may be?
[Galaxy S 4 i9505 Original Android Development] mismamente:
[MENTION=4277844]chenxiaolong[/MENTION] I've attached the logs. The tar is from getlogs. If I install from TWRP the rom installs fine, without errors (and that's the logs attached).

But when I try to flash with the android app, it fails. The log is MultiBoot.log

Kind regards
[Galaxy S 4 i9505 Original Android Development] fmotta:
[MENTION=4277844]chenxiaolong[/MENTION] thanks for this work. Really appreciated on my OnePlus 2.

Any plan to release with ZUK Z1 compatibility?

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done :) 8.0.0.r2015.g6cd2015
[Galaxy S 4 i9505 Original Android Development] Eliminater:
i think just the old kernel for the s3 have the dual boot implementation

the newer arter kernels for S4 (ks01lte) and S6 (zerofltexx) doesnt have it !
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'd say probably not, but I'm not sure. I only tested Flashfire once on my Note 4 before and when it restarted the Android framework to go into "flashing mode", the GPU driver crashed, so I never able to get the app to work. You could try flashing the attached test zip in Flashfire. It simply creates an empty file at /system/testing, /cache/testing, and /data/testing. Then, you could check with a file manager to see where it's really installed.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for giving me logs in both cases. It's actually passing the DualBootPatcher checks now. However, the ROM itself also manually checks to see if "ro.patcher.device" in your build.prop file is set to one of the following:

jfltexx

i9505

GT-I9505

jgedlte

i9505g

GT-I9505G

jflte

The flashing works from recovery because your recovery reports the device as "jfltexx".
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've downloaded the latest kernels for those two devices and both do indeed have that feature built-in.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure :) Would you mind flashing the GetLogs zip from https://snapshot.noobdev.io/ and sending me the log file from /sdcard/logs/? That should get me all the information I need to add support for the ZUK Z1.
[Galaxy S 4 i9505 Original Android Development] mismamente:
Ok thank you! I'll ask rom makers to add support this configuration.

kind regards
[Galaxy S 4 i9505 Original Android Development] karkasss:
Really thanks. You are so nice!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] New update!!

After some 2 or 3 more no such file or directory error, I was encountered by failed to flash boot.img error message (forgot to copy the multiboot.log, I will do it again if you need, but it said no error message).. Anyway, I told you how I got the Androium ROM work. By editing the boot.img part.. I did the same here and it seemed to work :highfive: But....... The ROM doesn't boot :crying: It reaches the bootsplash and reboots to recovery.. I think it is something wrong with the kernel. Anyway, I'm attaching the multiboot.log.. It shows some weird stuffs. Should I flash getlogs zip to get some other log?? Also is there any way to flash boot.img other than making it into a zip for the extsd-slot ROM?

Thanks
[Galaxy S 4 i9505 Original Android Development] virulentt:
[MENTION=4277844]chenxiaolong[/MENTION] I have a feature request for you (if it's not already implemented, i may just be retarded). Would it be possible to install a secondary rom into the internal storage? I made a guide to dualboot CM13 and TW on the galaxy s6, but unfortunately, the creator of the rom has already implemented his own fancy dualboot method, which is too complicated for normal user. We can install his rom has primary and set the kernel, but patching the zip file seems impossible. I'm scared that whenever we'll update our primary rom, it will erase our secondary rom (system). I think installing it in the data or cache partition would get wiped if we factory reset, so the internal SD card seems to be the solution. Do you think it could be possible? The rom dev is arter97, you probably heard of him.

Here's the CM thread : http://xdaforums.com/galaxy-s6/orig-development/cyanogenmod-13-galaxy-s6-t3269984

Here's my guide thread : http://xdaforums.com/galaxy-s6/general/guide-dualboot-cm13-tw-t3271545
[Galaxy S 4 i9505 Original Android Development] ilker4fun:
I have note 4(n910c). Dual boot working fine but app sharing isn't working.I did everything.I updated ramdisk clicked share individual apps and I managed what apps I choose on first rom.Then I went to second rom and clicked share applications and share paid applications. And I restarted my phone but apps that I choose to share didn't show second rom. Can somebody help me please? Where do I wrong ?
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
Is it possible to use my backup for the rom in multi1 and put it in to my primary?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Reboot to recovery is good! That means it's started to load the multiboot components. Yep, if you could flash the GetLogs zip and send me the tar file in /sdcard/logs/, that would be great. Make sure to do it when it auto-reboots to recovery. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the info! Yep, I noticed the other dual boot implementation in the arter97 kernel as well. I haven't tried working around his implementation yet, but for right now, I don't think there's anything to worry about with regards to your ROMs. No matter what slot you choose, your data always ends up somewhere on your data partition in /data/multiboot. Unless the kernel wipes the data partition (which would be very unusual), the worst case would be that a ROM gets deleted, but the data stays intact. In that case, all you would need to do is to reflash the ROM.

Once I find a way to make his kernel compatible with DualBootPatcher, the best way to update the primary ROM would be to patch it for the primary slot. I've added a lot of code to ensure that a patched ROM will never overwrite any files in any other ROM.

As far installing to the internal storage, it is technically possible, but it's not very practical. Nearly every ROM resets the permissions and SELinux labels for every file in the internal storage on boot. Once that happens, the ROM will no longer be able to boot.

Hope that answers your questions!
[Galaxy S 4 i9505 Original Android Development] virulentt:
After numerous testing and help of other users, we came to the conclusion that arter's kernel and rom are compatible as primary rom, but not if you patch it. His CM ROM seems to be pachable aswell. We are currently recommending people to flash on the data partition like you just said, it keeps the data intact. Thank you for your response.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Great...

I have attached the logs

Thanks

EDIT: I think I'm going to disappoint you, but reporting you the latest update... I don't think you've seen my post saying that updating ramdisk was not working in any version above v1778.. It is the same issue reported by 911_Future.. Anyway, the reboot to recovery after installing this ROM seemed familiar and I remembered it was when the ramdisk was updated in newer versions.. So, I thought I would try with the V1778 to patch and flash the edited ROM.........

And, guess what?? It worked flawlessly.

Yes, I'm now Dual Booting that MIUI ROM.. So, I think the problem is the new versions of the Patcher and hope that you remember what you changed after that version and fix it.. I hope the attached logs will be useful..

Anyway, it is not entirely that bad.. It almost fully my fault. Because I was the one who gave you the logs when I tried to install ROMs with system.new.dat (the ROMs I have managed to install are having /system/ format) and asked you to fix the dumchar_info bug for which you did some fix.. And I came up with a ROM that was already working with the edits and made you confused.. [emoji29]

I'm really sorry.. I totally messed up. I admit.. I apologise for it..

Anyway, I've tried a system.new.dat ROM and it fails but I didn't get a log.. But I've my last exam tomorrow and I'll help you after..

P.S.: Please please don't be disappointed or angry with me.. I'm stupid, I know..

EDIT2: When this MIUI ROM booted for the first time, it took a long time that I thought the edits have made un bootable.. But it booted after some time and guess what?? All the apps of the primary ROM has been copied to this ROM and my internal memory is almost full.. What can be the reason for this??

Also, it has a installed an app to my primary ROM.. I didn't know ROMs were connected like this..
[Galaxy S 4 i9505 Original Android Development] pvsgh:
Hi Chen, when you get a chance can you add support for AT & T Note 2 (SGH-I317), please look at this post for the logs:

http://xdaforums.com/showthread.php?p=63964320#post63964320
[Galaxy S 4 i9505 Original Android Development] Ashwin Prabhunerurkar:
Tysm Works well on tab s 10.5 wifi:highfive:
[Galaxy S 4 i9505 Original Android Development] axel87:
Hi all.

I am currently on cm13 on note 4 N910f o have installed dual boot patch the from I want to use I then install the from vai dual boot but nothing shows up in the from section .

Any ideas?

Thanks

Kevin
[Galaxy S 4 i9505 Original Android Development] vineeth314:
Add yureka plus support plz
[Galaxy S 4 i9505 Original Android Development] fmotta:
I read the instructions. But i can't even try to flash a ROM since the Zuk Z1 is not recognized. So have I to flash it in recovery even if no errors in booting?

Inviato dal mio Z1 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] ham4ever:
Thanks worked for me :D
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Flash the GetLogs zip from that sitein recovery.. It's not a ROM. It creates logs

---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------

Flash the GetLogs zip from snapshots.noobdev.io in recovery and upload the .tar file in sdcard/logs/
[Galaxy S 4 i9505 Original Android Development] fmotta:
Logs

Here are the logs for Lenovo Zuk Z1

Thanks
[Galaxy S 4 i9505 Original Android Development] Blackiisky:
Hey, I got around to trying to flash a second ROM on the nexus 6p and ran into some problems. Other than posting the multiboot log is there anything else I need to do to help such as flash the getlogs zip? (from what I read it seemed to be needed only if the ROM failed to boot.)
[Galaxy S 4 i9505 Original Android Development] karkasss:
[MENTION=4277844]chenxiaolong[/MENTION]

My roms are below. (S4 Exynos)

Primary : Stock Lollipop rom (stock kernel)

Data-slot1 : MIUI7 (4.4.2)

Data-slot2 : Stock kitkat rom (stock kernel)

But I cannot access internal memory on Stock Kitkat rom.

I heard that mount position for internal memory is different between Lollipop & Kitkat.

(Lollipop : data/media, Kitkat : data/media/0)

Is this reason that I cannot access internal memory on Kitkat rom?

If so, is there any solution?

BTW, I wonder why MIUI7 doesn’t have any problem for internal memory even if same kitkat.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Sorry, repost

Deleted..
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] I am attaching the log got after installing the system.img ROM..

Ignore the first part of it.. It still shows the open /proc/dumchar_info fail (No such file or directory) error..

Flashing in recovery and in built-in flashing method didn't produce any logs.. I had to use the DualBootUtilities zip.. It's a bit hard to operate.. Is there any way to operate AROMA using touch?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Damn Mediatek, they hide all the debug output from the logs and only show errors. After you're done with your exams, could you try this debug build and grab the logs the same way again? https://snapshots.noobdev.io/misc/XDA/Salman A./Post8047/Android_GUI-debug.apk I changed the code so everything is logged as an error message. Note that this debug build installs alongside the snapshots, so make sure to open the app named "DualBootPatcher (Debug)". Thanks!

Not angry with you at all :), but please don't try an old version like 8.0.0.r1778.ga8db742 when the newest one doesn't work. Your MIUI ROM probably started loading half from it's own slot and half from your primary ROM. The newer versions contain a lot of safeguards that prevent this kind of stuff from happening. The code is specifically designed to always fail (ie. reboot to recovery) instead of breaking something.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2018.gfe25c8c :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2019.g50a7dab :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks, that was my mistake. I skimmed through the logs too quickly and I though the partition paths were in /dev/block/platform/f9824900.sdhci/by-name/partition like other Snapdragon 810 devices, but it actually is /dev/block/platform/soc.0/f9824900.sdhci/by-name/partition.

This should be fixed in 8.0.0.r2020.gc298a0b
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah, that's the notorious SELinux issue on the Galaxy S4. TouchWiz KitKat expects every file in /data/media/0 to have the SELinux type "media_data_file", while Lollipop ROMs expect the files to have the SELinux type "media_rw_data_file". When you installed the Lollipop ROM, it probably changed the type for all your files. The best way to fix this is to update the ramdisk for the primary ROM.

If you're using the latest version of the app (>= 8.0.0.r2007), the update ramdisk feature is in the 3 dots menu next to your ROM in the app. If you're using an older version, it's under ROM Settings.

By the way, every version of Android after 4.2 (or was it 4.3?) uses /data/media/0 for the internal storage. If you have a table and add additional users, their storage becomes /data/media/1, /data/media/2, etc.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Darn, that /proc/dumchar_info issue is what's breaking the installation of the system.new.dat file. In 8.0.0.r2007, I tried to make that file available to the multiboot installation environment. I'm guessing that failed.

Can you flash the attached list_proc.zip file (without patching, just flash via TWRP) and send me the recovery log, just like you did here?

As far as AROMA goes, touch is supposed to work, but it may be incompatible with the touchscreen on your phone. You're lucky it even loads, it either crashes my recovery or shows a black screen on all of my devices :)
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Here's the log.

Thank you so much..
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
I'm using the r1778 because it's the only version that works for me.. All the other versions end up in reboot to recovery when I update ramdisk. That's why I stick to it.. Just now I tried updating ramdisk with the debug version.. Same result. Anyway, I'm ready to do what you say. Should I flash Getlogs zip when I reach the recovery? Will it work for the primary ROM??

Thank you so much [emoji4] [emoji5]
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks. So it looks like all the /proc files exist, but dumchar_info is not in there. Could you check if /proc/dumchar_info exists from the TWRP file manager? (Guess we should have done this from the beginning lol) There's a chance that the ROM won't flash in your recovery.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, just flash GetLogs.zip when it fails and autoreboots to recovery (even for primary ROM) :) Thanks.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Oh

You are right!

There's no /proc/dumchar_info in TWRP file manager either

Isn't that strange?

But I must tell you that I've installed this ROM once without any errors as the main ROM.

There's driver starting with d[emoji15]
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thanks

Here's the log I took when it auto-rebooted to recovery after I updated ramdisk Primary ROM using the debug version.

This log is bigger (5 MB) compared to the last log (4).. I really hope you can fix the issue :good:

And I use the r1778 only to update ramdisk and install ROMs.. Then, I update to the latest version.. Will I still be vulnerable to safety issue??

P.S.: I always what this ramdisk was and what its use was.. What are they exactly? [emoji2]
[Galaxy S 4 i9505 Original Android Development] karkasss:
[MENTION=4277844]chenxiaolong[/MENTION]

I updated ramdisk for primary as you said but same result (No access of internal memory of stock kitkat rom)

Could you analyze my logs files when you are available?

I'm not sure both logs files (one is generated primary rom booting, other is data-slot rom booting) are needed for you but attached both of them

Logs file:

https://mega.nz/#!88UQFT4b!LWLOPUy64NlG1o0HGb7uYQRzz-1nZRf30mJnhLcD4eA

Dual patcher version is

8.0.0.r2015.g6cd2015
[Galaxy S 4 i9505 Original Android Development] fmotta:
Thanks man!

At the moment I am unable to dual boot any rom.

I Use to patch and flash to slot.data (as I did with OnePlus 2).

It seems everything is flashed OK from inside yur program.

But when I exit the patch section to go to the rom list, I have a spinning circle and I have to quit the program.

If I relaunch I find the slot data rom; I select it and reboot. But I always get the primary.

Any logs to send you?

BTW: I am using this one DualBootPatcherAndroid-8.0.0.r2020.gc298a0b-snapshot.apk
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] Please tell me this is good news.. Pretty please ?

The open-source code of my phone has been published!!!!!

Here's the link: http://support.lenovo.com/us/en/products/phones/k-series/k3-note/downloads/DS104361

I'll cry if this isn't a good news ? Please tell it is..