yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
No problem man. It's working good. I tested cm11 paranoid android and it worked good. But I tested avatar ROM 4.3 and it didn't work so well. Probably a ROM issue. And these were tested with my internal ROM as 4.3 touchwiz. You should put in the OP to flash with Odin. And I found a bug I think....

When you make a new ROM and flash the ROM in the new slot, you must swap back to internal in order for it to boot. So you can't swap to it, and then boot it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mikessv:
Is there anyway to make a regular zip for this? I don't have access to a computer for Odin
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fire_angel:
it's a great tool for the people than change ROM all the time or the testers...well....it's my opinion....XD:laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
Exactly! That's about be my exact purpose with this :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Thank's for feedback.

I will add the information that this preview has to be installed with Odin.

In fact, it is prerequisite to go back to original rom to be able to boot a Rom that you installed on internal sdcard ( /data/media/../) .

When you select a rom, it is to make operation on it ( install, wipe etc.. ) but not to boot on it. I admit that it is not very clear...

Yes, I will do it soon.

In my case, it was also to have my original rom (not rooted) for my work during work time, and use other roms outside work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] balrog558:
This looks awesome I will try it out asap. Thanks for the hard work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ChinDaChin:
Wow! This looks awesome! I'll have to try it when I grow a pair of balls haha. I'm too scared to mess with my phone any further. (Especially since I did the 4.3 OTA.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Works like a charm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks will try
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
It even flashes KitKat Roms without the status 7 even though it's based on twrp 2.6.3.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Okaham:
hey, i was wondering how one flashes this? i know it's through Odin, but do i flash through PDA? and what do i have to have checked? thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
That amazed me too. That was odd.

Sent from my I747 using 4G LTE! ROM stands for "Remedy of Mediocrity" (says my girlfriend)

---------- Post added at 03:20 AM ---------- Previous post was at 03:17 AM ----------

Using PDA. Correct. Flashed it again yesterday can verify.

Sent from my I747 using 4G LTE! ROM stands for "Remedy of Mediocrity" (says my girlfriend)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Okaham:
so what should i have checked? auto reboot, f. reset time...etc? thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
Close the program and reopen it. Use default settings. Make sure re - partition isn't checked. It normally isn't. So open odin. Click the file in PDA. Hit start. Done.

Sent from my I747 using 4G LTE! ROM stands for "Remedy of Mediocrity" (says my girlfriend)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] saranhai:
Nicely done OP! Tested and I can confirm that this does indeed work on the T-Mobile Samsung Galaxy S III SGH-T999!

One small thing though, this mod makes the recovery think that the device is an i747, therefore, T-Mobile ROMs (with the getprop in updater-scripts) cannot be flashed with this. I expect though, that this is a minor issue and can be fixed very easily. Once again, great work! :good:

-Saranhai
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
What kind of bugs are people running into? I just saved my device's ass from a hard brick for the second time in just a few months so I don't want to flash anyting with odin right now, some stability would be nice for a ltitle bit :P

However, if people have not been having problems once you boot into either ROM, at least nothing additional to what is already a known issue, then I am flashing this sucker RIGHT away. Question, how is /system/ looking? what about build.prop and the init.d folder? are they seperate for each ROM, and if so, how are they managed when I am not booted into one for instance?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
Every rom is sorted into its own folder in these incoded files. You see?

Sent from my I747 using 4G LTE! ROM stands for "Remedy of Mediocrity" (says my girlfriend)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
Hey guys I was wondering if someone could help me out? I got this installed, and booted a few roms. Obviously some worked and some didn't as originally stated. I want to know, those who are running TW 4.3, are you running just stock? Or is it something like S3Rx or DanDroid? Because I couldn't get S3Rx or DanDroid to work. Just not sure if I was doing something wrong.

Thanks

KM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
I'm running StockMOD as internal and Quantum as multiboot. Did you mean is anyone running a custom touchwiz in the other slot? Like the multiboot?

Sent from my I747 using 4G LTE! ROM stands for "Remedy of Mediocrity" (says my girlfriend)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
Yeah I can't get a custom TW to boot from the multiboot menu. Maybe I went about this wrong, this is what I did...

I backed up my Rom, Odin over the Recovery and then Wiped everything (Complete wipe, including internal). Went into Multiboot and set up a rom (4.4), then installed it, booted it and all is fine. Did another one (4.4) and all is fine. But when I try to use a Custom TW in Multiboot it starts to boot, and then shuts off and buzzes twice.

So if I would have stayed on TW and put the other roms into multiboot, would I be able to boot TW if I just rebooted the phone and did not go into the Multiboot menu?

Thanks

KM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
It maybe because touchwiz has some extra but I have tested many AOSP roms and they worked. So I'm guessing we gotta leave touchwiz on internal and use anything else on multiboot.

Sent from my I747 using 4G LTE! ROM stands for "Remedy of Mediocrity" (says my girlfriend)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
Thanks Smash2Bash, I'll give it a shot that way!

Big thanks to Phil_Suz and mkasic and anyone else who had a hand in this. Didn't think something like this was possible. You guys are the best!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Hi all,

Thank's all to give some feedback and especially Smash2Bash to help and share his experiences.

Hopefully (after project at work), next week I will come back working on this project.

Hi KingMike67, can you point me to the exact ROMs that failed to launch, I will try to find what's wrong.

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
So how do i revert back? Flash TWRP though odin or flash the zip file? Or it is harder than this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
I have flashed CWM using this and it worked. And either find a flashable zip for TWRP or use goomanager to download and install the latest TWRP Recovery.

Sent from my I747 using 4G LTE! ROM stands for "Remedy of Mediocrity" (says my girlfriend)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Multiboot program is only an add-on installed into recovery image.

Just flash back your previous recovery image and multiboot diseapear.

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
So will i be able to recover the space allocated to different rom?

And will different rom use the same memory? Internal or external
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
Phil_Suz

The two TW roms I tried were there:

S3Rx 3.0

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

Dandroid 5.4

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

Thanks man! I really appreciate the help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Hi KingMike67,

I successfully installed and multibooted Dandroid5.4 and S3Rx3.0 without any problem.

I installed those ROMs into "Internal Storage" because enough space and because it's also quicker to create sparsed img files for all filesystems. Next time, I will try to install them on my external sdcard (vfat) when I free some space there.

Can you try one time again and, if possible, into internal sdcard ?

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Hi matrixzone,

To remove space used by multiboot roms, just delete multiboot directories

Not sure to understand what you mean by memories, but all roms have separated devices/filesystems ( boot, system, cache, data, efs, modem, persist ) and do not interact with your real ROM installed internally.

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
Phil_Suz

Thanks man! I got it to work after Smash2Bash and you suggested using "Internal Storage".I couldnt' really wrap my head around the fact that "Internal Storage" is one place to install a rom and any roms you make in "Create Roms" is another place. I was thinking "Internal Storage" was everything, including multiboot, so thats why I never used it to install

Thanks again guys! This thing is awesome!!

KM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
so in the 0/emulated folder thus I see it's on the root of internal storage, multi boot folder and then the ROMs are each in a folder and in each folder contains those files? not exactly but you know, the ROM encoded into images and whatnot. So by the looks of it there's absolutely no way to edit anything in /system/ seeing as this is all held on the internal storage, am I correct? Or for example would something in system/init.d be loaded up on boot for BOTH roms? That last one I doubt.. I assume it is for now that you can't change it but I'd like to know.

also, at ability? Just a straight up question with a straight up answer... What kind of bugs are in store for me when I try this at the moment? when you boot into any rom, is it running as if it was booting into the flashed rom? are there bugs in the actual rom after you hoot or is it bugs in recovery? is this suitable for a daily driver considering I don't want crashing freezing or needing to reboot as much as possible... one or two times a day I can live with but can I rely on this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
You can probably get to the ini.d scripts and stuff once you boot up. Because you can access the system folder of the rom but not the internal of anything else. One thing..might be just me. Xposed installer didn't stay installed when using certain modules..very odd. So you could test that if you use xposed. But if don't that's cool you know lol but its definitely daily driver material. No bugs with the Recovery itself.

Sent from my I747 using 4G LTE! ROM stands for "Remedy of Mediocrity" (says my girlfriend)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
yeah init.d scripts are nothing special they're just like any other sh file extension.... the only thing is that init.d files are scripts that are ran in alphabetical order *on boot* so for example a cleaner script running once on boot is nicer than downloading smanager and creating the macro or whatever for every script you have.

however the xposed stuff is interesting to me, which modules have you had trouble with? I LOVE xposed and run like 8 modules including greenify so support of that would be fantastic. is it in the cards for the future?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
I see. I kinda knew about them but wasn't sure. And I just check it seems that it disables with any module. You could test it. It may just be quantum having issues. And I'm not sure. The dev said after his project that he would give some more time to it. I'm just helping him out :)

Sent from my I747 using 4G LTE! ROM stands for "Remedy of Mediocrity" (says my girlfriend)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
berryman13,

I can confirm that Xposed does not stick, well for me at least, on Roms installed in Multiboot. I have S3Rx installed on Internal and it sticks fine, but I have Validus/GZOSP and SlimKat both installed in Multiboot and it does not stick with either of them. Now, if you go into Xposed and install it again and Soft Reboot, its fine, so I am not sure if that works for you or not.

Also not sure if anyone else came across this, but with Validus/GZOSP and SlimKat I had to install BMS Kernel to get them to boot. Other 4.4.2 Roms booted fine. Just thought I'd share my findings.

Thanks

KM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
That's fascinating....So actually the original rom stays UNTOUCHED and this "multiboot" rom is added onto it and within multiboot you can load others? I thought it was much more "intrusive" if you will, where you had to get rid of your rom and do an advanced fresh install of multiboot that supports 2 separate rom images....but what you explained is SO much more useful....so, no xposed but what are the other limitations?

Would the dev please answer this? Also, where do you see development headed and what are you currently facing? I'm super interested in this it would just be a pity for it to a) never get finished/die off or b) not enough interest or users....

I am considering using this so I can use touchwiz to watch youtube and stuff with my TV. However no xposed is kinda a stinker :( Makes sense though because if it's not a very dynamic image file w/ storage then it wouldn't save custom system stuff like xposed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
Berryman13

I thought the exact same thing, that it was going to be intrusive, but it wasn't at all. After messing with it for a few hours, and the other guys helping me out, I was able to wrap my head around the fact that internal stays the intact. What I did was did a complete wipe with my current recovery and installed S3Rx and got it all set up. Then I installed the Multiboot recovery, created a multiboot rom, installed it, booted it and set it up and then repeated for another one. Other than the Xposed not sticking on Multiboot (Like I said, sticks fine for Internal Roms) I found not real drawbacks from using this mod/recovery.

Thanks

KM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Good work on this project.

One ROM which is not booting with multiboot is Slim ROM latest release. Hope OP can nail down the issue soon..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Hi berryman13,

Yes you are right, roms do not share data each other.

After checked, I confirm that Xposed is not working but I think I found a fix. Next version is almost ready and will include this fix. No need to reinstall roms, Xposed will work ( I hope so... )

A new feature will also be added : ability to swap from one rom to another from android ( no need to boot to recovery and manual action to select rom ) with an android app.

screenshots :

Hi Matrixzone,

Can you point the thread ( just to be sure ), I will take a look.

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
why someone would have that many roms blows my mind but AWESOME next update sounds GREAT DUDE!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Here you go:

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

Slim is quite popular in AOSP world
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Hi,

Original message updated with new versions/features

Hi Mikessv,

It took (too) long time but zip version is now ready.

Hi saranhai,

Thank's for feedback on SGH-T999. I can build a version for this model (if users are interested in). Just need product.device (d2xxx) ?

Hi Smash2Bash and KingMike67,

Can you check if new version fixed xposed problem ?

Hi matrixzone,

Is it Slim-d2att-4.3.build.2.2-OFFICIAL-1738.zip ? Because in my case, I did not have problem to install it.

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] saranhai:
SGH-T999 product.build.device is d2tmo :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The latest version is v2.6 RC2.

Download link:

http://slimroms.net/index.php/downl...51-slim-d2att-4-4-2-build-2-6-rc2-weekly-2670
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
This is incredible! I can't believe how well it works. Only thing I've noticed, and I'm sorry if it is a known issue and I missed it, is that I create a rom, set it, goto install, and get an error if I try and install FROM the internal memory. If the rom zip is on my external, everything is fine. I can browse to it on my internal, but in get an error as soon as I try and flash.

Not a big deal, but just wondering if that is how it's supposed to be. Thanks,

Andy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mkfryan:
Thanks this is just awesome! I've been hoping for this since it came out for my n7! Works flawlessly after I moved all rom files to my external SD

Making the iPhone jealous one user at a time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Yes it was a low level bug on kloard_hardboot ( kernel/ramdisk injection ). Version 1.1 has been posted on first message with fixed bug.

For future versions, I would like to reduce manual operations under TWRP and move maximum of things inside multiboot apk. In that case, this kind of malfunction will be corrected. However lot of work before to achieve this...

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Hi saranhai, d2tmo version of multiboot is ready. Zip file is attached to this post. If you can test it and if it is working well, I will post it to T999 forum.

Thank's,

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
Phil_Suz,

Wow man, you are incredible! I never got a chance to test the updates until tonight and version 1.0 fixed the Xposed problems. Everything is working flawlessly!!! Tomorrow morning I will re-flash my 4.4 roms to test the 1.1 update to make sure the packaged rom kernels work. Kudos to you and everyone else involved in this project, its truly awesome!!!

Thanks

KM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
Phil_Suz

Just an FYI, the zip you uploaded for version 1.1 is only a zip of the recovery, not one that can be installed in recovery. Not a big deal, I just opened it with 7Zip and put in the new recovery. Also it looks like the d2tmo zip is the same, just a zipped version of the recovery, not an install zip. After I loaded it all up, I installed carbon and did not have to flash a separate kernel for it to boot. Also reinstalled my other roms that needed a separate kernel and all is good. Great update! Keep up the good work!!!

Thanks

KM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Thanks KingMike67, fixed ( main message ) and also zip for d2tmo in previous message.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] saranhai:
Tested and all good to go, thank you for your contributions!

Side note: Does installing ROMs on external SD affect the behavior of the ROM (speed, freeze ups, random FC's, cannot mount /system as rw).

I'm having issues with another 4.4 ROM (AOSB) and am currently facing these issues... :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wickedninjalo:
Thank you very much! I was hoping someone could make this up for us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Hi, thanks for feedback.

Internal eMMC is more performant than external sd. So speed of roms running externally is a bit affected, especially at first boot. But I did not notice big differences.

There is indeed a problem mounting/unmounting /system (causing xposed framework not working properly ) but since version 1.0, multiboot mount by default /system rw. It solved the problem of xposed and did not notice side effects but maybee you found some. In fact, I use loop native functions directly inside init.rc, it is very simple but has this drawback.

Trying to do some funny things with multiboot, I succeeded to create a full live android ( all the system in memory, eMMc and sdcard not mounted) and to implement this, I had to find a better way to manage fs mounting. I think that this new method will possibly solve the mount/umount problems.

On this subject, can somebody tell me if it exits some "light" TW roms, I mean with a /system size not too big ( ~500 MB max ) ?

Thank's,

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingMike67:
Phil_Suz

The Dandroid series of TW Roms have always been the lightest I've found. Dandroid 5.4 (TW 4.3) is pretty heavy in /system, about 800mb, but version 4.7 (TW 4.1.2) is just over 500mb. Not sure if that good enough for your tests or not. You can download it here (Under downloads he lists the 4.1.2 version)

Hope that helps

Thanks

KM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Hello, I have a few questions before I try this.

1. will this work for i747m Canadian telus? With newest modem and bootloader.

2. Is this basically the same as multirom for nexus 7? I'm quite familiar with multirom for the n7.

3. Does ktoonsez kernel support hardboot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Hi ronedogg :

1 - The answer is probably yes but has to be confirmed. If you can install a custom recovery, just try it.

2 - Yes, as multiboot use original mkasic method (hardboot) with some adaptations.

3 - Yes, targeted kernel does not need any adaptation. To explain this, it is because the kernel that can load another one is only installed on the recovery partition and the targeted kernel/ramdisk is loaded and booted from there.

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Thanks!

I'm going to flash this tomorrow. I will update my success or failure lol

When I updated my bootloader and modem for the i747m I remember reading I can't install tar files or something. This is a zip I should be fine.

Is this going to be moved to the development thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
Works fine on my I747m (rogers). Should be the same hardware. And yeah, can't install tar files through recovery, you need Odin on the PC, or sometimes Mobile Odin can work on your device. The zip works great in recovery though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Did you update your bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
I had prior, I'm on mk5