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).
Related
I want to know if there is any ROM for my Galaxy Tab 4 7 Inch (SM-T230NU)?
just test if reply is working.. because i wroth you a big tutorial and i submited get a frustation error msg
---------- Post added at 02:29 AM ---------- Previous post was at 02:02 AM ----------
iSuperAwesome said:
I want to know if there is any ROM for my Galaxy Tab 4 7 Inch (SM-T230NU)?
Click to expand...
Click to collapse
Sorry to not get this Tutorial as elaborated as I wroth before but I get flustered by getting a error when submit
-----------------------------------------------------------------------------------------------------------------------------------------
I use a windows software call SamFirm do download VERY FAST the lastest original firmware from Samsung servers.
Link: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Note 1: You need to specify the “Region/Country” of the Firmware. For that, you can look at some sites that have the same Firmware (Links below). But don’t download from this sites, because is VERY SLOW.
http://samsung-updates.com/device/?id=SM-T230NU
http://www.sammobile.com/firmwares/database/SM-T230NU/
http://www.androidayos.com/galaxy-tab-4-stock-firmware/
http://forum.xda-developers.com/tab-4/general/links-stock-galaxy-tab-4-firmware-t3013128
Note 2: The region “BNN” is for the Samsung galaxy Tab 4 7.0 Nook Edition
How to use SamFirm:
1 - Model = SM-T230NU <-----------------(Ex: Samsung Galaxy Tab 4 Nook 7.0" = SM-T230NU)
2 - Region = BNN <------------------------(Ex: “BNN” for Nook Edition)
3 - Auto = ON
4 - Click "Check Updates", if firmware for the particular region exist you see a msg in Log Window below
5 - Check CRC32 = ON <--------------------- Check is the file is intact
6 - Decrypt automatically = ON <----------- Decrypt file after download
7 - Click "Download” and choose the destination folder
8 – Extract the .md5 using 7-Zip (Nota: WinRAR get error sometimes)
9 – Done, now you can use Odin3 to upgrade you firmware
Cheers
iSuperAwesome said:
I want to know if there is any ROM for my Galaxy Tab 4 7 Inch (SM-T230NU)?
Click to expand...
Click to collapse
It sounds like you were asking about custom ROMs, as opposed to keeping official firmware up to date which is what BXA is talking about. For the record, instead of installing an extra app just to keep up to date on official firmware releases, you can always check my threads which I keep up to date on official firmware releases for all Tab 4 variants:
--Official Tab 4 KitKat Firmware thread
--Official Tab 4 Lollipop Firmware Thread
Assuming you were inquiring about custom ROMs, below is a list of the most popular and/or well-maintained ROMs that will work for your device (pro-tip, even if the ROM says it's only for the SM-T230, it will work on your device, but you probably will lose IR blaster functionality). Before you ask, there are no viable CyanogenMod-based or even AOSP-based ROMs for this device (or SM-T230). They tried to get CyanogenMod working for your device, but as of right now the available builds either don't boot entirely or boot but have bugs like Wi-Fi not working. I'll link to the thread with the relevant info and downloads, but don't expect much, certainly nothing stable enough for daily use. The list I promised you:
--Acheron ROM (well maintained, popular, great dev to interact with, and even though I don't own your device, my recommended starting point)
--Prism Barebones (unfortunately apparently no-longer maintained, but still a solid, popular ROM by a well-respected dev, a legit alternative to Acheron)
--TranchidaKat (seemed to be gaining in popularity, unfortunately the dev recently took a break from maintenance)
--T230 Smooth ROM (I don't really know much about this ROM, but from what I can tell it seems/seemed reasonably popular)
There are a couple more ROMs I feel reluctant even mentioning, and can't really recommend with any sort of confidence. The first had an OK dev (seemed to be in the up and coming, eager to learn but not experienced stage of being a ROM developer): Octagon ROM
The next ROMs I'm going to mention I can't recommend in good confidence not just they're now slightly out of date, but because they seemed to have a few bugs, but more so the developer doesn't do much to instill my confidence in their knowledge base when it comes to developing ROMs for android. Also they're not really custom ROMs more than they're just the stock ROM with themes and skins applied, as opposed to any real under-the-hood performance improvements: Everything Google ROM; the previous ROM with a Marshmallow skin; and Android 5.0 Lollipop Material Design -{theme}-
Finally the CyanogenMod thread I mentioned, even though as I said, you will be disappointed if you insist on downloading anything to try it out: http://forum.xda-developers.com/tab-4/general/dev-cm12-1-t230-nu-development-thread-t3190971
One last thing before I go, in case you haven't found the custom recovery you need, you have three (although the first two are more recommended) choices: an older version of TWRP which I can guarantee will work: http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
Or a newer version of TWRP which should work for your device but I cannot personally guarantee that (click the link that says twrp-3.0.0.0-degas-160207-0212): http://forum.xda-developers.com/tab-4/development/recovery-twrp-2-8-1-0-samsung-galaxy-t2922795
Regarding that newer TWRP, I'm pretty sure I've seen posts confirming it works for your device but I can't recall for sure and I personally installed the first (older version) on a friend's SM-T230NU, so your call. If you have a strong personal preference for CWM as opposed to TWRP, you can try the following recovery, but it's not actively maintained any longer, so be warned. Although to be fair, it works fine as far as I can tell, so again your call: http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094
thisisapoorusernamechoice said:
It sounds like you were asking about custom ROMs, as opposed to keeping official firmware up to date which is what BXA is talking about. For the record, instead of installing an extra app just to keep up to date on official firmware releases, you can always check my threads which I keep up to date on official firmware releases for all Tab 4 variants:
--Official Tab 4 KitKat Firmware thread
--Official Tab 4 Lollipop Firmware Thread
Assuming you were inquiring about custom ROMs, below is a list of the most popular and/or well-maintained ROMs that will work for your device (pro-tip, even if the ROM says it's only for the SM-T230, it will work on your device, but you probably will lose IR blaster functionality). Before you ask, there are no viable CyanogenMod-based or even AOSP-based ROMs for this device (or SM-T230). They tried to get CyanogenMod working for your device, but as of right now the available builds either don't boot entirely or boot but have bugs like Wi-Fi not working. I'll link to the thread with the relevant info and downloads, but don't expect much, certainly nothing stable enough for daily use. The list I promised you:
--Acheron ROM (well maintained, popular, great dev to interact with, and even though I don't own your device, my recommended starting point)
--Prism Barebones (unfortunately apparently no-longer maintained, but still a solid, popular ROM by a well-respected dev, a legit alternative to Acheron)
--TranchidaKat (seemed to be gaining in popularity, unfortunately the dev recently took a break from maintenance)
--T230 Smooth ROM (I don't really know much about this ROM, but from what I can tell it seems/seemed reasonably popular)
There are a couple more ROMs I feel reluctant even mentioning, and can't really recommend with any sort of confidence. The first had an OK dev (seemed to be in the up and coming, eager to learn but not experienced stage of being a ROM developer): Octagon ROM
The next ROMs I'm going to mention I can't recommend in good confidence not just they're now slightly out of date, but because they seemed to have a few bugs, but more so the developer doesn't do much to instill my confidence in their knowledge base when it comes to developing ROMs for android. Also they're not really custom ROMs more than they're just the stock ROM with themes and skins applied, as opposed to any real under-the-hood performance improvements: Everything Google ROM; the previous ROM with a Marshmallow skin; and Android 5.0 Lollipop Material Design -{theme}-
Finally the CyanogenMod thread I mentioned, even though as I said, you will be disappointed if you insist on downloading anything to try it out: http://forum.xda-developers.com/tab-4/general/dev-cm12-1-t230-nu-development-thread-t3190971
One last thing before I go, in case you haven't found the custom recovery you need, you have three (although the first two are more recommended) choices: an older version of TWRP which I can guarantee will work: http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
Or a newer version of TWRP which should work for your device but I cannot personally guarantee that (click the link that says twrp-3.0.0.0-degas-160207-0212): http://forum.xda-developers.com/tab-4/development/recovery-twrp-2-8-1-0-samsung-galaxy-t2922795
Regarding that newer TWRP, I'm pretty sure I've seen posts confirming it works for your device but I can't recall for sure and I personally installed the first (older version) on a friend's SM-T230NU, so your call. If you have a strong personal preference for CWM as opposed to TWRP, you can try the following recovery, but it's not actively maintained any longer, so be warned. Although to be fair, it works fine as far as I can tell, so again your call: http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094
Click to expand...
Click to collapse
Many thanks for the tips
Btw, your links are great.. and can be downloaded VERY FAST
have a nice day
MOD EDIT by @gregbradley. I did not see the need for the expletive in the title, so i took it out for you.
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost
Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?
MasterCMTS said:
Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?
Click to expand...
Click to collapse
My issue?
On one hand Sony releases AOSP code, while on the other hand they make it a real damn pain in the ass to even run an AOSP rom. There have been several developers out there to try and build an AOSP rom. None of them managed to make a fully working one, because Sony made it so damn hard. I find this hypocritical and unjust.
What I want is for Sony to make it actually possible to run an AOSP rom, and stop pretenting like it's possible.
Me Gusta said:
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost
Click to expand...
Click to collapse
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.
savo83 said:
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.
Click to expand...
Click to collapse
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Me Gusta said:
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!
Click to expand...
Click to collapse
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
Me Gusta said:
- There's a possibility of losing your DRM Keys when unlocking bootloader.
Click to expand...
Click to collapse
That is true and disappointing. However, there is a way to backup the keys and restore whenever the need arises.
Me Gusta said:
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
Click to expand...
Click to collapse
fastboot oem lock or restoring the DRM keys should relock the bootloader.
Me Gusta said:
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
Click to expand...
Click to collapse
Sure it works, you just need to run 23.4.A.1.264 firmware or newer. I use fastboot flash recovery something.img all the time.
Me Gusta said:
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Click to expand...
Click to collapse
I think the Concept software is for those who don't need Sony enhancements (X-Reality, ClearAudio+, etc.) and want something that is close to stock.
So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
Evokkimus said:
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
Click to expand...
Click to collapse
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
I was eager to try out FXP's aosp ROM, due to 3.10 kernel and such, but I got an error about updater-script in META-INF, didn't read further. I have my suspicions that it was a bad download, but their current site is so slow to download from (about 2 hours to download, and only a +20kb/s faster if you register), and i'm not going to pay for that site. If it helps any, i just wiped data, system and caches and tried flashing the ROM.
---------- Post added at 12:14 PM ---------- Previous post was at 11:56 AM ----------
CedArctic said:
So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
Click to expand...
Click to collapse
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
Evokkimus said:
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
Click to expand...
Click to collapse
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)
nailyk said:
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)
Click to expand...
Click to collapse
Basically the error I get is with extract-files.sh. When I run "./extract-files.sh" while phone is plugged in, I get permission denied. The other option for me is to run it with sudo, but then I get "line XX adb: command not found" (many lines of this error). Someone suggested chmod or opening a terminal window inside the folder where extract-files.sh is located. There shouldn't be any errors with my AndroidSDK path, even though some suggest the error is with this.
Also the reason I'm trying to pull these blobs, is because the CM tutorial told me so
{
"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"
}
https://wiki.cyanogenmod.org/w/Build_for_z3
------------------------------------------------------------
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
Evokkimus said:
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
Click to expand...
Click to collapse
No worries.
So it may be a little more complicated.... If you just need a functional self build CM, try to include themuppet repo. If your device variant is not currently officially supported it can be more complicated.
I suggest you to open (or find) a dedicated thread and quote me, or join #[email protected]
Otherwise I'm following this thread because I found some point really interesting. I'm currently in trouble with Sony, that's why I subscribe.
Sorry for off-topic answers.
sorry did not see the date
arminbih said:
sorry did not see the date
Click to expand...
Click to collapse
Customer service troubles. They didn't respect law about unlocked bootloader into my country and refused to fix my device.
I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:
The Android Robot said:
I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:
Click to expand...
Click to collapse
Lots of OEM are doing this stuffs to protect their intellectuals rights with DRMs. AFAIK oneplus allow bootloaders unlock.
Just for fun, the TA partition of sony contain so much things... It is crazy! BTW I think we have fuse too
idk where you live but in Europe there is a law which basically said: hardware and software are separated and OEM need to fix hardware, except if they can prove this is user fault.
1999/44/CE in date of 1999-05-31.
Considering modifying stock HTC 10 with Lineage. I don’t use Google. Unfortunately that’s tied to Pay by phone. The only feature I miss. Other than that what benefits do people find going through the root/install Lineage option? Sprint makes it difficult due to firmware, but I can deal with that if there are enough payoffs. Reasons to install Lineage these days?
I love using LOS and it is the pinacle of ROMs for any phone. For Sprint and HTC there are a few different options that you can use with this phone. However if you are new to phone modding and rom flashing, I would approach this topic gently and start with something more fundamental. OMJ makes great stock roms for your phone that you may want to try flashing first just to learn. Moving to lineage os will take quite a bit more knowledge and practice with ROM flashing and phone modding. You will have to have sunshine first of all and you will have to have modded your firmware to go straight to LOS. If you are comfortable with those things, LOS 15.0 for example will take the stock rom size of 3.2gb down to about 450mb for a bare bones aosp stock rom. I love LOS and it is where I want to be with my devices for unbloated roms without any bloat. They are fast, snappy, have great battery life, unlocked tether, and you will reap the benefits of having a bloat free rooted and unlocked device without all that sprint spamware. Using a tool like magisk or xda on a pure android phone unlocks tremendous potential and many options for your device like audio engine mods, theming, gps spoofing, the options are limitless. Let me know if you have any specific questions and I will do my best to help.
Well, I'm not new to flashing ROMs. Would i still be able to use Pay? I realize i'd need a slim version of Gapps. This is the only feature i'd like to keep. I don't use it, have used it and it's quite useful in case i lose my wallet. Know what i mean?
I mean, i've done quite well without Google. Here's my apps...without ever logging into a G sccount.
Well, I've taken the first steps. Unlocked bootloader, Installed TWRP and rooted. Seems phone makers have made ROM installs more complicated these days. What's a good source for getting around the firmware issue on these sprint phones when installing Lineage? Is there a good solid tutorial? I mean, the Lineage OS site is good, but points out the firmware issue and says to search XDA. I can't seem to find a simple tutorial on that aspect. Thx.
Oh, also... I'm no longer on Sprint with this phone. I've had them unlock the sim and I'm on Simple Mobile. Does that make a difference? Is this still considered a Sprint phone as far as flashing goes?
OK, I installed Lineage OS. Weird that Oreo version isn't available. Anyhow. Everything seems to work fine except home button/Reader. Not a deal breaker as onscreen buttons work fine. Is this because I'm on different firmware? I'm on stock Oreo firmware?
Great to hear that your making progress with no hiccups. I'm just patiently waiting for the Pi update for lineage on this device. Now if you want root, you can flash magisk and even start playing around with substratum to do some theming!
Thanks. Does your home button/reader work?
I guess the issue could have been avoided if I'd RUU'd back to N before installing Lineage. Are there any other issues I might have? If not, I can live with onscreen buttons and wait patiently for Lineage on Oreo update.
Well, that didn't last long. I was getting the dreaded password upon entering recovery. When backing up I noticed could not mount data. So I've taken the plunge and installed unofficial lineage for 8.0. Seems okay. Got my home button and fingerprint reader back.
KEB64 said:
Well, that didn't last long. I was getting the dreaded password upon entering recovery. When backing up I noticed could not mount data. So I've taken the plunge and installed unofficial lineage for 8.0. Seems okay. Got my home button and fingerprint reader back.
Click to expand...
Click to collapse
At least it keeps you off the streets!
:laugh:
Hahaha
Well, I'm back on Official 14.1
I need my speakers and there are too many crashes for me to use 15.1 as a daily. I do understand that 15.1 is not even beta yet. That guy has obviously done quite a bit of work. Nice to see the HTC 10 has not been forgotten.
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...
What exactly is the benefits of unlocking the bootloader and rooting the YB1-X90L?
There aren't any custom roms that work with it, and from I can tell you can't uninstall any of the junk apps either.
Installing windows 10 on the android version is useless since not everything works (probably because of the bios being different between the two versions)
I already know that the source code is available, but the Stock Rom for Nougat (as far as I can tell) is not available. So there is no way to start developing a custom rom without having lots of experience with that.
So what's the point of going through all that trouble (which actually isn't that much effort I know)? The modding community for this device is completely dead from what I can see. Which kinda sucks since this tablet would be amazing if it could be loaded up with a custom rom. It's specs are far from low end, and seems to offer some really nice performance.
I really want to pick one of these up it's gonna be possible to mess around with custom ROM's....
There is no point buying this device anymore. I was pretty much hyped of because it really is a nice tablet. But for some reasons unknown it failed at XDA. I have mine Rooted, just to remove câncer apps and adware.