yashsingh1/xdaforums huggingface dataset:
[LG Optimus G Pro] t3chwizard:
[MENTION=4961763]ecrum[/MENTION] how can i modify this to have it work with the E980? I am very eager to do so? Or do you have a working version for the E980?

---------- Post added at 02:04 PM ---------- Previous post was at 01:57 PM ----------

[MENTION=6079287]culot[/MENTION] is there any way to get this version working on the E980?
[LG Optimus G Pro] culot:
This was based on a test version I put out, not sure if it has been modified much. Here is its origin: gank. This was from a couple/few months ago and I believe it had some issues. I'm pretty sure the EFS backup ability is useless, as I had the partitions wrong (G Pro's use mkefs whatever partitions instead of the modemst* ones I specified). I don't remember exactly what else was wrong with it and I'm not sure it's trustworthy.

I'll have 2.8.7 w/ github repos within the next couple/few days.
[LG Optimus G Pro] t3chwizard:
Woooohoooo thank you soooo much. You are awesome. Will it work with the encrypted internal storage as well? I know the nexus TWRP has an option to decrypt the internal storage if you have it encrypted so that you can make backups and flash things as well.
[LG Optimus G Pro] culot:
If TWRP can handle it, then I don't see why it shouldn't work. I've not tried any encrypted stuff yet as I thought it was still nonfunctional. Will test, will peep Omni Nexus5 repos.
[Galaxy S6 Q&A, Help & Troubleshooting] hillbeast:
So my Galaxy S6 is on its way and should arrive tomorrow. I might do some development on it if I get some time, but there is no point if someone is already working on the S6. I probably don't know anything that someone else might know already, but I'm interested in knowing if ANYONE knows any technical difference between the Exynos 5433 and the Exynos 7420. They're obviously two very different processors, but I'm not sure if they're dramatically different.

The Exynos 5433 for those who don't know, is in the Note 4 Exynos, while obviously the S6 has the 7420. Both have a 4+4 arrangement of Cortex A57 and A53 cores, both have a Mali T760 GPU (albeit in a different configuration), but from there it's all a bit hazy. I know both have different memory subsystems, but that should all be handled at the kernel level.

Aside from the memory subsystem being different (DDR3 vs DDR4) and the GPU having more cores, I really don't know what else has changed. If they are both similar, we can in theory branch the work being done on the Exynos 5433 by TeamEOS and RaymanFX (https://github.com/TeamEOS/hardware_samsung_slsi_exynos5433), and it gives us a good start at least on development for the Galaxy S6. It should at least have some basic components in place and then it should be a matter (if I'm right that that are still very similar) of improving and making new code that is specific for the Exynos 7420.

Really this is all theoretical, I'm not that great with this sort of development, just wanting to know if anyone knows more about this, or is the Galaxy S6 world completely barren of developers. It would be good to get the ball rolling at least.
[Galaxy S6 Q&A, Help & Troubleshooting] AndreiLux:
I know the in-depth differences but that won't help you. The rest of the hardware changes won't affect the software stack. The RIL will cause more problems than anything SoC related.
[Galaxy S6 Q&A, Help & Troubleshooting] hillbeast:
RIL is what I'm scared of most. That will be heavily undocumented and proprietary.
[G4 Q&A, Help & Troubleshooting] m0b1liz3:
Is there a model # key for the different countries? For instance, the G3 D855 was for Aus.

Nothing will come here until June at the earliest but my current phone has died so considering sourcing one from overseas.
[G4 Q&A, Help & Troubleshooting] mingkee:
H810 and H811 will be American models.
[G4 Q&A, Help & Troubleshooting] m0b1liz3:
Any idea for Australia?
[G4 Q&A, Help & Troubleshooting] ChitownWingMan:
This is also being covered in another thread: http://xdaforums.com/showpost.php?p=60563548&postcount=12

Maybe these two threads should be combined.
[Galaxy Note 3 Android Development] hsbadr:
​

MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices.

★ Disclaimer:

★ Notes:

★ Features:

★ ChangeLog:

★ Instructions:

★ Downloads:

★ Credits:

I'd like to thank everyone who made a donation just to show appreciation.

Verizon Samsung Galaxy Note 4 (N910V), Note 3 (N900V) & LG G3 (VS985)

Hit thanks, follow thread & add 5-star rating/review

... Donations are always appreciated!

​

XDA:DevDB Information

MultiSystem, Tool/Utility for the Samsung Galaxy Note 3

Contributors

hsbadr

Source Code: https://github.com/hsbadr/MultiSystem

Version Information

Status: Testing

Current Stable Version: 1.3.1

Stable Release Date: 2015-05-09

Current Beta Version: 1.1.1

Beta Release Date: 2015-05-02

Created 2015-05-06

Last Updated 2015-05-10
[Galaxy Note 3 Android Development] hsbadr:
Supported Devices

+++
[Galaxy Note 3 Android Development] hsbadr:
Reserved #2
[Galaxy Note 3 Android Development] hsbadr:
Reserved #3
[Galaxy Note 3 Android Development] hsbadr:
Reserved #4
[Galaxy Note 3 Android Development] hsbadr:
Reserved #5
[Galaxy Note 3 Android Development] TrypelZ:
If this is what i think it is,you just made me smile like a little baby who got a truck full of candies
[Galaxy Note 3 Android Development] TheDarkKnight:
Can you please a video tutorial?

I can't fully understand the instructions. Maybe it's because my English skills are bad..

And also the link to the Q&A Thread?

A virtual ROM is basically a normal ROM, right?? Or are there any limitations??

Isn't this true multiboot like MultiROM by Tasssadar?

Thanks for your hard work, the concept is amazing!
[Galaxy Note 3 Android Development] qualkuno:
Yeaah man, it is just what you are thinking it is and right now I look like a baby crying bacause of happiness more than you! hahahah
[Galaxy Note 3 Android Development] TheDarkKnight:
Me too!! :D
[Galaxy Note 3 Android Development] TrypelZ:
I always wanted to get two roms on my device ( TW and AOSP ) and now its finally there...*.*
[Galaxy Note 3 Android Development] Schrotty35:
Great to see this but i dont understand this: PARTITION your microSD card into two (FAT32/ExFAT & EXT4) partitions

How can i do this under Android? With Windows i can use Fat32 but exFat or ext4? Which is faster, exfat or ext4?
[Galaxy Note 3 Android Development] kataeb:
will wait for a video tutorial

thanks dev

:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
[Galaxy Note 3 Android Development] WhateverMan2:
Can I use my internal storage Instead?
[Galaxy Note 3 Android Development] hsbadr:
The current version allows you to run multiple virtual ROMs compatible with the running kernel, b/c it's originally designed for locked devices. In future versions for the unlocked devices, kernel execution or swapping feature will be implemented. Read the Q&A section for more details!

Please read the Q&A section posts #1-6 & this PDF tutorial!

Not in the current implementation. Maybe later!
[Galaxy Note 3 Android Development] dkonect:
Can you share the link of the Q&A thread please
[Galaxy Note 3 Android Development] hsbadr:
http://xdaforums.com/galaxy-note-3/help/qa-multisystem-android-t3101511
[Galaxy Note 3 Android Development] t-shock:
I followed the guide but I couldn't create an img file nor a green led during the boot
[Galaxy Note 3 Android Development] hsbadr:
Please post MultiSystem.log
[Galaxy Note 3 Android Development] hsbadr:
MultiSystem v1.3

Download the latest version from the main development thread!
[Galaxy Note 3 Android Development] TheDarkKnight:
So, all the ROMs can only be TouchWiz??
[Galaxy Note 3 Android Development] hsbadr:
No, If you use a custom kernel that supports multiple ROMs, you could use all ROMs in virtual IMGs. Anyway, that's only for the current version; future versions for unlocked devices will implement kexec to execute the required kernel for each AOSP or TW ROM.
[Galaxy Note 3 Android Development] ESTIMULO:
That's could be fantastic! Miui, CM and Tw together each one with his own kernel . Thanks
[Galaxy Note 3 Android Development] nitrous²:
As far as I can tell [MENTION=5868929]hsbadr[/MENTION]'s MultiRom solution has no kexec (yet?). So unless this MultiRom solution get's a kexec implementation, or you find a kernel that supports both TW AND AOSP/A/CM, you'll most probably have to use TW or non-TW based ROMs only.

Still, first we get Paranoid Android, and now this! Awesome!

Update:

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

Just saw that the question was already answered. Sorry.
[Galaxy Note 3 Android Development] 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!
[Galaxy Note 3 Android Development] hsbadr:
MultiSystem v1.3.1 [May 9, 2015]

★ ChangeLog:
[Galaxy Note 3 Android Development] ESTIMULO:
I have installed multisystem in my note 3 9005 international but I have not installed any virtual rom yet, is there a kernel that support tw and aosp roms at the same time? Or it doesn't exist?
[Galaxy Note 3 Android Development] 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:
[Galaxy Note 3 Android Development] Tenacious--M:
Will this tool allow me to bypass the locked bootloader on my AT&T Note 3 (n900a) and install CyanogenMod?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xshadowinxbc:
I'm really frustrated. I've been trying to update this Galaxy S3 for days now with no success. Currently I am running on Slimkat 7.0. It's sometimes slow and buggy and needs some updating.

For reference, this is the phone at its current state:

- Bootloader: i747ucalh9 (literally taken from the fail message when trying to update to any other bootloader)

- Modem/firmware (?): I747UCLH9

Here's what has happened, greatly summarized (note I'm using CM6.0.4.7 for all of these operations, and when I say "update", I mean "flash"):

- I tried updating to Slimkat 9 but received no signal. I gave up on it entirely for a while

- I tried installing various LP ROMs, including CM12.1.

- I had 12.1 running for a bit, but I had no connectivity. LTE, 3G,H+ nothing.

- I tried installing a newer modem (this thread. Finally at MJB, I could actually get connectivity in some of the newer ROMs (including Slimkat 9)... but it was very erratic. It would just randomly oscillate between LTE and 3G and H+. This also broke CM12.1 entirely.

- Again, the above problem was always present. Most of the LP ROMs would just bootloop me, though. The only one that worked was Cyanide L... which I didn't really like.

- I thought maybe the issue was the bootloader. My bootloader is still i747ucalh9. So I tried updating it to various bootloaders from here, but none of the updates will work. Literally, they give me error 6 or 7 and pretty much essentially tell me that I can't do it.

- So after repeating the cycle of "let me try to update this" several times and having the update fail on me, I'm still stuck at Slimkat 7 as the only thing that worked on LTE (note the past tense). Worse yet, I tried simply downgrading my modem to match my current bootloader version, but that made things worse than better. I am now stuck at 3G... which just recently went back to LTE. Talk about erratic.

- I also tried going full stock by flashing this: http://xdaforums.com/showthread.php?t=2363882 But it expects 5 arguments for format, and got 3... or something. Failed hard.

So, I'm pretty much at the end of my rope here. I really might just go and grab a new phone at this point. I just really don't want to because this thing still works fine.... I guess I got unlucky and am at a version of the bootloader that is difficult to update from. I can't seem to go anywhere with this thing. Anyone have any ideas? Do I need to use a different recovery?

Thanks...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:

getprop ro.bootloader

If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).

Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.

Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.

Good luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xshadowinxbc:
Thanks a lot for the help! I actually did/tried a majority of this an hour or two before you posted that, except the latest firmware update link you supplied. I knew it existed and I had seen that thread before, but I couldn't dig up the link again before I had to go to work. Thing is I kind of wanted to avoid Odin for some reason but I finally gave up and used it. And yeah I already knew my bootloader version. The phone told me when it failed to update the bootloader lol.

Here's what happened thus far:

- I used Odin to flash the sammobile 4.1.1. The flashing worked just fine, but booting into it did not. It hung on the Samsung logo. So, OTA updates were out the window.

- I have no idea why, so I just used Odin to flash TWRP onto it afterwards (from here)

- I tried one of the ROMS. Data still didn't work.

- I used the thread you linked to update to MJB bootloader and whatnot. The update went fine.

- Tried another few ROMs. Data worked, but LTE was still erratic.

- Updated to NE4 and then grabbed the deoxed stock ROM.

- The deoxed stock rom failed to boot (stuck at ATT globe logo). For some reason my phone can't use stock ROMs.

- So again used Odin to put TWRP onto the phone

- Installed various LP ROMS. Again the data was erratic and plus the battery life was horrid.

- Tried getting the ktoonsez kernel. My service was murdered.

- Gave up on LP. Tried Slim 9.0. Erratic data.

- Tried Liquidsmooth 4.4.4 instead.

Currently that's kind of where I'm at. The LTE data works fine (takes a bit to get up and running after reboot though) and thus far everything is okay (though that can quickly change considering I haven't done much of anything), so I don't even know if I want to mess with it anymore. It looks like this specific ROM includes a custom kernel. So I'm guessing it's an incompatibility between the kernel and the firmware version on the other ROMs. It seems like most of the LP roms have horrible battery life (back of my phone feels like a furnace on them), so I'm not even sure if I want to do that last firmware update to use them.

It'd be kind of nice to use the OTA but apparently my ability to go stock in any form or fashion is just totally borked.

Thanks for the post though, that's pretty gold. I'm sure someone in a situation like me where they have a super old firmware will find this thread of some use as it has actual instructions and links to what you need to do to get up and running. Before you posted that, I had to go digging around pretty much everywhere figuring out what and where was going wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Glad you've got it mostly working.

You might have been able to get that stock ROM to boot if you had booted into the stock recovery and run a full wipe. Touchwiz ROMs can be tough to get running after being on AOSP. As a general progression try to format internal storage with TWRP (the wipe where you have to type "yes" to confirm), if that doesn't work try a wipe with Philz, and if that doesn't work nothing, not even Odin, is effective as a wipe in the stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrkhigh:
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.

Are these the steps?

1) verify latest software

2) twrp via Odin

Alt 2) root via apk then use rashr or similar to flash twrp

3)wipe

4)In twrp install official d2att from cm website

5) install current gapps

6) profit

I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.

Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Yep. You've got it. If you're on the latest and greatest firmware I think the towelroot exploit has been patched, unless geohot has retaken the lead in that arms race.

Easiest way to root on this phone since the bootloaders are unlocked is to just use Odin to flash a custom recovery then use the custom recovery to flash SuperSU. There's just a little trick to it. Store SuperSU.zip somewhere on your phone before flashing the custom recovery. Uncheck everything but f.reset time when you use Odin; don't let it auto reboot. Upon success pull battery. Replace battery and boot straight into recovery with vol up + home + power. If you mess up and boot into unrooted stock ROM with a custom recovery it will get overwritten with a stock recovery and you'll have to Odin custom recovery back onto it and try again.

I would do this to root your stock ROM just to execute this command in a terminal app or adb shell before any more serious flashing:

su
reboot nvbackup

That fixes a derp and gives you a working efs backup on a few backup partitions built into your phone instead of a blank one. Highly recommended before doing any ROM flashing. This will just look like a pretty normal reboot. You might see a quick flash of tiny blue text if you're watching for it.

Then you're ready to make a nandroid backup (just in case), wipe, and flash away. Take a look at LiquidSmooth if you're looking for a good lollipop ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrkhigh:
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.

Thanks for the suggestion on the ROM but I think I'll stick to official cm12.1 it's not my phone and that should be a nice readily updatable bland flavor of lollipop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
At the Android 4.3 update it was noticed that flashing a custom recovery would be overwritten by the stock recovery on the initial reboot unless following the method Jason described. Another solution was to delete two lib or .so files. On devices still on stock recovery, stock recovery does not overwrite itself.

There is a blank EFS partition on the device intended for a backup. The nvbackup command populates that partition with an image which will rebuild your EFS if it is lost during a modem update or ROM flash. The loss of EFS does happen. I believe wanam, of the xposed module fame, created an EFS backup tool for Samsung devices. I don't believe he updates it any longer because he rolled the functionality into a partition backup tool, the later is in the PlayStore listed under a different creator name, yet it's still him.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] coolwhipp420:
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..

I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..

So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..

I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Since you are on LK3 you may want to considr applying the free sim/carrier unlock method before upgrading; that is if you are on stock LK3 and you have not previously carrier unlocked your device.

There was an OTA release for the MG2 stock ROM, I believe that was 4.1.2. You may want to go to that before MJB. Did you make the nvbackup suggested by Jason?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] coolwhipp420:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..

Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..

Any information is appreciated.. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
There is a command to manually trigger the restore routine. I think it's

reboot nvrestore

but don't hold me to that. I'd never execute that command except if in dire need. The problem with this phone is there is an automatic routine that can be triggered in the event of a bad flash that will overwrite your nvram with the backup, even if the backup is blank. I don't think the backup stores anything modem specific, but I've never been able to confirm that. So I've always done it again after updating modems (only had to once).

Having the phone sim unlocked can be nice if you plan on traveling internationally. Otherwise, potential future carrier hopping or added resale value are the only reasons to do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If you will never be switching carriers, nor ever sell/give/trade the phone to someone who will switch, then it is an unecessary step to do the carrier unlock.

I see Jason beat me to answering both of your questions.