yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] canne:
Unable to boot virtual

I followed q&a and instructions, but I was only able to boot virtual copied from stock once.

Now I find this in the log:

[12-12-2014 07:06:24] MultiSystem <0256>

[12-12-2014 07:06:24] Exit 0

[12-12-2014 07:06:24] Turn on LED R: 0 G: 255 B: 0

[12-12-2014 07:06:24] Find gpio keys event node

[12-12-2014 07:06:25] gpio keys: /dev/input/event13

[12-12-2014 07:06:28] Turn off LED

[12-12-2014 07:06:28] MultiSystem <1234>

[12-12-2014 07:06:29] Exit 0

[12-12-2014 07:06:29] MultiSystem <1235>

[12-12-2014 07:06:29] Exit 0

[12-12-2014 07:06:29] VOLUMEUP key pressed

[12-12-2014 07:06:29] MultiSystem <1320>

[12-12-2014 07:06:29] Exit 0

[12-12-2014 07:06:29] Booting Stock System!

[12-12-2014 07:06:29] MultiSystem <1327>

if I:

- run reboot virtual

- press up

- press down

- select primary

- select secondary

- mount rootfs and system r/w before selecting virtual

What am I missing?

I'm on a samsung S5 international (g900f) with lollipop and MS 1.3.1

Thank you for any advice
[Android Software/Hacking General [Developers Only]] s0ulreaver:
Does this work on the Canadian Galaxy S4 i337m?

Thanks
[Android Software/Hacking General [Developers Only]] canne:
Since it may be useful to somebody with my same problem: I resolved uninstalling MS, mounting again rootfs and /system r/w and reinstalling the APK.
[Android Software/Hacking General [Developers Only]] hsbadr:
MultiSystem v2.x Update

MultiSystem v2.x is the 2nd generation that will support different ROMs with separate data & cache. It'll also provide options to skip microSD card partitioning to make it easy to install & operate for a longer list of supported devices. No ETA though! I'm very busy writing my PhD dissertation; just wanted to provide updates for the followers of this project.
[Android Software/Hacking General [Developers Only]] benlm72:
Multisystem: Not found

Hi,

I've tried to install MultiSystem on my Galaxy S4 gt-i9505 with stock samsung lollipop 5.0.1.

I've read the thread and followed the OP. All is OK till the TE command to update busybox. At this point I get an error message telling me Multisystem: Not found. I've checked that \MultiSystems directroy exists, but it is empty. I've tried to update configuration according to the pdf doc found in the thread : no change.

The log in /data/log/MultiSystem.log doesn't show errors, always exit 0 on commands.

Could you tell me what's wrong with my process ?

Thank's !
[Android Software/Hacking General [Developers Only]] mystic74:
Are you sure you followed the steps below(for some mount steps are very crucial):

READ everything about MultiSystem here & Q&A thread

BACKUP all your data to an external storage or computer

INSTALL a stable stock ROM for your stock system

PARTITION your microSD card as described (here)

DOWNLOAD the latest version of MultiSystem APK

MOUNT rootfs & system read/write in Terminal Emulator

Code:

su

mount -o remount,rw rootfs

mount -o remount,rw /system

INSTALL BusyBox to /system/xbin

INSTALL MultiSystem APK & open it

INSTALL MultiSystem binaries by pressing Install button

UPDATE BusyBox by runnig the folowing commands in Terminal Emulator

Code:

su

MultiSystem advanced update_busybox

REBOOT to check LED indicator for boot options

CHECK permissive SELinux after reboot

Now, you should be able to create a virtual ROM & boot into it...

---------- Post added at 09:49 PM ---------- Previous post was at 09:47 PM ----------

You may install busybox via busybox app from play store as well
[Android Software/Hacking General [Developers Only]] muniz_ri:
Fantastic, thx. And I believe you mentioned it early on as a future addon but at some point having the ability to boot into a twrp like ramdisk instead of a virtual system would be extremely well received.
[Android Software/Hacking General [Developers Only]] benlm72:
Yes I've followed these instructions.

After rebooting my phone, the MultiSystem command to update busybox ran fine, perhaps was it necessary to fix some modifications before going on ?

Now I'm a little lost with the app : I just want to install and run another rom (cm12.1 opt) in the virtual system, but I don't really find how to do ?

And I'm not sure to post in the good thread : this one or the Q/A's one ?
[Android Software/Hacking General [Developers Only]] hsbadr:
Check the Q&A section posts #1-6! Everything you need is explained there. If you've successfuly repartitioned your microSD, you should find /MultiSystem directory & then, you may need to manually link the binary:

mount -o remount,rw /system
busybox ln -sv /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem

I agree that 2nd-init recovery on LP+ would be great. It'll also be very handy to add support to create/flash/manage virtual/stock system(s) in the recovery. It's getting improved by eliminating the complex steps (like partitioning) & I'll consider adding option to load TWRP ramdisk on boot for low-level recovery/flashing, mainly on locked-bootloader devices.
[Android Software/Hacking General [Developers Only]] benlm72:
Hi !

Thank's for your answer ! What I don't manage to understand in the posts you mention is how to install a zip rom. To be clear :

- I think MultiSystem is now correctly installed on my phone

- do I have to create an img for my stock rom ?

- I don't find an img of the cm12.1 opt rom, just a zip file : how do I creat it/install it as the first virtual rom, so I can have my stock rom and this cm12.1 one ?

Many thank's for your help.
[Android Software/Hacking General [Developers Only]] jaymazz13:
So after partitioning my SD card I downloaded multisystem apk on my Verizon note 3. I installed busybox actually updated since I already had it installed and opened multisystem and installed, it looks like it installed correctly and I do see multisystem files on my root directory but it wont launch terminal emulator from the multisystem app so when I launch terminal emulator and check status I get a touch: /multisystem/log//multisystem.log: read-only file system all the way down and in between some of the logs I have a multisystem for android (c) 2014-2015 hsbadr [MENTION=243864]xda[/MENTION] message then some more logs then if you'd like to donate message then some more logs

Not sure what I did wrong, but I can't create a virtual image so something is wrong, any help would be appreciated, thanks
[Android Software/Hacking General [Developers Only]] hsbadr:
For easier flashing & to be able to smoothly switch between different ROMs (e.g., AOSP- & Manufacturer-based ROMs), I'd recommend to wait for MultiSystem v2.x.

You need to install Terminal Emulator & FlashFire separately. Also, check this post for general information & video tutorials for VZW Note 3, besides MultiSystem Q&A thread posts #1-6.
[Android Software/Hacking General [Developers Only]] midimench:
Followed instructions to the letter last night, and successfully installed the Jasmine 5.1 rom image, but let me warn everybody who doesn't want to install this 2X, do not tell titanium backup to restore the old ID. If you do, your phone will reboot into a hopeless loop, and you have to start everything all over again. Instead tell TB to start a new ID. Save yourself the 2 hours I wasted.
[Android Software/Hacking General [Developers Only]] BobC43:
Thanks for the heads up!!!!!
[Android Software/Hacking General [Developers Only]] outbackpaul:
I'm on a 4.4.2 ROM with Safestrap. I want to leave that in the stock slot. Do I uninstall Safestrap before installing Multisystem? When do I do that in the process?
[Android Software/Hacking General [Developers Only]] midimench:
Go to the Jasmine 5.0 rom instructions and follow them carefully. It will step you through installing it (which is lollipop 5.0 rooted). It requires safestrap 3.75 b4, and version 4.4.2 to be present. It will take you through a process of installation and odin. When you come out of the rabbit hole, safestrap will be gone and your new, rooted lollipop in its place

Sent from my Galaxy Note 3 with Jasmine 5.1 and MultiSystem 1.31

---------- Post added at 03:51 PM ---------- Previous post was at 03:50 PM ----------

Removing safestrap on your own would screw up the whole deal.

Sent from my Galaxy Note 3 with Jasmine 5.1 and MultiSystem 1.31

---------- Post added at 03:56 PM ---------- Previous post was at 03:51 PM ----------

Here is the website for the Jasmine ROM: http://xdaforums.com/showthread.php?t=2760380

Be sure to go to page 1. Once 5.0 Jasmine is running, you'll use flashfire and run the Jasmine 5.02 upgrade. After that, you install MultiSystem 1.31.

Sent from my Galaxy Note 3 with Jasmine 5.1 and MultiSystem 1.31
[Android Software/Hacking General [Developers Only]] BobC43:
Loaded Jasmine 5.1 and running fine. Played with Xposed and all seems well.
[Android Software/Hacking General [Developers Only]] midimench:
What exactly is exposed, and why should I even touch it.

Sent from my Galaxy Note 3 with Jasmine 5.1 and MultiSystem 1.31
[Android Software/Hacking General [Developers Only]] outbackpaul:
It's an app that gives you access to more mods.

http://repo.xposed.info/module/de.robv.android.xposed.installer
[Android Software/Hacking General [Developers Only]] benlm72:
Hi,

I finally manage to install MultiSystem, create an img from my stock rom and switch between the stock rom and the img (checked with MultiSystem status).

I've tried to flash a rom zip after mounting the copy img, but it failed. Tried with Terminal Emulator as advised, but the pb is the same. I've tried to flash it via FlashFire, without success (is seems to work but when I reboot after wiping cache and dalvik, my phone stays stucked on the samsung logo or the rom animation). I will wait the MultiSystem v2 version : when do you think it will be released ?

And I have another question : when I set the first primary img and boot on it, it works fine. If I use my TWRP recovery to flash a rom when MultiSystem is set to boot on the primary img, do the flash will affect the primary img or the stock rom ? Thank's for your answer !
[Android Software/Hacking General [Developers Only]] xGMERZ:
Have you managed to separate data/cache for the primary and virtual roms?
[Android Software/Hacking General [Developers Only]] trav11887:
I'm currently on SafeStrap B04 with JAZROM 2.44. Do I need to flash to a stock rooted room and uninstall SafeStrap? Thanks in advance.
[Android Software/Hacking General [Developers Only]] hsbadr:
TWRP will flash based on the updater-script in the ZIP file, which 99.99% will mount the original system partition not a virtual IMG. When I get some time for it, I'll post a mod for TWRP/CWM/Phylz/etc recoveries to deal with virtual IMGs, or a script for ROM devs if they wish to offer virtual ROMs. No ETA though.

As a concept YES, but I don't have enough time to finish MultiSystem v2.0 right now. As soon as I finish writing my dissertation, I'll work hard to release initial version.

Follow the video tutorials here!
[Android Software/Hacking General [Developers Only]] nukeboyt:
I've installed Multisystem and loaded an .img (Jasmine 5.1) onto the phone. I'm ready to begin using the virtual system. Before I "pull the plug" I have a question. Does it take a long time to reboot into a different system image EACH TIME you switch, or just the first time? For example, I am looking for unrooted stock .img to make a setup for work. Are the re-boots to a different image going to take minutes, or tens-of-minutes?
[Android Software/Hacking General [Developers Only]] panchalgl:
Can this is used for RedMi Note 4G (DIOR) single SIM?

Thanks in advance
[Android Software/Hacking General [Developers Only]] mrdeadlock:
I'm looking to try this on the Verizon Samsung Galaxy S4. What kind of experience have people had with this on the S4? Can I run Kitkat and lollipop roms across 2 dif setups?
[Android Software/Hacking General [Developers Only]] 140hours:
Problems booting 5.1

I used Root Explorer Pro to write 5.1 to the proper Multisystem Directory, updated through your control panel, but when I go to mount

(activate) the first virtual rom in the panel there is nothing in the list!

In Terminal Emulator status it says the current system img is 5.0.1?

I used FlashFire to install 5.02.

What am I doing wrong?

Thanks!

Gary Brant

---------- Post added at 08:47 PM ---------- Previous post was at 08:08 PM ----------

Everything seems to be 100% - I get in trouble every time I doubt HSBADR's brilliance!

Than you again!
[Android Software/Hacking General [Developers Only]] hsbadr:
In MultiSystem v1.x, data partition is shared & Android will re-optimize apps upon switching different ROMs; so, you need to wipe system data before switching. This will get resolved in MultiSystem v2.x with an option to isolate data & cache for each ROM.

Test it & report back!

Not in v1; you need to wait for v2.

Check this post for hints & please move JasmineROM-related questions to this thread!
[Android Software/Hacking General [Developers Only]] chevycam94:
Ive been reading inside MultiSystem 1.3.1 for a while now, and still find it difficult to understand. I just want to run, say Jasmine 8.0 as one, and SkyDragon 5.0 as the other. Its fairly unclear on how to "flash a new ROM" to a "virtual" system. Im not even clear on IF that can be done. It sounds like it just makes a copy of your current system, so you basically have two of the same thing. Once you have a copy, you then modify that copy (or whichever your booted into), and thats that.
[Android Software/Hacking General [Developers Only]] hsbadr:
Fo LG G3, wait for MultiSystem v2.x...
[Android Software/Hacking General [Developers Only]] hsbadr:
How to convert recovery-flashable .ZIP to MultiSystem .IMG

Until MultiSystem v2.0 comes out, the easiest way to convert recovery-flashable .ZIP to MultiSystem .IMG is to remove system mount line in the updater script & mount any available IMG (e.g., stock copy) before flashing, as follows:

su
mount -rw -o loop /MultiSystem/img/system/system.img /system

I assume that the IMG is stored in /MultiSystem/img/system/system.img. Test the above command before flashing, by checking /system contents & running the following command:

mount | grep /system

This should show a loop device instead of the actual system partition.

Then, you can replace system mount line with a script that mounts the IMG. To create an IMG from the system partition:

su
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/MultiSystem/img/system/system.img
[Android Software/Hacking General [Developers Only]] midimench:
I just extracted the img file from the zip file and copied that to the multisystem folder. Then open the multisystem app, did an update, hit the drop down list, selected the new img and booted to it. Works great.

Sent from my Galaxy Note 3 running Jasmine 5.1.1 and MultiSystem 1.31

---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------

Btw, is there an ETA on multisystem 2.0?

Sent from my Galaxy Note 3 running Jasmine 5.1.1 and MultiSystem 1.31
[Android Software/Hacking General [Developers Only]] Zade_xSniper:
Can't install?

It doesn't appear to install on my phone. Is it because of my phone (SM-G860P) or am I just not giving it enough time? Hard to tell since it says literally nothing.
[Android Software/Hacking General [Developers Only]] rogersb11:
Wouldn't mind adding note 2 lte version if possible. I can help if necessary etc, have device trees blah blah. I haven't Eben looked at your source, just saw the thread and was immediately interested

Sent from poisoned Note 2 CyanideL
[Android Software/Hacking General [Developers Only]] Azlun:
NOTE 4 China varriant, N9100 trltechn with this partition, can we get support for this?

adb shell su -c "ls -al /dev/block/platform/msm_sdcc.1/by-name"

lrwxrwxrwx root root 2014-06-22 11:19 aboot -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2014-06-22 11:19 apnhlos -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2014-06-22 11:19 boot -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 2014-06-22 11:19 cache -> /dev/block/mmcblk0p26

lrwxrwxrwx root root 2014-06-22 11:19 cp2_modem -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 2014-06-22 11:19 dbi -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2014-06-22 11:19 ddr -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2014-06-22 11:19 efs -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2014-06-22 11:19 fota -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 2014-06-22 11:19 mdm1m9kefs1 -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2014-06-22 11:19 mdm1m9kefs2 -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2014-06-22 11:19 mdm1m9kefs3 -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2014-06-22 11:19 mdm1m9kefsc -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2014-06-22 11:19 misc -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 2014-06-22 11:19 modem -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2014-06-22 11:19 pad -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2014-06-22 11:19 param -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2014-06-22 11:19 persdata -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 2014-06-22 11:19 persist -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 2014-06-22 11:19 recovery -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 2014-06-22 11:19 rpm -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2014-06-22 11:19 sbl1 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2014-06-22 11:19 sbl1bak -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2014-06-22 11:19 ssd -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 2014-06-22 11:19 system -> /dev/block/mmcblk0p25

lrwxrwxrwx root root 2014-06-22 11:19 tz -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2014-06-22 11:19 userdata -> /dev/block/mmcblk0p27
[Android Software/Hacking General [Developers Only]] maxpayne4:
Any update on sm-n900
[Android Software/Hacking General [Developers Only]] Raj d:
It'll work on micromax canvas a116..?
[Android Software/Hacking General [Developers Only]] QuazIqbal:
Is it safe to use it on android x86 devices like YOGA Tablet 2-830LC?
[Android Software/Hacking General [Developers Only]] shamescool:
Please add support for xperia zr i appreciate it indeed
[Android Software/Hacking General [Developers Only]] hallevison:
Hi:

I also am running 4.4.2 ROM with Safestrap. I would like to keep 4.4.2 as my stock ROM. Is there anyway to do that and still use Multisystem to run 5.x?
[Android Software/Hacking General [Developers Only]] midimench:
Nope, wrong kernel (you have kit kat 4.4.2) and MultiSystem was developed to run on lollipop 5.0+

Sent from my Galaxy Note 3 running Jasmine 5.1.1 and MultiSystem 1.31
[Android Software/Hacking General [Developers Only]] hallevison:
Bummer. I wanted to have a cake and eat it to. Thanks.
[Android Software/Hacking General [Developers Only]] SeraphSephiroth:
Hello

Will it be possible to get this running on an SM-N910U (Exynos) Note 4. Partition details appended.

C:\ADB>adb shell

shell@trhplte:/ $ su

su

root@trhplte:/ # ls -l /dev/block/platform/*/by-name

ls -l /dev/block/platform/*/by-name

lrwxrwxrwx root root 2015-08-18 22:14 BOOT -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2015-08-18 22:14 BOTA0 -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2015-08-18 22:14 BOTA1 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2015-08-18 22:14 CACHE -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 2015-08-18 22:14 CARRIER -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2015-08-18 22:14 CDMA-RADIO -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2015-08-18 22:14 DNT -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2015-08-18 22:14 EFS -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2015-08-18 22:14 HIDDEN -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 2015-08-18 22:14 OTA -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2015-08-18 22:14 PARAM -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2015-08-18 22:14 PERSDATA -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2015-08-18 22:14 RADIO -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2015-08-18 22:14 RECOVERY -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2015-08-18 22:14 RESERVED2 -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 2015-08-18 22:14 SYSTEM -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 2015-08-18 22:14 TOMBSTONES ->/dev/block/mmcblk0p14

lrwxrwxrwx root root 2015-08-18 22:14 USERDATA -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 2015-08-18 22:14 m9kefs1 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2015-08-18 22:14 m9kefs2 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2015-08-18 22:14 m9kefs3 -> /dev/block/mmcblk0p6

root@trhplte:/
[Android Software/Hacking General [Developers Only]] workdowg:
Deleted

From my LG-G4, Rooted running Stock 5.1
[Android Software/Hacking General [Developers Only]] Dhs92:
I'm curious as well, I have an H810g
[Android Software/Hacking General [Developers Only]] sub77:
could you provide the source or make a non led version, because of missing ledson the galaxy tab4?
[Android Software/Hacking General [Developers Only]] Tinkerer76:
Did you attempt to use on the note 2?
[Android Software/Hacking General [Developers Only]] xformulax:
hmm, i cant seem to move a system.img to /MultiSystem/img/system without my phone locking up.
[Android Software/Hacking General [Developers Only]] midimench:
Use root browser. What file app are you using? Also be sure you're not over writing an existing file.

Sent from my Galaxy Note 3 running Jasmine 5.1.1 and MultiSystem 1.31
[Android Software/Hacking General [Developers Only]] xformulax:
Root explorer pro and es file browser in root explorer mode, both lock up the device (or severely bog it down), unless i need to wait longer than 6 or 8 minutes for it to complete and it just appears locked up? the first 50% of the copy only takes seconds.

edit: trying root browser now... its taking a while, but at least the "copying" animation is actually moving.
[Android Software/Hacking General [Developers Only]] midimench:
Copying a typical 2.5 gig img file can take 10-15 min. Start the process and take a break, then come back.

Sent from my Galaxy Note 3 running Jasmine 5.1.1 and MultiSystem 1.31
[Android Software/Hacking General [Developers Only]] xformulax:
thanks, see the late edit above, but i think it was a combination of poor transfer reporting and not being patient, root browser seems to be working on it now without issue.
[Android Software/Hacking General [Developers Only]] midimench:
Root browser is what worked for me. Be sure to go into MultiSystem and do an update to show your latest img file.

Sent from my Galaxy Note 3 running Jasmine 5.1.1 and MultiSystem 1.31
[Android Software/Hacking General [Developers Only]] radavi98:
New Install

Samsung Note 3. Finally got MultiSystem installed, working and copied the image to multisystem/img/system. Booted to the virtual image and now want to load 6.1. Instructions say to extract the system.img file to multisystem/img/system but am getting permission denied. Chmod to 755 and still can not copy the file there. Is there another vehicle to get the .img file there? Should I have changed the permissions at all? I am trying to copy/paste or move to the multisystem/img/system location using ES Explorer. Any suggestions?
[Android Software/Hacking General [Developers Only]] bd177:
If you booted to the virtual system then you are using the system.img that is in the MM/system/img directory, hence you can't copy an img file there because the file is in use. What you could do is flash the 6.1 zip in FlashFire which will upgrade your virtual img to 6.1. That's what I did.
[Android Software/Hacking General [Developers Only]] midimench:
I've always had luck using Root browser. Remember copying a 2.5 gig file can take 15 minutes.

Sent from my Note 3 running Jasmine 6.1 stock
[Android Software/Hacking General [Developers Only]] kutlay1653:
can i use it on mtk6572
[Android Software/Hacking General [Developers Only]] radavi98:
Im close, found a newer .24 version of flashfire and that installed and worked. But that was on stock. So now to do the same thing and get new flashfire to work on the virtual img. Which I made a copy so I would have both then correct? I am assuming that it would keep the same name. Would like to get that permission fixed to save images off but moving forward is better than not ;) Will continue with flashfire. Thanks !!