yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Plz try from recovery and feedback!!

---------- Post added at 09:08 PM ---------- Previous post was at 08:57 PM ----------

@chenxiaolong hey mate, is there workaround this mbtool needing Updated from primary ROMS, coz after updating it, there'll be a boot loop all the time!
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
It appears your device "noblelte" is not supported or you need to edit your build.prop to include. See below:
[Galaxy S 4 i9505 Original Android Development] thag12:
Same. It does not work. Mybe im doing something wrong?

I would paste log from twrp but i dont find where it is saved.

---------- Post added at 08:47 PM ---------- Previous post was at 08:42 PM ----------

Oooh! Mybe is becouse im using an N5 ROM ? And it's not recognized as n9005 but as note 5. Also tapatalk recognoze it as n5
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
What the other mate is saying is to add this line in your build.prob but in ported N5 ROM that's already there, look below!

That's the line that's needed so m Multiboot app knows your real hardware, check that system file and verify that You have it added!!
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Oops
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Looks like your ROM doesn't support selinux (or it's broken somehow). I've added a workaround in 8.0.0.r1923.g6725e82
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm getting HTTP 404 for that link :)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
https://www.dropbox.com/s/7tjcfyj2k4bvhkz/20151110.003446.tar?dl=0

There it is again!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Nope you're not just unlucky :) MediaTek devices are just weird. Could you see if (or maybe ask) the developer of that ROM if the source code is available? I'm really not sure what their installer needs /proc/dumchar_info for and would rather not reverse engineer it to figure it out.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm unable to do anything about this at the moment. My S4 is now my mom's phone and I need to wait until she lets me play with it for a few hours :)
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Ok, thanks alot. I'm using a stock Odex TouchWiz version (that came with the phone) with this kernel: http://xdaforums.com/s6-edge-plus/development/arter97-kernel-galaxy-s6-edge-plus-t3189913
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, I don't have a device that AROMA supports right now for testing, but I think something is wrong with AROMA and not mbtool. Since you're comfortable with running mbtool manually (thanks for all the backup and restore testing!), could you try the following to see if the ROM is correctly wiped?

MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery utilities wipe-system data-slot-blah
MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery utilities wipe-cache data-slot-blah
MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery utilities wipe-data data-slot-blah
MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery utilities wipe-multiboot data-slot-blah

EDIT: It's not necessary to reinstall something to data-slot-blah for testing. It should remove the leftover files you mentioned.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There's no workaround for that. Can you grab the logs for the boot loop?

(I think I mentioned this before, but you can undo the ramdisk update by rebooting to TWRP and tapping Install -> Images (bottom right corner) -> /sdcard/MultiBoot/primary/boot.img.before-ramdisk-update.img.)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Yes I'll try get log files, I'm not worried about booting back, I'm happy with your last guide, I'm just concerned coz for APP sharing primary ROM mostly requests updating mbtool that eventually lead to that error I mentioned!!

I'll try recreate the bootloop by updating mbtool and send you the logs!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! But I'm really not sure what's causing the issues with AOSP 6. Your device unfortunately didn't log anything regarding the failed boot.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah, looks like that's exactly the issue then. Under the features section of the kernel, it specifically lists "SELinux completely disabled". :)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Thanks bro!

I'll just wait for more stable versions of AOSP 6 and attempt installing them as secondary then!

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It looks like your UPDATE-SuperSU-v2.46_extsd-slot-test10.zip file was still patched with the older version (8.0.0.r1912.g966670c) :) Could you try with a newer version? Thanks!

I'll flash Philz on my Note 4 so I can give this a whirl :) AROMA doesn't support the Note 4, but I might be able to do some debugging to see why it's trying /external_sd over /storage/sdcard1
[Galaxy S 4 i9505 Original Android Development] GioBasi:
I want to use Ext_Sd card for system apps and for gapps which are installed for ExSD_ ROM_slot .....

is it possible or not?

I have installed link2sd and foldermount, I have second partition formatted as ext4 on exsd card and so on.

,

now I am trying to use dual boot patcher to achieve this goal but still every apps, system or gapps and other are using only internal data storage.

Any tutorial link please. I searched everywhere but maybe with not correct words... :confused::confused:

help please

CM 12.1

GT-i9192
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Hello [MENTION=4277844]chenxiaolong[/MENTION],

we have new problem. :) DualBootUtilities dont't wiping multiboot/[ROM_name]/data folder. Multiboot/[ROM_name]/system is deleted but multiboot/[ROM_name]/data exist. Bual Boot Patcher app wiping multiboot/[ROM_name]/data and Multiboot/[ROM_name]/system correctly.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Almost all the ROMs for my phone are made by Chinese or Russian devs, so it's not that easy to contact them..

But I'll try a different ROM.

Thanks for your hard work.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
OMG! Now Extsd Slot working amazing! :D I have already flashed Marshallow to Extsd and it working fantastic!

Thank you so much! :)

Now it is correctly. Zip file with new version 8.0.0.r1923 shows:

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

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

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

so all is correctly :)

Btw what recovery do you use now? TWRP?

And could you correct it:

Internal SD Size: -1 MB

Free: -1 MB

Thank you in advance for your hard working! :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Great! Glad it's working for you now! :)

I personally "use" TWRP on Note 4. ("Use" in quotations because my phone is broken 75% of the time and I manually fix stuff from my computer instead using the recovery :D).

The internal SD issue should hopefully be fixed in 8.0.0.r1924.gb6bbfdc.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
What did you do that your phone is broken? :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahh, right. It detects which ROMs are installed by checking if the corresponding system folders exist. If that is wiped first, then it no longer allows wiping the other directories because it doesn't think the ROM is installed. This should be fixed in 8.0.0.r1924.gb6bbfdc.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I think so too. :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Well 75% might be exaggerating, but I always make stupid mistakes when I do stuff. Normally, my phone is broken because I test a change or bug fix right before I go to school or work then I reboot and find out it gets stuck at the Samsung logo lol. My worst was when I wanted to delete /data/multiboot to remove all the ROM's data. I stupidly did this:

rm -rf /data/m*

and I lost /data/media with all my pictures and everything. Lesson learned -- always backup to external SD :D
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Yes, yes, yes :D I had this same stupid moments :D

Last time I had some bootloops in school when I tested Xposed. You know Samsung stocks 5.0, 5.1 = problems with Xposed. And I had to reflash ROM on lesson and since then I hate boot sound (sound was too loud :P).

I remember too when I wanted to delete files and folders from /data partition via Aroma Filemanager. Some minutes later I turned on my phone with new ROM. I opened File Explorer on internal sd and I see: "what? Where are my files? Photos? TitaniumBackup folder? Oh no!". All files lost and now I remember: never touch /data/media/0 :D

I wiped my Note 1 by accident when I bought Note 3. Now I always do backup to external sd before I do anything with my ROM :) I wanted to buy Note 5 but it hasn't MicroSD slot and replaceable battery :/ Ahh Samsung why you did that?? I need external sd for files and backups.
[Galaxy S 4 i9505 Original Android Development] remowrx:
Hi [MENTION=4277844]chenxiaolong[/MENTION]

I have problem while installing TW based aroma roms in recovery. Both roms are patched with your latest apk, however while installing their respective patched zips from latest TWRP to different data slots, both installation quits from aroma and I'm back at the TWRP initial screen. I have tried both and then installed your log creator zip and attached it for your review. I just want to know if it is rom problem or is there something you can do.

I'm successfully using three different roms in my N9005 thanks to you but I have problems with those two..Below are the links for the roms as well;

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

http://xdaforums.com/showthread.php?t=2776887
[Galaxy S 4 i9505 Original Android Development] thag12:
Sorry but i'm still a begginer in this. How do I add this ? Do I ask this in q&a ?
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Obviously rooted, with your file manager, not stock, use either root explorer, solid explorer etc, head to system folder and look for build.prop open as text file and at the end add that line and save,grant su permissions when asked!!

---------- Post added at 03:08 PM ---------- Previous post was at 03:02 PM ----------

Method 2 and more simpler since you saying you're new to the scene:: go to play store download kernel adiutor and follow steps shown I the pic and then save, you're done!!
[Galaxy S 4 i9505 Original Android Development] thag12:
I've done it, from recovery. Thank u guys :))))) im happy now
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Failed to update ramdisk

Guys, can anyone tell me why it's not working anymore? Using the latest 1924 build. The same error with the previous one. All was good till I made the mistake to flash other primary rom in recovery. Till then ramdisk was updating fine on multiple roms, but now failing. I even formatted the internal sd and still the problem persist.
[Galaxy S 4 i9505 Original Android Development] todivefor:
I have done some more testing with this. Restored data-slot-renegade multiple times and it has worked each time. To test the above, I restored and then wiped with DB utilities 1924. I got the result attached DButl.pdf. On device, I was left with remnants as described in screenshots attached in zip AfterDBUwipe-x. I next tried the code you suggested above. On each I got "ROM ID data-slot-renegade is not installed." After this I did another restore. On this one I did a wipe from the app. I was again left with remnants on the device, but not as many. These are as described in screenshots attached in zip AfterAPPwipe-x.

This is not high priority as I think I know how to cleanup manually. Backup/restore is going to be of tremendous benefit.

Let me know if you need anything tested.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
1. Delete primary kernel image (boot.img) from [Internal SD]/MultiBoot/primary.

2. Reboot phone and open DualBoot Patcher app. On primary ROM tap Set kernel, again reboot phone.

3. Now try update ramdisk.

These steps helped me.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
But I don't have any folders in Multiboot directory like primary, data-slot etc. because I wiped my internal memory trying to fix the issue. :/
[Galaxy S 4 i9505 Original Android Development] todivefor:
Have you tried going into app and setting kernel?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Actually no... thx for the suggestion. Just tried now and the app throwed another error message. I'll guess this could be due to the current rom I'm using - CM12.1 for K3 Note as it is well known to be quite buggy. Is it worth to try with different rom?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Have you successfully patched and flashed a rom? This is complaining that K50-T5 is not supported. If that is your device, it is not supported. You might get away with adding that to the build.prop. I am just guessing here. You'll have to wait for someone that knows.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
No, this rom I flashed the usual way via recovery and it wasn't patched. My device is Lenovo K3 Note K50-t5 and while it may not be supported it all worked fine before I stupidly flashed another primary rom without patching it first. In the desktop Dual Boot app these is an option to choose K50-t5 so I'm not sure if it's supported or not.
[Galaxy S 4 i9505 Original Android Development] todivefor:
The only reason you patch a primary rom is so during flash it won't wipe out any of your secondary roms which could have parts in system, cache, or data. If there is an option to choose K50-T5, then it is supported. You are going to have to wait for [MENTION=4277844]chenxiaolong[/MENTION] or someone more knowledgeable than myself to explain why codename "K50-T5" is not recognized.
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Time for an update from me. Tried to use 'Set kernel' and 'Update ramdisk' again with the new r1924 version. I still got the same 'failed' messages when i tried to use those. This is with the new v9.3 kernel here: http://xdaforums.com/s6-edge-plus/development/arter97-kernel-galaxy-s6-edge-plus-t3189913

The funny thing is that i don't even get up the 'popup window' from SuperSU asking for root access from the 'Dual Boot Patcher' app. So i believe that is one of the issues most likely.

EDIT: Nvm, a simple reboot fixed my issue.https://dl.dropboxusercontent.com/u/7309753/ramdisk-update.log
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
If you installed new version DualBoot Patcher and you don't get up the "popup windows" from SuperSu try reboot phone. Open app again and try to accept root privileges from SuperSu. Root privileges are needed to correct working app. :)
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Actually, that was the issue. I just took a reboot of the phone and boom, it's now working.
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
I had a similar problem so I knew how to help you. :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There's nothing you did wrong. It's just that nobody ever told me that "K50-T5" is a valid codename for your device. If you look here (https://github.com/chenxiaolong/Dua...2daf4d33bd89221/libmbp/patcherconfig.cpp#L724), the codenames the patcher recognizes are "K50", "K50a40", "K50t5", and "aio_otfp".

I've just added K50-T5 to that list in 8.0.0.r1925.g255c9c5 :)
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
[MENTION=4277844]chenxiaolong[/MENTION]

When you'll have a more free time, please fix this if you could:

DualBootUtilities dont't wiping multiboot/[ROM_name]/data folder. Multiboot/[ROM_name]/system is deleted but multiboot/[ROM_name]/data exist. Bual Boot Patcher app wiping multiboot/[ROM_name]/data and Multiboot/[ROM_name]/system correctly.

Thanks so much! :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks again for the detailed testing. I think 8.0.0.r1926.g3261cb5 should fix the wiping issues. mbtool detects if a ROM is installed based on whether the system directory (or ext4 image) exists or not. If the ROM's system directory was wiped first, mbtool no longer detects the ROM as being installed so all subsequent wipes would fail. This behavior doesn't particularly make sense when wiping ROMs, so I have removed this check.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is exactly the issue [MENTION=2688336]todivefor[/MENTION] was describing. It should be fixed in 8.0.0.r1926.g3261cb5 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, I'm tempted to say it's a ROM problem because it crashed the entire recovery and TWRP reloaded (which is why you were sent back to the TWRP main screen). If you flash the unpatched version of the ROM (wtithout actually tapping Next and installing), does AROMA show up properly?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Ah yeah, yeah, you are right. I didn't read his post :)

---------- Post added at 01:27 AM ---------- Previous post was at 12:28 AM ----------

@chenxiaolong

How can I delete MultiBoot/[ROM]/data folder? You know - 0 folder in MultiBoot/[ROM]/data/user is a symlink. And with symlinks I have bad memories :P

Command rm -rf will work?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, "rm -rf" will work. As long as you don't have a trailing slash character in the path, there's nothing to worry about :)

rm -rf /data/multiboot/[ROM]/data # Do this
rm -rf /data/multiboot/[ROM]/data/ # [b]Don't[/b] do this. If the "data" folder is a symlink, you would lose stuff
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
All issues have been solved. Now all working fantastic.

Very big thanks! :)
[Galaxy S 4 i9505 Original Android Development] zhuoyang:
Hi [MENTION=4277844]chenxiaolong[/MENTION] ,

Can you add support for Xperia Z1 ?

I already made pull request, Would you mind to build with the commit and let me test it out ?

I tried to build but encountered error like this

/root/DualBootPatcher/mbtool/packages.cpp: In function 'bool mb::parse_tag_cert(pugi::xml_node, mb::Packages*, std::shared_ptr<mb::Package>)':
/root/DualBootPatcher/mbtool/packages.cpp:368:18: error: base operand of '->' has non-pointer type 'pugi::xml_node'
[Galaxy S 4 i9505 Original Android Development] remowrx:
Thanks for the reply. The unpatched versions of both roms installs fine actually. I even redownloded the roms and checked the md5's and did try your windows tool for patching but unfortunately the result is the same..

SM-N9005 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S 4 i9505 Original Android Development] corncobman:
I encountered a similar problem trying to flash a couple of Kitkat ROMs on my i9305 while my main ROM was Lollipop. It goes through the installer, Aroma and everything and finishes fine. When I reboot, it goes straight into recovery.

I just put it down Kitkat not playing well with Lollipop bootloader and kernels.
[Galaxy S 4 i9505 Original Android Development] Ather:
[MENTION=4277844]chenxiaolong[/MENTION] i have a Note 4 running Custom TW Rom with Note 5 Features, the rom changed device id to that of Note 5 so i cant flash any ROMs through the app since it fails at patching, saying this device is a note 5, any way to bypass this check?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Many thanks [MENTION=4277844]chenxiaolong[/MENTION]! I tried again with v1927 and sadly I'm getting the same errors. It's strange because as I said it was working fine before I flashed another primary rom, because I messed the permissions. Did you take a look at the logs I provided? Thanks for the time you're spending replying on our numerous issues mate. I'll proceed to flashing a new rom and will see how it goes.
[Galaxy S 4 i9505 Original Android Development] monkteo:
The problem regarding installing and reboot in recovery is not the KitKat or Lollipop, it's Aroma from rom.

So you can install any rom in secondary or dataslot or extSD but without Aroma installer
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Update! 1778 latest working build for me.

Hey friends, an update from me: I fixed my issues with flashing new ROM replacing my old CM12.1 setup. Now ramdisk updates successfully, yay! Thanks all for the help. It's still strange why problems like these are happening... Now I'm ready to setup my triple boot environment again lol.:highfive:

EDIT: IMPORTANT DEV chenxiaolong PLEASE TAKE A LOOK!

Something is broken for me in the newest builds. I'm talking for the issue when I update the ramdisk and after reboot the phone goes straight into recovery. The method of deleting the new patched boot.img and flashing the original boot.img works, but only to get the phone back into a working state and this is a temporary solution. If you try to update the ramdisk again the situation repeats: the phone goes into recovery while attempting to load the kernel. Thankfully I remember that the build 1778 was fully working for me while the newest 1927 and some previous builds I tried don't work and the effect is that the phone reboots into recovery after ramdisk update. For now I'll stick with the 1778 till the dev doesn't confirm what's going wrong.

In 1778 this is what is working for me and may be it's worth to note that all roms I tried are 5.1 and 5.1.1, and the recovery is TWRP 2.8.7.0 Material Mod:

Roms->Set Kernel for primary when prompt->Update ramdisk->Reboot->All working.

In 1927 and some previous builds I tried the following non working steps:

Roms->Set Kernel for primary when prompt->Reboot(as some members suggested)->Update ramdisk->Reboot->Not working, the phone goes into recovery.

May be the key is to NOT REBOOT after setting kernel for primary and right after that to update the ramdisk? Because as we see if I reboot after setting kernel the things are not working. I didn't tried the second scenario in 1778 and I think it will not work, but if it works it's a strong indication that something in the latest builds is broken. If it doesn't work that means these is only one scenario at least for my device to get the things working and there is nothing wrong with the newest builds.
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear [MENTION=4277844]chenxiaolong[/MENTION], is there anything that can be done with app sharing in CM13 installed as second ROM?

While I'm in 2nd ROM, I switch on app sharing, then reboot. But it doesn't stay enabled...

I don't know if that log is of any help, but here is the link:

http://1drv.ms/1PEuFNv