yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Gibson99:
the tool i used is basically just a front end/wizard. it installed and opened odin then walked me through (told me what to click, when to do power/home/volup, etc) flashing twrp onto the phone. it walked me through everything from installing drivers to doing root, and killing knox. pretty awesome utility, really, especially considering how many different devices it supports.

that said, i didn't follow its instructions perfectly - after twrp was installed the first time, something in the phone put the stock recovery back on (which the tool said happens sometimes), so the tool walked me through fixing that. then when i quit out of twrp, it offered to install supersu, which i did. booted into the stock rom, opened supersu from app drawer, it downloaded and installed the rest of the supersu package, detected knox and offered to kill it, which i did. knox is still listed in the installed apps, and of course i can't "turn it off", but su seems to be working - i was able to install busybox, use the root explorer functions of es file explorer, and flash the standard twrp from inside android using twrp manager - so i obviously do have root. didn't use root checker, but at this point i don't think i need to.

i still have stock 4.3 on the device memory. basically the only thing that has been replaced is recovery. my intention was to leave the stock rom alone and have a custom rom as the secondary using multiboot. but after watching a few other videos about multiboot, it looks like i should make a backup of stock, restore that to a secondary "rom", then flash whatever i want to try into the actual system partition. that way when i reboot, it'll stay in the custom rom rather than reverting to stock. safestrap worked a little nicer in this respect - you would just select which rom slot you wanted to be active - stock or 1-4 - and every time you rebooted, it would always boot to that active rom slot, unless you interrupted the boot process and chose a different slot.

anyway, using standard (non-multiboot) twrp, i still wasn't able to write a backup to my sd card, so that tells me something's goofy. i was using a 32gb sd card formatted in fat32, which ought to be fine for regular use in twrp, right? it can obviously mount it because i can browse the sd card inside twrp and even delete stuff from it. the only thing on the card right now is the multiboot zip and a couple zips for cm11 and cm12 and their respective gapps.
[T-Mobile, Samsung Galaxy SIII] Gibson99:
so after making a couple of backups of stock, decided to just try putting a rom in the stock area without trying to multiboot. got exactly the same results. so apparently i've got multiple bad downloads of different roms. gonna try downloading them to the sd card directly rather than downloading to my server then copying to sd card... if that works i'll be pissed but at least i'll be able to use the phone.
[T-Mobile, Samsung Galaxy SIII] ShernDog:
Gibson, you should try to ODIN back to stock 4.3. Get the root66 tar file from Doc's post and use ODIN to flash it using the PDA option.

After you do that, flash the latest TWRP tar file using the BOOTLOADER option in ODIN. Be sure to uncheck auto restart, and once it is done boot STRAIGHT into recovery.

Once you do that boot up the stock ROM, get a GPS lock so that works and make sure you get an internet connection.

After that, flash the MultiBoot version 2.2 zip in TWRP and reboot recovery. You're now ready to flash a new ROM and use the MultiBoot feature.
[T-Mobile, Samsung Galaxy SIII] Gibson99:
well i've found some issues in the cm11-based rom i'm using right now - camera not working is the biggest. i think for now i'm gonna go back to stock, root, debloat, and learn how to use xposed modules. Keep It (relatively) Simple, Silly. :p
[T-Mobile, Samsung Galaxy SIII] ShernDog:
If camera isn't working in CM11 based ROMs you definitely need to ODIN to stock... Because something is messed up. But after that and updating modem etc. you will be set. The latest CM12 ROMs now have working camera and video as well.
[T-Mobile, Samsung Galaxy SIII] chalky7880:
Has anyone had any luck flashing any of the new cm12 5.1.1 roms from the last couple of days using multiboot? I can flash 5.1 roms but every 5.1.1 rom seems to fail.
[T-Mobile, Samsung Galaxy SIII] draymond1987:
Seeing as this thread might be dead: I hope the OP or somebody can help. I had the latest multiboot and I had the latest firmware on my T999 (but I converted it to T999v ) Hey, 4.4.2 is better than 4.3 :D Anyways, whenever I boot into a secondary ROM, it's brutally slow, and just crashes all over the place. I know it's not my ROMs or Backups, because I flashed them using the latest TWRP. Is there a reason that secondary ROMs are like that? I tried a TW based ROM (stock,to be exact) and made another TW as the secodary. Or made stock the secondary. I can't remember. Also 5.1.1 completely flashes with no problems, but it's brutally slow. Is it because my SD card isn't formatted as the OP states? I didn't try Internal because I don't have the space to try. I believe my SD card is FAT32? I have ADHD and just forget everything LOL.
[T-Mobile, Samsung Galaxy SIII] Fry-kun:
Does not work with Marshmallow

Trying to install on internal storage: http://forum.cyanogenmod.org/topic/123220-cant-install-cm13-in-multiboot/

On external storage, qcow2: installs to root device, not the virtual one (TWRP/multiboot reported I was in my "virtual" env. while installing)
[T-Mobile, Samsung Galaxy SIII] noidodroid:
BUMP

To OP [MENTION=5593099]Phil_Suz[/MENTION] or anyone else you can shed some light on this ... Was there ever a d2vzw (Verizon) coded? I read in a post Phils had versions for all the main US carriers models but when i visit AFH https://androidfilehost.com/?w=files&flid=12830 and attached here i see ATT and TMO. Nothing under Verizon (d2vzw) which is what i'm on the hunt for. Thanks'

EDIT: Ok so yeah recovery works on d2vzw and now im attempting getting all the rest working.
[T-Mobile, Samsung Galaxy SIII] noidodroid:
Bump
[T-Mobile, Samsung Galaxy SIII] LoGiK915:
Amazing

This is awesome. Works perfectly once you figure it out. Thanks a lot.
[T-Mobile, Samsung Galaxy SIII] jtford:
Video plug-in

My phone is showing "plug-in needed to view content" where the videos are posted. Just flashed S3RX and have never seen this on here before. Anyone know which plug-in I need?
[T-Mobile, Samsung Galaxy SIII] Tomb77:
What exactly are you saying. Are you trying to view the tutorial videos on the op from your phone?
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Beautiful job. Simple to use and worked like a charm.
[T-Mobile, Samsung Galaxy SIII] jtford:
Yes, that's correct. I should have specified.
[T-Mobile, Samsung Galaxy SIII] Tomb77:
I just used the XDA app and could watch the second two YouTube tutorials, but not able to watch the first one for some reason. I had no issues watching any of them from the browser. Assuming you used a browser, you should try another one or the xda app.
[T-Mobile, Samsung Galaxy SIII] jtford:
Will do. Thanks. Hopefully all goes well. I really want to be able to have TWRP & CWM to switch between. Been having issues with flashing using the latest of both for some reason.
[T-Mobile, Samsung Galaxy SIII] Tomb77:
How long has it been since you odin back to stock and full wiped with the original recovery? If it's been a while you may want to and start things over before you start messing around with multiboot. I was having issues with roms and flashing that became to random and after I did this I mainly have the issues that most others have with different roms and such.
[T-Mobile, Samsung Galaxy SIII] jtford:
Never have actually. Guess I need to find a stock 4.3 to odin with and try. I've only odin for root and recovery. Never rom. Could that be why my LTE SUCKS beyond all belief? Connections usually time out before loading. I've tried literally every modem firmware for the AT&T SGH-i747 and they don't work at all. No service, period! I'm on S3RX MJB which is the only one that gives me cell and data. Would be the best rom I've flashed if the data was worth a damn. There's got to be something I can do to fix it. Just don't know what. :(
[T-Mobile, Samsung Galaxy SIII] Tomb77:
What SGH model do you have?
[T-Mobile, Samsung Galaxy SIII] jtford:
It's an unlocked i747 (att) that I use on tmo thru net10. I just tried the tmo s3rx MJC which provides a little better results, but not good enough for daily driver. Damn I want this to work. Love the rom!
[T-Mobile, Samsung Galaxy SIII] Tomb77:
Sounds confusing, you should throw your issues up on Q&A. At&t or tmo, which forum I don't know, maybe both will get you some help. I would before you go back to stock.
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
I probably just missed something somewhere but I can use multiboot app to get into my secondary rom but I can't boot back to my primary from it. It only shows (int)asob in the drop down. Just curious since I can boot primary by just restarting.
[T-Mobile, Samsung Galaxy SIII] Tomb77:
A regular reboot will get you into you original rom, whether you reboot from current rom or recovery it will boot the origional. Only the secondary roms show up in the multiboot app and can be boot from the app or recovery.

Edit: For me the multiboot roms do not show up in the app when in my original rom, so from the original I need to go to recovery in order to boot a multiboot rom.
[T-Mobile, Samsung Galaxy SIII] :
Just to confirm...if I set up a recovery ROM (such as PhilZ) as a secondary recovery, any actions I take with it only affect the internal ROM. Correct?
[T-Mobile, Samsung Galaxy SIII] Tomb77:
I haven't used multiple recoveries yet. You may find your answer on the AT&T thread linked on the OP. I may mess with it in a couple of days but I am running four roms plus the internal right now and don't want to mess it up. I would like to know too.
[T-Mobile, Samsung Galaxy SIII] :
I set up PhilZ's latest recovery as a secondary recovery and I used it to flash a new ROM on my internal memory. Worked like a charm.
[T-Mobile, Samsung Galaxy SIII] kojam:
Uhm...

Am I missing something?

I flashed the twrp as my recovery, wiping out my CWM recovery..

I created the recovery just like him in the vid. It only created a blank folder? Is there an actual recovery that I need to download? A zip file? Or was the attached twrp the one I'm supposed to use again? I tried to install that again (where he installs recovery in vid) but it fails during creation.

Do I need another file? I'm confused...:eek::confused:

Thanks!
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Hi all,

New version is now ready. Change log in first post.

http://www.androidfilehost.com/?w=files&flid=12801

Philippe,
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
New version at&t only?
[T-Mobile, Samsung Galaxy SIII] Tomb77:
No update also available for the d2tmo.
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
From the link, there are 4 subdirs - d2aat, d2tmo, d2vzw and d2spr. Go to the right subdir to download your model version.

Philippe,
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Cool.

I saw the linked page showed folders and a file labeled as att
[T-Mobile, Samsung Galaxy SIII] Tomb77:
Just to confirm. Did you find the tmo zip?
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Yeah. Its lower on the page in the "popular downloads" thing.

---------- Post added at 03:59 PM ---------- Previous post was at 03:59 PM ----------

Yeah. Its lower on the page in the "popular downloads" thing.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
AFH is down. Does anyone have a mirror?
[T-Mobile, Samsung Galaxy SIII] Tomb77:
AFH is back online. Is the multiboot app no longer working with this recovery? When I use it, it always just boots into recovery.
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Works fine for me. Booting from internal (pre-existing) to an internal rom w/o fine. Reboots to initial rom like always.
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Works fine with ktoon kernel too.

Dual boot + overclock ftw.

Only issue im having is moving files from one internal sd to the other so I can install secondary roms and zips without an sd card.

I wouldn't have noticed that if I didnt have to make my sd card a bootable usb drive earlier today for a friend to borrow.
[T-Mobile, Samsung Galaxy SIII] ktetreault14:
Will you be able to make for tmo note 3.
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Ok... well, I played with this and found one more issue.

A flash went bad on my second rom and its stuck in a boot loop.

However I cannot get it to boot recovery or first rom. It just tries to boot to the secondary (broken) rom.

I "fixed" the issue by using odin to flash cwm recovery but if I put this one back on I get stuck in a bootloop of death.

Any way to remove the script telling my phone to boot to the secondary rom so I can use multiboot again?
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Hi ktetreault14, I don't own a note 3 but as my method is quite easy to adapt, I think it could be possible. I will need to download CM for note 3 and get few answers ( content of /proc/iomem for example ). If you want to do it by yourself, I can give you indications.

Hi tokenpoke, I don't know well stuff about secondary rom. Maybe you'd better to ask in questions forums.

For All,

Version v2.0 is now ready with qcow2 support.

I opened a dev thread in d2att sub to continue discussion about this projet and to start to speak about how it works and technical aspects. If you wish, you can go there now.

http://xdaforums.com/showthread.php?p=51144880

Philippe,
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Has anyone ever just deleted the boot to file or the whole multiboot folder?

I mean, I can test later and see if that fixes it but im at a gig and need my phone.
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Renaming the multiboot folder worked.
[T-Mobile, Samsung Galaxy SIII] ktetreault14:
Wow thanks man for even considering to Dev a device you dont even have. I would love to help and we do have official CM also.
[T-Mobile, Samsung Galaxy SIII] OdiemanSAM:
Is there anyway to use the Multiboot.apk in the internal rom to boot back and forth between my second rom and my internal daily driver? when I open the app in the second rom it shows the rom I have loaded but when i go into recovery and restore to internal i can not see anything in internal app for roms to boot to.
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Hi ktetreault14, successfully received iomem content, I will take a look when I get time to work on it. keeping this to my mind.

Multiboot.apk has to be rewritten (since v1.2). will start to rewrite this hopefully soon.

Philippe,
[T-Mobile, Samsung Galaxy SIII] ktetreault14:
Thanks you very much man
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Hey guys. Word of warning.... this recovery does not play well with flashing roms that have an AROMA installer as the secondary rom. It caused bootloops in every test I did yesterday. Seems like the aroma installer forces an install of the boot partition on the first rom slot (internal rom) and writes the rest to the multiboot folder.

Not 100% sure, thats just what it seems to be doing based on my experience.

---------- Post added at 01:26 PM ---------- Previous post was at 01:15 PM ----------

Hey. Figured I should let you know a couple things so you can put them in the op....

If your second rom is bootlooping you can fix it by removing the scripts in the "multiboot" folder using one of three options...

1. Adb commands (must know how to use adb and command prompt, just rename the folder to anything)

2. An advanced cwm with file manager

3. Flash any other working recovery and use the phones file manager.

For options 2&3 you must use odin to flash a different recovery than this one as this checks the scripts to decide where to boot from.

After deleting the scripts or renaming the folder you can boot back to your internal rom with no issue.

I havent found a way to stop the loop without a pc as it wont boot into recovery once the loop starts.
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Hi tokenpoke, it's a bit weird that you the only one that report this. Never got this behavior during my tests neither with aroma nor others.

Did you follow strictly the video examples ?

If you want that we troubleshoot, you can, after selected "SET ROM", and select a rom ( red color on top ), just go with adb shell and launch these 2 commands :

"ls -al /dev/block/mmcblk0p*"

"losetup"

and send the results.

also can you give precisions about : multiboot version, image type (img or qcow2), where you install ( internal sdcard or external sdcard) and rom that you want to install. I will see if I reproduce that.

PS : And please don't quote me on a sentence that I never wrote ! (Originally Posted by Phil_Suz View Post

some stuff I deleted because I dont know how to tag on tapatalk)

Philippe,
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Oh, no I quoted you and just deleted the stuff between the quote bracket. Lol.

Sure, let me backup my phone and put dualboot recovery back on real quick.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
[MENTION=3900179]tokenpoke[/MENTION]: this is how you tag somebody on XDA so you know for the future

Sent from my Cleared Out T999L on CM11
[T-Mobile, Samsung Galaxy SIII] xoxo_xdagirl91:
This sounds pretty awesome. Quick question before I try this, if I install two roms and decide to remove one, how would I do that? Do I have to do it within the recovery or just delete the files from the sd card?
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Removing the secondary rom is as simple as deleting the multiboot folder, specifically the boot scripts and the rom folders you dont want anymore.

Backup data first (like any downloads or pics that you didnt save to sd) or just move them to external sd with es file explorer or similar.

You can optionally delete from within recovery.

If you want to delete the main rom and use one of your secondary as primaries ive done that by backing up my second rom (with the backup otion in recovery) and then wiping the main rom and restoring my backup to there.
[T-Mobile, Samsung Galaxy SIII] xoxo_xdagirl91:
awesome, thanks! :good:
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Hi tokenpoke,

Commands are correct, you have to launch them on the device : "adb shell ls -al /dev/block/mmcblk0*". Sorry if it was not clear in previous post.

If you can, can you upgrade to v2.0, as v2.0 better manage return codes from scripts ? In fact, v1.2 was an intermediate version, it is recommended to go to v2.0. Already installed multiboot roms will still work.

Philippe,
[T-Mobile, Samsung Galaxy SIII] :
For some reason, using 2.0 with Cyandelta doesn't kick off the automatic update. I went back to 1.2 and the auto update works perfectly.
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Thanks Phil.

I did upgrade and realized the partition SD card option poofed. I don't mind as I don't plan to use it.
[T-Mobile, Samsung Galaxy SIII] Ellises:
I just got a Nexus 5 earlier this month and I am using multiboot on it which is fluid... the multiboot option on the recovery is more friendly (I think), and there is even a screen when you boot the phone to allow you to select the rom to boot.

How different is this multiboot mod compared to the one used on the Nexus 5 (technically)?

At the moment I'm trying this out, on the first step to setup a new rom. I chose the external sdcard and i've been waiting 10 minutes now.

I kind of wish there was a cancel option for i could just choose the internal instead.
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Hi All,

Multiboot v2.11 is now ready.

This version adds feature to multiboot ubuntu touch 14.04 on galaxy S3 ( img format only, external sdcard strongly recommanded).

I did this ubuntu port on my d2att model but it could possibly work on your device.

If you want to test, I prepared a d2lte test version (0.13) here : http://www.androidfilehost.com/?fid=23329332407583872

Important recommandations and details of working features can be found in this thread : http://xdaforums.com/showthread.php?t=2702692

multiboot v2.11 is at same usual location.

Note : Please let a feedback message in this tread or original one if you tested it. if you report that it is not working, I will remove download link.

Philippe,
[T-Mobile, Samsung Galaxy SIII] Tomb77:
Thanks for the update and all the work. Would give the ubuntu port a go. Is it d2lte unified, I'm have t999? No file to dl in the link though, is it not working?
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Hi Tomb77, yes I removed the link as cell features (gsm and data) were not working on d2vzw.

I created specific versions, has to be tested.

Download links are there : http://www.androidfilehost.com/?w=files&flid=13392

Philippe,
[T-Mobile, Samsung Galaxy SIII] Tomb77:
Thank you. I will test it out in the next couple of days.
[T-Mobile, Samsung Galaxy SIII] Tomb77:
I successfully booted ubuntu. I used internal. No apparent issues. It took a couple mins to install and booted in less than a minute. Will play with it.
[T-Mobile, Samsung Galaxy SIII] Anthonol:
Sweeeet! Did you get a data connection on the Ubuntu Touch (4G, 3G, EDGE, WiFi) and if so does regular calling work?
[T-Mobile, Samsung Galaxy SIII] Tomb77:
Wifi works great. Data says 3G and works, pulling 4G speeds here. Apps like browser and phone come up with a white screen after a while when trying to access them. Calling doesn't seem to work, will have to test it more. The bar shows one. Sms works great. Naving and the touch-only is a lot to get use to. Moves slow mostly and after trying to stress it out, there are no crashes. Looks great, would be amazing to have a beta.

Without multiboot, this wouldn't be so pleasant. Can't say it enough, thank you to all who made this happen.
[T-Mobile, Samsung Galaxy SIII] Anthonol:
I realize that sometimes it crash to lockscreen but there is no prompt displayed to say it crashed but when you try to go back to you were doing, you realize that the app you were using was closed.... Music player needs work, file manager does work but it seems to be able to only copy and paste one item at a time, social networks doesn't seems to sync contacts to phonebook but that's ok since the calling is busted, I received a text message though.... I like it despite the kinks though, I hope to see improvements on some of the above mentioned next build....:D
[T-Mobile, Samsung Galaxy SIII] Phil_Suz:
Thanks for your feedbacks. If you get no audio during calls, here is a working patch on my d2att : http://www.androidfilehost.com/?fid=23329332407584604

This ubuntu version (14.04) is still in beta from ubuntu. Hopefully some of problems (not caused by the porting) will be fixed at official release.

Important

: When installing the patch, dont't forget to do "multiboot" -> "set rom" -> "your unbuntu rom" before installing patch.

Philippe,
[T-Mobile, Samsung Galaxy SIII] Tomb77:
I assume we shouldn't wipe anything? Thank you
[T-Mobile, Samsung Galaxy SIII] allendj81:
delete