yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] hsbadr:
Simple One-Click Installation

I've fixed the installation script by setting the required symlinks (this makes it a very simple one-click installation for future versions), but I'll keep it a bit complicated for everyone to go through the Q&A thread (posts #1-6) to learn more before being able to use it.

On a side Note, I'd recommend to backup your data via TitaniumBackup & only wipe system data before rebooting to a completely different ROM.

Good luck!
[Verizon Samsung Galaxy S 4] hsbadr:
MultiSystem v1.3.1 [May 9, 2015]

★ ChangeLog:
[Galaxy S 5 Q&A, Help & Troubleshooting] Pacanins:
Hey!!

Im having issues with mi G900M related to OTG. I bought a Micro Duo Usb with OTG support and used it without problems, but it suddenly (Cant remember when) stopped being recognized by the phone. The usb works perfectly with my Samsung Tab S an PC, but cant be recognized anymore by my S5. The phone detects a USB being connected, but cant access anymore to files. Im running stock FW... and everything else too.

I would really appreciate your help guys.
[Galaxy S 5 Q&A, Help & Troubleshooting] Pacanins:
Bump!
[Galaxy S 5 Q&A, Help & Troubleshooting] Akalsemann:
If you connect via MTP you must unlock the screen before you can access your phone. (if you have a screen lock)
[Galaxy S6 Original Android Development] mskip:
The latest versions of TWRP have problems with sideloading files and with openrecoveryscript which the ALLINONE procedure uses (which is why most of the devices are still using TWRP 2.7). If your module uses a 2.8 version and you have problems with the above just select the push option which will always work.

Also Chainfire updated SuperSU beta (2.49) with a fix for the deepsleep problem so select that version until the release version has been updated.

Mark.
[Galaxy S6 Original Android Development] mskip:
**FAQ**
[Galaxy S6 Original Android Development] mskip:
**VIDEOS**
[Galaxy S6 Original Android Development] CreepyE:
Does this trip knox?
[Galaxy S6 Original Android Development] wafro:
Yep I think so. According to the following information from OP.
[Galaxy S6 Original Android Development] SirrJonathan:
Unlocking the bootloader or rooting this device WILL trip the KNOX security system
[Galaxy S6 Original Android Development] -Mr. X-:
The version of odin it grabs doesnt work for me i had to manually use 3.10.X
[Galaxy S6 Original Android Development] mskip:
I have updated the S6 module files (v1.0.2) to set odin 3.10.6 as the default odin program. If you clean the s6 module files using ToolKitClean.exe then restart and select your device new module files and odin 3.10.6 will be downloaded.

May help with Nand Write Start getting stuck.

Mark.
[Galaxy S6 Original Android Development] -Mr. X-:
It should resolve the nand write start issue. since thats what i had and 3.10.6 fixed it for me :) thanks for the work!
[Galaxy S6 Original Android Development] vegetaleb:
So no deepsleep issue with this tool? Or we have still to do the trick to fix it?
[Galaxy S6 Original Android Development] mskip:
I thought SuperSU beta 2.49 included a fix for deepsleep issue but if not just download http://skipsoft.net/download/toolkit/sgs6toolkit/UPDATE-S6DeepSleepFix.zip and flash via TWRP custom recovery. I will add this fix to the Toolkit today and push an updated module file which can be downloaded by cleaning the existing module files with ToolKitClean.exe and selecting the device again (or you can just update automatically if you are a pro user).

Mark.
[Galaxy S6 Original Android Development] paul8811:
I get a error that a required file wasn't available to download just after it downloads TWRP, mine is a Aussie vodafone 920i running Singapore firmware

Product Manufacturer: samsung

Product Model: SM-G920I

Model ID: UNKNOWN

Device Type: zeroflte

Build Description: zerofltedv-user 5.0.2 LRX22G G920IDVU1AOD1 release-keys

Build Date: Tue Mar 31 21:22:16 KST 2015

Hardware: samsungexynos7420

Board Platform: exynos5

Build Version Release: 5.0.2

Build ID: LRX22G

Bootloader: G920IDVU1AOD1

Build PDA: G920IDVU1AOD1
[Galaxy S6 Original Android Development] mskip:
I think I found the error please try again.

Mark.
[Galaxy S6 Original Android Development] paul8811:
Thanks worked great.
[Galaxy S6 Original Android Development] datboy143:
Worked for me thanks.
[Galaxy S6 Original Android Development] the_real_fosgate:
Hello,

I get the Pro Version of your tool.

I come from a HTC device, so everything is a bit new for me.

Is it possible to flash a custom Rom with your Tool?

Thank you

Robert
[Galaxy S6 Original Android Development] liderbravin:
will this root the metro pcs version os the galaxy s6? thanks in advance ...
[Galaxy S6 Original Android Development] openmatrix:
Does this support boe3?
[Galaxy S6 Original Android Development] lgsshedden:
first time user and sent a small donation for the pro version before using -- pleased to support your work and thanks for enabling ADB for those of us who know enough to use its capabilities but not enough to program them ourselves!

looking forward to 5.1.1 updates
[P3600 ROM Development] mark885:
Hi!

I've installed mUn's Rom, but from yesterday I've a problem. I have signal, but I can't make/receive calls and message because signal is false.

I've tried to go back to original rom, but it's impossible because after update process process during the automatic installation of original HTC plug-in, my trinity reset himself when installation is yet incomplete and after soft reset the comm manager has some carachters of mUn plug-in, and my signal is one more time false!

Now I have a little bit of original rom and a little bit of mUn's rom...How can I return completely to original rom?

Sorry for my english, but I'm italian

.

Thanx.
[P3600 ROM Development] raphael02:
you must download ROM from hTC site: http://www.europe.htc.com/support/index.html?device=htcp3600unload,or from pocketdevice site: http://www.pocketdevice.it/

then it dawns like as you have made when you have installed WM6
[P3600 ROM Development] mark885:
I do it! But remains some carachters of mUn release! (for ex. commmanager)...
[P3600 ROM Development] mndgz:
flashing Hard-SPL first should help
[Xperia Z1 Compact Q&A, Help & Troubleshooting] AMDFenics:
Hey, i got a Problem with the recent apps screen. On top is a box with "widget could not be loaded " See attachment. How can i remove that?
[Xperia Z1 Compact Q&A, Help & Troubleshooting] AMDFenics:
Has nobody a idea?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hsbadr:
MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices with many features that at least includes the following:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hsbadr:
Video Tutorials

A quick preview of MultiSystem v1.0 tested on Lollipop for VZW Note 3. The video has been captured on a stable virtual ROM of JasmineROM v5.0.1. It's FULLY compatible with FlashFire on virtual/stock systems. More devices will get supported as well, after required testing.

[YOUTUBE]CsMZl2PfQFQ[/YOUTUBE]

[YOUTUBE]A7fYBPiArlw[/YOUTUBE]​

Facebook: https://www.facebook.com/hsbadr/videos/vb.331488823689599/428178174020663
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hsbadr:
How to check if you are running a Stock/Virtual System?

There're many ways to check whether you're running a Stock or Virtual system. MultiSystem app should include this simple check at some point. That's important to avoint ruining the Stock system & keep it safe. To make it clear to NOOBZ & anyone who's requesting "another" proof even though I owe hime nothing. Very weird!

Anyway, BusyBox mountpoint applet can print the current block/device mounted to /system mountpoint by running the following command:

busybox mountpoint -n /system

The stock system is mounts the original system partition:

[B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]

while the virtual system mounts a loop device associated with a system IMG:

[B][COLOR="Blue"]/dev/block/loop0[/COLOR][/B]

Here're two videos for both stock & virtual systems...

[YOUTUBE]lks1D4eAZ1g[/YOUTUBE]

[YOUTUBE]o2ryf2Xr1rU[/YOUTUBE]

UPDATE:

Now, you could run the following command to print the current system (stock or virtual) and the system device (physical partition or loop device):

MultiSystem status

Note: The block device number (mmcblk0p23) may vary per device & per variant !
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hsbadr:
How to repartition microSD card for MultiSystem?

You can use any tool/program for partitioning on Android, Linux, Mac, or Windows. For example, MiniTool Partition Wizard is a good partitioning tool for Windows. So, let's use it for this task. Simply, you need to follow this PDF tutorial (thanks to [MENTION=3271517]carl1961[/MENTION]). In sum:

Step 1: delete old partitions on SD card

Step 2: create FAT32 PRIMARY partition

Step 3: create EXT4 PRIMARY partition

Then, apply changes (note that the program UI may get changed in newer versions).
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hsbadr:
How to check microSD card partitions for MultiSystem?

You need to correctly repartition microSD card into two partitions:

exFAT or FAT32 for the 1st partition (your new external storage)

EXT4 for the 2nd partition (your MultiSystem partition)

Use the directions in this post!

You should check your 2nd SD partition in EXT4 format mounted to /MultiSystem:

check that the /MultiSystem directory exists after a reboot

check that the 2nd SD partition (/dev/block/mmcblk1p2) is mounted to /MultiSystem by running the following command in Terminal Emulator or ADB shell:

mount | grep /MultiSystem

The output should be:

/dev/block/mmcblk1p2 /MultiSystem ext4 rw,seclabel,relatime,data=ordered 0 0
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hsbadr:
How to check MultiSystem Installation?

The 1st thing to do after installing MultiSystem is to check the /MultiSystem directory & its contents (it shouldn't be empty!). Then, check usage by running the following commands in Terminal Emulator or ADB shell:

su
bash
MultiSystem

If it retuns "MultiSystem not found" or permission denied, try to use open MultiSystem app to Update Configurations & try again. If this does't fix it, try the following command:

/MultiSystem/bin/MultiSystem

This should work if you've MultiSystem binaries installed in (extracted to) /MultiSystem directory. If so, you can create a symlink in /system/xbin as follows:

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

Then, test it by running:

MultiSystem

The last thing before using it is to check the boot options: reboot & monitor the GREEN LED indicator for 3 seconds (change in the app) , which give you the following options:

Volume UP = Primary virtual ROM

Volume DOWN = Secondary virtual ROM

HOME KEY = Stock System

Sure, you should have installed one or more virtual ROMs.

Backup & restore or creating/installing a virtual ROM are easy as copy & paste: all img's will be at

/MultiSystem/img/system

To backup a virtual/stock system, you have many options:

Use create function to create from stock system

Use copy function to copy the IMG

Copy & paste with a new name

Use FlashFire (fully supported on virtual/stock ROMs)

...

If you've IMG mounting issues, run the following commands:

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

If this 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
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hsbadr:
MultiSystem Video Tutorial

[YOUTUBE]CsMZl2PfQFQ[/YOUTUBE]​

Thanks To: [MENTION=4246643]Tomsgt[/MENTION] , aka RootJunky ;)

Don't forget to subscribe & like the video to show appreciation of his great effort & time spent in making the video :highfive::good:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] emptyPD:
hi, thanks for the work! i have a problem, i have MultiSystem installed, when i put MultiSystem status in the terminal it appears same as the tutorial video, now when i use the "Create Virtual IMG" button, the led goes green, but after 5 minutes turns off. then i cannot select the system img in the "Primary System IMG" section, and when i go to the MultiSystem directory and search for the img on "img/system/" there is a img file but without size, the size says something like "-1400897536".

thanks for your help!

Im using a Samsung Galaxy Sgh-i337 with locked bootloader, runing multisystem on stock Lollipop 5.0.1 rooted. i have busybox.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] emptyPD:
i solved the problem using "MultiSystem update" in the terminal emulator. after that i was able to view the IMGs
[Galaxy S6 Edge Original Android Development] mskip:
The latest versions of TWRP have problems with sideloading files and with openrecoveryscript which the ALLINONE procedure uses (which is why most of the devices are still using TWRP 2.7). If your module uses a 2.8 version and you have problems with the above just select the push option which will always work.

Also Chainfire updated SuperSU beta (2.49) with a fix for the deepsleep problem so select that version until the release version has been updated.

Mark.
[Galaxy S6 Edge Original Android Development] mskip:
**FAQ**
[Galaxy S6 Edge Original Android Development] mskip:
**VIDEOS**
[Galaxy S6 Edge Original Android Development] Nefasto:
Thanks man
[Galaxy S6 Edge Original Android Development] jarwintee:
any plans for G925L support?
[Galaxy S6 Edge Original Android Development] carrsteven:
Where are you getting your twrp recoveries from?
[Galaxy S6 Edge Original Android Development] LinS123:
You sir are awesome. I will gladly donate for the pro version.
[Galaxy S6 Edge Original Android Development] ilyasuzun55:
thanks man :)
[Galaxy S6 Edge Original Android Development] iigrs:
Downloaded the toolkit, donated, converted to Pro.

Anything I'm doing I got 2.8.6.0 was unexpected at this time.

Pls Help. What's wrong ?
[Galaxy S6 Edge Original Android Development] ra_eng:
I have the same problem after donating to pro version.
[Galaxy S6 Edge Original Android Development] SantinoInc:
Has anyone used this to put TWRP on Sprint Edge?
[Galaxy S6 Edge Original Android Development] Fauert:
Thanks a lot !! ☺ ?
[Galaxy S6 Edge Original Android Development] bcoolnow2005:
Any one use it and can confirme it's OK , what about deep sleep ?
[Galaxy S6 Edge Original Android Development] iigrs:
Is there a way to provide us some help regarding the problem we face with the Pro donated version ?\
[Galaxy S6 Edge Original Android Development] TookRDerbs:
+1 :confused:
[Galaxy S6 Edge Original Android Development] mskip:
http://galaxys6root.highonandroid.com/cwmtwrp-recovery/

Mark.
[Galaxy S6 Edge Original Android Development] mskip:
The lte recovery (downloaded when selecting any variant) should work fine with the LTE-A. Try it and see if it works, you can always flash the stock recovery back if it doesn't as images are avaialble to download on samsung-updates.com http://samsung-updates.com/device/?id=SM-g925l

If it works I can add support to the toolkit.

Mark.
[Galaxy S6 Edge Original Android Development] mskip:
Im now getting my son to sleep I will look at this as soon as I get back to my pc (less than an hour) and update the module files with the fix.

Mark.
[Galaxy S6 Edge Original Android Development] eniux:
Thanks!

Verstuurd vanaf mijn SM-G925F met Tapatalk
[Galaxy S6 Edge Original Android Development] mskip:
Ok I found the problem and pro users should find the Toolkit downloading the recovery properly now.

I fixed a problem with recovery not downloading if the sprint variant is selected and uploaded the new module files. Run the ToolkitClean.exe program and select option 27 to clean the S6 Edge files. Select y or yes to restart the Toolkit and select the S6 Edge (27) to download new module files. Everything should work fine now.

Now making an autoupdate for the pro users but doing the above will give exactly the same results.

Mark.
[Galaxy S6 Edge Original Android Development] ra_eng:
Thanks. it worked again after the update.
[Galaxy S6 Edge Original Android Development] iigrs:
Works for me too, thanks a lot
[Galaxy S6 Edge Original Android Development] lusciousbeard:
NAND Write Start!

sprint s6 edge....odin just stuck at NAND Write Start!

---------- Post added at 08:29 PM ---------- Previous post was at 08:01 PM ----------

I've tried it but get stuck at Nand write start! ! I was able to get twrp installed and I can backup via flashify but when boot to recovery I have no touch screen
[Galaxy S6 Edge Original Android Development] raakaysh:
Same here! Tried on my S6 Edge SM-G952I, stuck at NAND Write Start! Waited for an hour but no progress. Tried your recovery files with Odin 3.10.6 but it end with FAIL!
[Galaxy S6 Edge Original Android Development] mskip:
Is there an option in the settings, developer options screen to unlock the bootloader. I know samsung may start locking the bootloaders because of certain laws but enable it to be unlocked via the settings screen.

Also have you tried the recovery from *HERE*?

Mark.
[Galaxy S6 Edge Original Android Development] mskip:
I have updated the S6 Edge module files (v1.0.3) to set odin 3.10.6 as the default odin program. If you clean the s6 edge module files using ToolKitClean.exe then restart and select your device new module files and odin 3.10.6 will be downloaded.

May help with Nand Write Start getting stuck.

Mark.
[Galaxy S6 Edge Original Android Development] ktetreault14:
Sweet dkwnloaded
[Galaxy S6 Edge Original Android Development] lusciousbeard:
still didnt fix problem.....but I did follow this and now have a working twrp on sprint s6 edge

http://xdaforums.com/sprint-galaxy-s6-edge/general/recovery-twrp-2-8-6-0-touch-recovery-t3102034
[Galaxy S6 Edge Original Android Development] raakaysh:
Thanks for responding, Mark! Yes, I have checked that but the option is not there. As I said mine is SM-G925I, should I try the TWRP meant for the Sprint version? I found that TWRP yesterday and I going to try it. You did a good job by replacing Odin 3.09 with 3.10 in your tool. :)
[Galaxy S6 Edge Original Android Development] raakaysh:
Okay, I tried flashing the TWRP file you linked above but it gave the same result.

<ID:0/006> Added!!

<ID:0/006> Odin engine v(ID:3.1005)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> SingleDownload.

<ID:0/006> recovery.img

<ID:0/006> NAND Write Start!!

<ID:0/006> FAIL!

<ID:0/006>

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

On the Download Mode screen on device I see "Custom Binary (Recovery) Blocked by R/L. What does that imply? Any thoughts?

P.S.- Found out the R/L is Reactivation Lock. Just disabled it and flashed CF-Root successfully. Rooted now!

Used the files from here: http://www.droidviews.com/how-to-root-samsung-galaxy-edge-sm-g925i/
[Galaxy S6 Edge Original Android Development] mskip:
QUESTION (for all variants)

Do all the variants of the S6 Edge have the Reactivation lock enabled or disabled by default?

Go to Settings -> Lock screen and security -> Find My Mobile and check if reactivation lock is enabled/disabled.

This is a new security feature on 5.1 on certain Android devices to protect your device should it be stolen. If it is enabled then you will need to disable it before you can flash anything to your device. You will first be prompted to verify your Samsung account password or your fingerprint before you can open the sub-menu. You can then toggle the setting.

Please let me know if your variant has this enabled/disabled (with your model number) so I can add this information to the Toolkit if needed.

Mark.
[Galaxy S6 Edge Original Android Development] raakaysh:
On mine, it was not enabled by default. I remember activating it while playing with the settings after getting the phone.
[Galaxy S6 Edge Original Android Development] mskip:
So the reason you couldn't flash the recovery image via odin was because the reactivation lock had been enabled? And disabling it allowed you to successfully use odin?

Mark.
[Galaxy S6 Edge Original Android Development] raakaysh:
Yes, I had been facing the error since the beginning. Noticed that some R/L thing has been blocking the flash but did not figure out what R/L was. Had I known it meant Reactivation Lock, things might have been much easier!
[Galaxy S6 Edge Original Android Development] Alex-V:
thanks for this nice tool
[Galaxy S6 Edge Original Android Development] Tripledrop:
I wonder if you could help?

I have installed your software, and donated to pro. However when trying to backup or check device info, it says either waiting for adb, or usb debugging to be detected.

To confirm, I am already rooted, screen is on, and usb debugging on.

EDIT: Don't worry, all good now! I think the usb was loose...
[Galaxy S6 Edge Original Android Development] srkoza:
i have the canadian version from bell and i remember activating it when i was setting up the phone so ours isnt automatically on but you should probably suggest it in the OP :D most people forget about stuff like that, and i havent tried the toolkit yet, been worried ill have deep sleep issue and dont know which thread i have to flash roms off of, havent had time to read into it either lol. gonna wait till more roms come out anyway, for now i need a bug free phone, i have used your toolkit before on my note 2 and it was too easy so thank you sir will donate when i finally want to root
[Galaxy S6 Edge Original Android Development] Fauert:
Hi [MENTION=5450771]Mark [/MENTION], mine S6 Edge International , is NOT enabled by default ..
[Galaxy S6 Edge Original Android Development] Diamond777:
permanent black sceen continous with no TWRP

Hi all

Ive been fighting two days my following issue. Black Screen permanently.

It all of a sudden decided to black out on Friday and its been like this ever since. It comes up once in a while, but once I hit the power button, it wont turn back on.

Seems TWRP would be able to fix this as I have read, but I cannot get TWRP to work properly, not even a boot in recovery.

I have the 925F international, but CF root ddnt do anything for me, I used the 925T instead and was able to get root. But my intentions to flash a custom ROM (there aint that many..) and kill this deep sleep SOD or whatever this is since I assume this is a factory ROM scenaio I am dealing with

Can anyone who has solved this elaborate? All help is appretiated.

Thanks alll
[Galaxy S6 Edge Original Android Development] mskip:
I will add the deepsleep fix zip file to the Toolkit tomorrow and update all the module files (and push an update) to make things easier. I will also add some information to the OP about the reactivation lock, thanks for the suggestion.

Will post when its updated.

Mark.
[Galaxy S6 Edge Original Android Development] mskip:
Can you boot in to download mode at all?

Mark.
[Galaxy S6 Edge Original Android Development] Diamond777:
Hi Mark, yes I can enter download mode, im thinking about flashing stock and start all over again the root process.Its just too frustrating the black screen for hours
[Galaxy S6 Edge Original Android Development] mskip:
If you are having any problems at all the safest thing is to flash a stock image back which should restore functionality (the s6 edge is wayy too expensive to use as a paperweight).

Go to http://samsung-updates.com/device/?id=SM-G925f and download the correct image for your region. If you have trouble downloading just post the link to the file and I can download/reupload it to my server for you.

Mark.
[Galaxy S6 Edge Original Android Development] Diamond777:
Thanks for the help Mark, exactly what Im I looking for in the link? Theres alot of 925F and I cant check on anything now since my phone is black. I can boot in download mode cause Odin notifies me of the connection but I cant see no info. I just tried flashing stock:

Vodafone SM-G925F Galaxy S6 Edge Stock Firmware

Android Version: 5.0.2

PDA: G925FXXU1AOCZ

but failed in the end after some hidden.img....