yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Nicene Nerd:
The "dual" folder is supposed to hold two files, boot-int.img and boot-ext.img, naturally the internal and external kernels. Have you use the "Set Current ROM as External" button yet? Also, (I realize you probably have this taken care of already, but I figure I'll mention it anyway), have you made sure to grant MaulBoot superuser permissions?

In the mean time, this should work as a temporary fix. Take the boot image from your internal ROM zip and place in in /mnt/extSdCard/dual/boot-int.img. Then, using ADB or a terminal, run the command:

cat /dev/block/mmcblk0p7 > /mnt/extSdCard/dual/boot-ext.img

After this, the ROM booting buttons should both work.

Finally, I have been hard as work on the next version of the MaulBoot app. I plan to upload it today, so if you can't figure anything out by then, try the new app.
[Verizon Samsung Galaxy S III] deskjet390:
Thank you sir. This will suffice..... can't ask for more. Finally dual boot on D2 s3!s....... question, did the SD debrick get u thinking about this? I knew it was just a matter of time. It should work on the s4 right?!
[Verizon Samsung Galaxy S III] Nicene Nerd:
Actually, I didn't know about the SD debrick until after I started on this. I began this project because I saw someone from an old thread wishing for it, and I had done a similar (but rougher and less convenient) project on the Galaxy Tab 2 7".

As for the S4, there is a possibility that this could be used for it as well. Actually, it could potentially work for many Samsung devices. A few partition references in the script and the app would need to be updated, but there probably wouldn't be much else to it.
[Verizon Samsung Galaxy S III] deskjet390:
Yeah that's what I mean..... This is huge. I halfway understand because the SD debrick works across many Samsung devices that this will deff work. See if u can automate the patching to be on the s3 itself......there are plenty of Roms that have converters for different carriers and things .....same concept and ease of use is what its about. Its all right there now finally
[Verizon Samsung Galaxy S III] Nicene Nerd:
New version of the MaulBoot app uploaded! Better root command handling, proper icon, extra safety features to prevent soft-bricks, external partition wipes, backup and restore for external ROMs. Download the new APK on the original post, or here:
[Verizon Samsung Galaxy S III] echoedge:
Awesome. :good:

Any plans for "Boot External Rom 1" "Boot External Rom 2" "Boot External Rom 3", etc. in the future?
[Verizon Samsung Galaxy S III] deskjet390:
Outstanding. Works flawless...... the s3 is conquered.
[Verizon Samsung Galaxy S III] Nicene Nerd:
Thanks, but no plans for that in the future. It would require a very different setup than the one I'm using.
[Verizon Samsung Galaxy S III] deuce237bblock:
I'm dual booting Omni ROM and it doesn't come with a superuser app, in the instructions for flashing the ROM it says to flash Chainfire's SuperSU in recovery, so I download it and tried to patch it with the GApps patching instructions but when I open the updater-script it says "# this is a dummy file, the magic is in update-binary, which is a shell script" so how do I patch this to install to my external ROM "Omni ROM" which has no root?
[Verizon Samsung Galaxy S III] YevOmega:
Will this work with Safestrap? I wanna say yes, but I feel like the answer is no.
[Verizon Samsung Galaxy S III] Nicene Nerd:
I'll try to get CF's permission to upload a modified ZIP here, but in the meantime you need to edit the update-binary. Since it actually is a shell script, you can edit it using a text editor. Just replace the following:

mount /system
mount /data
mount -o rw,remount /system
mount -o rw,remount /system /system
mount -o rw,remount /
mount -o rw,remount / /

With this:

mount -o rw,remount /
mount -o rw,remount / /
mkdir /system
mount -rw /dev/block/mmcblk1p2 /system
mkdir /data
mount -rw /dev/block/mmcblk1p4 /data
[Verizon Samsung Galaxy S III] Nicene Nerd:
As I understand it, SafeStrap is meant for devices with locked bootloaders. This will only work if your bootloader is unlocked.
[Verizon Samsung Galaxy S III] YevOmega:
Damdamdam. I need a solution to Knox. Lol. Thanks for the quick response.
[Verizon Samsung Galaxy S III] Nicene Nerd:
Update to all: if all goes well, the next version of the app will be able to automatically partition your SD card, patch ROMs, and root them.
[Verizon Samsung Galaxy S III] deuce237bblock:
I ran into another problem, the dev of Omni ROM recommends to flash BMS kernel with Omni ROM, so when I went to patch it I got an error saying there was no boot.img. So when I open the kernel zip there is no actual boot.img, it gets created during the flash process. So is it possible to get the kernel patched some how?
[Verizon Samsung Galaxy S III] Nicene Nerd:
I inspected the BMS flashing process, and it looks like it patches your existing boot image. So if you patch the BMS updater-script, flash an external ROM, then boot into recovery and flash BMS you should be set.
[Verizon Samsung Galaxy S III] deuce237bblock:
So just patch the updater-script using GApps patching instructions then flash in recovery? The BMS kernel making process will just patch the already existing boot.img? Thank you for all your help and knowledge!
[Verizon Samsung Galaxy S III] Nicene Nerd:
You are correct and quit welcome.

Based on everyone's questions so far, I've added some Q&A to the #3 post.
[Verizon Samsung Galaxy S III] cammykool:
can you whip up a patcher script for the Mac? i have a windows partition on my Mac but i prefer not to use it
[Verizon Samsung Galaxy S III] Nicene Nerd:
I have no way to test on a Mac, nor do I know if all the tools I need are available on one. However, the next release of the MaulBoot app should include ROM-patching abilities on-device.
[Verizon Samsung Galaxy S III] cammykool:
when will that be? it will be nice :P
[Verizon Samsung Galaxy S III] Nicene Nerd:
May take a day or two. Patching ROMs on-device is pretty complicated, but I think I can make it work.
[Verizon Samsung Galaxy S III] Nicene Nerd:
Status update:

I have successfully implemented automatic SD card repartitioning in the MaulBoot app. All you'll have to do is specify the size of the card and the desired space to leave for your stuff.

I've made substantial progress on enabling the app to patch ROMs on-device. However, I may be able to do this using a better method than the way I've been working on, so I will attempt to refine this before releasing that feature.

Just have some other various app improvements coming up. If you have any suggestions, keep 'em coming!
[Verizon Samsung Galaxy S III] deuce237bblock:
Sounds great! You did an awesome job with this.

Sent by me.
[Verizon Samsung Galaxy S III] Domunus:
Is there a way to set your internal ROM to boot when in Recovery?

The ideal of dualbooting is great to try out new roms without having to wipe your primary. However, should for some reason the ROM you are flashing to the external storage not work, there doesn't appear to be a way to boot back to internal ROM. At least not without having to flash the internal ROM again so it becomes boot priority.
[Verizon Samsung Galaxy S III] Nicene Nerd:
At present, your best bet is to backup your boot partition in recovery when you first start.
[Verizon Samsung Galaxy S III] rpz3.14:
Is the updated version of the app with SD card repartitioning released, or are you waiting until the on-device ROM patching is worked out?

Looking to testing this out with the new functionality!
[Verizon Samsung Galaxy S III] Nicene Nerd:
My plan was to make a release with both features at the same time, but since I've been having a bunch of trouble with on-device patching, I may go ahead and release the SD card update tomorrow morning (I'm about to go to work for a night shift; if I wasn't I'd go ahead and serve you).
[Verizon Samsung Galaxy S III] KevinGee:
All this stuff sounds really complicated, but that's probably because I'm half asleep. But will read the op more thoroughly in the morning to see if it actually is more complicated than I think it is. ?
[Verizon Samsung Galaxy S III] Domunus:
LOL, i had thought the same thing when i first read through. But Nicene actually has it outlined pretty well. The only complication I had in the entire process was getting the darn SDCARD to format correctly. I ultimately used an app called Aparted. No matter what i did with the windows minitool partition applicaiton the phone would not see the partitions correctly. But now that the OP is adding it to his app, this setup will be a breeze!

Thank again Nicene for bringing this to the S3!
[Verizon Samsung Galaxy S III] KevinGee:
Yeah im waiting for it to be added to the App so i can go ahead and do it much easier. :good::D
[Verizon Samsung Galaxy S III] Nicene Nerd:
The MaulBoot app has been updated to include SD card repartitioning (download at post #1). I've tested it quite a few times, so it should work fine, but make sure to tell me (with a logcat!) if it doesn't work for you. Unless you habitually make sure you keep BusyBox updated, you will probably need to update it for the new functionality to work.
[Verizon Samsung Galaxy S III] KevinGee:
I probably already answered this in my head already but, doing this would indeed erase everything in the SD card am I right?

Another thing, as the op states "roms with aroma aren't compatible for external" that means if we want to use a rom with aroma, it can only be on internal storage?
[Verizon Samsung Galaxy S III] Nicene Nerd:
Yes, your SD card will be erased. I know it's a pain, but the process tends to act wonky if I don't delete the whole partition table first.

Let me clarify: the AROMA installer is not compatible with the patching script, but ROMs which use AROMA can work perfectly well on external storage. They must, though, be patched manually.

Major update: I've finally made a breakthrough in my efforts to patch ROMs on-device. Assuming no other complications (a semi-reasonable assumption), I should have the next release ready tomorrow. Other planned app features include the ability to patch gapps packages and kernels, root external ROMs, and share the /sdcard internal storage.
[Verizon Samsung Galaxy S III] deuce237bblock:
The MaulBoot app doesn't seem to be wiping external partitions. When I choose to wipe cache or anything else it shows in the status bar that a wipe is in progress but it will never finish. I sat there for 20 minutes waiting for it to finish wiping but it never did.

Sent by me.
[Verizon Samsung Galaxy S III] Nicene Nerd:
The wiping does actually finish; it is simply the notification which is bugged. I have just corrected the error and will include the fix in the next build later today.
[Verizon Samsung Galaxy S III] Nicene Nerd:
So I ran out of time to get the update ready when I wanted to, but that's only because I'm working hard to give you guys killer features! Expect the new release in less than 24 hours.
[Verizon Samsung Galaxy S III] deuce237bblock:
Take your time. I'm sure it will be worth the wait. I am loving being able to dual boot my S3. Thank you for your very much appreciated hard work.

Sent by me.
[Verizon Samsung Galaxy S III] Nicene Nerd:
The update is here! The update is here! Head back to the original post and download posthaste!
[Verizon Samsung Galaxy S III] KevinGee:
SO I went ahead and partitioned my SdCard (32gb) and it finished successfully, then i patched CleanRom8 for external and it patched successfully, then i set my current rom as internal (SlimKat-Build3) and it saved the boot.img, I rebooted into recovery to flash the external-cleanrom8.zip and it took quite a while to finish flashing, but it eventually did. But now when I rebooted it got to the Splash screen where it says (Samsung gs3) (MaulBoot) and it just hangs there.

Any ideas as to why?

UPDATE: So i re-Partitioned my SdCard (deleted the previous patched rom) and re-patched the rom again. wiped external partitions, Set current rom as internal and booted into recovery and flashed the external.rom.zip it flashed and I rebooted the phone and this time IT DID go past the Splash screen and all is good.
[Verizon Samsung Galaxy S III] KevinGee:
I tried with clean rom 8 and paranoid android beta 6 and after initial boot up, it lags so much I can't even set up gmail.

Could the problem be the SD card?
[Verizon Samsung Galaxy S III] Nicene Nerd:
It's pretty likely the card. When I tested without my class 10 card, lag was pretty annoying. After a little while, though, it settled in and wasn't quite as bad.
[Verizon Samsung Galaxy S III] -somebody-:
sadly im on safestrap but had to say i love the doctor who reference :good: :laugh: :good:
[Verizon Samsung Galaxy S III] jl2222:
I'm not near a computer currently. Can I perform SD partition and external ROM installation from the apk? After installing it looks like it has all the functions and tools to do so.
[Verizon Samsung Galaxy S III] deuce237bblock:
Yes. Make sure to backup everything on your extSdCard as I am pretty sure it will format it. After partitioning your SdCard, download the ROM you want to install and patch it through the app then install in recovery. Be sure to set your current ROM as Internal ROM before flashing the External ROM. And it's good practice to Nandroid before flashing anything. You want to especially backup your boot.img in recovery incase anything happens and you cant get back into your internal ROM. Hope this helps.
[Verizon Samsung Galaxy S III] Nicene Nerd:
Yep, that's basically perfect advice.
[Verizon Samsung Galaxy S III] Nicene Nerd:
Warning: I just discovered that attempting to patch very large ROMs (I was fine with ~800MB, but saw this with a 1GB one) may cause your phone to lock up, crash, and reboot. I'm looking into a way to fix this (the good news is that I discovered this while testing AROMA installer ROM patching).

Edit:

Also, I have updated posts #1 and #2 to contain basic starter instructions and helpful tips, respectively.
[Verizon Samsung Galaxy S III] rpz3.14:
I'd like your thoughts on the best way to troubleshoot issues I'm having. I installed the latest app update and partitioned my external SD card using the app. I'm using a 32 GB card, and allowed 12 GB for the external rom. I then tried to patch the latest mastamoon CM nightly with the app. It was reported as successful, but when flashed in recovery, it hung at the boot screen (I waited 20 minutes before pulling the battery and going back to the internal ROM). I nandroided back to my main ROM, wiped the external rom slots, tried patching the latest stable SlimKat rom, and had the same behavior.

I'm using TWRP v 2.6.3.1. Any ideas to troubleshoot this would be greatly appreciated, as the app functionality looks really nice.
[Verizon Samsung Galaxy S III] Nicene Nerd:
This mysterious issue plagued me for days while I was working on ROM patching, and I'm honestly not sure how it ever started to work. However, at one point it did begin working and it has (at least for me) continued ever since. Unfortunately, as far as I am aware there is no way to log whatever is causing your boot process to hang without a serial connection. If it were to automatically reboot, then you could check the file /proc/last_kmsg.

So, despite my completely unhelpful response, send me a logcat from the ROM patching process. I can at least check to see if the script is reporting any errors that don't throw exceptions.

Edit: One last thing. Did you make sure to update BusyBox prior to using MaulBoot? The version I needed for certain commands (though I forget exactly which ones) to work was BusyBox v1.22.1-Stericson.
[Verizon Samsung Galaxy S III] deuce237bblock:
I've been patching and flashing ROMs left and right using the app to patch and haven't had any problems yet. I always check the updater-script before flashing and sometimes have to change something but doesn't happen often. I can't thank you enough for this. I've always wanted to dual boot.

Sent by me.
[Verizon Samsung Galaxy S III] Nicene Nerd:
What things do you find yourself having to change? I'll see if I can update my patch process to take care of them.
[Verizon Samsung Galaxy S III] deuce237bblock:
Just the mount point for /data partition. Patching a ROM that mounts /data doesn't change the mount point for the /data partition.

ROM backup seems to have this problem, when I backup it finishes but the notification persists saying backup in progress.

Sent by me.
[Verizon Samsung Galaxy S III] KevinGee:
It happened to me also, if would just hang in the boot screen. But what seemed to fix it for me was to partition my SD card all over again and try again.
[Verizon Samsung Galaxy S III] rpz3.14:
I sent you a PM of a logcat from today for reparitioning and patching the ROM and GAPPS. Thanks for helping out!
[Verizon Samsung Galaxy S III] Nicene Nerd:
I checked your PM, but there was no unusual output from MaulBoot. Everything appears to have worked as usual. How many different ROMs have you tried to patch?

General announcement: I'll be off-project for a while. I got my wife an iPhone (I know, don't kill me!), but I misread the description and didn't understand that it is activation locked, so I'm dedicating my hacking efforts towards it for a while.
[Verizon Samsung Galaxy S III] Nicene Nerd:
So I'm done working on that horrid iPhone, and I intend to resume MaulBoot development. Any bugs or requests as I get back into gear?
[Verizon Samsung Galaxy S III] deuce237bblock:
If you look up a few post I found a bug with the app.

Sent by me.
[Verizon Samsung Galaxy S III] Nicene Nerd:
Ah, yes, I forgot. So planned updates for the next release include notification bugfix, support for patching updater-scripts which mount /data, support for patching AROMA ROMs, and a lockup warning against trying to patch ROMs which are 900MB+.
[Verizon Samsung Galaxy S III] deuce237bblock:
Not asking for an ETA just wondering how the updates coming? Would love to be able to flash AROMA ROMs to external.

Sent by me.
[Verizon Samsung Galaxy S III] Nicene Nerd:
Ah, sorry about my slowness. I've been working long nights and usually only have a couple hours of free time in a day, so this has been pushed to the backburner for a bit. I will, however, get this up soon. Also, just a note about AROMA ROMs, many of them are really big, so bear in mind the 1GB ROM limit that will be in place in the update and check the size. Trying to patch 1GB+ ROMs tends to crash the phone.
[Verizon Samsung Galaxy S III] negativedrew:
this is awesome! definitely keeping an eye on this and hoping for support for the t-mobile s3.
[Verizon Samsung Galaxy S III] Nicene Nerd:
If you run the command "ls -al /dev/block/platform/msm_sdcc.1/by-name" and give me the output I can help you with T-Mobile S3 support.
[Verizon Samsung Galaxy S III] somerandomguy1:
Firstly, thanks [MENTION=4533145]Nicene Nerd[/MENTION] for the cool app! I ran it for a few days without hiccups thanks to your guide.

I did run into an issue today, however. When I hit boot external ROM, the app got SU permissions but then didn't do anything. The phone still functioned as though it hadn't tried to reboot at all. I manually rebooted, it booted into the external ROM, but now it's stuck there. Any way to get back to the internal ROM? Hitting "Boot Internal ROM" reboots and dumps me right back into the external, as does "Boot External ROM".

It's not a huge deal, as I don't keep anything important on either of them, but I'm curious what happened.
[Verizon Samsung Galaxy S III] negativedrew:
thanks! !

lrwxrwxrwx root root 2014-03-28 06:01 aboot -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2014-03-28 06:01 backup -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 2014-03-28 06:01 boot -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2014-03-28 06:01 cache -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 2014-03-28 06:01 efs -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2014-03-28 06:01 fota -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 2014-03-28 06:01 fsg -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 2014-03-28 06:01 grow -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 2014-03-28 06:01 modem -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2014-03-28 06:01 modemst1 -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2014-03-28 06:01 modemst2 -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2014-03-28 06:01 pad -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2014-03-28 06:01 param -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2014-03-28 06:01 persist -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2014-03-28 06:01 recovery -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 2014-03-28 06:01 rpm -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2014-03-28 06:01 sbl1 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2014-03-28 06:01 sbl2 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2014-03-28 06:01 sbl3 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2014-03-28 06:01 ssd -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 2014-03-28 06:01 system -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2014-03-28 06:01 tz -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2014-03-28 06:01 userdata -> /dev/block/mmcblk0p15

u0_a132@d2tmo:/ $
[Verizon Samsung Galaxy S III] Nicene Nerd:
Your partition layout matches the Verizon S3 in all the right places, so MaulBoot should work without modification. Tell me if it does so I can post MaulBoot in the T-Mobile forums, too.
[Verizon Samsung Galaxy S III] Nicene Nerd:
It's hard to say what exactly happened. Check to see if boot-int.img is present in the /dual folder on your SD card. For that matter, make sure there is a /dual folder on your SD card. MaulBoot should have created it.
[Verizon Samsung Galaxy S III] somerandomguy1:
Yes, the /dual folder is there and boot-int.img and boot-ext.img are both there. Easy way to see if anything is wrong here?

Thanks for the response :)
[Verizon Samsung Galaxy S III] Nicene Nerd:
Okay, compare the file checksums on boot-int.img and boot-ext.img. If they are identical, you have somehow ended up with the external boot image set for both ROMs. To fix that, unzip the boot.img from your internal ROM and replace boot-int.img with that file. I don't exactly know why this would have happened if this is the cause, though.
[Verizon Samsung Galaxy S III] Prack:
Great project! I used a similar app back on my original droid and my droid x called boot manager. Anyway are we able to install slimkat as external yet or is that still not working?
[Verizon Samsung Galaxy S III] Nicene Nerd:
You can try. Though it never worked in the early stages, I successfully flashed SlimKat at random a while back.
[Verizon Samsung Galaxy S III] Nicene Nerd:
I've finally got an update up. Changelog:

Notifications should be fixed.

Added support for patching AROMA ROMs.

Fixed support for ROMs which mount /data during flash.

Enjoy!
[Verizon Samsung Galaxy S III] Prack:
This app is awesome, any reason you haven't published it to the play store? Thank you again for the great app!
[Verizon Samsung Galaxy S III] Nicene Nerd:
I've been thinking of uploading it, but I have some stuff I want to work out first. I would like to confirm support of at least all the major S3 variants, improve the UI, refine the code (which is a bit clunky because I figured this thing out as I went), and smooth out some awkward usability elements.

Speaking of all this, is there anyone good with UI design who would like to help me improve the MaulBoot app?

Also on my agenda is using a modified TWRP-based recovery as an alternative option to the in-app backups and restores, since they are painfully slow and clunky. The app would give you the option of rebooting into MaulBoot TWRP to backup and restore, and then booting back into your ROM and restoring your previous recovery.
[Verizon Samsung Galaxy S III] Nicene Nerd:
Alas, bad news. MaulBoot development must end for the foreseeable future. My S3's screen has entirely deceased, and unless I get one by donation, I'll have to get a different phone. If anyone wants the source code, just ask.
[Verizon Samsung Galaxy S III] Prack:
Aww man that's terrible. Sorry about the phone and sorry to all of us S3 owners who will be missing out on updates for this awesome app. Thanks again for the hard work and the app that we do have. It is very much appreciated.