As I understand it, SafeStrap is meant for devices with locked bootloaders. This will only work if your bootloader is unlocked.Will this work with Safestrap? I wanna say yes, but I feel like the answer is no.
As I understand it, SafeStrap is meant for devices with locked bootloaders. This will only work if your bootloader is unlocked.Will this work with Safestrap? I wanna say yes, but I feel like the answer is no.
As I understand it, SafeStrap is meant for devices with locked bootloaders. This will only work if your bootloader is unlocked.
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:
With this:Code:mount /system mount /data mount -o rw,remount /system mount -o rw,remount /system /system mount -o rw,remount / mount -o rw,remount / /
Code:mount -o rw,remount / mount -o rw,remount / / mkdir /system mount -rw /dev/block/mmcblk1p2 /system mkdir /data mount -rw /dev/block/mmcblk1p4 /data
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.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?
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.
You are correct and quit welcome.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!
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.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
May take a day or two. Patching ROMs on-device is pretty complicated, but I think I can make it work.
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!
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.
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!
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).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!
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. ?
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!
_______ __ _______. ______ __ ___ __ .___ ___. _______ .______
| \ | | / | / || | / \ | | | \/ | | ____|| _ \
| .--. || | | (----`| ,----'| | / ^ \ | | | \ / | | |__ | |_) |
| | | || | \ \ | | | | / /_\ \ | | | |\/| | | __| | /
| '--' || | .----) | | `----.| `----./ _____ \ | | | | | | | |____ | |\ \----.
|_______/ |__| |_______/ \______||_______/__/ \__\ |__| |__| |__| |_______|| _| `._____|
[B]REMEMBER:[/B] Use this utility at your own risk. I am not responsible for any
data loss, bricked devices, thunderstorms, or undesirable election
outcomes that result from using this utility.
ls /dev/block/
Find Replace With
----------------------------------------------------------------------------
/dev/block/platform/msm_sdcc.1/by-name/system /dev/block/mmcblk1p2
/dev/block/mmcblk0p14 /dev/block/mmcblk1p2
/dev/block/platform/msm_sdcc.1/by-name/userdata /dev/block/mmcblk1p4
/dev/block/mmcblk0p37 /dev/block/mmcblk1p4
/dev/block/platform/msm_sdcc.1/by-name/cache /dev/block/mmcblk1p3
Find Replace With
----------------------------------------------------------------------------------------------------------------
run_program("/sbin/busybox", "mount", "/system"); mount("ext4", "EMMC", "/dev/block/mmcblk1p2", "/system");
run_program("/sbin/busybox", "umount", "/system"); unmount("/system");
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.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?
MaulBootPatcher rom-package-here.zip