Related
Hi sailors out there
When I'm going to read through the available sailfish threads the question about how to set up multirom & sailfish have been asked many times. So I thought I'm writing this little guide. I describe the procedure along the nexus 4 mako. But it have to be very similar on other devices like nexus 5 for example. The important parts that differs from mako are the kernel and modem image you've to use. I will describe the easiest way in my opinion. Experienced users have more capabilities to reach the goal. I will not describe how to install twrp recovery and unlock bootloader. Both are prequesites. Please use xda search or google to get this. But this little guide want's to be simple as possible. So let's begin .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Beginning:
First we have to detect you're actual setup and where you want to go. Because nexus 4 is up to date I think the most common goal is to run android 4.4 as primary and sailfish os as secondary. Atm I have only paranoidandroid 4.4 on my device and will show you how to get everything working.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements / Download following parts:
kernel aosp: http://d-h.st/A99
kernel cm: http://d-h.st/CCn
aosp = android open source rom. Ask in you're rom thread what version you're on with the rom
cm = cyanogen mod rom. Ask in you're rom thread what version you're on with the rom
Modem for nexus4 in version 0.84: http://d-h.st/cIJ
or
through an app in play store: https://play.google.com/store/apps/details?id=com.bpear.makomodem&hl=de
sailfishOS ea4: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
cm 10.1.3: http://get.cm/get/aWH
Multirom manager in play store: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before we're going on check up the following
1. All zip's you've downloaded have to be transferred on the device
2. Apps from play store are installed
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation process
Reboot in twrp recovery
Flash the new kernel
Flash the modem 0.84 in twrp. Or via the modem flasher from playstore. It's you're decision.
Boot back into android
Proof the functionality in android withe the new modem and kernel. Wlan working? Bluetooth? NFC?
Open mutlirom manager. Follow the installation steps.
After some time you'll be back in android. You have now the right modem, kernel and and a twrp multirom version on you're device
After this. Please reboot back into twrp recovery
There select the advanced button.
Then the multirom button
Select add rom and mark up the entry sailfish os
Press next.
Now you can choose two zip files to flash
zip1: Select the cm10.1.3 zip file
zip2: Select the sailfish EA4 zip file
Installation process is beginning.
After this select reboot
You automatically went into multirom where you can cancel the automatic boot process for the primary rom. Then you can select which rom you want to start.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And the most important thing is to read: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 for further question before you ask. I have described there many things to start with sailfish. If you find this useful think about to press the thanks button.
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
anttimonty said:
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
Click to expand...
Click to collapse
lol. and you ask why it won't work? It gave reasons for the instructions. Also look in the linked q&a thread at the bottom of first post. And here for you the relaese notes. Hope things becomes clear now. enjoy
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of alpha quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Click to expand...
Click to collapse
Also I stated in first post why I only described the way I've did
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
anttimonty said:
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
Click to expand...
Click to collapse
yes. that's a great benefit of this device Do you like sailfish?
With modem version 0.84 you have all parts working in sailfish and android
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
anttimonty said:
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
Click to expand...
Click to collapse
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
v3ng3anc32002 said:
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
Click to expand...
Click to collapse
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
mudnightoil said:
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Works nicely on my n4. Looking for getting gapps to run....
mudnightoil said:
They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
Click to expand...
Click to collapse
This is just wrong
mudnightoil said:
I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
paulle said:
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Click to expand...
Click to collapse
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
iuno said:
This is just wrong
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
thank you for information, followed your links to look at. It seems there for the z1c is a lot of remaining, we will need patience.
iuno said:
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
Don't think I'll regret getting the Z3C, from a hardware perspective ... held one the other day, as a friend had been gifted one by Sony. It's absolutely superb. Granted, I despise Android .. but for when the Jolla ****s itself / runs out of battery / when GPS or a camera is needed / roaming / skype /outdoor use, I can suffer it until there's a Sailfish port.
Hopefully as work is already under way for the One Plus One, the identical SoC used in the Z3 & Z3C won't be too much additional work.
For all the moaning and groaning about Mediatek, I'm guessing the simplest and best port of Sailfish will probably be for the Meizu MX4, as there'll be an Ubuntu ROM for it, and libhybris is used by Ubuntu Phone ...
Also, hopefully future iterations of the HADK will smooth out some of the problems porters are facing.
mudnightoil said:
Don't think I'll regret getting the Z3C, from a hardware perspective
Click to expand...
Click to collapse
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
iuno said:
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
Click to expand...
Click to collapse
I wasn't saying Mediatek in general will be easier (though it's possible), but any device with an official Ubuntu ROM certainly will (should) be - Meizu MX4 (Mediatek) is the first of those.
P.S. The Z3C is fantastic ... though unfortunately in black as opposed to the red I ordered (it's being swapped tomorrow).
Thank you very much for these instructions. i have one question though. In order to download CM 10.1.3, it says to click that link which takes you to download CM installer app. Ive used that app before and as far as I kmow, it doesnt let you choose which version of CM you want to install, instead it just sets you up to install the newest CM 11. I downloaded 10.1.3 from their site. Either way, no big deal.
Also, which kernel do I download to install? Aosp or CM?
Thank you
Still up to date
Hi,
are these steps still up to date or should we follow a different set up guide to install the latest sailfish OS on the Nexus 4? Because most, if not all, the links on the first page end up 404...
Bluetooth sync from Jolla to Nexus 4
Flashed my Nexus 4 with the factory 4.2.2 from google with radio .48 and then flashed cm-10.1-20131003-SNAPSHOT-TREATFORCOOPER-mako-signed.zip because that seemed to be the 10.1.3 mentioned in the guides to end up flashing the latest sfos from this guide http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823.
I didn't try calling, it has 3G network working and wifi is working but I can't seem to get the contacts from my Jolla phone using the Bluetooth sync from the settings.
Anybody has some advice on this?
Just had a good look at the wiki of devices on the mer website and found out the bluetooth is not yet working on the Nexus 4...
Works perfectly on my oneplus one
Updated 10/22/2014 10:20pm EST - Thread closed see new thread http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/general/cyanogenmod-tab-pro-12-2-sm-t900-t2914991
chhaggerty has now posted his source built cm11 for SM-T900 that has a full OP, why this post no longer is needed. Additionally, his build is the most complete and also runs smoother than its predecessors. However, without the initial work carried out by crpalmer, Valera1978 and bonuzzz this release would not have seen the light until much later, if ever.
I know this is not the correct place for this info, but the original thread is very, let's call it, chaotic. The OP is not maintained (do not flash .zip-files available in the OP), and it's very hard to find details unless you participated from the start and followed the development. Further, I believe this is of public interest for the community members, as the T-900 has not seen much development until now.
Tired of your laggy base ROM?
Valera1978 and bonuzzz from the P-900 forum has successfully ported crpalmer's cm-11 T-520 picassowifi to the SM-T900. The cm-11 ROM is very snappy and responsive, there is no reason not using it as a daily driver. Before flashing it's recommended to update to TWRP 2.8.0.0, see my note for details
Attention: This is a non-stock based ROM, why you also need to install gapps (set of packages - full, mini, micro, nano, pico). I prefer the Pico in order to be in control of the maximum of what is installed, but that's up to you.
Finally: Don't forget to make a backup of the ROM you currently have installed.
Do you want to try but are afraid to make the change? bonuzzz has released MultiROM for T-900. This will allow keeping your TouchWiz ROM, and concurrently install cm11. You can then, seamlessly, go back and forth between the two alternatives.
Alternatively, you can also try it the traditional way. However, some people had issues in going back to StockROM after having tried cm11, but after flashing bonuzzz's MultiROM kernel on the top of the TouchWiz ROM, it boots up immediately and radically improve the performance, isn't that a bonuzzz.
For the cm11, there might be some minor, non-verified, remaining issue(s);
- auto-rotation - screen orientation is always presented in landscape mode, independent of settings. However you can use an app, eg Ultimate Rotation Control, to lock the screen in any direction.
- IR blaster - I used IR 2.0 and had no issues with TouchWiz, but no reaction with cm11
I will try keeping a POST up to date with latest developments
- LED notification lights - don't look for it, functionality is not supported by the device
- Proximity sensor - don't look for it, according to Samsung's specs the device does not have one
Details of what has been fully tested can be found HERE
Valera1978 said:
cm-11-20141012-UNOFFICIAL-v2wifi
Merge with latest official nigtly 20141012.
Also included new kernel.
https://drive.google.com/file/d/0B-6...ew?usp=sharing
Please test it.
Click to expand...
Click to collapse
Note: the BROWN text contain links to the actual postings
Need help installing the rom
arcadia2uk said:
Updated 10/18/2014 08:40am EST
I know this is not the correct place for this info, but the original thread is very, let's call it, chaotic. The OP is not maintained (do not flash .zip-files available in the OP), and it's very hard to find details unless you participated from the start and followed the development. Further, I believe this is of public interest for the community members, as the T-900 has not seen much development until now.
Tired of your laggy base ROM?
Valeria1978 and Bonuzzz from the P-900 forum has successfully ported crpalmer's cm-11 T-520 picassowifi to the SM-T900. The cm-11 ROM is very snappy and responsive, there is no reason not using it as a daily driver. Before flashing it's recommended to update to TWRP 2.8.0.0, see my note for details
Attention: This is a non-stock based ROM, why you also need to install gapps (set of packages - full, mini, micro, nano, pico). I prefer the Pico in order to be in control of the maximum of what is installed, but that's up to you.
Finally: Don't forget to make a backup of the ROM you currently have installed.
Do you want to try but are afraid to make the change? Bonuzzz has released MultiROM for T-900. This will allow keeping your TouchWiz ROM, and concurrently install cm11. You can then, seamlessly, go back and forth between the two alternatives.
Alternatively, you can also try it the traditional way. However, some people had issues in going back to StockROM after having tried cm11, but after flashing Bonuzzz's MultiROM kernel on the top of the TouchWiz ROM, it boots up immediately and radically improve the performance, isn't that a Bonuzzz.
For the cm11, there might be some minor, non-verified, remaining issue(s);
- auto-rotation - screen orientation is always presented in landscape mode, independent of settings. However you can use an app, eg Ultimate Rotation Control, to lock the screen in any direction.
- IR blaster - I used IR 2.0 and had no issues with TouchWiz, but no reaction with cm11
I will try keeping a POST up to date with latest developments
- LED notification lights - don't look for it, functionality is not supported by the device
- Proximity sensor - don't look for it, according to Samsung's specs the device does not have one
Details of what has been fully tested can be found HERE
Note: the BROWN text contain links to the actual postings
Click to expand...
Click to collapse
Hello,
I tried to install your rom but it gave me an error. I installed twrp 2.8 and then I flashed the cm11 rom. See attached picture for the error.
I am very new in flashing stuff so I hope someone can help me and tell me what to do.
Many thanks.
Deslang16 said:
Hello,
I tried to install your rom but it gave me an error. I installed twrp 2.8 and then I flashed the cm11 rom. See attached picture for the error.
I am very new in flashing stuff so I hope someone can help me and tell me what to do.
Many thanks.
Click to expand...
Click to collapse
I hope that you started by making a backup of your current ROM. Thereafter, I assume you did a factory reset, and also wiped your system.
However, It looks like you are installing gapps before the ROM, it should be the other way around. First ROM, then gapps.
So, I have been using an S3 {yeah S3 , i know old, but duh i just love it } for over 3 years now . I started out as a complete noob, still am, and S3 was the first phone that i started working on. Over the years i have tried many custom ROM's , Kernel's and MOD's and i have tried here to create a List of Best Performing Custom Items over the course of 1 year, with special care for people like me who have just started out in the world of android, So here goes. {in 4 steps} :-
<1> Best "FAIL-SAFE" Method of Rooting/Installing a custom ROM - I know most of the people are afraid of bricking their device's, the first time they root. I have been in that situation and had my phone soft bricked many times while trying out different thing's. So the Most FAIL-SAFE Method that i have come up with is this:-
Many people suggest rooting the devices first and then installing a custom ROM. I have tried to do things a little differently so that the first timers can get comfortable.
A. First thing to do is install CyanogenMod on your specific devices. [without rooting] , The developers at cyanogen have made an application to directly install Cyanogen to your devices from your PC like a regular Software Install. The Link and the Instructions can be found on the official Website - http://get.cm. The process is very simple and easy to do and after the install your device gets automatic root access. The xda thread - http://http://forum.xda-developers.com/android/apps-games/app-cm-app-installer-t2959922 - {you get CM - 11 from this download }
B. Now that your device is has CyanogenMod, you get a rooted device and a custom ROM. But the problem with Cyanogen is that the Custom recovery which it provides has very limited options available. So the next step is to go to Google Play Store and download "TWRP Manager" or "ROM Manager" [i personally use TWRP]. This application will help you to Install the TWRP or CWM recoveries on your Phone. The process is fairly simple, After Installing the App, Choose your Device Model and Version and Let the app do the rest of the work. PS the apps require ROOT access which your phone can provide now.
C. By now if all the steps are performed correctly [very less chance of something going wrong because most of the tings are done automatically] your respective device should have a custom Recovery installed. Next and Most important step is to Create a NANDROID BACKUP [basically an ultimate backup to restore everything]. Go to recovery mode [Home+Volume up + Power button] and select backup, and make a complete backup on your SD card. It's really important to create a Backup before doing anything. This step must not be skipped in any case.
D. Now it's time to let your imagination run wild xD, Download custom ROM's, Kernel's MOD's etc and just copy the zip's to the SD card and install them using the recovery. In case anything goes wrong Just restore from the Backup you made earlier.
[PS: Update your backup's regularly]
<2> Now's the list of My Personal Favorite's which Have Improve the overall Performance of My Phone Greatly. All the ROM's, Kernel's etc have been personally tested by me for over 3 month's for Issues related to Stability, Performance and Bug's . I have tried to put forward the Best package for optimal performance.
1. Recovery [doesn't affect much] - - TWRP Recovery: Personally "Team Win Recovery Project (TWRP)" is my favorite because of it's easy to use touch control's , it's efficiency and Design. I like the cool blue texture theme of TWRP and the speed with which it create's backup and install's new things. The performance of the Phone does no depend upon the Recovery though and you may choose whichever recovery you are comfortable with.
2. ROM - BlissPOP v4.0.3 (CM 12.1 base) : Yes i have chosen this ROM out of the many other i tried. The reasons are very simple, This ROM provides outstanding stability and Performance to the device. There is no bloatware in the ROM and there are simply hundred's of features available for customization. It's compatible with generally all the Kernel's and Mods available for your device and the regular Nightlie's are an added bonus. It's the only ROM based on Lollipop(5.1.1) in which i haven't found any Bug's or stability issues.
Many people told me to try Paranoid ROM but personally i find Paranoid a little buggy, and i found that the PI controls and Halo, due to which the ROM is popular are not of any important use to people like us. They only add a touch of appearance to the device [strictly my view and i mean no offence to any other person ].
3. Kernel - Archie kernel for Galaxy S3 - http://forum.xda-developers.com/galaxy-s3/development/kernel-archikernel-v1-0-power-hands-t2785337
4. MOD's -
A. Audio Engine - Ac!d Audio - http://http://forum.xda-developers.com/galaxy-s3/development/mod-acid-audio-engine-v5-0-samsung-t2002197
Viper4Android -http://forum.xda-developers.com/showthread.php?t=2191223
6. Root Applications -
A. Titanium Backup:
You can backup, restore, freeze (with Pro) your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card. You can do 0-click batch & scheduled backups. Backups will operate without closing any apps (with Pro). You can move any app (or app data) to/from the SD card. Available on Google Play
B. AdAway for Android [built-in app in BlissPop ROM]:
to block ads on your Android device this app is not avalibale on the playstore but you can still install it from this link
C. Greenify:
Is a good application to make your Android device more faster, by hibernating the background apps that you don't use. this application is completely free. Available on Google Play
These are the only Apps which i find useful in the long run as i have to use them constantly. Rest application's are used from time to time but not regularly. So this is My List, i'd be glad if anyone want's to add to it ^.^
I'd Like to Thanks the Amazing People who have Made the above Programs to make our Phone More performance and Appearance efficient. ------> CyanogenMod community, BlissPOP community, xda developers, Jeeko, JustArchie, amarullz, the Ac!d Audio Engine Team,zhuhang(Viper Mod), TWRP team.
Give a Thanks if u were helped by the post
================================================================================================================
Intense Testing Period -> Over 8 months [tried the new Lollipop ROMS's , over 20 kernels, Latest Android M ROM's , some personal opinions
================================================================================================================
Firstly sorry, for the delayed updates, i have been a little busy trying to develop my own ROM (surprise! surprise!, not for S3 unfortunately thought as i can never come close to the current ROM wiz's ), now in the second edition , I have tried to utilize my knowledge over 8 months to put up a new more enhanced guide and have also put up common and uncommon bugs which I experienced along the way and have provider the working solutions for them. Also I am extremely sorry for all those broken links and not working Mods, i'll try to keep my list precise, sharp and accurate this time.
1. Alternate method to Root (super easy, risk free, takes at maximum 5 minutes) - {for windows running PC, stock ROM or any other custom ROM can be used}
So, I would still recommend using my method 1 in order to initially root your device, install a custom ROM and a Recovery as i know the fear and anxiety or every new user trying to root his phone for the first time.
Now for a little more experienced users (quickie guide) [for I9300 version] who do not want to spend a lifetime to just get their devices rooted -
(a) Download the Chainfire's AutoRoot file here and place this file on your PC.
(b) Download Odin (latest version) on your PC here and unzip the file and start odin.
(c) Power down the device, then reboot in Download Mode [ press Power button + Home Button + Volume Down Key] and press volume up key at the caution screen. (little Hint: mostly the device reboots itself when you do not press the 3 buttons at the same time, to counter this press the volume up button and the home button first and hold them and then press the power button until you see the Galaxy S3 logo)
(d) Now connect your device to your PC using a sturdy USB cable. After doing this 2 outcomes are possible:-
~1. Your device is identified by Odin and a faint blue colour is shown on one of the top tabs indicating the port through which your device is connected. In this case proceed to step (e).
~2. If your device is not recognized by odin ie no blue colour, then the drivers of your device might not be installed on your PC. To tackle this download the Driver Suite from Samsung here and run the program. If done correctly when you next connect your device the drivers should get installed and odin should recognize your device.
(e) Click the "AP" button on odin and select the "Chainfire's v-xxx .mad5.tar " file which you downloaded above, odin will then take some time to check the file and when it's ready press start. CAUTION - do not change Odin's settings and assure that Reset Runtime and Auto Reboot are selected, never select re-partition on the odin interface.
(f) After the installation is complete your device should reboot automatically and you should have SuperSU installed (indiacting 99.99% times that your device rooted successfully ).
(g) If you want you can then install a custom recovery using the method indicated in my "method 1" [above].
-feel free to message me for any doubts-
Here are some of my new recommendations based on personal experiences:-
2. ROM's - I will try to divide this section based on firstly Android System and then further based on Stability, Features, Performance. Further i will be adding 2 ROM's for Android M . [i will not be naming ROMS which have a touchWiz interface]
(A) Android Lollipop and Below
Stability - Official CyanogenMOD 11.x [kitkat 4.1.1] - Zero Doubt, this one is the most stable thing out there for S3, old, yes but well you can do anything you want with this ROM and it will not seriously bug out on you when you need it. If someone does not mind going for an older version of android and needs epic stability, just go for it.
Features - BlissPop v3.0.x [CM 12.1 base][ Lollipop 5.1.1] - This ROM is filled with features, you name it, this ROM has it, PI controls, Built-in apps including AdAway, Kernel Modifier, Greenify, SuperSU etc, seamlessly integrated into the build environment. Each and every feature of this ROM is customizable, every font, colour and animation. Simply put, for someone who needs features and customizations go for this one. On the other hand, this ROM is less stable (crashes quite often ) and provides a slightly laggy gaming experience. No bloatwares in this ROM.
Performance - ArchiDroid [CM12.1 base][Lollipop 5.1.1] - Performance, Performance and more performance, all the technical aspects of your device will be enhanced and although the customization features are minimal but this ROM turns your device into a Performance Beast. All the gamers and performance lovers, what are you waiting for
Android 6.x.y Marshmallow
1. RESSURRECTION REMIX M - Fast, Durable, Amazing performance. Fell in love with this one when i used it, and this is my current ROM, no bugs so far and have been using it for over 1 month. Immensely Customizable, no lag during gaming, an amazing upgrade from Lollipop.
2. NamelessROM 3.0 - Feature Loaded, Minimal, good Looks and customization features and of course the ever caring support team of Nameless makes this a go to ROM.
>>> A bit more studying will be required before i finally divide the Android M ROMS's based on their features, performance and stability. Will be posting the results as soon as i am finished.
3. Kernels - AGNi pureCM and Boeffla-Kernel (26-03-2016) , tied, tested and proved that they are the best on very benchmark or performance test, although battery usage is better balanced on AGNi whereas Boeffla is more inclined towards performance.
You can find the Links to all the above ROM's and Kernels and many more in this thread - here
PS - Please Post your bugs in the thread and i will do my best to try and solve them out with an easy and sure solution
Cheers!
Awesome rundown for a new user like me. I've just got an S3 after using a Nexus S for 3 years. The S3 feels like such a beast compared to it!
I want to root and put a custom ROM on my device this weekend. I currently use cm11 on my Nexus S but it's a bit slow (which is understandable considering the hardware) so I can't wait to try it on the S3. My priority is long term stability ( I don't like flashing the emperors new clothes every 5 minutes). I just want to flash a ROM and forget it.
Have you tried any slimroms on the S3?
Sent from my Nexus S using XDA Free mobile app
[email protected][email protected] said:
A. First thing to do is install CyanogenMod on your specific devices. [without rooting] , The developers at cyanogen have made an application to directly install Cyanogen to your devices from your PC like a regular Software Install. The Link and the Instructions can be found on the official Website - http://get.cm. The process is very simple and easy to do and after the install your device gets automatic root access. The xda thread - http://http://forum.xda-developers.com/android/apps-games/app-cm-app-installer-t2959922 - {you get CM - 11 from this download }
Click to expand...
Click to collapse
Hi.
Can you just go over this again. Do I use my phone to download an installer from http://get.cm, install the apk then I will have root?
edit - damn I don't use WIndows, only Ubuntu. I can't use it.
Cheers.
Hi warren
Yes I have used slimrom too on the s3. Its good but as u are looking for stability I would suggest go for cyanogen because in my experience cyanogen shells out a better performance as compared to slimrom. My gaming experience was a little reduced in slimrom and I experienced a little lag but no such issue in cyanogen.
Secondly if you use ubunto I would suggest going for a virtual box to install windows and then the cyanogen application as it's the safest way to install a ROM.
U have to got to " get.cm " from both your phone and PC
On PC a windows installerbwoll be downloaded and on the phone an APK will be downloaded first install the apk the install the windows program and then continue as given in the installer setup.
Else mate, I wud say first download the stock ROM of s3 as a backup and the continue to root in the traditional way .
Any problem just ask me
Cheers
Hi.
I was thinking the same. CM11 all the way! I used Slimrom on my Nexus S but it was very very slow. I almost smashed my phone in frustration.
Nice tip about using a virtual machine to install cm. I will have a think about that. At the moment I have found a very good guide that involves using Heimdall on Ubuntu and Chainfire,so i will probably go for that method.
I am definitely going to try arter97 kernel. It looks immense. It has boeffla sound which I am looking forward to trying.
Sent from my GT-I9300 using XDA Free mobile app
A little Confused....???
[email protected][email protected] said:
Hi warren
Yes I have used slimrom too on the s3. Its good but as u are looking for stability I would suggest go for cyanogen because in my experience cyanogen shells out a better performance as compared to slimrom. My gaming experience was a little reduced in slimrom and I experienced a little lag but no such issue in cyanogen.
Secondly if you use ubunto I would suggest going for a virtual box to install windows and then the cyanogen application as it's the safest way to install a ROM.
U have to got to " get.cm " from both your phone and PC
On PC a windows installerbwoll be downloaded and on the phone an APK will be downloaded first install the apk the install the windows program and then continue as given in the installer setup.
Else mate, I wud say first download the stock ROM of s3 as a backup and the continue to root in the traditional way .
Any problem just ask me
Cheers
Click to expand...
Click to collapse
My understanding is that unless you rooted your S3 quite a while ago, pre 4.4.2, you can't add custom ROMs. The late-rooters would have a locked bootloader and would be severely limited on what mods are possible. Is my understanding incorrect? Thanks!
Oh my I hope this isn't the case.
Is this not just on Verizon or all s3's?
Sent from my Nexus S using XDA Free mobile app
Sorry to confuse things. I believe the locked bootloaders only apply to those unlucky enough to have Verizon phones.
Yay not me then! NP.
P.S. Verizon suck!
Yes mate unfortunately Verizon version of S3 has a locked boot loader and it does not allow the user to install a new recovery. I would suggest using Odin to auto root your phone which in turn also unlocks the boot loader. I can make a step by step guide for Verizon version if anyone requires it. Personally I prefer the international version though. It has more optimized system functions.
Tell me if u want a Verizon guide
$$-
Thanks for your reply. Sure, if you have something that will allow me to unlock my Verizon Galaxy S3 bootloader, that would be great! Is that what your verizon instructions will allow me to do? I've never heard of any way of doing this, so that would be great if it works! Btw, I am running 4.4.2. Thanks again!
What about /EFS backup and locked boot loader?
I have been an old time user of android starting with sony xperia X3. I had a bad luck with that phone. When sony updated android from 1.6 to 2.2 , the phone went into a boot loop and finally got dead. I sold the battery and screen separately to make some cheap buck!!
After that experience, I have been reading a lot for rooting and there seems to be lot of info on that.
My phone model is Samsung S3 GT-I9300 international version. I am still on the stock Rom with 4.3 on it.
I tried with kingroot app and it bricked the phone and was able to recover with kies.
What I want to know is that, you have mentioned option A, do I need to make any backups (not the contacts and personal stuff which I am not worried when I start playing with the phone) of EFS partition?
Will I be able to restore to old stock ROM just by using ODIN and the firmware which is available from the market?
What I need to know is , will I need any specific data (IMEI or EFS) unique from my phone?
Hi [email protected][email protected]
I used Heimdall in Ubuntu and I managed to root and put SuperSU on my phone ! I also put TWRP recovery on as well and then did a backup of my stock ROM. I am now ready for some ROM flashing!
I am unsure whether to go for CM11 or something like Tamasek's CM12.1 ROM. Have you used Tamasek's ROM before? Thinking about it for the first flash I think I will use CM11 snapshot and arter97 kernel. Then I will nandroid backup and then I have a stable ROM/kernel combo to fall back on in the future.
Looking at arter97 kernel can you tell me about f2fs support and how I get it? Does it speed up certain parts of the memory? Is it worth flashing? Also, the kernel mentions touch wake. Is this available for the S3?
Cheers.
I can't believe it I bust my sim slot! I cut my old sim card with a tool cutter and it looked good but it was a little tight going into the slot and I pulled it out and that’s when I must of bent some pins. I'm gutted :crying::crying:
Thankfully a replacement is only £3 and swapping it over looks a doddle :fingers-crossed:
Looks like I will have to wait a week until I can have a proper play. I did download BlissPop ROM and I like it. Been playing around with that all day but Its still not a phone until I get my sim in it.
You live and learn
mathew_p_a said:
I have been an old time user of android starting with sony xperia X3. I had a bad luck with that phone. When sony updated android from 1.6 to 2.2 , the phone went into a boot loop and finally got dead. I sold the battery and screen separately to make some cheap buck!!
After that experience, I have been reading a lot for rooting and there seems to be lot of info on that.
My phone model is Samsung S3 GT-I9300 international version. I am still on the stock Rom with 4.3 on it.
I tried with kingroot app and it bricked the phone and was able to recover with kies.
What I want to know is that, you have mentioned option A, do I need to make any backups (not the contacts and personal stuff which I am not worried when I start playing with the phone) of EFS partition?
Will I be able to restore to old stock ROM just by using ODIN and the firmware which is available from the market?
What I need to know is , will I need any specific data (IMEI or EFS) unique from my phone?
Click to expand...
Click to collapse
Hi Mate,
First of all, don't worry at all about the bricking thing, with the option A that i have mentioned, it's 99.99% success, i haven't found a single person yet for whom the method didn't work.
Secondly i would suggest u take the backup of your phone contacts in a vCard format using Kies first so that u don't loose them. And copy all your Personal things on your PC (pics, videos etc).
Thirdly you do not need to make a separate disk partition for the method to work, the CM installed will do it for you. Also if u have an International i9300 version u need not do a single thing yourself. Just start the setup and sit back and relax. Just follow my method to the letter and you can have a great custom ROM with root access in no time.
MOST Importantly - You can go to stock firmware of samsung but this time you will have to use odin instead of Kies to do that. You won't be able to use Kies once you have installed a custom ROM, but trust me that's a small price to pay for a very efficient ROM.
You do not need to know the IMEI or EFS number though i would suggest u still make a note of it somewhere in case ur phone is lost. Prevention is always better Message me if u have any queries. Cheers!
Warren_Orange said:
Hi [email protected][email protected]
I used Heimdall in Ubuntu and I managed to root and put SuperSU on my phone ! I also put TWRP recovery on as well and then did a backup of my stock ROM. I am now ready for some ROM flashing!
I am unsure whether to go for CM11 or something like Tamasek's CM12.1 ROM. Have you used Tamasek's ROM before? Thinking about it for the first flash I think I will use CM11 snapshot and arter97 kernel. Then I will nandroid backup and then I have a stable ROM/kernel combo to fall back on in the future.
Looking at arter97 kernel can you tell me about f2fs support and how I get it? Does it speed up certain parts of the memory? Is it worth flashing? Also, the kernel mentions touch wake. Is this available for the S3?
Cheers.
Click to expand...
Click to collapse
Hello Warren,
Good to hear that you are having fun with your new phone.
Firstly yes i have used Tamasek's/JustArchie's CM12.1 ROM and it's quite good to be honest. So first i'll talk about it then i'll come to the kernel.
So 12.1 yes, the most noticeable change android L 5.1, all good, nice appearance, but i would say just think again for a bit.
A comparison between the two is a mammoth task but i'll try to brief it for you and tell you why i like the CM11 better even though it has android KK. It's upto to you though what you choose to flash. i even have a nice tip for you in the end
So first let's see the CM12.1 -
Quite stable, i used it for like a month or so for testing and got a good result. The performance was at par with the rest of the ROM available for S3. The Graphics, Audio and Processing quality is also good and is suitable for light use. Here's the catch though, Firstly the Gaaps, many gaaps available Android L are not compatible with the unofficial 12.1 so u'll have to look around to find the correct set of Gaaps.
Secondly i personally find that the CM 11 has a much neat finish as compared to CM 12.1, i don't really care about the android version as for me if i can have all the features of android L in a more stable KitKat ROM i don't usually upgrade my ROM. THe reasons are very simple
Firstly it's Unofficial, No Nightlies, rare updates. Also the unofficial ROM is alive only till the Developer is still working on it. Once he stops his work it's a very slim chance that you can get your bugs fixed.
As for the Official one, there are thousands of forums on Solutions to various Bugs and Numerous customization options. We can't really know whether the unofficial 12.1 supports all the things available for the official ROM.
Based on Performance both the ROMS perform equally, there's a camera Bug in the 12.1 which can be a problem sometimes but rest is all good.
On a personal side [not really of importance] i like the Calculator of the CM 11 better than CM 12.1.
Now the Kernel - arter97 is simply amazing, The most noticeable changes are - 1800 GHz overclocking [yeah from 1400 to 1800 BOOM!],
the Knock feature - Tap the screen to unlock the phone, no need to use any buttons, Battery Tweaks etc.
Also it used a custom engine to allocate the Files to various partitions to the memory so yeah it saves space plus we can even Increase our RAM a bit by using the Internal Memory of the Phone.
I am a Hardcore Gamer and use my phone to the limit sometimes [ Playing Asphalt 8, Real Racing, GTA: San-Andreas, FIFA 15 and WWE Immortals can take it's toll on the phone.] these games require very high end phones but with this kernel they all run liquid smooth on my phone without even a slightest bit of lag. So yeah i would surely recommend arter97's Kernel. PLUS u get Boeffla Audio Engine which is an added BOnuS
Touch WIZ -- Not Necessary, I flashed it using TWRP and it worked Just fine.
f2f - f2f has better memory allotments and it's pre configured, we usually don't have to enable it, it's much better than extD though.
TIP - arter97 supports dual Booting so you can even enjoy cm12.1 and cm 11 at the same tine [Dual Booting i'll cover in the next post if you have a problem doing it ]
-----> Also U can use the Siyah Kernal, which work's just fine and even has an amazing Boot Image but now as much features as arter's.
straykat said:
$$-
Thanks for your reply. Sure, if you have something that will allow me to unlock my Verizon Galaxy S3 bootloader, that would be great! Is that what your verizon instructions will allow me to do? I've never heard of any way of doing this, so that would be great if it works! Btw, I am running 4.4.2. Thanks again!
Click to expand...
Click to collapse
Hello,
well i have two methods for Verizon Phones, One i have tried myself the other one was tested by one of my friends,
For the First one -
Using Odin Use the Chainfire's Auto Root Application to give root access to your phone. https://autoroot.chainfire.eu/ This application in turn also unlocks the bootloader and hence you can easily install further ROM's. Check the Xda general Samsung forum to learn how to use Odin if u don't know , or just message me
Second - This Method requires Root Access on you r Phone. THere's an app on Google Play named "EZ Unlock" to unlock the bootloader , I think this app can help you out but i haven't tried it myself so i can't really comment. But looking at the reviews i would say that this app really works. ----> http://www.mediafire.com/download/qozzz1p43kxzs3z/EZ-Unlock14.apk
Here's a custom Recovery that can help too - http://forum.xda-developers.com/showthread.php?t=2797314
Cheers!
Hi..I did a search but i am completely confused and bewildered by the vast amount of different posts and opinions in threads..so i apologise if this has broken any rules.
Basically i have a stock s3 i9300 (uk) with original samsung jellybean 4.3 rom,I am getting a bit sick of it now (and the bloat) and i am looking to move on to something more appealing..I have already rooted and installed Rom Manager and CWM..i was wondering what the "Best Simplistic dark themed (small footprint) rom" to go for As i want minimal installed size to make the most of my 16gb memory,i dont mind which android version as long as the process is easy and the battery life is among the best available..And of course it is as stable as my current Samsung android rom..
i would really appreciate any valued veteran guidance..many thanks.
[email protected][email protected] said:
Hello,
well i have two methods for Verizon Phones, One i have tried myself the other one was tested by one of my friends,
For the First one -
Using Odin Use the Chainfire's Auto Root Application to give root access to your phone. https://autoroot.chainfire.eu/ This application in turn also unlocks the bootloader and hence you can easily install further ROM's. Check the Xda general Samsung forum to learn how to use Odin if u don't know , or just message me
Second - This Method requires Root Access on you r Phone. THere's an app on Google Play named "EZ Unlock" to unlock the bootloader , I think this app can help you out but i haven't tried it myself so i can't really comment. But looking at the reviews i would say that this app really works. ----> http://www.mediafire.com/download/qozzz1p43kxzs3z/EZ-Unlock14.apk
Here's a custom Recovery that can help too - http://forum.xda-developers.com/showthread.php?t=2797314
Cheers!
Click to expand...
Click to collapse
[email protected]
Thanks for the info! I looked on a Chainfire thread here on xda to see if others have done what I would be attempting to do with my Verizon S3, but I don't see anyone else saying they've used this method to unlock their bootloader & install roms. By chance, do you know any place on this forum or any others that talk about peoples' successes using this method on a Verizon S3? I'm a little nervous about attempting this method without knowing that lots of other people have done so successfully.... Thanks for your help & your understanding of my feelings on this.
Broken Link
Your "Mods" links are broken.
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
LGAGaming said:
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
Click to expand...
Click to collapse
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
aybarrap1 said:
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
Click to expand...
Click to collapse
Thanks I thought that it was the marshmallow as I seen a thread that said it was the marshmallow baseband
aybarrap1 said:
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
Click to expand...
Click to collapse
Is there a way to get The Marshmallow BaseBand?
LGAGaming said:
Is there a way to get The Marshmallow BaseBand?
Click to expand...
Click to collapse
Not quite sure what's meant by your own meaning of Baseband. Your more than likely going to be answered by people still using the phone in different degrees of knowledge.
The experienced with a real practical application of this XT1575 device mostly have moved on to another device by now - but will any left on it be answering you. I'm glad to see @aybarrap1 has answered.
@stevejohnson42 uses the XT1575 too, and reports here and there of his flasholic tendencies on this device - might be helpful in any Nougat based ROM's to use the search box there and see if he's added anything in it.
Custom ROM Marshmallow development was always greater cause the XT1575 stayed on the Marshmallow OS for so long and because of Motorola not releasing Nougat sooner for it.
There are some Custom ROMS based on Nougat - just read their OP's to understand what's being required to using each one of them...
Nougat ROMs built for a Stock Nougat Kernel and Modem.
To answer your question without you going into a Blackhole in having to know more about your device in getting it back to good ground - I OFFER THIS-
Only way I know is to buy a XT1575 device that's never taken the servers Nougat OTA or has been ADB flashed to Nougat OS...
This as in ADB flashed questioned basically being understood by the device still having the bootloader status to LOCKED - as DEVICE LOCKED, the STATUS will still show 0, and it's software status of OFFICIAL.
Note: The Status Code will always show 2 = (relocked) or 3 = (unlocked), and it can never go back to 0 = (device locked), if it's ever been unlocked by a Motorola token code obtained from their site.
Otherwise you need an image of the Bootloader screen of the device up for sale.
THAT'S THE ONLY WAYS TO KNOW AND A SELLER SHOULD SUPPLY THIS AS A GUARANTEE AND/OR AN IMAGE SHOWING YOU FIRST...
OR YOU BUYING FROM A SITE AND ASKING THESE QUESTION OF THE XT1575 SELLER FIRST BEFORE THE PURCHASE AND THE SITE (LIKE EBAY) HAS A GUARANTEE IN THAT AD - TO FALL BACK ON...
To check this yourself-
1. Using (vol down + power button) put the device in bootloader mode where all of this is visible / should read as follows - see images also.
(A) - totally Stock non-rooted Marshmallow Baseband should read as - M8992_1255331.29.01.88.02R SUPER_NA
as taken from my Marshmallow XT1575 build MPHS24.49-18-16 devices Bootloader.
(B) - Shows the very same thing with device from the ABOUT PHONE in settings.
(C) - Rooted Custom Rom Nougat Baseband M8992_1255331.29.01.88.09R - from the ABOUT PHONE in settings / using the NuclearROM.
(D) - M8992_1255331.29.01.88.09R SUPER_NA - from the Bootloader Mode on same device - using the NuclearROM.
PS: I'm thinking, changing to a different Android build changes the Baseband build as well being applicable to the OS build version.
Warning:::
No don't ever do a complete ADB MM downgrade flash - if wanting to OTA back up to Nougat at some future point after already being on the Nougat OS.
To be clear "It's not recommended to downgrade" and allow a Moto X Pure device in taking the Nougat OTA again.
Once bootloader.img and gpt.bin are updated, there is no reverting back without the serious and the likely risk of a hard-bricked device. Only remedy at this time is a mainboard replacement. Confirmed in this threads post #75 .
A COUPLE POINTS - I'd like to make:
I've always clean flashed my XT1575 in custom roms and to going back in a stock Nougat OS - point being, I have never had any problems thereafter...
Another thing I'm thinking with an LOS based ROM - writes / changes some partitions parts that only with your ADB flashing back to the factory Official Stock Nougat can fix - changing everything back to an original partition structure.
- TWRP only backups a few partitions on the device, so partitions out of it's reach never gets restored back to an original stock environment with a TWRP backup when you do a restore using it/one made thereafter.
OTHER Reading you might want to do:
#30
#61
#73
#147
#179
#184
Baseband
I'm far from being a real practical experienced user in a XT1575 device but, I share in what I've taken a grasp of.
Hope this helps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LGAGaming said:
Is there a way to get The Marshmallow BaseBand?
Click to expand...
Click to collapse
Sorry I never got around to replying. @ResistanceIsFutile did a pretty good job explaining things as far as I can see. I just flashed stock Nougat within the last month with the intention of staying on stock rooted. I don't know if it is possible to downgrade any parts successfully but from what little I read a month ago on it, I did not remember anything staying how to do so.
LGAGaming said:
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
Click to expand...
Click to collapse
As @aybarrap1 has pointed out already, you are running a stock Nougat baseband,
Meaning you've also upgraded fully to the Nougat OS on your device.
Possibly, for someone new to the XT1575 on Nougat OS it's a good place to stay and get acquainted.
There's nothing wrong with Nougat. Root and TWRP are possible, as well advancing us further than what the Marshmallow OS offered.
I can understand Custom Rom wise, your wanting to "Is there a way to get The Marshmallow BaseBand?" but, consider that's just water under the bridge now - never to be the same for you. In anything you'd do to achieve this would just put your device in a Mixed-State, and where an advanced user would be better adapted of dealing with that.
That's why in my 1st. post to you I was trying to encourage you to read more, let it go awhile and sink-in, and read some more getting a mental picture as you understand the depth of everything related.
Or simply sell off your now XT1575 Nougat OS device and what to look for in a stock-locked bootloader of a Marshmallow OS XT1575 device and stay there not taking an OTA of Nougat.
Even in some Custom Rom's built for a Stock Nougat Kernel and Modem there have been changes related to the TWRP version needed to be used of them.
Here gives abit about that information.
I use the NucleaROM on one XT1575 and kind of bias towards it as I've stayed with it in my first flashing of a custom rom when OTAing up to Nougat that is after failing with LOS of the jumbled up thread for clark it uses.
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Moto X Pure 2015 (clark)
Trying to decipher this LOS thread posts of Official versus Unofficial builds, versus using Modems of MM and Nougat and talking about LOS 14.1 and 15.1 builds along the way and all the different involved posts of each Official - Unofficial unlabeled subjects there of all the posts.
It's no place for an inexperienced user to go and easily understand it.
These are the posts https://forum.xda-developers.com/showpost.php?p=75763876&postcount=1303%22]https://forum.xda-developers.com/showpost.php?p=75763876&postcount=1303 that clearly pointed out the specific information in details that helped me to know of the differences to the posts while I was active in that thread.
I like the NucleaROM because it's being based on LOS, then I can and do - do it without Google for the most part. I've not flashed any g-apps what so ever, play store is not a concern for me to use - there are other less invasive places that don't have the requirements Googles PS imposes. (F-Droid)
Even running a root file explorer I don't see anything Google related - with the way I've installed NR
Besides running an apk through Virus Total gives me peace of mind.
Android is by Google and that's were G stops with me...
NucleaROM - (root - g-apps), all are optional for the two NucleaROM builds out.
Note:It's the wakeblock app or it's folder that is mandatory to do something with in NucleaROM.
In disabling it's app in phone settings (Apps) after 1st. boot, or removing it's folder in NucleaROM's root directory via TWRP before your very 1st boot into OS where you initially setup the OS.
Did any of this help?
aybarrap1 said:
I don't know if it is possible to downgrade any parts successfully but from what little I read a month ago on it, I did not remember anything staying how to do so.
Click to expand...
Click to collapse
Don't take this as Gospel and I don't advise it since we're Post Nougat now.
As it was Pre-Nougat - but, still don't hold me to it...
A stock firmware downgrade (in the terms of) Recovery, Kernel and OS may be performed without any noticeable adverse affects.
This was prior to Nougat, every OS update changes something with a deep impact.
So I'd advise you to check in whatever thread of a Custom Rom using Marshmallow base that your interested in. To finding out any facts before hand. Notably kernel and modem related THERE IN downgrading from Nougat to using it...
As too with what's been said - Once bootloader.img and gpt.bin are updated - there is no reverting them back (DOWNGRADING) without a serious likelihood in risk to having a hard-bricked device. You'd need to skip those parts in the downgrade commands used of your flashing sequence.
I have no real world practical application of experience doing this - just reading about it or book knowledge - that ain't squat to help in a time of trouble if that's what it yields...
ResistanceIsFutile said:
Don't take this as Gospel and I don't advise it since we're Post Nougat now.
As it was Pre-Nougat - but, still don't hold me to it...
A stock firmware downgrade (in the terms of) Recovery, Kernel and OS may be performed without any noticeable adverse affects.
This was prior to Nougat, every OS update changes something with a deep impact.
So I'd advise you to check in whatever thread of a Custom Rom using Marshmallow that your interested in. To finding out any facts before hand. Notably kernel and modem related THERE IN downgrading from Nougat to using it...
As too with what's been said - Once bootloader.img and gpt.bin are updated - there is no reverting them back (DOWNGRADING) without a serious likelihood in risking to having a hard-bricked device. You'd need to skip those parts in the downgrade commands of your flashing sequence.
I have no real world practical application of experience doing this - just reading about it or book knowledge - that ain't squat to help in a time of trouble if that's what it yields...
Click to expand...
Click to collapse
Thanks. As I mentioned earlier, I had planned on potentially using custom ROMs but I have decided to stay stock rooted. I just don't get that much into customization so a custom ROM just doesn't make sense for my purposes.
There's a change in the wind with Oreo...
aybarrap1 said:
Thanks. As I mentioned earlier, I had planned on potentially using custom ROMs but I have decided to stay stock rooted. I just don't get that much into customization so a custom ROM just doesn't make sense for my purposes.
Click to expand...
Click to collapse
Your happy with the stock Nougat - as I've said there's nothing wrong with it.
I get it and respect your decision to do just that in staying with a stock Nougat.
Custom ROMs aren't merely for customization's, back in the day especially with the array of cheaper devices it was the norm though. To make it in ones liking of a polished look or for performance enhancements.
The added themes and applications preinstalled by a manufacturer were reduced to almost nothing. This saved a lot of memory space and increased the device's performance, then with being able address the questionable UI design decisions that a manufacturer had made.
Besides with the XT1575 Moto X Pure, you needn't worry much about Motorola's manufacturers bloat and being skinned to something hideous and repulsive. By that, I mean your not dealing with and like the other manufacturers (tweaking Androids OS) add/remove/change the interface and apps to make it their own highly styled branded system.
Customization's was a way to truly make a phone your own and still is...
After installing a Custom ROM on Android you are the Admin of your Device which means no Objections, no Restrictions, and basically nothing hampering you as your free to do anything with your Android device.
But, customization's is only one facet in the equation to consider with a custom rom.
Taking a view of all devices in the realm of Custom ROM's offered to each (not just an MXP), there's something more also to be gained.
Updates:
One of the most frustrating things about owning an Android device is waiting for your manufacturer to push an update to your phone, so you can get the latest features. The newer versions of Android are not only interesting because they bring new features but, also because they fill security gaps.
Often times manufacturers will even cut support for your device entirely (thinking of Motorola's support for the MXP). This leaves you stuck with a phone on an older version of Android and less secure. The solution is a custom ROM on the newest or a newer Android version for it.
Privacy and Security:
The recent alarming News surrounding data collected by OnePlus devices (along with a second claim that the company has denied), having highlighted the amount of trust we have to place in our phones by the manufacturer itself now.
This doesn't apply more to budget phones in that they may have security problems. And even the world’s second largest smartphone manufacturer, Huawei, has recently found its US ambitions blocked by US security agencies over concerns about it's spying.
And even once you get past this, every Android user is handing over vast amounts of personal data to Google and others (App's) every single day.
[[Like I pointed out in post #7, I like the NucleaROM because it's being based on LOS, then I can and do - do it without Google for the most part. I've not flashed any g-apps what so ever.]]
Lineage OS has numerous privacy controls built in, including a Privacy Guard that restricts how apps can use your data. Plus, you can use it without Google apps if you prefer !
A custom ROM can help address your security and privacy concerns. ROMs are, or should be open source. The code is available for anyone to scrutinize. Even if you don’t have the skills to analyze it yourself, you can be assured someone will flag any privacy concerns to it's custom rom using community.
Other Benefits:
Then one can benefit possibly with Performance, Battery Life. In some cases, you might even be able to unlock new functions or find features from newer flagships ported back to older devices. These are the types of phones that rarely get updated, and are often not as well optimized as their higher end siblings.
Disadvantages:
Sure Custom ROMs have their own, it's not going to be a sunny days walk in the park everyday. Expect some rain too, like in adding an app, tweaking hidden settings of the Android's OS and like-
"many phone cameras have dual lens setups nowadays, fancy HDR effects, and high frame rate 4K video. They all need special tools to drive them, and these are all part of the phone’s manufacturers firmware. There’s no one app that you can simply lift and install on another device. Nor can you replace all of the cameras functionality with a third-party camera app."
Closing thoughts:
One of the biggest draws of custom ROMs used to be that you could install the stock Android experience on any device. You could replace the bloated software from Samsung, Huawei, or HTC and other manufacturers with a ROM based on the open source version of Android. Throw in the suite of Google apps, and you’d have something akin to a pure Android device. This is the principle around which Google’s Nexus phones were built. {In reality, Android is but one of the parts of your phone's software today, not the total sum of those parts as manufacturers hardware needs it's own drivers to function.}
But, that makes the stock Android no longer the best version of Android, even Google admits this. The best parts of the company’s Pixel phones aren’t Android. The camera app, Google Assistant, and the fast streamlined launcher are all proprietary software. They’re developed and owned by Google. In fact, on the product pages for the Pixel phones, Android barely even gets a mention there.
Custom ROMs can be wonderful for older devices but, before you decide to change your device's original manufacturers firmware you should familiarize yourself with the disadvantages of the process.
Custom ROMs are perfect for those who love a good challenge. But if this doesn't sound like you then you won't like custom ROMs. Between the devices need for security updates that custom roms can offer. Comes a need to unlock the bootloader, install a custom recovery, gain system root and dealing with unstable versions being pushed to a device, and having an active ROM maintainer.
Those are some of the things where your patience could reach its limits fast.
Not forgetting, third-party firmware (as in custom roms) comes with very few or no Google apps. The Play Store application has to be installed again if you use that source for you add-on apps.
Then hardware specific software (drivers) to make a devices hardware function properly.
So is it Your device because you've paid for it, or is it a manufacturers device with their own branded apps, style and the flair they choose for you of the price you've paid for it.
It's Your choice and decision to change it or not... :good:
PS: Devices that started to ship with OREO installed will change the custom rom landscape.
There's a change in the wind with Oreo...
Project Treble has some interesting implications for the revival of the custom ROM scene.
XDA community members are excited about the prospect that we may be edging closer to a time where Android software can be easily ported across a range of devices.
Other developers have also already shown off a single system image capable of booting on different devices with different processors.
ResistanceIsFutile said:
Not quite sure what's meant by your own meaning of Baseband. Your more than likely going to be answered by people still using the phone in different degrees of knowledge.
The experienced with a real practical application of this XT1575 device mostly have moved on to another device by now - but will any left on it be answering you. I'm glad to see @aybarrap1 has answered.
@stevejohnson42 uses the XT1575 too, and reports here and there of his flasholic tendencies on this device - might be helpful in any Nougat based ROM's to use the search box there and see if he's added anything in it.
Custom ROM Marshmallow development was always greater cause the XT1575 stayed on the Marshmallow OS for so long and because of Motorola not releasing Nougat sooner for it.
There are some Custom ROMS based on Nougat - just read their OP's to understand what's being required to using each one of them...
Nougat ROMs built for a Stock Nougat Kernel and Modem.
Click to expand...
Click to collapse
Not much to add - I share @ResistanceIsFutile comment - once you have updated - don't try to go back to earlier modem / baseband on this phone
Here is another collection that gives you choices and very clear which version to use for
https://forum.xda-developers.com/moto-x-style/development/collection-random-projects-t3662970
Personally - I flashed the stock ROM that is here ( make sure you have correct variant before doing ) :
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
to move from Marshmellow modem - as noted above ; much more development on the original modem -- but I had a nagging issue with the Fly Delta app that could be duplicated but not something developers of custom ROMs should have spent time on - going to Nougat stock cleared it - then I went to NucleaROM almost immediately and everything worked fine
I have never tried - but , by searching xda-- you will find many active developers noting it is a good way to brick the phone .. I do not pretend to fully understand -- but have learned long ago to do research , carefully read OPs and safest to follow instructions of those who have much greater knowledge than me .
The phone is still my daily driver - I am currently on rooted stock that was installed by the method noted in the thread above. I have been on NucleaROM as DD and a good ROM ..and have flashed many posted by obsolete1. I have found with many back to back clean flashes - reflashing stock can eliminate issues that you might run into ( don't remember them all - but do recall having an issue wiping phone once )
Also - check carefully what TWRP to use - some of the ones using the Nougat modem require the unofficial TWRP that Hashbang developed for the earliest ROMs that worked on it.
We had a pretty good run on this phone and it appears there still might be a few developers looking at it .. but I understand ; most of them have moved on to other phones or the reality of life has required them to leave development for awhile
Regards
@ResistanceIsFutile
Thanks for the run down and I'm quite aware of many of these things. The MXPE in itself is a great phone with the few added features for Moto being actually somewhat useful.
I am not overly concerned with updates. If I were I would get a pixel or Android one phone.
Prior to the MXPE I had carrier branded phones and found custom ROMs to be quite useful in terms of bloat and better performance.
@aybarrap1
Only meant it peaceably - didn't mean by steps on any toes or persuade - crowd you or anyone at all.
The Moto X style/pure devices age has probably 3rd, 4th even 5th generation owners by now that have no ideal what we're talking about at times.
I then see it as a funneling effect, when I answer one it spreads out to others not knowing, especially in a threads topic as this. If you prefer I'll answer generally and not address anymore to you - I'm easy and would like to make friends on XDA - not loose any prospects.
I like and see your posts as helpful as I hope mine are, and it's encouraged to answer if you can at any experience level on XDA. So please forgive any misunderstanding or intentions on my part.
Thank you.
Everything is beneficial but not useful to all
@ResistanceIsFutile
Thanks. Reading back I see how the "tone" came across. I'm good and only intended to put out my reasons. I do have to say it is good you post this info as it was posts like yours that helped me a lot when I first started looking into rooting and custom ROMs some many years ago (LOL...7 or 8 years only but in terms of phone tech that is a very long time).
If this post or just part of it was usefull to you, please give a thank you, it's just one click below this post and encourages authors to keep their threads up to date.
What is this thread for?
To all those wondering what to install on their old Samsung Galaxy S6, abreviated "S6". This thread will tell you what you need to know concerning available ROMS for the Canadian W8 model of the S6.
There are 5 major guests in the Samsung Galaxy S6 Android world:
Versions 5.x.x named Lollipop abreviated "LL"
Versions 6.x.x named Marshmallow abreviated "MM"
Versions 7.x.x named Nougat abreviated "NG"
Versions 8.x.x named Oreo abreviated "O"
Versions 9.x.x named Pie abreviated "P"
Versions 10.x.x named 10 abreviated 10
Basic things you must know:
Stock ROMs which are kept as is with only deknoxed but still stock won't show you much besides keeping your phone as it is with the freedom of installing what you want.
AOSP ROMs are usually the most debloated ones and best ones. LineageOS IS an AOSP based ROM.
Debloated ROMs: There seems to be a lot of different levels of debloating. High, Partial, Light. When using a Custom ROM, you usually want to remove most of the stock stuff and install the things you desire after. But in this ROM world, when debloating, authors often rebloat them with some of their prefered apps and mods. So Debloated ROMs are mainly to say that stock apps were removed.
Kernels are not ROMs, just saying AND, they need to be installed with the PROPER version of the ROM you are installing AND must fit AOSP or Stock because they will not work and you will get bootloop.
Aroma installer which permit to choose options during the ROM's installation. These take soo much space and are huge files to download. They boost the ROM's file size. Of course, you can choose what you want during the install process, but most ROMs are over 1Gb in size which is enormous while a non-aroma file can be way under 700Mb and do the job perfectly.
LL (v5.x.x):
These are just old, your cell phone can handle much more up to date roms AND stock roms are already way passed these versions.
MM (v6.x.x):
If you need well working, functional and complete ROMs, there's a few of these which have been tested and work very well. I'd go back without hesitating if I were not too greedy on later versions,
NG (v7.x.x):
There has been a lot of apps and mods that have been made stable from NG ROMs. A system on this would be considered a good in-the-middle installation. Not too old but not too young. There is also a custom framework app out there permitting some nice handling and modding that is considered stable for this version of Android. BUT, there's a bit BUT here. There is v7.0 and 7.1.x. 7.1.x seem to have audio issues, at least, the AOSP ROMs I tested.
0 (v8.x.x):
OK! I have read sooo many articles concerning battey problems in this ROM and I have also lived the battery problem myself with a custom ROM in this version. Oreo would be the system which crosses the line between old and new, merging from MM and NG to PIE.
P (v9.x.x):
Well, you are now up to date. BUT, We are now going well over S10 models of the Samsung Galaxy nowdays so a ROM in this version working bugfree is a bit of a dream, at least, for now. Problem encountered from these ROMs are audio, camera and wifi. Camera app is just nonesense with very poor audio quality. Users talk about bluetooth audio problems and echos during calls. Frequent application crashes notably when using camera, for example in messenger. BUT, the good is a cleaned up interface with a nice fresh modern feel.
10 (10.x.x):
Please refer to Pie (v9.x.x). Pretty much the same things happen.
I decided to give you a list of ROMS I have tested and believe should still stay alive for those questionning what the best ROM is for your needs or dreams.
Links to my suggested custom ROMs:
LL (5.x.x):
• None (just don't install any of these, too old)
MM (6.x.x): Only one stands out which I used for years and has a very nice position in recommended mods.
• XtreStoLite 3.3.1: https://forum.xda-developers.com/ga...xtrestolite-deodexed-mod-edition-1-0-t3094423
XtreStoLite has made me happy for years. If you want a stable ROM with what the S6 looked like during it's glorious days, that's the ROM to install.
NG (7.x.x): Most of these ROMs seem to be stock ROMs with not so much debloation so huge file sizes and Samsung's connection wizard AND all the Google Apps you did not ask for. I fell on 1 which boasts being HIGHLY debloated.
• OdexLite 4.2: https://forum.xda-developers.com/ga...rom-odexlite-rom-920f-920i-925f-925i-t3550706
If you do not install any of the Samsung or Google apps in the aroma installer, this is a highly debloated rom. I'm mentionning it here because I managed to instal it once but not a second time. Some users have reported a boot loop which makes the ROM below pretty much safe for install compared to this one. Because of a first successfull try, I still list it here, but I suggest Ultimate Nougat below. If you want to try and have time, then I suggest to try OdexLite if you are willing to test out and see for yourself.
• UlTiMaTe NouGat V3.1:https://forum.xda-developers.com/ga...elopment/rom-ultimate-nougat-s8-port-t3681259
I managed to make it work after wating for about 15 minutes for my phone to boot initially. It is not as much debloated as OdexLite but is a bit more flexible for adblock and Magisk since you are offered to install or not in the Aroma Installer. This actually is a flaw I found in OdexLite where some applications detect Magisk and AdBlock so they make certain options unavailable. With this version, you can install AdBlock and Magisk after and get apps to work flawlessly. System is stable and a good solution if you want, what I consider, a semi-debloated acceptable ROM. Many users also mentioned that mobile and LTE networks work flawlessly with this ROM.
O (8.x.x): None (I just di not try any of them after my battery problem)
P (9.x.x): 2 Came out of the lot and work strait out of the box. OK, WORK is a big word here, be prepared for a few issues. BUT, battery life is good, not too many apps and some fun customized options.
• LineageOS 16.0: https://forum.xda-developers.com/ga...opment/rom-unofficial-lineageos-16-0-t3880888
Used it for a few months without major issues besides the common Pie ROM issues notably camera and audio issues and some WiFi problems.
• ViperOS 6.3: https://forum.xda-developers.com/ga...elopment/rom-unofficial-viperos-v6-3-t3921301
I was pretty surprised by this ROM. It's basically Lineage OS 16 with extra Viper mods for extra customizations and configuration with, as a user stated, the extra no audio during calls problem. I still consider the Viper addons as bloatware but at least, there's no Samsung apps.
10 (10.x.x): I stopped at Pie. Same issues when reading the ROM threads so I have not even tried any of them because I overuse camera and video calls, who doesn't during COVID-19?
Recommended and usefull apps:
AdAway: https://f-droid.org/packages/org.adaway/
Removes many inapp ads, not those in full screen, but removes lotsand most of them.
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Adds root access to your apps if you don't have it pre-enabled in your ROM
OpenGApps: https://opengapps.org/
Installs Google Play and other Google stuff on your phone
Xposed Framework: https://forum.xda-developers.com/showthread.php?p=58828974#post58828974
Adds numourous other possibilities to customize your phone. NOTE: Please allow an extra boot time after installation.
Xposed Modules: https://forum.xda-developers.com/xposed/modules
Launchers and other apps:
Launchers will give more style to your phone. From changing icon size to drawer's background color, you may want to have a look at launchers for a more customized experience. 2 Launchers held my attention. There's not too many out there that are worth the download even with an above 4/5 star rating. Some of them even show ads which is ridiculous for a launcher as you will see ads popup just in the middle of nowhere.
Microsoft Launcher: My prefered launcher. Has everything you need, notifiction dots, decent customizations and works with icon packs. It lacks a few customizations such as folder colors and opacity, but that left asside, I still think it is the best out of all of them considering that it is totally FREE.
Nova Launcher: The only problem with THIS launcher is that you need the paid version to enable notification badges on your icons.
Evie Launcher: Well it's one or the other, Nova permits lots of customizations with background colors but no badges. Evie permits badges but no background colors or status bar customizations. But, very fast and simple.
MX Player: I've tested a few, one of the best. Reads almost anything, fast and highly customizable. Some may say VLC would be nice but VLC showed a few lags here and there and ended up not reading some files MX read OR had more time with videos accros the network, MX Player does a very nice job.
Options you may want to change:
Enable programmer's options and disable all animations for a faster response time in apps.
Enable USB Debugging and set USB mode to File Transfer or Media Transfer Protocol.
Final Notes: I love the Pie experience but I had to resigne and go back to Nougat for stability and the camera which I use very often. It took me a while to find a reasonable Nougat ROM because I was going to resigne and go back to XtreStoLite. If you plan on testing, Facebook and Google accounts are your best friends to save your stuff so you don't need to restart your games or retype your contacts.
The chosen one: ULTIMATE NOUGAT
I hope this will help people make a choice on what to install for Canadian W8 phones. Do not hesitate to post your comments on your experiences and if you have suggestions or more information on tests you did with other ROMs not mentionned here.
Additional Bloatware you may not need
Now this is for modders who may come upon some bloatwares installed. When installing Ultimate Nougat, I decided to uninstall apps I do not use and found combersome and irritating for me. Here is the list of package names that can be removed which include App Lock, Weather and other widgets. If you are not sure of what you are doing, please do a Google Search on the package names to make sure you are uninstalling something you really do not need. In my case, I chose to uninstall these packages. You may want to get a package name virwer to know where these have been installed to remove them.
I use Total Commander with root permissions and I delete them. When I delete these packages, the phone boots properly and I get no messages or service stopping errors so I consider this my safe to remove list.
List of packages that I removed in the "system" folder (you need root permissions or use TWRP to delete):
Spoiler: KNOX
app/KNOXStub
app/KNOXStore
app/KnoxAttestationAgent
app/KNOXAgent
app/KLMSAgent
app/ContainerAgent
app/ContainerEventsRelayManager
app/KnoxFolderContainer2
app/KnoxRemoteContentsProvider
app/KnoxAppsUpdateAgent
app/KnoxFolderContainer
app/KnoxSetupWizardClient
app/KnoxSwitcher
app/MyKNOXSetupWizard
app/KnoxMigrationAgent
app/KnoxSetupWizardStub
app/SamsungDLPService
app/BBCAgent
app/SecurityLogAgent
priv-app/MyKNOXSetupWizard
priv-app/KLMSAgent
priv-app/SPDClient
priv-app/SKMSAgent
container
tima_measurement_info
framework/knoxsdk.jar
framework/knoxvpnuidtag.jar
etc/secure_storage/com.sec.knox.store
etc/secure_storage/com.sec.knox.store!dex
Spoiler: AUDIO
media\audio\ringtones\A_Rustling_in_the_Trees.ogg
media\audio\ringtones\Basic_Bell.ogg
media\audio\ringtones\Basic_Tone.ogg
media\audio\ringtones\Beep_Once.ogg
media\audio\ringtones\Beginning.ogg
media\audio\ringtones\Bunny_Hopping.ogg
media\audio\ringtones\Chimes.ogg
media\audio\ringtones\Crossing_a_River.ogg
media\audio\ringtones\Dance_Party.ogg
media\audio\ringtones\Day_by_Day.ogg
media\audio\ringtones\Drifting_Downstream.ogg
media\audio\ringtones\Ecliptic.ogg
media\audio\ringtones\First_Light.ogg
media\audio\ringtones\Fresh_Morning.ogg
media\audio\ringtones\Mystic_Tone.ogg
media\audio\ringtones\Ocean_Voyage.ogg
media\audio\ringtones\One_Step_Forward.ogg
media\audio\ringtones\Prelude.ogg
media\audio\ringtones\Scampering_Tone.ogg
media\audio\ringtones\Somewhere.ogg
media\audio\ringtones\Ticktac.ogg
media\audio\ringtones\Warm_Greetings.ogg
media\audio\notifications\Beep_Once.ogg
media\audio\notifications\Good_Time.ogg
media\audio\notifications\Run.ogg
media\audio\notifications\S_Harmonics.ogg
media\audio\notifications\S_Opener.ogg
media\audio\notifications\S_Temple_Bell.ogg
media\audio\notifications\Sweet_Favour.ogg
media\audio\notifications\Whisper.ogg
media\audio\notifications\Hello.ogg
media\audio\notifications\Peanut.ogg
media\audio\notifications\S_Bubbles.ogg
media\audio\notifications\S_Charming_Bell.ogg
media\audio\notifications\S_Dew_drops.ogg
media\audio\notifications\S_Knock.ogg
media\audio\notifications\S_Tickety_Tock.ogg
Spoiler: SAMSUNG
app/SamsungSans
app/VirtualTour_N_OS
app/VideoTrimmer_Dream
app/VideoEditorLite_Dream_N
app/VideoCollage_Grace_N
app/SlowMotion_Dream_N
app/EasterEgg
app/EasyOneHand3
app/GameOptimizer
app/WallpaperBackup
app/Weather2017_SE
app/WeatherWidget2017_SE
app/SmartRemote_zero
app/SmartSwitchAgent
app/SecFactoryPhoneTest
app/SecurityProviderSEC
app/STalkback
app/OneNote_Compact_Samsung
app/GearManagerStub
app/SecMemo3
app/AllshareFileShare
app/AllshareMediaShare
app/SBrowser_5.0
app/SPrintSpooler7
app/CloudGateway2017
priv-app/DiagMonAgent
priv-app/GalaxyAppsWidget_Phone
priv-app/SamsungPayStub
priv-app/SamsungBilling
priv-app/GalaxyApps_3xh
priv-app/GalaxyCare
priv-app/GalaxyThemes
priv-app/PowerPoint_SamsungStub
priv-app/SamsungAccount_Dream
priv-app/SamsungCloud
priv-app/HealthService
priv-app/LegacySmartManagerProvider
priv-app/SamsungPass_1.1
priv-app/VoiceNote_5.0
priv-app/Word_SamsungStub
priv-app/ThemeCenter
priv-app/SecLiveWallpapersPicker
priv-app/SHealth5
priv-app/SmartManager_v5
priv-app/SmartManager_v5_DeviceSecurity
priv-app/EasyLauncher2_Zero
priv-app/SVoicePLM
priv-app/SVoiceLang_EnglishPack_US_1.0
priv-app/SVoiceLang_FrenchPack_1.0
priv-app/SamsungMagnifier3
priv-app/SecEmail_N
priv-app/SecureFolderStub
priv-app/EasySetup
priv-app/GameHome
priv-app/GameTools
priv-app/OneDrive_Samsung_v2
etc/sysconfig/samsungaccount.xml
etc/sysconfig/samsungauthframework.xml
etc/sysconfig/samsungemail.xml
etc/sysconfig/samsungfidouafasm.xml
etc/sysconfig/samsungfidouafclient.xml
etc/sysconfig/samsungpushservice.xml
framework/gamemanager.jar
I just picked up a used SM-G920W8 as a backup until I get my Pixel 2 XL back. I plan to keep it as a backup phone but also as a music player for around the house, on trips and at the gym. The battery life is pretty poor!
I was hoping to put a custom ROM and was wondering if you'd be able to give me some guidance. So many posts on this forum are from 3 years ago and I'm not sure what is valid anymore. After seeing your post, and thank you, I would suspect you have a good deal of experience with this Canadian version of the S6.
My questions are:
What is the process to get TWRP on my device?
Can any of the other ROMs you tried but didn't run be made to work if we flash a custom kernel after flashing the ROM?
In your OP the problems you say you have, are those with your current Unofficial Lineage ROM? I'd hate to have the camera issues.
Thanks in advance.
Installing TWRP with ODIN
blyndfyre said:
I just picked up a used SM-G920W8 as a backup until I get my Pixel 2 XL back. I plan to keep it as a backup phone but also as a music player for around the house, on trips and at the gym. The battery life is pretty poor!
I was hoping to put a custom ROM and was wondering if you'd be able to give me some guidance. So many posts on this forum are from 3 years ago and I'm not sure what is valid anymore. After seeing your post, and thank you, I would suspect you have a good deal of experience with this Canadian version of the S6.
My questions are:
What is the process to get TWRP on my device?
Can any of the other ROMs you tried but didn't run be made to work if we flash a custom kernel after flashing the ROM?
In your OP the problems you say you have, are those with your current Unofficial Lineage ROM? I'd hate to have the camera issues.
Thanks in advance.
Click to expand...
Click to collapse
A simple Google search makes it easy to find but, having a thread like this one , I believe that your questions are relevant. So...
Question #1 (getting TWRP on your phone): 2 links to start with ODIN to make the flash and TWRP, the thing you need to install:
ODIN (remove spaces in the following link): ww w.droid views.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
TWRP: https://twrp.me/samsung/samsunggalaxys6.html
Follow the instructions on the ODIN website. ODIN is used to flash your phone to have TWRP installed. Also note that this process is pretty critical as it can brick your phone so be carefull and follow the instruction properly. I have flashed TWRP a few times without any problems on my side.
Question #2 (Installing a custom kernel):
I have not tried this and did not adventure myself into installing any such thing. I tend to stick with original stuff to make sure to not brick my phone. AND seeing that many custom ROMS for Pie are not out yet and also seeing the battery problem with OREO, this simply means that noone has ever found anything stable yet for this device. I don't believe that installing another kernel may make things work better. But this is just an opinion and since I did not try any custom kernel, I don't believe to have the best answer for you concerning this.
Question #3 (Camera issues with custom ROM):
Samsung Galaxy S6 is made to work with Marshmallow abreviated as MM in certain threads and posts. So anything after MM is a risk, stable or not. I had XtreStoLite for many years and I had absolutely no problems until some apps just said that MM was not supported anymore. That's pretty much the only reason I decided to install something new. I also noticed that Nougat is still very popular but have not found any Nougat ROMS that were not too heavy or simply unavailable for my Canadian phone. But, if you install any MM ROMS, your are mostly not going to have any problems. You could try OREO roms and fall in luck and find someone that figured out how to elliminate the battery issue but in my case, I tend to stick myself to the latest ROMS and live temporarly with my problems until an update fixes it as I don't have too much stuff on my phone that makes me take the reinstallation as a waste of time. I can install over 15 custom ROMS in one day while only 3 or 4 Windows during the same period, I believe that trial and error in this case is worth it. There are few stable builds that correspond to my criterias which are very few custom apps and lightweight that are less than 650 mb ROMS. Most roms go over 2 Gb while som maintain between 1.2 to 1.7 gb which I find pretty huge to my opinion seeing I can get a fully working rom for 550 mb.
I hope this helps a bit. I'm not one of those geeky people with all the technological knowledge to explain or understand the nuances of kernels and roms. I'm not a developper nor a ROM creator myself so just following the installation processes proposed makes me a simple user. I applaud those creating custom kernels and roms from scratch with nothing but their knowledge without any installation instructions until they figure out by themselves how to explain their procedures, these people are the real fun guys or girls that make us use our phone to their outmost potential without any controls giving us the freedom to use the full unlimited functionalities of our android phones.
Just so you are aware the Canadian s6 is the same as the T-Mobile version, so any separate Rom download or fixes for the T-Mobile s6 apply. Any Oreo or Pie rom will have custom kernel prepackaged, as Samsung never released those on this device.
@Rouwdyboy Well that's a very constructive comment. Thank you, this may open up some possibilities and other tests on my side once I get some time again. Thank you for your comment!
@green3water5 how did you get a Canadian S6 to work? Wow!
Other than my S6 being edge, my SM-G925W8 installs LineageOS 16.1 fine but there is no cellular data at all. Calls go through but there's no sound...
I have a suspicion that the installer installs the zeroltexx version of the ROM which is causing the issue.
I guess the only thing that can differ from my installation to yours is Twrp, so which version of Twrp do you use?
Thanks (in advance)
Jeffreyyou said:
@green3water5 how did you get a Canadian S6 to work? Wow!
Other than my S6 being edge, my SM-G925W8 installs LineageOS 16.1 fine but there is no cellular data at all. Calls go through but there's no sound...
I have a suspicion that the installer installs the zeroltexx version of the ROM which is causing the issue.
I guess the only thing that can differ from my installation to yours is Twrp, so which version of Twrp do you use?
Thanks (in advance)
Click to expand...
Click to collapse
I have to admit that I do not use my cell phone using cellular data. I constantly need wifi to use GS Wave for VoIP calls. I have not tested cellular data but I do know that MOST Pie ROMS have sound issues and some Nougat ROMS also. The sound issue is pretty redundant but in my case, using GS Wave, I do not encounter those bugs. The only problem I encounter, I have already mentionned above, BUT, I have updated my first post to warn people of possible sound problems when using cellular data. I'm sorry that I'm not of big use for your problem but thank you for your reply!
I have updated my tests and added my point of view on ViperOS.
Calls
I have no sound in phone calls, everything else is working fine.
i tried to see if there was something like "persist.vendor.audio.fluence.voicecall=true" in the build prop to edit, hoping to fix the issue.
After testing out and other numourouse trials and errors. Here's my new comments on ROMs for G920W8 models. Hope this helps. I rewrote the entire thread content for clearer explanations.
Jeffreyyou said:
@green3water5 how did you get a Canadian S6 to work? Wow!
Other than my S6 being edge, my SM-G925W8 installs LineageOS 16.1 fine but there is no cellular data at all. Calls go through but there's no sound...
I have a suspicion that the installer installs the zeroltexx version of the ROM which is causing the issue.
I guess the only thing that can differ from my installation to yours is Twrp, so which version of Twrp do you use?
Thanks (in advance)
Click to expand...
Click to collapse
I have the exact same problem as you do. I tried many roms and so far, none kept the data ON execpt Resurrection Remix 7 (zerofltecan) for about... 3 hours.
But, when I go back to stock, mobile data comes back.
@green3water5 I sent you a private message AND THEN found that thread. Sorry to have bothered you, will keep writing in here
coolmat said:
I have the exact same problem as you do. I tried many roms and so far, none kept the data ON execpt Resurrection Remix 7 (zerofltecan) for about... 3 hours.
But, when I go back to stock, mobile data comes back.
@green3water5 I sent you a private message AND THEN found that thread. Sorry to have bothered you, will keep writing in here
Click to expand...
Click to collapse
That's why I chose to use OdexLite which is a Nougat based ROM. Oreo and Pie seem to be too recent to have perfect functionalities seeing that S6 is way outdated today. So seeing Pie ROMS work seems, for now at least, a bit more dreamy than reality. Nougat has passed pretty much all possible tests and seeing most of them being abandonned by their authors, I think that most problems may have been resolved and that other issues which may raise are probably corrected with Oreo and Pie ROMs. But again, I do not use cellular lines as I use voip through wifi connections so I cannot suggest anything more than my experience as a computer technician concerning roms and softwares installed on old systems. We are now at the S10 phone, 4 versions higher with Pie starting to be the default system sold on recent phones.
My experience so far with OdexLite without cellular data: I have nothing but good to say. I've had no camera issues, no sound issues, no wifi issues and no problems installing anything I wanted. Up to now, it's the best and most stable ROM I've installed after XtreStoLite. Of course there are small things that I liked in Pie like theme changes and some keyboard changes but nothing compared to how fluid and stable the system is compared to Oreo and Pie ROMs I had tested.
And I am not bothered by any messages. Thank you for your usefull comment.
green3water5 said:
That's why I chose to use OdexLite which is a Nougat based ROM. Oreo and Pie seem to be too recent to have perfect functionalities seeing that S6 is way outdated today. So seeing Pie ROMS work seems, for now at least, a bit more dreamy than reality. Nougat has passed pretty much all possible tests and seeing most of them being abandonned by their authors, I think that most problems may have been resolved and that other issues which may raise are probably corrected with Oreo and Pie ROMs. But again, I do not use cellular lines as I use voip through wifi connections so I cannot suggest anything more than my experience as a computer technician concerning roms and softwares installed on old systems. We are now at the S10 phone, 4 versions higher with Pie starting to be the default system sold on recent phones.
My experience so far with OdexLite without cellular data: I have nothing but good to say. I've had no camera issues, no sound issues, no wifi issues and no problems installing anything I wanted. Up to now, it's the best and most stable ROM I've installed after XtreStoLite. Of course there are small things that I liked in Pie like theme changes and some keyboard changes but nothing compared to how fluid and stable the system is compared to Oreo and Pie ROMs I had tested.
And I am not bothered by any messages. Thank you for your usefull comment.
Click to expand...
Click to collapse
I was not able to install OdexLite, it always bootloop, but I was able to install Ultimate Nougat and I can confirm that it's the first ROM that mobile data works. So what I deduct is that Canadian providers locked mobile data (LTE) to Android 7 (Nougat) for SM-G920W8. I can't remember where I read that before, but it's not the first time I see that people had to update in order to get mobile data for it to work.
Sadness...
@coolmat Thank you for this very usefull comment. Even though I do not really understand why you get a bootloop with OdexLite, you still managed to get a Nougat ROM to work. If this resolved your issue for LTE network, I glad that Ultimate Nougat worked for you. And I think we just need to be patient and wait until there is more serious work for Pie ROMs until someone finds out how to resolve the network and other issues we have.
Added Ultimate Nougat in the list of Tested Nougat ROMs. Thanks to @coolmat for this little info. Tried the installation another time and rom worked.
**EDIT: I'm editing this because some people might not scroll more... Don't install this ROM. As green3water5 stated (below) it is in beta and after further testing, there's a big issue where rebooting kills it.
Guys, I just found the BEST ROM for the SM-G925W8! It's Android PIE and mobile data WORKS REALLY WELL!!!. (When you install, install the "US Variant")
This ROM is faster than all the other PIE, OREO, NOUGAT, and STOCK! It's faster than my S8 lol.
**MiUi camera, don't use stock
The ROM is also for the Note 5 and other S6 variants, hence 2GB size.
https://forum.xda-developers.com/note5/development/rom-floyd-n7fe-port-v1-0-t3882804
JeffYou said:
Guys, I just found the BEST ROM for the SM-G925W8! It's Android PIE and mobile data WORKS REALLY WELL!!!. (When you install, install the "US Variant")
This ROM is faster than all the other PIE, OREO, NOUGAT, and STOCK! It's faster than my S8 lol. This ROM gets an A+ (or as we Ontarians say "level 4+")
**MiUi camera, don't use stock
The ROM is also for the Note 5 and other S6 variants, hence 2GB size.
https://forum.xda-developers.com/note5/development/rom-floyd-n7fe-port-v1-0-t3882804
Click to expand...
Click to collapse
It states that the ROM is under Beta. Did you compare the sound recording of tha camera compared to the other ROMS I listed. Does the camera work flawlessly with Facebook Messenger and other apps asking for camera?
green3water5 said:
It states that the ROM is under Beta. Did you compare the sound recording of tha camera compared to the other ROMS I listed. Does the camera work flawlessly with Facebook Messenger and other apps asking for camera?
Click to expand...
Click to collapse
Sorry, my bad. Don't install the ROM. I used it all night and it worked great but if you boot it the second time, it will shutdown/reboot right after booting into the OS ( kind-of like a bootloop(?) ).
Did not work on SM-G920W8...
coolmat said:
I was not able to install OdexLite, it always bootloop, but I was able to install Ultimate Nougat and I can confirm that it's the first ROM that mobile data works. So what I deduct is that Canadian providers locked mobile data (LTE) to Android 7 (Nougat) for SM-G920W8. I can't remember where I read that before, but it's not the first time I see that people had to update in order to get mobile data for it to work.
Sadness...
Click to expand...
Click to collapse
Same here...