yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Thanks for replying. Unfortunately using the latest test build v9.0.0.r15 for Oukitel K6000 Pro I still get "corrupted sdcard" notification after updating the ramdisk. Da*n these MTK devices man! :D My extsd card is with two primary partitions fat32+ext4. I thought I should mention it. I'm attaching the patched boot.img in case you need it and as I already uploaded the stock boot image in post #9806 hopefully you can see what's wrong with the patched boot. I noticed it's half the size of the original. I'm also attaching the logs after updating the ramdisk. I didn't yet tried to flash a rom to internal slot, but I'll keep you informed. :highfive:
[Galaxy S 4 i9505 Original Android Development] Eagle:
Everything is working! Currently there are 3 ROMs that are in Dualboot patcher. 2 Touchwiz ROM + 1 CM based. No need for wiping system and all that stuff :victory:

[MENTION=4277844]chenxiaolong[/MENTION] for PRES. :laugh:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] I tried to boot a rom from the extsd-slot and the primary ROM's bootanimation appeared. I didn't wait and rebooted to twrp to flash the logs. Below are the logs after doing that. This is without ramdisk updated. May be it won't switch as long as I don't update the ramdisk, but I don't want doing so because my sdcard is recognized as corrupted. Or better to update the ramdisk for debugging to see if that rom will boot and then focus on eliminating the sdcard issue? Oh, I forgot if I update the ramdisk I won't be able to boot that rom because the extsd in not recognized, I must install to internal then.
[Galaxy S 4 i9505 Original Android Development] niufy:
Sorry for my question....has someone success dual booting the s7e g935f...?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Strange things happen..:D Patcher indicates that it's currently running a CM 13 rom from extsd slot, but in fact it's the primary stock Android 6.0. This is with updated ramdisk only on primary. And the funny thing: it's running the kernel of CM13 ( or just indicates it's doing so), but instead the primary rom is booted and the epic joke....the sdcard corrupted message is gone. I'm not a newbie, but I don't have any clue what's happening here. [MENTION=4277844]chenxiaolong[/MENTION] even if we have the right dev/block paths in json.devices I don't know why it's such a mess trying to run the DualBoot app on K6000 Pro. The data slot rom that I installed didn't boot. Strangely for an MTK device I don't face any problems during installation of the roms in data or extsd slot, it's just that the roms don't boot. Logs after trying to boot the data slot rom attached. The shot is showing extsd slot is running, but in fact it's the primary. I can't see the /raw path at the moment, this is also a sign the kernel from the sd2 slot is running.
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
Hey I installed the boot ui.When I try to boot into my secondary rom, boot ui asks for my password.I had a pin 1984, but it doesn't work.I removed the pin but the boot ui still asked for a password.There is a default password for decrypting.I mean, most times TWRP just receipts my data partition using the "default password". Please look into it, I still haven't figured how to make a log for it.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
A breakthrough! The data slot rom started loading after updating it's ramdisk, but it's stuck at the bootanimation. [MENTION=4277844]chenxiaolong[/MENTION] as I was thinking, we made a progress now the rom is booting, but something is preventing it to fully install all the files and to initialize. Of course now the sdcard corrupted message returned as I updated the ramdisk of the primary from the state I was in the previous post, this is something to be investigated, but first to focus on the easier (I think) issue here on my data slot. I attached the daemon log as I see a few repeated errors that may be the reason.

This is one of the repeated errors:

[2016/10/18 18:58:47 EEST][W] Unrecognized attribute 'pkgFlagsEx' in <package>

And the other

2016/10/18 18:58:49 EEST][E] Failed to parse XML file: /raw/data/multiboot/data-slot-data1/data/system/packages.xml: File was not found
[Galaxy S 4 i9505 Original Android Development] nutpants:
here is the boot image from the rom that is not working

(pulled it from the original zip file.)

the original logs i created were on the v2awifi sm-t900 tabpro 12.2 wifi

but honestly i have not found enough info to be sure if there are any differences.

( at least that is the only device i have, the us tab pro 12.2 wifi which should be the v2awifi which is what the patcher thinks it is )
[Galaxy S 4 i9505 Original Android Development] Steven1962:
Have really no idea how you guys succed to backup a rom from a slot. The app freezes at one point and I can't complete a backup... Also it is not quite clear how to restore a backup. Is there a tutorial somewhere?
[Galaxy S 4 i9505 Original Android Development] LordHelmchen89:
[MENTION=4277844]chenxiaolong[/MENTION] At first I want to thank you for this beautiful app.

I hope its not the wrong place for my request and I realy hope that I dont want to much from you, but could you please add support for the Elephone P9000. It would be sooo nice.

I hope my english is good enough to understand me.

Greetings from germany
[Galaxy S 4 i9505 Original Android Development] adilahmad1:
How can I install gapps to the secondary rom??
[Galaxy S 4 i9505 Original Android Development] nisarpari:
bro.. is everything working on your secondary ROM... like fingerprint and all.. ? would u plz tell me how u did that... i tried but cudnt succeed .. running 3.5.4 now... wanna try N7 Rom as secondary...
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] The CM13 rom also started loading from data slot, but it's stuck in bootloop.
[Galaxy S 4 i9505 Original Android Development] Pcsx2006:
Finger print works but pin/pattern doesn't.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Easy..just patch the zip for secondary.
[Galaxy S 4 i9505 Original Android Development] nisarpari:
sent PM since don't wana spam this thread with silly questions... reply if you have time.. thanks .:)
[Galaxy S 4 i9505 Original Android Development] adilahmad1:
From 2ndry rom? I'm really confused and appreciate if you gave detailed instructions :rolleyes:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Why not? No need for a sarcasm icons here please, I have enough problems getting my second phone to work correctly with the DualBoot patcher. It seems you're new while I'm using this app for more than a year. Patch the gapps zip in whatever rom you're right now then boot to any other rom DIFFERENT than secondary and flash the zip.
[Galaxy S 4 i9505 Original Android Development] adilahmad1:
this bricked my phone
[Galaxy S 4 i9505 Original Android Development] agueijo:
Yesterday I upgraded to version 9 and everything works fine. Except that when I want to switch with utilities from twrp I get the error:

[E] no device information file specified

I have a LG G4 h815 and I tried with version 9.0.0 r9, r12 y r14 with the same error. But with my old version of utilities (8.0.0.r2709) I can switch perfectly.

Thank you very much in advance, excellent app!
[Galaxy S 4 i9505 Original Android Development] physwizz:
Boot into the primary

Patch the gapps to go onto the secondary

Flash the gapps into the same place as the secondary.

Reboot into the secondary.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Thanks [MENTION=4277844]chenxiaolong[/MENTION] for the reply :P

Here is the twrp source code:

https://github.com/TeamWin/android_device_lge_d855

Caution! this is only for LG G3 D855. no the other g3s!!

Do you need anything else?

I'm feeling lucky with ya!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Can you try the test build at https://github.com/chenxiaolong/DualBootPatcher/pull/240?

The Boot UI support is enabled for all the LG G3 devices as the options related to TWRP graphics (which is all we care about) is the same across the following repositories:

https://github.com/TeamWin/android_device_lge_d850

https://github.com/TeamWin/android_device_lge_d851

https://github.com/TeamWin/android_device_lge_d852

https://github.com/TeamWin/android_device_lge_d852g

https://github.com/TeamWin/android_device_lge_d855
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Fixed in 9.0.0.r17.g6428cf6! I completely forgot to update the utilities after making some breaking changes in 9.0.0.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I've added a workaround for the fstab file issue and also added v2awifi to the codenames. Can you give the test build here a try? https://github.com/chenxiaolong/DualBootPatcher/pull/242
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oh yay! Another bug caused by app sharing. That is probably one of the worst things I've ever created. Anyway...

The missing /data/system/packages.xml file means that the "installd" service never started (it's responsible for building the dalvik-cache, among other things). Since the dalvik-cache doesn't get created, none of the Android apps can load and thus, you get stuck at the boot animation. The app sharing code does some very ugly hacks with installd, so it's extremely likely that it's the culprit.

I have a new test build for you to try. I've modified the patcher so that none of the app sharing code will load unless the user specifically enables it. https://github.com/chenxiaolong/DualBootPatcher/pull/224
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you try decrypting a few times, hit the cancel button, reboot to recovery, and grab a new set of logs with the GetLogs zip? I'm not really sure where it's failing.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Umm, wow. I have no idea how the extsd-slot-sd2 slot is booting to the primary ROM. It normally just reboots to recovery if it encounters any error.

Can you try rebooting and, as quickly as you can, run the following commands and upload the 2 files? (Quickly only because the kernel log has a limited size)

dmesg > /sdcard/dmesg.txt
mount > /sdcard/mount.txt

I am very curious as to why this happens.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure! Can 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] chenxiaolong:
Unfortunately, the kernel with the multiboot components added is too large to fit on the partition:

2414 dd: writing '/dev/block/mmcblk0p7': No space left on device

My guess is that the ROM developer probably added a bunch of things, like busybox, to the boot image.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Can you give the test build here a try? https://github.com/chenxiaolong/DualBootPatcher/pull/242

Part of the fixes in that test build should hopefully solve your boot issues.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm working on this now. Just need to compile cm-14.0 for my Galaxy S4 first. :)

Very likely. I run into this when flashing a dummy file that does nothing on my S7 also.

Can you pull /proc/last_kmsg when a TW 5.0.1 ROM autoreboots (or flash the GetLogs zip)? They're probably two different issues. TW ROMs prior to Marshmallow should be working.

Nope, a permissive kernel should be all that's needed. (Actually, enabling just per-type permissive mode will work too.) I have not tested on my S7 Edge yet, but I'm pretty confident that's all that needs to be changed.
[Galaxy S 4 i9505 Original Android Development] agueijo:
Perfect, with r17 I can switch without problem!

Thank you!
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
Here you go, hope it helps.
[Galaxy S 4 i9505 Original Android Development] monkteo:
I don't think (for the moment) I try but don't switch to the patch-rom (second-rom)

something related with "can't connect to the mtboot" and if I update ramdisk broke my sd-card, but steel not change the rom
[Galaxy S 4 i9505 Original Android Development] LordHelmchen89:
Thanks for the quick answer and the circumstances.

I have appended the logfile. Can you please tell me when the time comes.

Thanks again, you are my hero, I could kiss you :D
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION]: For some reason in-app flashing is not working in 9.0.0.r14 on K3 Note, I get mbtool null. I didn't force updated the ramdisk may I should? Flashing in twrp works. Previously was using 8.0.0.2709
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Using the latest test build none of my two data slot roms booted, they're still stuck at the bootanimation. The good news is that there are some files installed in the /data for both roms----

Can you edit the boot image and remove all the junk as you wish to make it fit the partition? Boot.img of the CM13 and xOS (the 2 roms I'm trying to use) below.

---

EDIT:

[MENTION=4277844]chenxiaolong[/MENTION] Added the output I get from the dmesg and mount commands with updated and stock ramdisk.

Also can you add an option for custom save path of Backups in future releases? Thanks.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Ok [MENTION=4277844]chenxiaolong[/MENTION] here is my report:

Boot UI is working properly but It have a little Issue

I wipped out my phone competely. (So I lost everything on my Internal Storage but not to worry)

1st I have installed aosp 7.0 on primary to begin the test, so the first launch of the app request root permissions and update the ramdisk.

2nd When is done I cannot turn on the phone. As no longer the boot.img is bumped. So I bumped it again and the phone boots.

3rd I install the boot UI support and works fine. But again, I have do bump the boot

4th I patched another rom CyanogenMod 13 to my data slot. And installed it. but I still want to boot the primary slot and reboot.

5th The boot UI appears and the primary rom boot fine.

6th Reboot again BootUI appears but this time I change back to CyanogenMod 13 (Data Slot).

7th The phone cannot boot because the boot.img again is not bumped. I reboot in recovery and bumped again.

8th The phone boots fine into CyanogenMod 13. reboot.

9th BootUI popped out, switch to primary. the phone canoot boot due the boot.img is not bumped.

10th Bumped again and phone boots correctly.

Conclusion:

Boot UI works but you need to bump your kernel every time you switch the rom or update the RAMDisk.

Its possible to inject or something similar the bumping process in Boot UI?

The stable version of Dual Boot Patcher (Without BootUI) works flawslessly. no needing to bump anything.

I bump the images with the attached zip

Thanks a lot Chen.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
[MENTION=5926282]kingknuts[/MENTION]

What do you mean by bumping the kernel?

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Successfully booted both roms from the data slot with the latest 9.0.0r17 build. Unfortunately I was unlucky getting the test build to boot the same roms. So when you have the time, you can officially add support for Oukitel K6000 Pro, thanks. If you need more info about the phone I'm here. The CM13 rom was suffering from problems with the included SuperSu, so I manually replaced it with 2.71. The bad news is that both roms are showing "sdcard corrupted" message. Below are the outputs from the dmesg and mount commands under the CM13 rom. I hope we can find what's causing the problem. Interesting enough the AICP 11 rom that I'm using on my other phone Lenovo K3 Note was having the same "sdcard corrupted" notification, but the recent update fixed that. I wonder what was changed in the rom. I'm sure it's because of the rom update and not the patcher, because I also tried to patch and flash an older AICP11 with the 9.0.0.r17 and suddenly the problem was still there. I can send you the vold files from both roms to see what was changed. So we'll try to find a workaround for a ROM's problem, that's most probably caused by a crappy programming of the rom. I hope you realize how helpful your app is my friend. :highfive:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
You can dump the boot.img which contains the kernel. You also can do that while in Android as you're using the phone. ;)

Use the following commands in Terminal with root privileges (su).

1)The first command is for listing all the partitions of your device.

ls -al /dev/block/[color=red]platform/mtk-msdc.0/11230000.msdc0/by-name[/color]

2)The actual command for dumping the boot image is:

dd if=/dev/block/[color=red]platform/mtk-msdc.0/11230000.msdc0/mmcblk0p7 of=/mnt/m_external_sd/dd.out/boot.img[/color]

*You'll find the dumped boot.img in the /dd.out folder on your extsd. Change to a location you want.

**Change the color in red corresponding to your device.

The following method works "out of the box" on MTK devices, but you still have to double check the correct paths.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
we "LG G3 users" have locked bootloaders without the possibility to unlock it. So when we are bumping an image (boot, recovery) we are just singing those files.

In case that you dont have a valid LG signature. The phone refuses to boot with a blinking (Red and blue) light and a message saying:

Boot certification verify

Secure booting Error!

Cause : boot certification verify
[Galaxy S 4 i9505 Original Android Development] kingknuts:
I know its confusing but Im not Dumping the kernel. Im Bumping the kernel
[Galaxy S 4 i9505 Original Android Development] nutpants:
It boots up fine now in both roms.

Thank you very much..

Could not update the mbtool I the primary samsung touchwiz 4.4.2 while in that Rom(it would not write a log file either )

But I was able to update when I booted into the secondary rom so all works is working fine

Thank you again for all your hard work and efforts.
[Galaxy S 4 i9505 Original Android Development] physwizz:
It now flashes and boots up just fine. Thank you. Great job!

When I try to backup, it seems to stop part way through. I checked the backup and there seems to be a lot there. I might try to flash it and see what happens.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you also flash CM 13 to the same (or similar) slot and post the /sdcard/MultiBoot.log file? This looks like a kernel issue to me, but the CM 13 installer might have been ignoring the error.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I've merged the changes and it will be in the next snapshot.

I realize there's currently a freezing (dead lock) issue with the backup process. It's actually unrelated to backing up and can happen with any background process in the app (eg. flashing ROMs, patching files, etc.). However, the backup runs separately from the app and continues to run even if the app crashes. An ugly way to tell if it finished is to look at the backup directory and see when the file sizes stop changing.

The fix for this will require parts of the app to be rewritten, so it won't be fixed until I have a bit more time.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The fixes has been merged. You should be able to use snapshot 9.0.0.r20.g799b1e5 or newer.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Yeah, sure :)

Btw could you fix these problems also from this link#9863

Thanks in advience :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'd like to, but the kernel your device's recovery uses does not have /proc/last_kmsg or /sys/fs/pstore/console-ramoops support enabled. It prevents me from seeing what went on during the boot. I haven't figured out another way of dumping the kernel log yet :(

EDIT: Aha!

BLKDISCARD ioctl failed: Operation not supported on transport endpoint
failed to execute command [erase 14,66050,97792,131586,163328,197122,228864,245382,261632,262658,294400,295523,327168,328194,359936]
Verifying the updated system image...

So CM13 has the exact same error, but the installer ignores it. I'll have to see if I can find a way around it.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Hmm... So how can I help you to find an error? Do you think that is the fault of the kernel?

Thanks! :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you give the test build here a try and see if it fixes the CM 14 flashing issue? https://github.com/chenxiaolong/DualBootPatcher/pull/244

As for the boot issue, I'm working debug build that will save the kernel log to the cache partition as the device is booting :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry to keep sending you in circles, but could you try it again with this test build? https://jenkins.noobdev.io/job/Dual...r-builder && fast,target=android-all-gcc/274/ Your kernel is discarding any log message that isn't an error so this test build will log everything as errors.

You'll need to update the ramdisk or repatch and flash the ROM and then uninstall and reinstall the Boot UI.

Also, when you grab the logs, could you use the new GetLogs-20161019.zip zip at https://snapshots.noobdev.io? It has been updated to grab the Boot UI logs.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, S7/S7 Edge support is not ready yet. I haven't had a chance to work on it.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs!

Can you give the test build here a try? https://github.com/chenxiaolong/DualBootPatcher/pull/245
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Error again with cm14 flash :p

But I have good news too :) I flashed cm13 kernel from other customrom and now I am with updated ramdisk :) But I think, previous kernel was a little better (I sense battery drain :p).

Btw TW 6.0.1 ROM don't boot, I get 5 vibrations before booting and recovery booting :)

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! That is indeed good news.

Unfortunately, the patcher has no way of detecting what is safe to remove. Some ROMs will fail to boot if busybox is removed, for example.

Sorry, I was unclear about this. Kinda got confused since we have two issues.

For the corrupted sdcard issue, I'll need the logcat:

logcat -d /sdcard/logcat.txt

For the extsd-slot booting into primary issue, I'll need the output of the dmesg and mount commands.

Take a look at the app settings :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Whoops, that was a very dumb mistake on my part. A new test build is available :) https://github.com/chenxiaolong/DualBootPatcher/pull/244

TW 6.0 support will come once I get it working on my S7 Edge.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Hmm... I think, version r23 working correctly but I minimalized DBP and app crashed when I switched:/
[Galaxy S 4 i9505 Original Android Development] physwizz:
Could you please look at the log file after i flashed the backup?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
CM14 ready. Time to try. I will first :D

EDIT: Not working. File system.img is clean (no system files).

EDIT2: I think, this was a trap :p
[Galaxy S 4 i9505 Original Android Development] physwizz:
Excellent.
[Galaxy S 4 i9505 Original Android Development] corsicanu:
Not working here either. But on my phone doesn't pass the flash. Here i pasted the log. Cheers!
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
New zip isn't available on the given link.

Edit :

Never mind, replacing date was enough to get the correct zip.

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.