yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Andycar:
Hi chenxiaolong, did you managed to add support for S3 mini?

Anyway, here is the link to the logs for GT-I8190 (ro.product.device=golden):

https://drive.google.com/uc?export=download&id=0B-WWoHMICGTgZXdIUXNSWFZmNlE

Thanks for your patcher!
[Galaxy S 4 i9505 Original Android Development] alahkel:
Hi.

This is the link for the aosp rom for hennessy, the one from the first multiboot log I attached. This gets flashed properly through twrp as primary.

https://drive.google.com/file/d/0B8XqHLzLoIRBdFVPcGUyNDFUOFE/view?usp=sharing

As I said before this is now my primary.

The assert preloader failed multiboot log (the second one) is from the miui.it rom (second multiboot log). I cannot link you that rom because miui.it has removed links for some technical problems and I dont know if multi miui roms from xiaomi.eu have the same zip/updater script structure. But I can attach here the original updater-script (the one causing the flashing failure as secondary/data slot through twrp after having the zip patched for dual booting) which is this https://drive.google.com/file/d/0B45XWDIN0gIKaHd6ZVE4VUZ1YjQ/view?usp=docslist_api

This is the zip structure (see pic attached below).

From the updater-script, scroll a lot to the bottom: I simply removed (from the patched zip) the string "

assert(write_preloader("preloader.img"));"

P. s. please note that the updater-script linked here is the one from the original unpatched rom zip!

Tell me if you need anything else :)

Oh and removing the assert preloader string I mentioned above just did the trick, it perfectly flashed the miui.it rom as data slot and I'm writing from that right now :)

If you understand what's wrong with aosp zip file it would be really great though.

Thank you again and sorry for bothering you so much!

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], looks like it flashed ok now. It tries to boot twice and then goes to recovery. With my limited knowledge, it looks like the selinux issue you mentioned. Attached logs.

EDIT: However, I noticed /data/multiboot/data-slot-mm/data is empty.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
[MENTION=4277844]chenxiaolong[/MENTION], I have been backing up all my slots via ADB and I just ran into a problem were it fails to finish backing up my primary. This has never happened before. What I noticed is that my data is over 4.4GB and it was always failing at the 4GB mark. So I uninstalled some apps and got so that my data is under 4GB and now it just backed up with no errors. Is there a limit on size in the backup commands? I have a 64GB SDcard that I use that is formatted with FAT32 so I have no issues with CM13. Thanks for the advice..
[Galaxy S 4 i9505 Original Android Development] alahkel:
So, new info for you.

There was an update for the aosp rom, it has a lot of fixes, mostly regarding the fingerprint sensor which is now working 100% (not bad since it is a non-miui rom).

So I patched it as primary (I read it is the best way to update primary rom) and flashed the patched zip via twrp. Failed.

Here's the multiboot.log file https://drive.google.com/file/d/0B45XWDIN0gIKcUo3Zll2NGVjeEk/view?usp=docslist_api

I noticed that the zip contains just a system.img and boot.img file, other than the meta-inf directory.

What do you think could be the problem?

EDIT: after a bit of searching on the web I found a workaround. It looks like that the multiboot system wasnt digesting the "write_raw_image("", "")," string, so I've replaced it simply with "package_extract_file("imagefile", "partitionblock");" and it succesfully got flashed.

Well, with imagefile, in this case, I meant boot.img and partitionblock was /dev/block/mmcblk0p7[emoji14]I'm gonna reboot to the updated primary rom, finger crossed!

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
The backup commands/tools have no *limitations , only issue it's the filesystem type of the medium to which the backup it's being saved to!

Look below for filesystem types and each file size they support!

FAT32 support up to 4096MB per file, you can save to this medium if your system file(>4GB) it's spilt, same tHing done by nandroid backups..splitting!

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

[New World Order (NWO)

Telegram it's better than Whatsapp In every way!]

---------------------------------------------------------------------
[Galaxy S 4 i9505 Original Android Development] chavdar:
Thanks for the hint. I saw the unpatched kernel backup after I restored a previous boot twrp backup ? Backup is always the way to go?.

Here is the kernel.log

https://www.dropbox.com/s/ixou3qgcc7kzjxg/kernel.log?dl=0

Thanks again for finding the time to look at my problem
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unfortunately, FAT32 filesystems cannot hold files larger than 4GB. You'll have to format your SD card as exFAT to store larger files. In the future, I'll probably add an option to split the backups over multiple files (like what TWRP does) to avoid hitting the 4GB mark.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'll take a look at it today. I spent all of yesterday being pissed that my brand new S7 Edge has a locked bootloader lol.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
It's matter of days before that's knocked out!

Knox my ass, as soon as I have mine!

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
So do you know if the mbtool supports the file splitting?
[Galaxy S 4 i9505 Original Android Development] Gerxp:
I found out that app sharing can be tricky.

Some apps like Playstore can not be shared. Well you can but then you will get trouble with app updating for that active Google account on any rom and even on other devices.

As soon as I disabled the sharing updating was fine again.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Nope...but can be implemented, the code can be written into the app...but for now I just keep my backups on my pc or emulated storage, hardly write them to extSD, [MENTION=4277844]chenxiaolong[/MENTION] is there a way that the backups can be compressed during backup?

Plz look into this if possible!

Thank you!

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] Gerxp:
[MENTION=4277844]chenxiaolong[/MENTION]

I have only the primary rom installed. But still there is an option in the 3dot menu to "wipe rom". I don't think it is smart to wipe it right. Maybe it's better to hide that option when there is only 1 rom installed.
[Galaxy S 4 i9505 Original Android Development] alahkel:
[MENTION=4277844]chenxiaolong[/MENTION] and anyone has info about it: is there any ways to backup/restore/swap the single multiboot roms?

I saw that app+aroma tool linked on op that should do the trick but it isnt compatible with my device I guess..

Is there a way to do it manually or with a script? like if I want to backup a rom eg as primary and then restore it in data slot..

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] kingknuts:
[MENTION=4277844]chenxiaolong[/MENTION] enjoy!!!!

https://android.googleapis.com/pack...3ec3e78cb2a7d3.signed-platina-ota-2576000.zip
[Galaxy S 4 i9505 Original Android Development] alahkel:
Wow thank you so much! You guided me even too much, I know a bit of adb and dos lol xD I just read it really quickly, I get it.

Thank you again, I'll try this asaI need it :)

I could think about making it a script.

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Regardless of how many ROMs are installed, the app will never let you wipe the ROM that is currently running :)
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=4277844]chenxiaolong[/MENTION]: Thanks for the hint. I saw the unpatched kernel backup after I restored a previous boot twrp backup ? Backup is always the way to go?.

Here is the kernel.log. Hope you find the problem, because since knox 0x1 I would very much like to play with DualBoot ?

https://www.dropbox.com/s/ixou3qgcc7kzjxg/kernel.log?dl=0

Thanks again for finding the time to look at my problem[/QUOTE]
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! (8.0.0.r2332.g6a2e8f5 EDIT: 8.0.0.r2333.g908c97f) Thanks to the libarchive library I use (https://github.com/libarchive/libarchive), adding support for compressed .tar archives was a breeze :)

The mbtool_recovery backup command now takes a "-c <compression>" argument (see "--help" for more info). For example, you can run:

MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup -r multi-slot-1 -c gzip

which will use gzip compression. The currently supported compression types are LZ4, gzip, and xz. LZ4 compression is very, very fast--sometimes even faster than no compression--but it compresses the least. gzip has pretty good compression ratios, but the backup will take longer to complete. xz is very CPU intensive and will take a very long time to complete, but will give you the smallest backups. Here's a quick unscientific benchmark I made backing up a CM nightly with no Gapps on the Galaxy S4:

| Compression type | Backup size | Time to backup | Time to restore |
|------------------|-------------|-----------------|-----------------|
| None | 507.2MiB | 39.14 seconds | 78.65 seconds |
| LZ4 | 350.9MiB | 23.65 seconds | 66.34 seconds |
| gzip | 287.4MiB | 122.13 seconds | 83.43 seconds |
| xz | 231.4MiB | 1024.52 seconds | 113.91 seconds |

Note that LZ4 is the default now. All backups will use LZ4 unless another compression type is specified (or "none" for no compression). There is quite literally no downside to this as it results in faster backups and smaller sizes.
[Galaxy S 4 i9505 Original Android Development] alahkel:
[MENTION=4277844]chenxiaolong[/MENTION] would you mind having a look at my previous posts? ???

EDIT: what a pity I cant seem to be able to share whatsapp data between aosp and miui rom.. on the miui part after activating whatsapp to be share, each time I try to open it, it just fc :(

EDIT2: I was able to capture a log from another app I tried to share on the miui side, here it is:https://drive.google.com/file/d/0B45XWDIN0gIKNlZHM1lhbE1VVGs/view?usp=docslist_api

Thats definitely a miui issue..

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Thanks a lot, this now it's a genius method to even compete with nandroid backups made by TWRP, backups sizes now ~50% less!

Really appreciate your interest in reviewing our suggestions/comments!

God bless every part/aspect of your life!

Later!!

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

[New World Order (NWO)

Telegram it's better than Whatsapp In every way!]

---------------------------------------------------------------------
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
Thank you so much for adding this!
[Galaxy S 4 i9505 Original Android Development] Gerxp:
[MENTION=4277844]chenxiaolong[/MENTION]

STweaks in JDCTeam AOSP 6.0 rom for jflte says my rom is not rooted. But it is.

I guess something is incompatible?
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear [MENTION=4277844]chenxiaolong[/MENTION], many excuses, but I wonder of you have seen my post:

http://xdaforums.com/showthread.php?p=65828137

Thanks in advance!

Thanks for adding compression!
[Galaxy S 4 i9505 Original Android Development] ewangw:
mbtool

[MENTION=4277844]chenxiaolong[/MENTION],

For reference, I'm using the Moto X Pure with DBP.

I know that the Mbtool is hard coded to mount the extsd at Raw/extsd and that seems to be causing some problems since some apps are looking for the sdcard under /storage/* and not raw/extsd. Not overly a big deal in primary. If booting to a secondary ROM in any slot, I normally get a notification that my sdcard is corrupted and needs to be formatted. On top of that, TiBu currently won't read the raw/extsd location so I can't restore my apps. Is there someway that mbtool can set the external sd to whatever is in the fstab file? I've tried MultiRom for MXP for comparison and found that the ROMs I loaded could see the external sd with no issues. In looking at some of the code it appears that MultiRom uses the following to determine location. I know you went down the path of naming the location due to the different external storage naming conventions used within different devices.

/devices/soc.0/f98a4900.sdhci/mmc_host /storage/sdcard1 auto nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd

Does this make any sense? Better yet, is this possible within DBP? I've been using DBP since I had my S4 (RIP) and was happy when you added MXP to the list.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I was not able to find anything that would indicate why it might reboot to recovery. Would you mind doing a quick test for me? Could you try rebooting to recovery and running:

adb shell 'echo TESTING > /sys/fs/pstore/testing'

and then reboot back into recovery and run:

adb shell cat /sys/fs/pstore/testing

Some devices have /sys/fs/pstore where small files can be saved in RAM and remain after a reboot. If this works, then I'll make a debug build for you that will put the kernel log there (because there doesn't seem to be any other way to get the log on your device).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2334.gbbcbcea :)
[Galaxy S 4 i9505 Original Android Development] alahkel:
Noooo my hero [MENTION=4277844]chenxiaolong[/MENTION] didn't answer me ??? ?

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Help The Peace:
Wait... Does that mean that the S6 isn't supported by the latest snapshot from https://snapshots.noobdev.io ??

Edit: Of course it is supported... ^^
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! I've added support in 8.0.0.r2337.g2f0d23d. Note that the stock Android 4.1 ROM won't be able to work since its system C library is too old to support some functions we use in the code.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm not sure what you mean? The Galaxy S6 (Flat & Edge) have been supported for a while now.
[Galaxy S 4 i9505 Original Android Development] Help The Peace:
Yes, I saw that as well now! But one question: I ended up with this!

What did I do wrong? I installed the Gapps and CM13 both in data slot...

Gesendet von meinem Nexus 9 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs. In /proc/last_kmsg, I actually don't see it trying to load the mbtool at all, which is concerning. Are you able to force it to boot to recovery after the first reboot? If so, could you grab the logs from there?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahh okay, so this seems to be the same issue that's affecting all of the MTK devices. Let's hope the META-INF/com/google/android/update-binary file is open-source in this ROM. The Lenovo K3 Note's update-binary is proprietary and closed-source which made it incredibly difficult to debug (and that's why it's still not fixed).
[Galaxy S 4 i9505 Original Android Development] alahkel:
Well at least it works using that workaround, I simply need to check the zips I wanna patch and it should work..

For miui roms there was only the assert preloader string, w/o it everything worked fine.

Now I'm using sMIUI as primary and aosp as data slot.

What about the log from the fc after the app sharing?

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah okay, so it's failing to mount the cache partition on your phone. Are you using F2FS or some other filesystem for /cache? Could you flash the GetLogs zip from https://snapshots.noobdev.io/ and send me the file it creates in /sdcard/logs/? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The /raw/extsd path is only supposed to be used by mbtool itself and when Android boots, it should also be mounted at /storage/*. (So when everything works, the SD card is available at both /raw/extsd and /storage/sdcard1.) I've only tested it on Samsung devices, so there's a possibility that Motorola does something different. For the SD card to have two mount points, mbtool must mount the SD card with the exact same options as Android. I suspect that's where the issue is occurring.

Could you trying taking a logcat starting from when you see the manufacturer logo until you see the lock screen? I think that should be enough to see how Android is trying to mount the SD card. Thanks!
[Galaxy S 4 i9505 Original Android Development] ShehabElkhaligy:
Please sir [MENTION=4277844]chenxiaolong[/MENTION] did u see my post ? I hope u will add it :)
[Galaxy S 4 i9505 Original Android Development] danon.brown:
Don't want to hi jack the thread but this could affect your next device if it's samsung with a locked bootloader. If yall get a minute please sign and share.

https://www.change.org/p/samsung-unlock-boot-loaders-s7-s7-edge?recruiter=508719311
[Galaxy S 4 i9505 Original Android Development] ShehabElkhaligy:
Thank you very much ?
[Galaxy S 4 i9505 Original Android Development] gaww:
Signing over on S7 root thread.

Back to this thread - if duel boot without root will work, would that be possible here or does the locked bootloader block everything?
[Galaxy S 4 i9505 Original Android Development] danon.brown:
No dual boot without rooting. Locked bootloader would kill this patcher app.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
The first command tells me that system can't find the path specified!

Anyway the issue here it's that, after installing anywhere except primary .... ROM doesn't boot successfully....after the Samsung logo, the device screen remains black for eternity, it's not booting into recovery...it's just black screen till I'm pissed and intervene!

I've moved the ROM to diff slots and same results, it only boots only if ROM is primary....

I'm good for now,I moved my TW to data-slot-* from primary and it works well, so I'll install this AOSP as primary!

Thanks

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

[New World Order (NWO)

Telegram it's better than Whatsapp In every way!]

---------------------------------------------------------------------
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2338.gb35f622 might (hopefully) fix the preloader and write_raw_image() issues for hennessy. As for the app sharing FC, I'm guessing it's an issue with MIUI. I'm not really sure how to fix that.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I thought I answered that already? :) http://xdaforums.com/showpost.php?p=65858637&postcount=8820

Nevermind, looks like you saw it :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It would still require a custom recovery, so unfortunately, the patcher will not work on the US S7 devices.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes please. If anyone has a United States S7 variant and wants to see dual booting work on the S7 series, please sign the petition at the link above and also head to: http://xdaforums.com/tmobile-s7-edge/how-to/root-discussion-future-sticky-root-t3327399
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you send me the /sdcard/MultiBoot.log file it created? Thanks!
[Galaxy S 4 i9505 Original Android Development] alahkel:
Thank you so much! :) I'll try with unmodified zips and report back.

Btw I guess miui roms are simply incompatibile with any other aosp, just like tw roms with cm based are.

Thank you again!

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I just flashed that ROM (AOSP-6.0-20160314-jflte.zip) to multi-slot-1 and STweaks isn't having any trouble with root. Is root access for the app disabled in SuperSU?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Soon EDIT: It's here! 8.0.0.r2341.g1ad57eb

EDIT: Live theme reloading without restarting the app or interrupting patching:

[youtube]cfJcsQaa5co[/youtube]
[Galaxy S 4 i9505 Original Android Development] Gerxp:
[MENTION=4277844]chenxiaolong[/MENTION]

Thanks for the beautiful app.

Can I use 3C Toolbox to restore backed up apps and data?

Restore knows 4 options :

-To internal memory

- to system

- to SD card

- only data and settings
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=4277844]

SOLVED: I had to format again chache in twrp in ext4 and now patching ramdisk works fine!

Thanks for pointing me in that direction!
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
I use this APP on all my devices, of course you can restore with it! , you can restore with anything that had made the backup!

If restore app days after enabling sharing from ROM x.

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] todivefor:
Here you go. Looks the same to me.

EDIT: patched with 2341 in windows.

EDIT2: Something is not getting flashed /data/multiboot/data-slot-mm/data is empty.

Second problem: I have primary (custom rom), data-slot-stockol1 (stock ol1 from odin tar we worked on before), and data-slot-mm (my mm odin tar with problem above). Somewhere along the line I discovered I lost my link to /sdcard (it is empty). This is the emulated sdcard on the S6 (ie /mnt/sdcard). /mnt/sdcard looks the way it should /sdcard is empty. I restored from a TWRP backup which had parts of data-slot-mm laying around. Also /sdcard looked fine. I deleted the data-slot-mm remnants and this broke my /sdcard as before. I restored with TWRP again, and reflashed data-slot-mm. /sdcard looked fine. Did wipe of data-slot-mm from DB app. /sdcard is broken again. There must be a symlink that is incorrect and is getting broken when the data-slot-mm is being removed. Hope you can make some sense of these 2 problems.
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

Thanks for all your help on this one! Here is the log I was able to capture. It's probably more than you need.
[Galaxy S 4 i9505 Original Android Development] Help The Peace:
Here you go:

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

Hope you can help me!
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Is it compatible with the s7 edge yet?
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] or the room at large, I'm having this issue where switching a ROM and rebooting, the system booted is not what I chose, the rom switch and as soon as leaving the app or rebooting the app reset it's self to the other ROM I don't want to boot!
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Edited
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Well seems like this is once again completely broken on the Exynos Note 4:

Patched kernel zip's either can't flash or wipe the system and don't place anything back (TW),

Flashing just the kernel from the patched zip=stuck on the boot logo about 10 min and then reboots in recovery (TW),

Flashing patched CM13 same bootloop as with patched kernels,

App can't update ramdisk, reports that it can't flash kernel.

I just leave this report here for now, will post the logs once I'm back from the dentist, sorry for this, I'm kind of in a hurry right now.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It looks like the log is from flashing cm-13.0-20160312-UNOFFICIAL-zerofltexx_data-slot-cm13.zip and not the open-gapps zip from your screenshot before? The log is overwritten each time you flash a patched file, so could you grab the logs right after flashing the gapps that failed before? Thanks!