yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Run the following commands:

busybox mount -o remount,rw /system
busybox ln -sv /proc/self/mounts /system/etc/mtab

If thi doesn't help, try mounting from Terminal Emulator or ADB shell after selecting the IMG in MultiSystem app, by running the following command:

MultiSystem mount virtual
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Grompy:
Neither worked. First command resulted in this:

------------------------------------------

busybox ln -sv /proc/self/mounts /system/etc/mtab <

'/system/etc/mtab' -> '/proc/self/mounts'

ln: /system/etc/mtab: Read-only file system

Sent from Hsbadr's MultiSystem Ready LP Rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
I edited my comment; you should 1st mount /system read/write:

mount -o remount,rw /system
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Grompy:
Alright after running those commands I now have this:

[03-05-2015 17:42:28] MultiSystem <1315>

[03-05-2015 17:42:28] Exit 0

[03-05-2015 17:42:28] MultiSystem <1318>

[03-05-2015 17:42:28] Exit 0

[03-05-2015 17:42:28] MultiSystem <0398>

losetup: /MultiSystem/img/system/StockSystem_03-05-2015_120753.img

[03-05-2015 17:42:28] Exit 0

[03-05-2015 17:42:29] MultiSystem <0417>

[03-05-2015 17:42:29] Exit 0

[03-05-2015 17:42:29] MultiSystem <0422>

mount: mounting /dev/block/loop1 on /MultiSystem/mnt/system failed: Device or resource busy

[03-05-2015 17:42:29] Exit 0

[03-05-2015 17:42:29] MultiSystem <1369>

[03-05-2015 17:42:29] Exit 0

[03-05-2015 17:42:29] MultiSystem <1372>

[03-05-2015 17:42:29] Exit 0

[03-05-2015 17:42:29] MultiSystem <1375>

[03-05-2015 17:42:29] Exit 0

Sent from Hsbadr's MultiSystem Ready LP Rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Reboot & try again! b/c you've the loop device busy from previous trials.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Grompy:
So I rebooted and chose my virtual image and mounted it, but still don't see anything under /MultiSystem/mnt/system. I don't see any errors, but this is what logged.

[03-05-2015 17:48:41] MultiSystem <1315>

[03-05-2015 17:48:41] Exit 0

[03-05-2015 17:48:41] MultiSystem <1318>

[03-05-2015 17:48:41] Exit 0

[03-05-2015 17:48:41] MultiSystem <0398>

[03-05-2015 17:48:41] Exit 0

[03-05-2015 17:48:41] MultiSystem <0417>

[03-05-2015 17:48:41] Exit 0

[03-05-2015 17:48:41] MultiSystem <0422>

[03-05-2015 17:48:42] Exit 0

[03-05-2015 17:48:42] MultiSystem <1369>

[03-05-2015 17:48:42] Exit 0

[03-05-2015 17:48:42] MultiSystem <1372>

[03-05-2015 17:48:42] Exit 0

[03-05-2015 17:48:42] MultiSystem <1375>

[03-05-2015 17:48:42] Exit 0

Ideas? Also thx for spending the time to help me fix this.

Sent from Hsbadr's MultiSystem Ready LP Rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Mount it in Terminal

MultiSystem mount virtual
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Tada10:
Still can't make a copy of stock. See logs plz.

#

# MultiSystem for Android

#

# (C) 2014-2015 hsbadr @ xda-developers

#

# If you'd like to support my work,

# please donate via PayPal or Google to:

# Hamada S. Badr <hamada.s.badr@gmail.com>

#

[24-02-2014 23:31:45] MultiSystem <1315>

mount: can't read '/etc/mtab': No such file or directory

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] MultiSystem <1318>

mount: can't read '/etc/mtab': No such file or directory

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] START MultiSystem boot

[24-02-2014 23:31:45] MultiSystem <1197>

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] MultiSystem <0210>

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] MultiSystem <0214>

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] MultiSystem <0224>

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] MultiSystem <0230>

ln: /system/etc/mtab: Read-only file system

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] MultiSystem <0242>

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] MultiSystem <0244>

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] MultiSystem <0245>

[24-02-2014 23:31:45] Exit 0

[24-02-2014 23:31:45] MultiSystem <0254>

[24-02-2014 23:31:46] Exit 0

[24-02-2014 23:31:46] MultiSystem <0255>

[24-02-2014 23:31:46] Exit 0

[24-02-2014 23:31:46] MultiSystem <0256>

mount: /etc/mtab: Read-only file system

[24-02-2014 23:31:46] Exit 0

[24-02-2014 23:31:46] Turn on LED R: 0 G: 255 B: 0

[24-02-2014 23:31:46] Find gpio keys event node

[24-02-2014 23:31:46] gpio keys: /dev/input/event15

[24-02-2014 23:31:50] Turn off LED

[24-02-2014 23:31:50] MultiSystem <1225>

[24-02-2014 23:31:51] Exit 0

[24-02-2014 23:31:51] MultiSystem <1226>

[24-02-2014 23:31:51] Exit 0

[24-02-2014 23:31:51] MultiSystem <1297>

[24-02-2014 23:31:51] Exit 0

[24-02-2014 23:31:51] Booting Stock System!

[24-02-2014 23:31:51] MultiSystem <1304>

[24-02-2014 23:31:51] Exit 0

[24-02-2014 23:31:51] END MultiSystem boot

[24-02-2014 23:31:51] MultiSystem <1369>

[24-02-2014 23:31:51] Exit 0

[24-02-2014 23:31:51] MultiSystem <1372>

mount: can't read '/etc/mtab': No such file or directory

[24-02-2014 23:31:51] Exit 0

[24-02-2014 23:31:51] MultiSystem <1375>

mount: can't read '/etc/mtab': No such file or directory

[24-02-2014 23:31:51] Exit 0
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Grompy:
Same result.

[03-05-2015 17:55:07] MultiSystem <1315>

[03-05-2015 17:55:07] Exit 0

[03-05-2015 17:55:08] MultiSystem <1318>

[03-05-2015 17:55:08] Exit 0

[03-05-2015 17:55:08] MultiSystem <0398>

losetup: /MultiSystem/img/system/StockSystem_03-05-2015_120753.img

[03-05-2015 17:55:08] Exit 0

[03-05-2015 17:55:08] MultiSystem <0417>

[03-05-2015 17:55:08] Exit 0

[03-05-2015 17:55:08] MultiSystem <0422>

[03-05-2015 17:55:08] Exit 0

[03-05-2015 17:55:08] MultiSystem <1369>

[03-05-2015 17:55:08] Exit 0

[03-05-2015 17:55:08] MultiSystem <1372>

[03-05-2015 17:55:08] Exit 0

[03-05-2015 17:55:08] MultiSystem <1375>

[03-05-2015 17:55:08] Exit 0

Sent from Hsbadr's MultiSystem Ready LP Rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Ok, Why do you need to mount it now? You can boot the virtual IMG & mod it on the fly or flash to it via FlashFire with a compatible updater-script. I'll look into this for the next update.

Also, what's the version of BusyBox you have installed?

busybox cat --help
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Grompy:
I'm just trying to modify my virtual rom.

How do I mod on the fly? Let's say I want to delete syscope.apk from a virtual rom that I copied from my stock system. How do I do that? Is my /system/app directory mounted from my virtual IMG or is it still my stock system image? Just confusing. If it is remounted from the virtual image it'd be helpful to see a printout of mount points printed out on a MultiSystem status command.

root@hltevzw:/ # busybox cat --help

BusyBox v1.24.0-hsbadr.MultiSystem (2015-04-26 23:38:32 EDT) multi-call binary.

Sent from Hsbadr's MultiSystem Ready LP Rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Activate the target IMG & reboot. Then, check status:

MultiSystem status

This will confirm that you're running this exact IMG. This means that your /system directory is a mount point for this IMG. Just freeze/uninstall all apps you don't need. It'll only affect the Current System IMG (as printed above).
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Sometimes, you may need to press the key twice or so for it to pick up. I'll look into the cause of these minor issues b/c everything is working for me. Maybe, I've to add a function to restore/set all MultiSystem environment.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Tada10:
Looks like it's working? :)
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Grompy:
Well.. just gave this a whirl..

I checked MultiSystem status it showd I had my test rom active..

I added a file called test under /system/app/

I then rebooted to my stock system checked status using MultiSystem status it show'd I was under stock..

Navigated to /system/app/ and my file I created was there.. it doesn't appear like virtual rom is working for me? Any ideas what I'm doing wrong? Thanks!

Sent from Hsbadr's MultiSystem Ready LP Rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Sounds good!

Impossible! I'll give you a better test... I think you currently have Android L boot animation for all ROMs; right? Now, install Samsung bootanimation from 5.0 announcement post to stock/virtual system. Now, you could see a visual difference on boot.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Grompy:
Well I think my issue is that it's not running my virtual rom. I think the MultiSystem status is returning a false positive. I think when I activate my virtual rom then me spamming the home button to boot up actually does boot up the stock system. Then multisystem status still returns that it is my virtual rom. I think my problem is that I can't get my virtual rom to boot. It just hangs on the custom logo screen.

Edit: That was it.. I just activated another copy of my stock system I had made prior to creating that file and now the file isn't there.. so looks like it's working fine.. sorry about all the posts.. might want to fix the false positive so someone doesn't accidently mess up their stock system.

Sent from Hsbadr's MultiSystem Ready LP Rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Ummm, your virtual ROM might be corrupted or not activated (or the Active System is Stock not Virtual... check the switch!)! Recreate one from stock & for the MultiSystem status, you should also check the device (Current System DEV): if it's /dev/block/loop0, you're running a virtual ROM.

Also, it's confusing to rename a virtual IMG "StockSystem_***.img", which means a virtual IMG from Stock System... while "Stock" means the stock partition.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
5.0.2 does it automatically! You should find /MultiSystem directory after a reboot when you're on 5.0.2. I assume you've done the SD partitioning as described here (2 PRIMARY partitions). Then check this!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Grompy:
Read the instructions. Posts 1-6 somewhere through there it tells you everything you need to check and what else you need to do to get multisystem functioning correctly.

Sent from Hsbadr's MultiSystem Ready LP Rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Here's how to check if the IMG is corrupted from the log file or MultiSystem status

Current System IMG: Test_Rom.img
Current System DEV: [B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]

When you see "/dev/block/mmcblk0p23"; it's the original system partition; so MultiSystem failed to boot Test_Rom.img, but it should be your current system.

So, the check is simple based on "Current System Device":

/dev/block/mmcblk0p23 = Stock System Partition

/dev/block/loop0 = Virtual System IMG
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] G.moe:
On the VZW S4, the SD card is found at msm_sdcc.2, not msm_sdcc.3, so you might need to add a note about that in the card preparation section.

Have you (or has anyone else) tried using this with KitKat as stock? I see documentation about running kitkat when lollipop is stock, but what about running kitkat when kitkat is stock, or running lollipop when kitkat is stock? I haven't tried installing MultiSystem yet from KitKat, however I will if I don't hear from you shortly.

Edit: Also, if you want to message over Telegram or elsewhere for ease of communication, send me a PM.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
I use the physical SD partition (/dev/block/mmcblk1p2) not the link & it can easily changed in MultiSystem build.prop. So, no worries!

As for KK, it was originally running on KK (not released b/c Safestrap was working already), but I made many changes to fix it on LP.

Long story short, fixing it on KK is much eaier if it won't work by default.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Tada10:
Not sure what I am doing wrong. I can't get it to use /dev/block/loop0
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Tada10:
Forgot the logs plz look.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
Your Active IMG is corrupted! Create a new one or use the system.img from 5.0 ZIP.

Also Update Configurations & check BusyBox version!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Zrutisan:
Well, this is weird : I installed an app on my virtual ROM and I find it in my stock ROM... Is it normal?? I checked using busybox mountpoint command and I'm definitely not on the same partition...

EDIT : Actually it's identical, whatever I'm doing on my virtual rom is ported back to the stock partition. I'm very confused.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hoffeva:
Doing things like installing apps only affects the internal storage on the phone, so it affects all ROMs, virtual or not. Only the system files themselves are stored on the sdcard in the multisystem partition.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Gabbyii:
Multisystem Safe ROMs

So is there a way to tell if another ROM 's updater-script is safe/compatible? (and if its not safe and we flash/convert it - will it brick our phones?) or do we need to wait for ROMs to be released that are Multisystem compatible?

Thanks

Quote:

Is there a way to convert a normal ROM .ZIP into MultiSystem .IMG?

Create or copy any of your IMGs, activate it & reboot to the active IMG! Then, use FlashFire to flash the ZIP file. However, the updater-script should be safe/compatible. Some devs mount the phyical partition, which will redirect everything to it!!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Zrutisan:
Oh ok, thanks for replying!

So let's say I delete SystemUI or an important system app, I'm screwed? Since SystemUI will be gone in all of my virtual roms.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hoffeva:
No. Systemui is a system app, so it is installed in the system files. Apps that you yourself install are just regular apps so they aren't in the system directory. System apps are part of the system files.

Sent from my SM-N900V running JasmineROM 5.0.2 Virtual with MultiSystem
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Grompy:
Any user app is by default stored in the /data partition which is shared among your stock system and virtual systems. If you want to only install on a virtual rom you'll have to convert from a user app to a system app via titanium backup or some other app. Or manually push the app to /system/app.

Sent from Hsbadr's MultiSystem Ready LP Rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Tada10:
How do I fix the mtab error?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] murphyjasonc:
Yes this is normal. All Roms and the stock system will share apps and data.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bishop0114:
I have tried creating an img from stock. I let it run for over an hour with the red light on... I have tried multiple times to copy system.img from 5.0 but it shows copying to the MultiSystem folder taking 36+ days to complete. I tried ES Explorer and Root Explorer. If I copy the same file from a folder on my SD card (fat32) to another folder, it copies in about 1 minute. I have followed the instructions so for formatting the card, all folders and files appear to be correct for MultiSystem directory. I have repartitioned the card a few times with the same result. Any ideas?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Tada10:
Finally got it!

Running my virtual copy rom!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Tada10:
If anyone finds a way for viper4android to work please share!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] samccfl99:
The system sounds wonderful and intense. You surely know your stuff to do this. I have read about this in muniz_ri posts a while back. It seems that this may be the only way to get control over Permissive Mode for us due to stupid Samsung/ATT. Viper4Android needs that and it is sad we lost it going to LP. Also we are all waiting for Xposed. We will be last to be sure with Touchwiz. Just wondering when do you think you might turn it over to him for testing? If you don't know, i understand. Gotta make sure it works close to perfect. Lotta high level good work coming out of devs such as FlashFire. Don't know what we would do without you guys. ROTTEN APPLES? PERISH THE THOUGHT...LOL

Thanks for all the hard work. I am an old time programmer. Must be a fun and not fun project, but very satisfying.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
It's under testing for VZW/ATT S4, S5, Note 3 & (Note 4 DE); more devices will get supported. It'll take more time to support the devices I don't own (check my signature!) though.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] R-1 Rider:
Tada10,

how did you fix your mtab error? I get the mtab error and can not log in to the virtual system. I try to mount the virtual image, but every time I hit update configuration it doesn't seem like it does much except removes the Primary System IMG from displaying. I have run the commands in terminal and they show me running the stock image still.

Any help would be appreciated
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Tada10:
See screenshot. That's what fixed it.

The IMG mounting issue
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] R-1 Rider:
Thanks for the quick reply. I thought I did that, but I guess not. Unfortunately now it won't get past the boot screen. Booted back into stock system and I will keep digging to see what's up.

Thanks again.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Seion:
adb shell partitioning

Is there a way to partition the External SD Card via adb shell for multisystem? I don't think I have a card reader currently.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] BobC43:
Booting from Virtual Hangs

I have MultiSystem installed and seem to pass all the tests. When I attempted to make an Image from the Stock it appeared to work. But when I went to boot into the virtual Rom it hung. Had to pull SD card to boot up and turn off MultiSystem. I may have a corrupt img.

How do I delete the coppied image, as I thought it was in /MultiSystem/ under root.

What are the steps to copy the stock rom, and boot into a virtual rom.

Thank you
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] R-1 Rider:
The image is located in:

/MultiSystem/img/system

I had a problem with Multisystem making an image from the stock Rom. The image was corrupted, so I pulled the system image from Jasmine 5.0 and placed it in the Multisystem/img/system folder and now I am running on the virtual side. Time to start tweaking and see what I can mess up....
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] burbank:
This is good to know. I have been unable to get MS to build a virtual image from stock. So maybe I'll try that.

---------- Post added at 03:09 PM ---------- Previous post was at 02:39 PM ----------

I can't get through these steps successfully and I have no idea why. Is the MS app supposed to offer any feedback when the user presses a button? (All I get is are messages that the process has been granted su permissions.)

When I go through the troubleshooting steps above I have more success if I do a sudo first but I still can't get MS to launch from terminal.

Will a future version of MS do all of the partitioning and setup automatically or will that always be a manual process?

Thanks!

---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------

There's a button in the multisystem app that is supposed to build an image from the stock ROM. But I don't think it's working for me. If it is I'm not getting any feedback at all and when I look in the image directory within multisystem using the terminal there's nothing there.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] hsbadr:
You may try AParted from Play Store, but I think it doesn't work on LP.

You should turn off screen timeout (set to max. 10 minutes) & wait for the RED LED to disappear (should take a few minutes). Also, check the size of the created IMG before reboot. It's located at

/MultiSystem/img/system

I focused on the main functionality of MultiSystem binary (/MultiSystem/bin/MultiSystem) & this is my 1st Android app ever & the initial release of MultiSystem. So, SURE, it'll get improved in the future. I just wanted to release something working very quickly for you to survive root while mod'ing LP ROMs.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] gnexdude:
This is where I'm stuck:

"REBOOT to check GREEN LED for boot options & check permissive SELinux..."

I'm following all steps and checking everything, I got the files installed in the MultiSystem folder, I'm just not getting boot options to check permissive SELinux...help anyone? :silly:
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] captbeard:
Does multisystem mean anything to those on a retail phone that STARTED on 4.4.4 or 5.0? Or only those who got one when 4.4.2 rooting was still possible?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] nagi_007pk:
Awesome work!

Hi hsbadr!

While I know the FAQ on the first page highlights a great deal on how this project is supposed to work and it does completely answer most of questions however, I needed to know if kernel modification is possible for secured bootloaders?

I currently own an AT&T Note 3 and have been running Firekat since about two months on KK... Would this also pave the way for AOSP? If at all.

Delighted to have a dev still confidently looking out for the community

Thanks mate
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Dodger70:
Having trouble creating a symlink when I run this command: mount -o remount,rw /system i get Permission Denied what am I doing wrong?:confused:
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] G.moe:
Type "su" and press enter first to ensure you are acting as root.

Root is required to use MultiSystem; please read the first posts carefully.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Dodger70:
OK its working now but after I type this command:

ln -sv /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem

I get:

/system/xbin/MultiSystem: File Exists

then I run

MultiSystem (to test the symlink)

and I get:

not found

I cant seem to figure this out.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] G.moe:
Try removing the v:

ln -s /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] captbeard:
I did, but was still unsure because reading some of it was difficult to do, so I wanted clarification. I appreciate your answer, though.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Dodger70:
Same result.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] G.moe:
Try:

ln -s /MultiSystem/bin/MultiSystem /system/bin/MultiSystem

A crucial part of MultiSystem's initial development will be setting it up to automatically configure devices appropriately, and I've told [MENTION=5868929]hsbadr[/MENTION] about similar issues with the VZW GS4, so I imagine he's already looking into this.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] gnexdude:
I thought MultySystem is a read-only file...that's what I'm getting, thanks for the advice guys :good:
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Dodger70:
Awesome that worked!!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bd177:
From what I can see you only get the green led lit during boot at which time you can hit the buttons. There is no actual menu. Then from inside the app , I noticed that when you hit the "Create Image from Stock" there is no notification that anything is happening except a toast message from supersu. No red led or anything. I figured out that you just have to wait long enough for the img to be created. Then hit "update configurations" and you should see it in the dropdown menu for "primary" or "secondary". You should also use a Root explorer app to navigate to the img folder and verify the size of the img. I think 2.65 GB is normal for the stock img. Any other size means that the img is corrupted.