yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Works fine here on RR 5.7.4, all backups are on the extsd. Make sure you have full read/write permissions for the card. r43 build. [MENTION=4277844]chenxiaolong[/MENTION] I'm happy to report that after you reconfigured the background service I'm no more experiencing freezes while backup/restore. :highfive:
[Galaxy S 4 i9505 Original Android Development] Steven1962:
How do you grant those full permissions?
[Galaxy S 4 i9505 Original Android Development] corsicanu:
With r43 can't restore even from internal, being on data-slot. With r18 it works but i run out of space before restore is finished since my phone has only 16gb. When [MENTION=4277844]chenxiaolong[/MENTION] posted first 9.1.0 test builds i grabbed that (had still 9.0.0 tag) and worked like a charm everything. That was the moment i switched roms :) . Now can't do that. Even flashed today stock rom with odin and repartition, formatted all data, even sdcard and same thing.. :( Cheers!
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I already answered you regarding your concern. You can't bring back to original zip.

---------- Post added at 18:21 ---------- Previous post was at 18:20 ----------

Xposed and XInternalSD module. :)

If you're on Nougat where still no Xposed support there is a manual way doing it of course.

---------- Post added at 18:28 ---------- Previous post was at 18:21 ----------

I assume your backup location in settings is correct?
[Galaxy S 4 i9505 Original Android Development] Steven1962:
You mind specifying how to do that? Couldn't find a link...
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I don't think the size of the card does matter. It's not strange, this is the full path to the card, the /sdcard1 is symlink as often /sdcard is symlink of /storage/sdcard0 and so on.
[Galaxy S 4 i9505 Original Android Development] corsicanu:
Ofcourse. I will try each version released of 9.1.0 in few hours to see what's the commit that makes me issues. In primary sdcard is mounted as storage/path but in data slot is mounted as /mnt/media_rw/path. With storage i can restore from external sd. Seems like mnt/media_rw screws my paths. Forgot to mention that i can make backups even to that location but after the backup is made it won't show in flash menu..

[MENTION=4277844]chenxiaolong[/MENTION] - [MENTION=4467979]Steven1962[/MENTION] has the same issue i think...
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4467979]Steven1962[/MENTION]: I think CM14 should write to the extsd no problem, hell that's the reason we use CM - to break the barriers! lol :p Try this:

Go to /system/ect/permissions/platform.xml

Open it and add this code:

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="media_rw" />
<group gid="sdcard_rw" />
</permission>

Save the file.

Then go to /data/system/packages.xml, open the file and check if you have this line, if not add it:

<item name="android.permission.WRITE_EXTERNAL_STORAGE" granted="true" flags="0" />

Save the changes. Reboot. Done. ;)

Don't forget you need to be rooted to apply these changes.
[Galaxy S 4 i9505 Original Android Development] v00d007:
The produced zip file is corrupt, can't be opened by any app.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, it looks like the kernel log is missing. When (relative to the boot loops) did you reboot to TWRP? Would you mind pressing the key combo for booting to recovery while it boot loops and then grab the logs? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah yes, this is an SELinux issue. I'll look into it and see if I can come up with a fix.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! It looks like system.img is getting corrupted. When you formatted your external SD, did you use FAT32 or exFAT? The system.img is slightly over 4GB which cannot be stored on a FAT32-formatted drive.
[Galaxy S 4 i9505 Original Android Development] draymond1987:
I wanna say exFAT,but don't remember? BUT I do remember that when I booted back into Android, I had to format again, using Android's method. Should I format it within TWRP to exFAT and try again? I certainly don't mind! The reason I formatted again, is because I got an error.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The backup name should be set to the entire folder name, so "norma.12.03-19.34.57_primary" in your case.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Please give the test build here a try: https://github.com/chenxiaolong/DualBootPatcher/pull/330
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
I'm testing now, thank you,
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you post the log after you flash from recovery? I'm not sure what's going on. It's failing with no details about the error.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, it hasn't been fixed (in any version) yet. It is more complicated to fix than it seems. If you set the kernel for that ROM, you should no longer see the message.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is a known issue. It has to do with the new permissions system in Android 6.0+. I haven't had time to fix this yet, but in the meantime, your best bet is to copy that backup to the internal storage and restore it from there.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Are you on the latest bootloader by chance? This used to be an issue on the S4 also with an older bootloader. There isn't too much I can do about this since it freezes before any of the multiboot code runs.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you link to the file you flashed? It looks like all the system files are missing for that ROM, which is quite concerning.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, that should work just fine.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Yes. I'm on latest everything
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, this is a known issue :) I'll fix it this weekend. Basically, the reason is that no apps are allowed to access the /mnt/media_rw/ paths. The only way to access files on the external SD is using the Storage Framework API, which DualBootPatcher is not doing (for that specific feature only).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Wait, restoring from /sdcard fails too? What error does it give you?
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
[MENTION=4277844]chenxiaolong[/MENTION] everything seems to be patching fine but I'm getting hung on the splash screen. I can restore just fine with the original kernel. I don't know if it would be an issue with Superuser writing to data now because it matches the ram disk with the update binary maybe you would know more than that but that is what I'm getting right now
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I had to revert the change to fix the original MIUI flashing issue (which in turn broke everything else). This problem should no longer happen in 9.1.0.r45.g71e6b4f and newer.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This should hopefully be fixed in 9.1.0.r45.g71e6b4f.

This unfortunately requires a significant amount of work to fix. It is currently a lower priority issue on my list. :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
When you get the 5 vibrations and get kicked into recovery, can you flash the GetLogs zip and attach the log archive it creates? That's the only way I can get the kernel log. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[ 10.833046] <5>.(5)[1:init]SELinux: avtab: invalid type or class

Hmm, that looks very bad. Looks like the patcher patched the SELinux policy in a way that the kernel doesn't like. Can you upload your /sepolicy file from the ramdisk?

EDIT: Wow, your device has both /proc/last_kmsg and /sys/fs/pstore/console-ramoops. That's impressive. I've run into some very troublesome devices that don't preserve the kernel log across a reboot (ahem... Note 3).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
When it hangs at the splash screen, can you force reboot to recovery and grab /sys/fs/pstore/console-ramoops? (or flash the GetLogs zip, which includes the file) Thanks!
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Here is the logs, had to rename to .zip in order to upload.

http://cloud.tapatalk.com/s/5848e5ed4ce2a/20161207.222635.tar.gz.zip
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
Chenxiaolong,

It happen on my more 3 when I want to flashing new Rom to my primary. Before that I have done my wipe in utilities.
[Galaxy S 4 i9505 Original Android Development] Mike0505:
Yes in 9.1.0.r45 flashing non miui roms works :) . But miui not working

It's ok to have on primary 9.1.0.r45 for flashing non miui and on secondary rom 9.1.0.r43 for flashing miui roms ?

Thank You ! :good:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yup, I also think it's a kernel issue. The donor rom was running on 3.10.65 and I'm trying to port it to 3.18.19, talked to two other guys they also fail to boot it on 3.8.19

Meanwhile thanks Mr, yes I also see these kind of logs, basically they say nothing. And this is mtk device you know. :D
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
https://download.cyanogenmod.org/get/jenkins/188239/cm-14.1-20161206-NIGHTLY-oneplus3.zip
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
He means he needs the rom zip. :)
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
https://download.cyanogenmod.org/get/jenkins/188239/cm-14.1-20161206-NIGHTLY-oneplus3.zip with the newest Dual Boot patcher it Works. but i can't switch between mm and Nougat rom
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
Here you go,
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] After some reading I came up to a conclusion that the error I'm getting here:

[ 11.240226] <2>.(2)[1:init]SELinux: avtab: invalid type or class
[ 11.246134] <2>.(2)[1:init]init: SELinux: Could not load policy: Invalid argument
[ 11.247183] <2>.(2)[1:init]init: failed to load policy: Invalid argument
[ 11.248018] <2>.(2)[1:init]init: Security failure; rebooting into recovery mode...

is due to a missing SELinux patches in the kernel for Nougat. I think there is no other way fixing this other than recompiling the kernel.

My other port CM14.1 is failing to mount the fstab for some reason. I double checked the values in the boot image. I added a log for it. Btw the new console-ramoops log is awesome! I'm directly going to it disregarding the other info from getlogs. :)

[ 30.602565] <0>.(0)[1:init]mblog: Failed to mount /dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system (ext4) at /raw/system: No such file or directory
[ 30.604548] <0>.(0)[1:init]mblog: /raw/system: Failed to mount all 1 fstab entries
[ 30.605539] <0>.(0)[1:init]mblog: Failed to mount /raw/system
[ 30.606511] <0>.(0)[1:init]mblog: Failed to mount fstab
[Galaxy S 4 i9505 Original Android Development] serjbrest:
Dualboot

Hi! Can you add support dualbut, ZTE blade L3? (MTK6582)
[Galaxy S 4 i9505 Original Android Development] Eleo:
Just flash the GetLogs zip from https://dbp.noobdev.io/downloads/ and share the tarball it creates in /sdcard/logs/ (file extension is tar.gz)

This will aid developer to support your phone for dualboot.

Cheers
[Galaxy S 4 i9505 Original Android Development] jaskaran Singh1:
support

Can you please support galaxy note 3 neo hl3g version.:fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] Eleo:
Are you sure it doesnt? (Check attachment)

If you are sure it doesnt, then read just only one post above yours.

Cheers
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
chenxialong, i had try to change the name as entire folder name, but when come to recovery flashing the zip , its give me error flashing zip.

any problem causes it ?
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
[MENTION=4277844]chenxiaolong[/MENTION] disregard where I said it was not working it must have just been the original ROM I was trying to use

It is working good on the LG v20 I have successfully dual boot it into secondary and multislot.. Thank you so much
[Galaxy S 4 i9505 Original Android Development] jaskaran Singh1:
Actually the note 3 neo here is hlte and mine is hl3g. And how do i share tarball file.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Getlogs zip link works.

Why dont you read my post above? It states everything you need to know. You flash the zip file in recovery
[Galaxy S 4 i9505 Original Android Development] jaskaran Singh1:
How do i use the tarball file which is in logs folder.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Read
[Galaxy S 4 i9505 Original Android Development] Araltd:
Wow. I would love to see a rom with those feature for the note 4 (N910T).

Sent from my Note 6
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
After switching Rom with DualbootUtilities.zip, if I select reboot within the utilities, it always reboot into recovery. In order to boot into system, I have to select "Exit to Recovery" then Reboot System. Is this a bug or by design?

Sent from my N910P on Stock PH4 Rom, Ram Kernel
[Galaxy S 4 i9505 Original Android Development] Eleo:
I dont have that. I switch ROMs in utilities and reboot from within utilities. My utilities version is 9.1.0.r43
[Galaxy S 4 i9505 Original Android Development] jaskaran Singh1:
Sorry for the incovinence eleo. I thought to share file with app..
[Galaxy S 4 i9505 Original Android Development] draymond1987:
[MENTION=4277844]chenxiaolong[/MENTION] and everybody, I wanted to report that I finally got dualboot to boot into extsd on my T-mobile LG G4! YAY!

There's a slight problem, because why wouldn't there be with me LOL. I converted my /data and /cache to F2FS and I have AOSPC as my primary and I successful am booting into AICP, as we type! My problem is that, when I tried a stock based ROM, it would vibrate 5 times and throw me back into recovery. I DID patch an F2FS kernel and flashed it.

So my question to you, and anybody else: Does both ROM and kernel need to have support for F2FS? I only tried EXTSD slot for stock. And like I mentioned, I am currently facing no issues in booting another CM/AOSP based ROM.

EDIT: switched back to EXT4 and flashed stock as Primary and put AOSPC as EXT. Now my phone will only hang at bootloader screen when I try to switch to second ROM. I'm sorry for being a pain, I really am. I'm using the most up to date version of the app.

EDIT 2: Switched kernels and just let it sit at splash screen.........booting now. Please, forgive me, senpai ! Don't know if it was the kernel or I was just too impatient to let it boot past the splash screen.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The issue that some people are encountering with the in-app flasher where the /proc/self/fd/<fd number> symlink cannot be resolved is fixed in 9.1.0.r51.g120ecc4. There's no need to repatch anything. Just update the app.
[Galaxy S 4 i9505 Original Android Development] smitharro:
This latest version wants to update the mbtool. But it won't let me... It's telling me it needs root, but it does not ask for it! So it fails to update. How do I 'force' the app to ask for root? Primary rom: CyanMod 14.1. Device: Moto G4 Plus (XT1642).
[Galaxy S 4 i9505 Original Android Development] mbr007:
Error...current version mbtool is old, when updated it failed.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you grab a logcat after running into this error? I can't seem to reproduce the issue.
[Galaxy S 4 i9505 Original Android Development] rifle007:
i have this issue too
[Galaxy S 4 i9505 Original Android Development] am2010r:
Hi there,,

I have a problems with the app

First I have the note 8.0 (Gt-N5100) (3g version)

When flash a patched zip file from recovery I got error messages that my device model is Gt-N5100 not "kona3g"

But I solved by ignoring the device name or flashing the zip from the app.

Second : I can't boot any secondary rom. Tried many roms and different locations (extsd,data,multi slot) always stuck at booting animation for the second rom. I noticed that data partion size of the second rom is always 69.82mb.

Log file and screen shots are attached

Sorry for my bad English.

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] smitharro:
Sorry, here's my logcathttp://cloud.tapatalk.com/s/584d2d74549df/alogcat.2016-12-11-11-27-10+0100.txt
[Galaxy S 4 i9505 Original Android Development] umuturunc:
First of all thank you for this amazing tool.

My device is S4 Mini. My parimary rom is TW 4.4.2 kitkat. I patched MIUI V8(Android 6.0.1)

When I try to flash patched dual rom from in app. I got an error.

So I tried to flash it in twrp recovery. But this way failed too.

After flashed dual rom, used GetLogs zip file to get logs.

I can see the secondary rom in ROMs tab, but can't switch. It fails.

Can you help me
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi, according to a previous post of [MENTION=4277844]chenxiaolong[/MENTION] he said the issue is fixed in build r51. Make sure you're using r51 and up.
[Galaxy S 4 i9505 Original Android Development] mbr007:
Failed during first initializing with version 9.1.56.
[Galaxy S 4 i9505 Original Android Development] draymond1987:
Hey [MENTION=4277844]chenxiaolong[/MENTION] ! So I'm really not trying to be a pain, I swear! R45 is working flawlessly on my H811 (LG G4) . Couldn't update because of the root issues that two people have mentioned, but that's not the problem. I rather stick to whats working :P

It seems that every ROM I flash on an EXTSD NEEDS another kernel to boot, which would be Llama kernel. As stated before, I WAS converted to F2FS but I'm not anymore. I have waited and waited and waited, but it will not boot unless I have this particular kernel. Like I said, my ROMs all boot up completely fine with this kernel, so if that's what I have to do, than so be it. BUT I just wanted to bring it to your attention, in case it's the app?

I couldn't update your app because of it needing root and I just don't get the dialogue to request root, nor do I see it within SuperSU app. Please don't think I'm just complaining /: I have four ROMs that boot flawlessly!! And I value all your hard work!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm aware of the mbtool root issue and I'm able to reproduce it now. The issue is that mbtool is successfully started with root (despite what the error message says), but it reports the wrong version number. mbtool reports itself as just "9.1.0" (equivalent to "9.1.0.r0"), but the app is expecting "9.1.0.r56" or newer. Thus, the app thinks that the update failed. This has actually been broken for a very long time, but I never noticed it because we haven't had any major changes that required bumping the minimum version for a long time. I'm working on a fix for this now.

EDIT: It was first broken in 8.0.0.r2289.ga4b1564

EDIT2: The problem is resolved in 9.1.0.r63.g5da8137
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION], Yup, I have the issue too. No worries, I'll use an older build till you fix it.

Oh I see you fixed it in r63, thanks! :)
[Galaxy S 4 i9505 Original Android Development] smitharro:
Yup, r63 working fine! Just patched and updated my secondary rom without an issue! Thanks for the effort.
[Galaxy S 4 i9505 Original Android Development] fishersfish:
1.

The FC issue doesn't matter to me myself actually.:o

2.

Thanks a lot for fixing the current issues, now I can patch, flash and manage my ROMs smoothly...:good::laugh:

3.

Found a strange issue:

My device:oneplus2

Zips: supersu_2.78_SR5(patched by DBP_v9.1.0.63), AOSP-CAF 6.0 (patched by DBP_v9.1.0.63)

My situation:

a).Freshly installed them via DBP app(v9.1.0.63), no error. But after rebooted to the target system and opened SuperSU APP, it says: No su binary installed and SuperSU cannot install it, but the file(su) just sits there:/raw/data/multiboot/$romname/system/xbin/su .

b).Freshly installed them via TWRP, SuperSU is functional in the target system.

I tried to patch both supersu2.78_SR5 and ROM zips by DBP_8.0.0.2709, the issue exists. It does not matter, just be sort of annoying.

Here are the logs generated by GetLogs-20161128-1.zip

after installed zips via DBP app: View attachment 19700117.044854.tar.gz

after installed zips via TWRP:View attachment 19700117.051337.tar.gz

BEST WISHES!
[Galaxy S 4 i9505 Original Android Development] pehoko:
[MENTION=4277844]chenxiaolong[/MENTION] any chance to see working version for miui rom?
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
What could possibly forcing me to pull battery on reboot?
[Galaxy S 4 i9505 Original Android Development] buddhatrip:
Not able to flash any 7.1.1 based rom (like CM 14.1, RR, Mokee, AICP etc.) in any slot released after 1st. December 16. I patched the zip file from 9.0.0 r71 to 9.1.0 r63 version of DBP but no success. Any solution ?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yup, I already used quite a lot MIUI 7/8 roms back in time. :) Now I'm just not using miui, because it's not my cup of tea. Always feels laggy compared to CM/AOSP.

---------- Post added at 15:53 ---------- Previous post was at 15:47 ----------

Nobody can say what's going on without a log.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Yea. I'm on fph3

---------- Post added at 04:10 PM ---------- Previous post was at 04:09 PM ----------

I found that 7.1 Roms need to be primary or secondary. Idk why ?
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
I realize it is better to just select ROM and then power off wait a couple seconds then reboot that way I get no hangs
[Galaxy S 4 i9505 Original Android Development] umuturunc:
Thanks for reply. Installed 9.1.0.r63.g5da8137-snapshot version. But still having issue. [MENTION=4277844]chenxiaolong[/MENTION] Can you have a look
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Try to flash in recovery.

---------- Post added at 20:47 ---------- Previous post was at 20:46 ----------

I have 7.1 rom installed to extsd-slot and works just fine. ;)

Depends on the phone.
[Galaxy S 4 i9505 Original Android Development] pehoko:
Well I don't like it too, but I need this rom ... and still can't flash as always same error "miui_update bla bla ...".
[Galaxy S 4 i9505 Original Android Development] umuturunc:
symlinks failed again :(

[MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, that sounds like a bug in AROMA. There's probably not much I can do to fix it.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, it looks like with the CM14.1 kernel, the paths are detected in /dev/block/platform/mtk-msdc.0/by-name instead of /dev/block/platform/mtk-msdc.0/11230000.msdc0/[/red]by-name as specified in the fstab. :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Can you link to the ROMs you're trying to flash? It looks like the boot.img might not have gotten patched. I don't see any multiboot components in the log which suggests that it's trying to boot the ROM as if it were the primary ROM.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Support for hl3g has been added in version 9.1.0.r65.g0c4207b.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It looks like you ran out of space:

failed to mkdir /system/etc/firmware/wcd9310/wcd9310_mbhc.bin: No space left on device

You won't be able to use the secondary slot because the /system partition is too small to fix the two ROMs. If your /cache partition is big enough, you can use a multi-slot, which installs to /cache. If not, you can use a data-slot, which installs to /data. You can check how much space you have from the app.