yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION] trying to flash a new rom into data-slot-cm11f2fs on my Nexus 7 (2012). It flashes boot splash twice then goes to recovery. In looking at the logs, it looks like I have a mismatch between ext4 and f2fs. My main system is cache and data are f2fs and system is ext4. I think what I am trying to flash maybe all f2fs. This all gets beyond my knowledge. Not sure what rom requirements are for secondary roms when primary is a mixture of ext4 and f2fs.

Thanks for any help you can provide.

EDIT: I guess by this it shouldn't matter? However, looking at logs again, it looks like failing to mount system (f2fs), but my primary is ext4?

EDIT 2: Thought I had this figured out. Tried getting system to ext4. Closer, but no cigar. Logs-20151113.171628.

EDIT3: Primary is Data and Cache f2fs, system ext4. First log is flashing secondary rom (data-slot) all f2fs. Cache would go to primary cache (both f2fs, so OK). System and Data would go to primary data which is f2fs (so should be OK), but doesn't work. Second log flashing secondary rom (data-slot), with Data and Cache f2fs and system ext4. I wouldn't expect this to work. I think I am lost.

EDIT4: Tried another rom that is a newer version of primary. Same result as others. Hardware splash twice then recovery. Flashed getlogs. When I rebooted, logs.tar was zero bytes. For the first time I looked at /raw. /raw/cache/multiboot/slot/cache/recovery/nnnnnnnnnnnnnnnnnnnnnnnnn was all that was there. /raw/data/multiboot/slot/data was empty and /raw/data/multiboot/slot/system contained what I would expect.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Maybe by now you found a solution mate, but try the latest version and it will work, I too experienced that bug before using r1927!!

Fur sure it'll work for you too....
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Try this:

1. Open your build.prop.

2. Add

ro.patcher.device=[I][name_of_your_device][/SIZE][/I]

.

3. Try again.

Examples:

ro.patcher.device=hlte
ro.patcher.device=lgg2
ro.patcher.device=noblelte
[/SIZE]
[Galaxy S 4 i9505 Original Android Development] corncobman:
Actually, I installed a ROM with Aroma installer to extSD on my S5 and it worked fine...

:confused:
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
[MENTION=4277844]chenxiaolong[/MENTION]

New problem :P

When I am on primary ROM or on ROM on data slots I don't see versions and builds of ROMs on Extsd slots.

But when I am on Extsd slot I see versions and builds of all ROMs.

I don't know why it is. :)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Don't reboot from aroma and it will work, I've got installed 4.4.2 aroma install as my 3rd ROM to LL & MM
[Galaxy S 4 i9505 Original Android Development] monkteo:
Great, I try 5-6 day a go and I fail so I will try again!

THX:good:
[Galaxy S 4 i9505 Original Android Development] remowrx:
Which 4.4.2 rom are u using for N-9005. I have tried Multi-X Rom with no luck.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
http://xdaforums.com/showthread.php?p=63796690

Look at the pic I uploaded on the above link!that's MIUI 4.4.2
[Galaxy S 4 i9505 Original Android Development] Andycar:
Thanks! I found the solution, it worked on r1297!

(But I'm not sure if it really depends on the patcher version itself...)

See, the thing is that after I selected "Patch files" menu item in patcher, android asked me "Do you want to give access to files, photos, etc.. to this app?"

After I answered "yes", everything worked from now on, including saving the images and names for ROMs ... And apps sharing also stayed "on".

So I think it has to do with new permissions model in Marshmallow :) Anyway thanks :)

---------- Post added at 12:48 PM ---------- Previous post was at 12:43 PM ----------

Another question to all friends here and [MENTION=4277844]chenxiaolong[/MENTION]

There were a lot of talks here on the thread about using mbtool (?) for backup and recovery of ROMs while in recovery... How should I do this, exactly?

Sorry, didn't find it anywhere here on the thread... Thanks.
[Galaxy S 4 i9505 Original Android Development] Ather:
Thanks, now i have another problem, i cant update ramdisk, it failed..even switching roms it fails but its actually done, when i rebooted my phone it rebooted to CM rom...its the first time im having this issue
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
I have tried a different ROM (CM 12.1) but it still fails ?

In app flashing it gives some bad address error.. I'm attaching its log

In TWRP, it passes Patching image unconditionally (finally ? ) but fails after showing CM 12 by MDSteam.. But it doesn't make a log.. Don't know why. So, attaching a screenshot..

P.S.: I'm not sure if this is a bug of the Patcher, but anyway it's annoying.. Here's what, there is something called System data taking something more than 2 GB from my External SD.. Why I'm mentioning it here? Because I think it is due to the Patcher as when I delete the system.img from /sdcard1/multiboot/extsd-slot/ no space is regained.. And it was 10 GB last time.. And I had to format the SD card to get it back. Now, it's starting again.. So, please tell me if there is any possibility that the Patcher could be the reason for this.

Thanks
[Galaxy S 4 i9505 Original Android Development] thag12:
I had simmilar problem. But when I watched YT video and i installed it on data slot (1) it worked. In same slot u must patch gapps. And both flash from recovery
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], I feel like i'm double teaming you. Since there is little or no development on the Galaxy S6, I have to get my tech fix somewhere else, ie Nexus 7 and Dual Boot. I tried the backup on my Nexus 7 and it gets no where. I was developing a script for backup (so I wouldn't have to copy/paste the commands all the time). I ran into an error and after much consternation (my scripting skills are poor), I figured out the problem was with mbtool_recovery. This is what I get:

UserMacbookPro:platform-tools User$ ./adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup -r primary -n optipop
/tmp/mbtool_recovery: line 1: syntax error: unexpected ")"

I connected my S6 and ran the same command and it worked fine. The mbtool_recovery is pushed to both from the same location.
[Galaxy S 4 i9505 Original Android Development] pvsgh:
Great job done on making this Dual patcher.

Not sure how easy it is to add support for more devices, but would like to run it on my Galaxy Note 8 tab.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Download the getlogs_20151109.zip (https://snapshots.noobdev.io/) and flash it from your custom recovery(TWRP) then find logs in your "internal storage"/logs , then send that file to Chen and ask him to add SUPPORT for your note 8 , and he'll help, he's being awesome to everyone!
[Galaxy S 4 i9505 Original Android Development] pvsgh:
Thanks, will send the logs to OP.
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Ok, i have found another problem. I have used 'Set kernel' and 'Update ramdisk'. The problem i have now is that when i use 'Update ramdisk' and reboots, then my Galaxy S6 edge+ goes into a bootloop.

The only way to get out of the bootloop now is to re-flash the latest kernel i use. Because flashing the kernel again removes the 'Update ramdisk' thing.

Do you want some new log files for that 'chenxiaolong' ?
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
...well that's true flashing latest kernel also help, but that's NOT the ONLY WAY TO GET OUT OF BOOT LOOPS

This also helps:

While in TWRP go to INSTALL then select IMAGES( bottom right corner) browse to your INTERNAL MEMORY/ Multiboot/primary(or which ever ROM you've updated the mbtool from) select "boot.img.before-ramdisk-update.img" and select BOOT from TRWP then SWIPE TO CONFIRM FLASH...done, reboot and you're back to where you were before updating ramdisk!!

No more bootloop and no need flash kernel again!

...........

Working around ramdisk update:

..........

Go to the Multiboot folder on your internal memory, then delete the boot.img in the primary folder(or whatever rom you want)

Open the Multiboot patcher again, set kernel, reboot as requested, now check in rom settings if mbtool has any updated version, this MOSTLY works!
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
That didn't work.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Hmmmm
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Sorry about this being off topic to your current situation, but I noticed from the changelog that app sharing has been taken out or something like that. Are there any plans to bring it back in the future?
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
App sharing it's there and WORKING perfectly well...

Only global app sharing is removed!

Check it!!
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Ah thanks [MENTION=6080477]danerrickcuba@gmail.com[/MENTION] ! Haven't checked the app in a while so sorry about that. I'm gonna try it out now! :D
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Update: Apologies for bugging you about this, but unfortunately for me it isn't working on the LG G4, I don't know if it's because I'm doing something wrong though. I'm using build r1927.g47f1396 and when I enable app sharing on the primary ROM, and choose the apps I want to share, they don't show on the list of apps I can share on secondary ROM at all.

I also tried installing an app on both ROMs (since there's only a check box saying 'share data'), but the data didn't appear to be transferred to the other ROM.
[Galaxy S 4 i9505 Original Android Development] Andycar:
You have to install app in one ROM (let's say, primary), enable data sharing for it, then reboot this ROM. The data will appear like blank now. This is the moment when you actually might want to use Titanium Backup to restore your previously saved data of the app.

After ensuring your app is working as before on primary ROM, reboot to other ROM.

Install your up there, enable data sharing and reboot that ROM. Voila, your data should now be shared across two ROMs. [emoji6]
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Ah okay, thank you! I'll try it out later and let you know if it works :D
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
I'm using the feature on 3 devices and had not encountered any issues thus far::

1.I enabled app sharing from 1°, chose my app then rebooted, tested the app from 1° to make sure that it still has the same data and settings it did before activating app sharing!

2.switched to 2° ROM, installed same app i enabled for sharing from 1° ROM, if this was done properly as you pick up the app for sharing on other ROMS, you'll see a dialog telling you which other ROMS are sharing data of the same apk!

Then reboot once you're done, and test the app.

This should be working fine!
[Galaxy S 4 i9505 Original Android Development] Andycar:
Maybe, you've find the solution by now, m8...

But have you tried mbtool for 32 bits as per original instruction by Chen?

Here:
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Thanks for the info! I guess I just had no idea what I was doing XD
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
See my post here, where I discovered that if I set the kernel then reboot and then update the ramdisk

the phone does into recovery. Can you try to set the kernel and update the ramdisk right after that without rebooting?

You can try the 1778 build to participate in my research what's broken in the latest build mate.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Xposed framework installer for android M is out today and running very well ( modules might not be 100% compatible)

1.android M xposed thread:

http://xdaforums.com/showthread.php?t=3249095

2.download thread for LL-M

http://xdaforums.com/showthread.php?t=3034811
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Coming soon :) A new screen that shows the details of a particular ROM. (Yes, the background is dynamically loaded from the ROM's wallpaper.)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] Good to see that to backup ROMS Won't be as manual as it is currently, thanks for including that option on per ROM bases!!

Looking very much to testing that function!!

Great work!
[Galaxy S 4 i9505 Original Android Development] todivefor:
Good catch! No. I'll give it a try.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What other information about a ROM would be useful? This is what I've added so far:
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION]

SeLinux status

Kernel version

...if that's,not too much to ask!!!

But the already added information is also informative!!

Thanks man!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Have you looked into these, sir?

I see that you are busy, so I'm ready to wait

Take your time

Thanks for your hard work again
[Galaxy S 4 i9505 Original Android Development] gaww:
New patcher and Android 6.0

First to the OP - thanks for your continued great work!

I had not done much with the patcher app recently, as I had two good ROM sworking with app sharing.

I finally took a stab with the current patcher app and the Anteries CM13. It was patched and flashed without any issues on my M919. I had anticipated using a few hundred mb data in conjunction with the ROM, which was installed to EXtSD. However, I lost about 1 gb. Without doing anything to the two previously installed ROMs, would app sharing on them have stayed intact? I did not go there with respect to the CM13 ROM.

After playing around with it a few days, I am back to where I have been with CM ROMs for some time - so plain vanilla (and surprisingly not very fast), that I would like to wipe it an wait for a better AOSP to come available. I can easily wipe the new ROM partition (3 gb in the External SD), but how do i delete the partition?

Also for future reference, if I was to make a full TWRP backup - would the External partition be included if left intact ? And if I revert to an earlier patcher app to work with app sharing, will it have to update to a different Ramdisk?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I can do the kernel version, but the SELinux state cannot be known unless the ROM is booted :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I will reply to the posts from the past few pages tomorrow. Tonight, I'm just gonna watch The Walking Dead :D
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Is episode 6 from season 6 uploaded,lol, I just opened KODI and found 2 links with each a ~3minutes episode,trailer,damn...lol, but will have to few more hours guess!
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I've found another issue in the latest 1927 build. It's incorrectly setting the kernel which leads to rebooting in recovery or bootloop depending of the device. The original boot.img of my rom is 7.4mb, but the dual boot app is setting boot.img for primary which is 16mb why is that? I have to manually copy my original boot.img to /Multiboot/primary and then it works. It's definitely setting wrong kernel here. This needs fixing dear dev and I think this is more important than adding wallpaper preview in rom's menu.... I'm not crying or something, I'm just saying we need to focus and fix these general bugs in the app and when it's finally working correctly we can proceed to polishing the UI.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Not arguing with you or anything, but how many ppl do actually have the same error as you, like you said this might device based!

I'm using 4 devices (N3 arm,N4 arm, Tab3-x86 and Note 10.1) and I've never got any of the bugs you're facing, attempted to reproduce them but nothing, my boot.img from Multiboot folder are correct Sizes as my system files, hardly ever bootloop after ram disk update or setting kernel...there is obviously nothing broken in version 1927, we're all uSing same application here, so isolated problems must be clearly stated as such, provide logs and if you can't get them...

Try this

# connect your phone with adb debugging enabled to the computer, open up a shell on pc, run logcat, then try playing around with your Multiboot patcher on your phone. If there are any, then You will see the errors you're concerned about on your computer , then provide him with those errors#

What device are you using?

......

This is not for me to answer, but what he wants to add to the application when or what he adds it's not up to you, you're not paying complain appropriately!

.....
[Galaxy S 4 i9505 Original Android Development] todivefor:
Working great with correct MBTOOL. Thank you.

Dealing with 2 devices (Galaxy S6 and Nexus 7 having come from Galaxy S4), and I confuse easily. :o
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Better Material UI! Fantastic!

I'm satisfied :)

[IMG="satisfaction"]http://i.imgur.com/sY6Q7Tq.png[/IMG]
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
My device is Lenovo K3 Note and I already provided logs. The phone is pretty popular, but very few are using dual boot on it. May be the problems are related to my device as you said. I will continue to try the app as it seems the app doesn't work 100% correctly on this phone and I have no problem being something like beta tester which I believe will help the further development support for K3 Note.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Lenovo k3 note, hmm, I thought it'll be something most of my friends would have, would've taken it from them and tested and help upload logs to help you along, how's [MENTION=5207461]Salman A.[/MENTION] doing with his lenovo, I think he has this same model!

Maybe try see if he's winning while awaiting responses from Chen!
[Galaxy S 4 i9505 Original Android Development] Andycar:
Oh, I see. Glad that I helped you.:o
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Haven't you seen my posts?? It doesn't work at all for me. I have been posting logs here all giving

"open /proc/dumchar_info fail (No such file or directory) write failed: Bad file number [D] Child killed with signal: 11"..

I think he has managed to get it work using some workaround.. I'm trying it but doesn't exactly work..

But I think it is the problem with MediaTek processors and the ROMs for it rather than the Patcher app..

Anyway, we have a great helping dev with us, so we may wait his help ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
HAHAHAHAHA!!! That is by far the best post in this thread! I laughed so hard my eyes started watering :laugh:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It's not setting the wrong kernel. (EDIT: I don't mean to say that there's no bug, just that the boot.img size is not the cause.) The original boot.img is 7.4 MB because that's the exact size of the boot image. The boot.img saved in /sdcard/MultiBoot is a dump of the boot partition, which includes the original boot.img as well as any free space on the partition. So, the size will always be equal to the size of the partition and will always be larger than the original boot.img. (This is how TWRP/CWM boot.img backups are done also, btw).

Automatic reboot to recovery is always done on purpose. The multiboot code will do that if (1) it can't figure out how the boot.img mounts the partitions, (2) it can't initialize all the hardware, or (3) it couldn't modify the SELinux policy to allow multibooting operations to work.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unless I'm mistaken, the armeabi-v7a build should run on both 32-bit and 64-bit ARM devices :) mbtool doesn't depend on any other libraries or tools, so technically, it should work.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Haha ^^ When I edited this photo I leughed hard too :D This isn't your cat? :D
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Thanks for the answer @chenxiaolong. The things are now more clear. I have other question: I have problems installing roms containing system.new.dat or system.img in any other slots than primary. I think that's because the installer can't mount the system partition because the primary rom is running. Do you know how to modify the updater-script of these roms to be able to install them in other slots than primary? For example now I have to change:

package_extract_file("boot.img", "/tmp/boot.img");
write_raw_image("/tmp/boot.img", "bootimg");
delete("/tmp/boot.img");

to

package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot"); assert(run_program("/system/bin/dd", "if=/dev/zero", "of=/proc/driver/mtd_writeable", "bs=3", "count=1"));

and it works, but only when the rom is having the usual structure #ROM#.zip/system/app. If the rom is compiled to have system.new.dat or system.img instead of the folder structure the flash process fail.
[Galaxy S 4 i9505 Original Android Development] todivefor:
My problem may be the same as this. The format is system.new.dat or system.img. Unfortunetely, I don't understand the changes that [MENTION=5048731]911-Future_Maker[/MENTION] is making to the updater script. In particular - assert(run_program("/system/bin/dd", "if=/dev/zero", "of=/proc/driver/mtd_writeable", "bs=3", "count=1")).

---------- Post added at 06:46 AM ---------- Previous post was at 06:32 AM ----------

I was trying to run arm64-v8a on a 32-bit.
[Galaxy S 4 i9505 Original Android Development] pvsgh:
Support for Note 8 (GT-N5110)

Hi Chen,

Great work on dual boot patcher, working perfectly on my Note 4.

If possible, can you please add support for Note 8 (GT-N5110), PFA link for the log file.

https://www.dropbox.com/s/khrnsciypatc3nt/20151114.152319.tar?dl=0

Thanks,

pvsgh
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I also don't understand these lines, but some guy at 4pda.ru forum wrote these instructions in this post and it's working. Otherwise, no luck with system.new.dat... We will wait for chen to return in the conversation.:o

I think this is impossible dude. :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The patcher needs to know your real device, so what you want to do is add the following to your build.prop:

ro.patcher.device=trltetmo # or whichever Note 4 variant you have
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Try hitting the back button one more time before rebooting. The setting isn't saved until you leave the settings screen (I should probably fix this).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It actually doesn't matter where the ROMs are installed, as far as ext4 and f2fs concerned. The first step is to always mount:

System partition -> /raw/system

Cache partition -> /raw/cache

Data partition -> /raw/cache

It figures out which filesystem to use for mounting by looking at the ROM's fstab file:

...
/dev/block/platform/sdhci-tegra.3/by-name/APP /system f2fs ro,discard,nodiratime,inline_xattr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xattr,errors=recover wait,nonremovable,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
...

Your ROM expected f2fs for everything, so it tried mounting system -> /raw/system using f2fs and that's when it failed and rebooted to recovery.

It's after this initial mounting step that mbtool starts mapping /raw/data/multiboot/data-slot-cm11f2fs/data to /data and so on. At this second step, it no longer matters what filesystems are used because they are already mounted and available.