[T-Mobile, Samsung Galaxy SIII] tokenpoke:
[MENTION=4686120]Adreaver[/MENTION] thanks. didnt know that worked on tapatalk

[MENTION=5593099]Phil_Suz[/MENTION]

Adb

ls -al /dev/block/mmcblk0p*

losetup

twrp d2tmo v2.6.3.0 mb v1.1 (flashable zip)

steps used (starting from fresh boot into recovery

advanced

multiboot

create new rom (on internal sd)

set rom (named test)

open terminal on ubuntu 13.10

adb (sucessful)

result of other commands..

tokenpoke@tokenpoke-E-475M:~$ ls -al /dev/block/mmcblk0p*

ls: cannot access /dev/block/mmcblk0p*: No such file or directory

tokenpoke@tokenpoke-E-475M:~$ losetup

Usage:

losetup loop_device give info

losetup -a | --all list all used

losetup -d | --detach <loopdev> [<loopdev> ...] delete

losetup -f | --find find unused

losetup -c | --set-capacity <loopdev> resize

losetup -j | --associated <file> [-o <num>] list all associated with <file>

losetup [options] {-f|--find|loopdev} <file> setup

Options:

-e, --encryption <type> enable data encryption with specified <name/num>

-h, --help this help

-o, --offset <num> start at offset <num> into file

--sizelimit <num> loop limited to only <num> bytes of the file

-p, --pass-fd <num> read passphrase from file descriptor <num>

-r, --read-only setup read-only loop device

--show print device name (with -f <file>)

-N | --nohashpass Do not hash the given password (Debian hashes)

-k | --keybits <num> specify number of bits in the hashed key given

to the cipher. Some ciphers support several key

sizes and might be more efficient with a smaller

key size. Key sizes < 128 are generally not

recommended

-v, --verbose verbose mode

install stock modded rom 4.3 v4 from team inferno

aroma starts fine. Using stock aroma theme settings.

Start custom install

got success notice in aroma, pressed “next”

allowed aroma to send reboot commands

boot screen shows ktoon kernal spalsh. (its what the first rom was running...)

Boots to internal rom, not secondary.

Open multiboot app

select test rom....

boots cm guy splash

and apparent brick....ten minutes and 0 response.

Pull battery

reboot recovery

advanced

multiboot

boot rom (test rom)

starts booting.

Leave to grab monster and smokes

and... it booted.... weird

partitions in multiboot folder end in .img btw i seem to remember seeing "qcow2 successful" or something along those lines last night.

also, while coming back from the store i realized i didnt see the "repartition sd card" box last night or any other time before (i never intended on using it so i didnt notice it was missing) so maybe my recovery was a tiny bit corrupt or something despite it working fine to flash the aosb rom multiple times.

oh, and one last thing... did you mean "ls -al /dev/block/mmcblk0" and not mmcblk0p*? im just guessing here but dint bother running it anyway.

---------- Post added at 10:34 PM ---------- Previous post was at 10:15 PM ----------

[/COLOR [MENTION=5593099]Phil_Suz[/MENTION]

sorry dude. i just made a HUGE error in that whole process. last night i was using the v1.2 recovery.

let me do the whole thing over again.

sorry for wasting your time brb.

---------- Post added at 11:04 PM ---------- Previous post was at 10:34 PM ----------

ok. im back

repeated the same exact process, got same results except one minor tweak.

booting from multiboot app froze system and had to pull battery and then booting from

advanced

multiboot

boot rom

did the same. worked like a charm the second time and i did not see the cow message that i saw last night.