yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah, it looks like your recovery mounts the external SD at /external_sdcard, which was not recognized by the patcher. This should be fixed in 8.0.0.r1904.gf0d9065.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you grab a new set of logs so I can see if it's still the same issue? Thanks!

EDIT: Same method as before: Get to the point where it hangs and immediately reboot to recovery to get the logs.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Hi [MENTION=4277844]chenxiaolong[/MENTION],

I have a problem with my Note 3 on DarkLord Note5 RC2.1.

When I flash patched zip in Recovery (Extsd slot) I have error (screenshots in Logs.zip).

Thanks for fantastic app.

Attachment:

https://drive.google.com/file/d/0B1_R2RoVy6uSakxLa21pYmJfWlU/view?usp=sharing
[Galaxy S 4 i9505 Original Android Development] mabuan:
Thank [MENTION=4277844]chenxiaolong[/MENTION]! Here is my log.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
That shouldn't be the problem. I had tried it when I was using the old ROM.

But it was always the same[emoji21]
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1908.g37afd9b should fix the system verification error when flashing AOSP 6.0/CM 13-based ROMs. The issue was caused by the patcher not catching a new range_sha1() line in the updater-script. The installer would extract system.new.dat to a temporary image, but instead of trying to verify the image, it would try to verify a few bytes from the system partition (and mbtool does not allow direct access to partitions).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That is the issue unless the log file was not saved correctly. Maybe try deleting MultiBoot.log and see if it's recreated?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! That actually did fix the original problem, but as you found out, there's unfortunately a second issue. The ROM now fails to boot because the kernel cannot load a hardware driver and crashes due to that. You mentioned that you had upgraded to the new 5.1 bootloader bootloader before. That could probably cause issues like this. I've seen similar issues on my (Qualcomm-based) Note 4 where KitKat ROMs could no longer boot after upgrading to the Lollipop (5.0) bootloader. Unfortunately, this is way beyond my knowledge and we would need a kernel developer to take a look to see why the kernel is crashing.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] thank you so much for adding support to run AOSP 6.0/CM 13 as secondary ROMS!

[emoji106] [emoji106]
[Galaxy S 4 i9505 Original Android Development] corncobman:
Thanks. They flashed successfully this time, but it reboots straight into recovery if I try to boot either of the extsd ROMs.

DualBootUtilities is also showing the external sd card size as -1 Mb.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Has anyone managed to enable app sharing with primary ROM?

Last time I attempted it requested mbtool to be updated,I did update and got stuck in boot loop/samsung model logo and this happened using r1912!!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I have this same problem on Note 3 with DarkLord Note5 :/
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], I tried backing up my primary rom and restoring to data-slot-renegade. The backup worked fine and the restore appeared to have worked also. Using DB utililities, I tried switching to the new rom. It failed with attached message. I looked in /sdcard/multiboot/data-slot-Renegade and it was empty (no boot.img). It looks like everything worked, but the restore of boot.img to new slot.

EDIT: Patched and flashed kernel. It will now switch to rom, but never gets to rom boot animation. Flashed getlogs.zip, attached.

EDIT 2: I tried switching to data-slot from app. It switched and bootlooped with rom boot animation. I flashed DB utilities and cleared cache and dalvik, it said rom not installed. Before restoring back with TWRP, I tried restore back to primary. This worked fine. For last test, I flashed DB utilities and wiped primary system, data, cache, and dalvik, and then did restore. It boot looped at hardware splash and then into recovery. Probably should have captured logs, but didn't. Hope I have given you something to go on. Back to where I started without DB at all. It looks pretty good and is fast.

FWIW, I was using DB utilities - DualBootUtilities-8.0.0.r1707.g79cff94.zip. Have since upgraded.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] the added support for android M is very useful, CM 13 working perfectly as secondary ROM!, while AOSP 6 for x86 arch is promising but its getting stuck at the brand logo (Samsung galaxy tab 3) it does not make it AOSP bootlogo,find attachement below, crossing fingers that it contains useful data !!

https://www.dropbox.com/s/3jzpl1w9bjy1wud/20151108.110403.tar?dl=0
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
[MENTION=4277844]chenxiaolong[/MENTION]

Dualboot patcher: v1912

Device: SM-N9005 (hlte)

Rom: CyanogenMod 11 Official imstalled in data-slot-cm11

Problem: Device stucks in kernel logo (where there is written "kernel is not in selinux enforcing" in red)

Log: https://drive.google.com/file/d/0B2ftBoBlBHTIZ1pFOXpaalhQLWs/view?usp=docslist_api

Ps: Could you add support for i9300 (Samsung Galaxy S3 International)?

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] waplegend:
How do I do app sharing it's not working when u able it and switch Roms my apps doesn't appear it work on 8.0.777 but is working in the latest one now
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Instruction were that it be activated first from primary ROM, but you'll have to update mbtool and in my case tablet and phone with recent versions after updating mbtool and rebooting as requested, my device's get stuck in bootlogos!!!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
[MENTION=4277844]chenxiaolong[/MENTION],

I have a problem with my Note 3 on DarkLord Note5 RC2.1.

When I flash patched zip in Recovery (Extsd slot) I have error (screenshots in Logs.zip).

In DualBootUtilities I have:

Internal SD Size: -1 MB

Free: -1 MB

External SD Size: -1 MB

Free: -1 MB.

Thank you in advance!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Hi

Here's the new log.. I deleted the old one and flashed the ROM after editing the updater-script.. But flashing in recovery didn't make any log. So this log was made after flashing with in-app flashing tool.
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
@chenxiaolong. I think i stumbled upon a problem when i was going to use 'Set kernel' and 'Update ramdisk' on my Samsung Galaxy S6 edge+ (SM-G928F).

The newest 'Dual Boot Patcher' failed to execute both of those things.

Here are my logfile for that.

https://dl.dropboxusercontent.com/u/7309753/ramdisk-update.log

Do you see what the issue here is?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Looks like your kernel does not support /dev/block/loop-control. I've implemented a workaround in 8.0.0.r1919.gd1c9efc. Could you test that version and let me know if it works?

The -1 MB external SD size display issue should also be fixed in DualBootUtilities-8.0.0.r1919.gd1c9efc. It was caused by a hard-coded path to the external SD. This new version should automatically detect the correct path.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you flash the GetLogs zip from https://snapshots.noobdev.io/ and post the logs it creates in /sdcard/logs/ here? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for all the detailed info!

Regarding that missing boot.img issue, that was a mistake on my part. I'm so used to writing code that patches/edits boot.img files in memory that I actually forgot to save the result to a file. This should be fixed in 8.0.0.r1919.gd1c9efc. As for the kernel that you patched and flashed (the one you got the logs for), it seems that the kernel didn't get patched at all. I can't see any indication that the mbtool ran during boot. The kernel immediately started to boot Android and subsequently crashed, leaving you stuck at the manufacturer logo.

I haven't actually tested backup and restore for the primary ROM yet (just extsd-slot to another extsd-slot). Now that you've helped me find some bugs, I'll probably start working on getting that stuff fixed.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, it looks like you were booted into a working ROM for 8 minutes before you took the logs. Every time you reboot, the kernel log gets overwritten, so I actually got the logs for a working boot. :) Could you get to the hanging point, immediately force reboot into recovery, and grab the logs? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ohhh...I think I know what's going on. Touchwiz's tar probably doesn't support xz archives. The app doesn't check if tar failed to run because I assumed that such a basic tool would just work. That would explain why the log says that the patcher can't be found.

Oh well, I'll compile my own GNU tar and bundle it with the app.
[Galaxy S 4 i9505 Original Android Development] _Sofos_:
Hmm, has anyone managed to get Foxhound 3.1 as secondary Rom to boot?

Seems like it does get patched correctly but it's getting stuck in Samsung logo every time. Tried with the latest ausdim kernel, everything patched.

Sent from my S4 using TT2.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's touchwiz 4.3 correct? I haven't gotten those to boot properly yet.
[Galaxy S 4 i9505 Original Android Development] Bejda:
And (strangely?) i find no system/bin/tar under miui secondary system/bin... ;)

I grab it from my primary system and test right now..
[Galaxy S 4 i9505 Original Android Development] GhiGo65:
Edited....

sorry but carbon rom no longer work :(

it always made fc on initial setting

P.S.

can this rom added to supported one?

http://xdaforums.com/showthread.php?t=2483786
[Galaxy S 4 i9505 Original Android Development] RK:
Yup I patched kt touchwiz 4.3 kernel. Won't boot past galaxy s4 screen

I then patched faux touchwiz 4.3 kernel. It booted but without display drivers. I.e. the phone and the touch screen were working but the display was black
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you try this version and see if it works? This has a working tar bundled :)
[Galaxy S 4 i9505 Original Android Development] omnifarious:
It works for me. You have to use stock kernel.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Different error,unsupported zip for SuperSu..

http://pastebin.com/sQbH5JqA

I just installed latest tarfix app version on top,maybe I should remove previous before I'll try..

Edit:Nope same thing except that the error is different if SuperSu zip is on SdExt or SdCard..it gives "fail to apply patch" on SdCard,Unsupported zip if on SdExt ..:rolleyes::o

In the meantime i changed my secondary rom from miui to HellyBean and it works perfect of course (tried SuperSu)
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
Can anyone please upload a working share app script? For some reason I can't get it to work on PAC... Thanks in advance
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oh that lovely touchwiz... From the log, it looks like tar can extract the patcher files successfully now. "Unsupported zip" could be caused by Java not passing the filename over to the script properly. Do you happen to have a logcat for the "failed to apply patch" error? I think it's probably permission issues but I'm not sure.

By the way, what's your primary ROM? If it's not touchwiz 4.3, I can load it on my phone and try to figure out what's wrong.
[Galaxy S 4 i9505 Original Android Development] shremi:
Hi guys i was wondering if you guys coulkd help me out .... I have tried to to this thing 3 nights in a row and they all resulted in failure.

The roms that i am trying to dualboot are Goldeneye 9.1.2 which is a TW4.3ROM as the first and KANGABEAN which is a 4.3 GE ROM as the secondary rom. i have the att variant of the gs4.

First of all i couldnt get the latest App to patch the KANGABEAN rom either on my mac or via android directly . But since i used the older versions of the App in my girlfriends pone i have the KANGABEAN rom patched .

Here is what i have tried so far:

1.- Installed the dualboot App into my pone and saved my Ktweaker kernel as the main rom :good:

2.- Reboted into recovery (TWRP 2.5.2.0) and flashed the KANGABEAN dualboot rom and since Ktweaker kernel isnt supported to patch i patched audism kernel and flashed :good:

3.- Flashed the loki doki zip :good:

and then the problema starts i get the black screen indicating that the kernel is not supported so i flashed ktweaker kernel again managed to boot into the first room and from the dualboot App I selected to switch roms . Everyhting seemed ok rebooted and the pone gave me the unauthorized software thing .

I really dont know if the combination of roms that i am tryng to boot are currently not posible since the main one is a touchwiz 4.3 rom .

Any help would be appreciated.

TIA

Shremi
[Galaxy S 4 i9505 Original Android Development] Bejda:
I've been on TW 4.3 (via cwm custom so no new bootloader or whatever if that could matters in anyway...) but righ now It's 4.2 Echoe rom v3.1 (i need a 4.2 rom for some Square-Enix video games compatibility :) )

http://xdaforums.com/showthread.php?t=2372286 (link hidden somewhere on first post,v3.1 Eclipse)

Actually i'm trying to summarize things lol,the unsupported zip error only occurs with SuperSu zip on SdExt but a rom zip on SdExt gives a "normal" "fail to apply" error.

I'll try to make better logs i guess cause once the files are extracted (and yeah now i have stuffs under /data/data/git.../files ;) ) the logs i grab with OsMonitor on dual-boot patcher app specifically doesn't tell much http://pastebin.com/hvH0Vaqk A less partial log would be better maybe.

About the tarfix version..maybe it was just a one-shot exclusive TW test version but when i try it on HellyBean secondary rom (where normally it should work) it fails too. I reinstall previous app version and same zip works.

It's just that i wonder if it could tell us that there is just something's wrong with that app version..you'll know better lol.

I'm about too flash Miui again as secondary to try the tarfix version,you think it worth it? (mean the tarfix version could help on miui side as well?)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's because didn't really have the app log anything ;) (my fault) This version should log all commands and the environments for the commands. HellyBean and MIUI are both pretty small ROMs, so I'll try to figure out why the tarfix beta doesn't work there first.
[Galaxy S 4 i9505 Original Android Development] Bejda:
So tarfix beta should work on CM/AOKP based rom just like 2.4.1 works?

On Miui 2.4.1 fails (didn't tried tarfix beta for now) and on HellyBean tarfix fails to apply while 2.4.1 work perfect/normal with same zip (tried Su and rom).

Even if "aosp" Miui is sometimes a really different piece lol,i hope it won't cause much difficulties (TW is enough ;) )...+ no way to go back and forth from CM to Miui with no wipe sadly (SysUI fc...a little acore.process or whatever fc would have been nothing unsolvable lol but SysUI..)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Just patch HellyBean from Hellybean :) SuperSU too. I'm gonna try this version on MIUI now.

The problem was that the paths to commands cannot have ".." in them. ie. I can't run:

/data/data/.../files/DualBootPatcher-vX.Y.Z/scripts/../binaries/android/patch

but I can run

/data/data/.../files/DualBootPatcher-vX.Y.Z/binaries/android/patch

even though they're identical. Strange, but whatever :)

EDIT: Working in MIUI.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Beta2 works on Touchwiz :)

Still that unsupported zip statement if SuperSu is on sdext (ok on internal) but worked fine with miui zip under sdcard and HellyBean zip that was on sdext :victory:

Seen the edit ;) Great!

Thank you very much for your whole work.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Version 2.4.3 can now successfully patch TouchWiz 4.3 ramdisks. Also, Goldeneye (Touchwiz 4.3) for jfltetmo and IOKP are now supported :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hey marcoxx626, IOKP can now be patched using version 2.4.3 of the patcher (both on Android and PC). To keep things simple, I have the patcher use the AOKP patch (https://github.com/chenxiaolong/Dua...r/patches/jflte/ROMs/AOSP/aokp.dualboot.patch) because your updater-script is identical to AOKP's. As long as that doesn't change, there should be no issues :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You're welcome :) I'll download Kangabean and see if I can figure out what's going wrong. I haven't been doing much for AT&T and Verizon TouchWiz ROMs because I have no way of dealing with loki'd kernels yet.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This should hopefully be fixed in 8.0.0.r1920.g3aef1b0 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! The log is very useful this time. It looks like the ROM needs access to /proc/dumchar_info for the flashing to work. It appears that this file is specific to Mediatek devices. Could you send me a link to the ROM so I can see what this file is used for?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you also send me /sdcard/MultiBoot/daemon.log? Thanks!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thank you so much..

Here's the link: https://cloud.mail.ru/public/4pFvdmU7gtdX/Lenovo_K3note_Flyme_4.5.6_Final.zip

Thanks again for your help ?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Isn't a link to the revised backup/restore (8.0.0.r1919.gd1c9efc) code needed? Or don't you want further testing at this point?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
[MENTION=4277844]chenxiaolong[/MENTION],

Yes I flashed this zip but my folder /sdcard/logs is empty. When I remove this code from your GetLogs.zip:

rm -r "/tmp/${timestamp}"

rm "/tmp/${timestamp}.tar"

i can see folder with logs on /tmp partition but I can't find .tar file with logs. So maybe tar command don't working?

I attach today's logs in zip file.

Thanks too!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Thank you so much! I wait for this new version. Now I will test 8.0.0.r1919.gd1c9efc. :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
On shoot, sorry, I forgot I had provided them separately before. The code has already been merged into the master branch. You can grab mbtool_recovery from the "binaries" directory in the Windows builds or from the "assets" directory inside the apk.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Lets see if 8.0.0.r1921.g42b5e3e fixes it :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It looks like your recovery uses some non-standard options for its tar command. I've uploaded a new version of the GetLogs zip that should handle this (GetLogs-20151109.zip).

As far as the actual issue with booting the ROM, it looks like the boot.img might not have been successfully patched. It doesn't boot because it can't detect which slot it was installed to. Could you send me the broken boot.img file (in /sdcard/MultiBoot/[Your ROM]/boot.img) and also a link to the ROM itself? Thanks!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
[MENTION=4277844]chenxiaolong[/MENTION],

Now in DualBootUtilities 8.0.0.r1920 I have:

Internal SD Size: -1 MB

Free: -1 MB

and External SD size is correctly! :)

And could you help me in Extsd Slot error? When I flash patched zip in Recovery (Extsd slot) I have error (extsd_slot_flash_error.jpg).

I noticed:

(MultiBoot) - /system: /external_sd/multiboot/extsd-slot-test/system.img

(MultiBoot) - /cache: /cache/multiboot/extsd-slot-test/cache

(MultiBoot) - /data: /data/multiboot/extsd-slot-test/data

I have other mount point that /external_sd/ as External SD. I have:

Internal SD: /sdcard

External SD: /storage/sdcard1

so maybe here is the problem?

Thanks!
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Yeah, now logs file was generated correctly in /sdcard/logs. One small character "-". :D

My ROMs are booting correctly. I have two ROMs on /data partition but I can't flash ROM as Extsd slot and I think this is bad mount point. :)

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I doubt this will be a common use case, but restoring a backup stored on the external SD to an extsd-slot while booted into another extsd-slot stresses the fuse-exfat driver quite a bit and is very slow :p (Haven't tested Samsung's exfat kernel module, so unsure about that.) I'm guessing it's the journaled, non-sequential write to the ext4 image file that's killing the performance, not the sequential read from the backup. Or maybe my SD card is just slow. Anyway, restoring an 8.9GB backup of my primary ROM + data at 2.5MB/s is not very fun lol.

EDIT: It took a while but it worked. Restoring my backup of primary to extsd-slot-primarybak while I was still booted into CM worked.
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Here it is: https://dl.dropboxusercontent.com/u/7309753/daemon.log
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] this is the log I got after forced reboot into recovery, the AOSP 6 gets stuck at the SAMSUNG GALAXY TAB 3 logo if installed as secondary ROM!!, I've used the r1922 release

https://www.dropbox.com/s/7tjcfyj2k4bvhkz/20151110.003446.tar?dl=0

Thanks fur your time
[Galaxy S 4 i9505 Original Android Development] corncobman:
Thanks. I'll try it when I get home, I'm currently at work.
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
Could anyone help me?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
I'm sooo sorry, but it still doesn't work ??

Maybe I'm just unlucky ?

Anyway, here's the log

Thanks for all your hard work.
[Galaxy S 4 i9505 Original Android Development] corncobman:
I'm pleased to say that v1922 seems to work for the m3 i9305 now. I'm booting into Blisspop now. If this works properly, I'll try the other one.

Cyanide works too.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Backed up primary and restored to data-slot with r1922. Worked flawlessly and both booted. Hats off to you. Although a little cumbersome, at the moment, this is so beneficial even at this stage. I will continue to test. If there is anything you would like tested, let me know.

FWIW: I got the mbtool_recovery from the "binaries" directory in the Windows build. I got permission denied when I tried to execute from /tmp. Had to chmod 755 mbtool_recovery.
[Galaxy S 4 i9505 Original Android Development] Casual Gamer:
Hi [MENTION=4277844]chenxiaolong[/MENTION], you have fixed the bootloop for the ROM "Resurrection Remix v5.58 for GT-I9505"?
[Galaxy S 4 i9505 Original Android Development] todivefor:
DB Utilities problem

[MENTION=4277844]chenxiaolong[/MENTION], I backed up my primary restored to data-slot. Backed up data-slot, which worked great also. I then went into DB utilities and selected data-slot and checked to delete all. After deleting, I was left with /sdcard/multiboot/data-slot/boot.img, cache/multiboot had 2 data-slot directories. /data/multiboot/data-slot/data/...
[Galaxy S 4 i9505 Original Android Development] thag12:
Hey. I dont know what im doing wrong but i cant flash the cm 13 on my note 3. I tryed flashing as primary than as secondary and at last on sdcard. Here are some SC