I understand that the thread title seems like I am being a complete noob (although to be fair, I am).
My journey with this S6 Edge thus far:
I have a Canadian variant (G925W8) and managed to soft brick it through sheer idiocy. I then learned a ton of stuff from you guys here on the forums. My intent is to get this phone running in as close to stock form as possible, however the bloatware apps are not needed. I eventually got one thing working and then the next and currently the phone has XtreStoLite 3.3.1 Marshmallow Rom installed (found here: http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968)
I went after the Marshmallow install using the files indicated in that thread. So I have a Marshmallow bootloader, modem etc.
So now I can get into why my title is so strange. When I booted into the phone (which, for the most part, is working alright) I went to enable developer options again and noticed that my model number indicated in the phone is now a G925F. During the install of the custom rom, I made sure to select all options to indicate that my phone was a W8 variant and yet this is what the phone is reporting back to me.
The reason I have this question is because I am looking to get rid of the custom rom, for the aforementioned 'mostly working' comment, and go full stock firmware. Would I be able to find an F variant stock firmware and load that straight on? If yes, do I also need to switch over the bootloader and modem files to an F variant as those are probably hardware based? Which model number matters more? How much is the firmware version reliant on the hardware model number?
In the meantime I will tinker with the Aroma add-ons to get all the functionality the way I want it.
Thanks for any replies on this matter.
Related
Currently running ICS via XXLPH on a GT-I9100P. Unfortunately, that version doesn't include NFC support, which annoys me, since I paid extra for a phone with NFC hardware.
My question is - I see via the sammobile page that there is a firmware update for my phone more recent than what I have, albeit one with a different PDA to my current one (I9100XXLPH vs I9100PBVLP8).
What exactly does this mean? Does this mean it's simply different software, but still designed to run on the same hardware? If so, it should be compatible with my phone, no? Or are there other things I should be checking for compatibility?
(Also - would that update even help with NFC?)
I recognize that ultimately whatever I do when screwing around is on me. And I realize that flashing a different official ROM is pretty tame compared to all the unofficial ROMs here (though most of them don't seem designed for the P version of the SGS2). But I'd rather not brick my phone at the moment.
Note - this is not a phone I got from a carrier, and I rooted it, so waiting for OTA upgrades is not an option.
Faqa42 said:
Currently running ICS via XXLPH on a GT-I9100P. Unfortunately, that version doesn't include NFC support, which annoys me, since I paid extra for a phone with NFC hardware.
My question is - I see via the sammobile page that there is a firmware update for my phone more recent than what I have, albeit one with a different PDA to my current one (I9100XXLPH vs I9100PBVLP8).
What exactly does this mean? Does this mean it's simply different software, but still designed to run on the same hardware? If so, it should be compatible with my phone, no? Or are there other things I should be checking for compatibility?
(Also - would that update even help with NFC?)
I recognize that ultimately whatever I do when screwing around is on me. And I realize that flashing a different official ROM is pretty tame compared to all the unofficial ROMs here (though most of them don't seem designed for the P version of the SGS2). But I'd rather not brick my phone at the moment.
Note - this is not a phone I got from a carrier, and I rooted it, so waiting for OTA upgrades is not an option.
Click to expand...
Click to collapse
make a bkp of ur exsisting rom and then flash the I9100PBVLP8 and see for the NFC issue if it resolves u can keep it else restore the original one back
since pda is the modem if its diff no issue u can always change the same if its not wrk'ng properly for u
Thank you. So all I should care about in ROM flashing is the underlying hardware? PDA and CSC differences should not brick my phone?
You may want to check this out it should add NFC to any rom.
http://forum.xda-developers.com/showthread.php?t=1407808
First of all this is my first post. Hello to everyone. I have been searching/reading thru these forums. Great source of info.
Phone info:
Currently S-OFF, unlocked, lateset AT&T 4.4.2 firmware, viperone 6.2.1, twrp
I have a pretty good comprehension of how to install or revert pretty much anything that can be done to this phone and have done so with great success. What I don't understand is the relationship between the firmware base of an RUU and the build of any given ROM. How is it that a custom Rom based off let's say x.xx.401.x work with x.xx.502.x main version? The devs say to update to the most current available firmware. Does that mean I have to flash a firmware base that matches what the Rom base for optimal performance? Because I originally thought that was the case and when I did my phone developed syncing issues particularly with the stock mail and weather apps. They would only sync over WiFi. Everything else about the phone worked as normal. Believing there was a problem with the Rom I flashed a few different popular roms on here. Always returning to full AT&T stock first. I later fully converted to GPE and to my surprise everything worked as normal. So I then converted to stock developer edition by way of zip flash and RUU exe. (By the way, when I say stock I mean s-off & unlocked but otherwise factory.) Received all the ota's. Main version would show as x.xx.1540.x. supposedly this would make my phone a dev edition with AT&T as the provider. And yet the syncing problems returned. So once again I returned back to factory AT&T 4.4.2 and all returned to normal. I then decided to try and use a Rom based off 4.4.2 and not one from 4.4.3; expecting the syncing issues to return only this time they didn't. So now I am really confused.
My questions are:
If coming from 4.4.2 factory firmware, is it best to run a Rom from the same base or am I doing something wrong and I should be able to use a Rom from a newer base on an older firmware?
If the developer edition and GPE can be carried by AT&T then why was I having syncing issues with the developer edition and not GPE?
I thought by being s-off I should be able to flash any RUU from any carrier without problems, just that I would be limited to the network capabilities of the actual service provider.
Everything I know about this stuff I learned from this forum. But I think I missed something.
My AT&T M7 always works best on the stock software.
The only thing I could figure is that AT&T have refined the software and radio so well that all the other versions pale in comparison.
I noticed the Developers Edition always had a horrible Bluetooth and WiFi radio. Signal strength was always weak compared to the stock AT&T software.
To answer your questions
Flash any version Roms you want on the latest AT&T firmware. And you'll have the best your phone can be.
clsA said:
My AT&T M7 always works best on the stock software.
The only thing I could figure is that AT&T have refined the software and radio so well that all the other versions pale in comparison.
I noticed the Developers Edition always had a horrible Bluetooth and WiFi radio. Signal strength was always weak compared to the stock AT&T software.
To answer your questions
Flash any version Roms you want on the latest AT&T firmware. And you'll have the best your phone can be.
Click to expand...
Click to collapse
I get so mixed up with all the terms being used interchangeably. So to clarify, as long as I am using the latest firmware from AT&T (currently 5.12.502.2 kk4.4.2), I can flash any custom ROM base. Whether it is based on 4.4.2 or higher. Correct?
I still want to know why I experienced the sync problems while running the factory x.xx.1540.x dev edition but not with the GPE. I never tried the factory x.xx.401.x WWE firmware either. However, I just got an sim unlock code from AT&T earlier today. I'm gonna try that maybe tomorrow and see if it makes a difference altho I don't believe it should. And I'm not gonna switch to a different provider.
Honestly, I was happy with my phone before I got wrapped up in all of this. I just decided to tinker with the phone and the mod bug has bitten.
ANGRY_robert said:
I get so mixed up with all the terms being used interchangeably. So to clarify, as long as I am using the latest firmware from AT&T (currently 5.12.502.2 kk4.4.2), I can flash any custom ROM base. Whether it is based on 4.4.2 or higher. Correct?
I still want to know why I experienced the sync problems while running the factory x.xx.1540.x dev edition but not with the GPE. I never tried the factory x.xx.401.x WWE firmware either. However, I just got an sim unlock code from AT&T earlier today. I'm gonna try that maybe tomorrow and see if it makes a difference altho I don't believe it should. And I'm not gonna switch to a different provider.
Honestly, I was happy with my phone before I got wrapped up in all of this. I just decided to tinker with the phone and the mod bug has bitten.
Click to expand...
Click to collapse
I think I figured this out. I continued to flash different ROMs and firmwares with the same results as I posted in the OP. Then earlier tonight I decided to try to convert to developer edition again (x.xx.1540.x) and flashed an ruu.zip, went thru the setup process, and as before the same issues returned. Then I had an idea; lets try something I haven't done yet. I pulled the SD card and factory reset the phone. After I completed the basic setup process I inserted the SD card and let the phone do its thing. The phone now works as it should (same as it does with the AT&T xx.502.x firmware installed).
Just figured I would pass this along.
Cheers
I give up
I thought I had this figured out. Last night after to converting to dev edition with all updates, everything seemed normal. I flashed the latest viperone rom as it is the rom I want. Turn the phone on this morning and the sync problems are present once again. I have searched thru a tom of pages on this sight alone. I cant find an answer. So its back to stock at&t.
I solved the problem. Incorrect settings in 4636 menu.
I am fairly new to the whole ROM thing on this device. I have experience with older phones and am just getting back into this recently. That being said...
Current state is: Bootloader unlocked, currently running stock 4.4.4, Sense 6.0, Kernel 3.4.0-g931e842, Build 3.42.502.1 CL441323; ROM applied via RUU. (RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2)
Bottom line is that since I have attempted to root and flash ROMs I have had issues with making and/or receiving calls, or no SIM recognized at all, requiring S-off/firmware upgrades, etc.
I am looking for a stable build ROM which is compatible with the 4.4.4 firmware on my device which can be applied without obtaining s-off. Main goal is to be able to personalize the UI and to run a faster, debloated ROM.
Tried first using Renovate 5.0... could not receive calls on that one.
Removed. back to stock.
Next I found a Lollipop 5.0.1 ROM (HTC_One_M8_Lollipop_5.0.1LRX22C) which did not appear to require firmware updates... seemed to work great... except that I could not receive calls...
Removed... back to stock.
Next, I used ViperOneM8 and really liked it, but had to abandon once I was told by people that they were still getting sent straight to voice mail.
I did get some calls, so I tested having some people call me and it seemed fine... well turned out that during those tests I was on the 3G network... Once again, troubleshot down to the fact that anytime I was on 4G network I could not receive calls. Having had no way to change my network selection in this ROM (error was displayed when I attempted this). Contacted their support to confirm my issue. They are aware, no resolution available.
Removed... back to stock.
So my question is, are there any options OTHER THAN paying $25 to use Sunshine to get S-off, upgrade firmware? I am not a developer and I love my M8. I know there are people here who know exactly what I need and understand what I am looking for. Thanks in advance for any assistance.
GA_Android said:
Next I found a Lollipop 5.0.1 ROM (HTC_One_M8_Lollipop_5.0.1LRX22C) which did not appear to require firmware updates... seemed to work great... except that I could not receive calls...
Removed... back to stock.
Click to expand...
Click to collapse
I can't tell what ROM your are talking about based on that description. Possibly GPE stock rooted?
What I can tell you, is that most any Lollipop Sense ROM will have issues when used alongside 4.4.4 firmware.
Sense 4.4.4 ROMs will play well with your firmware, as will a number of 4.4.4 and 5.0 GPE and AOSP ROMs (that specifically state they support 4.4.4 firmware). However, when it comes to AT&T, there is more at play then whether the ROM corresponds to the firmware. That other complication is that AT&T does some annoyingly unique things with their network. In the past, this has included changes to build.prop and even the signal icons, which sometimes caused "international" custom ROMs to have some issues. And now you see that their HD Voice (Voice over LTE) is messing with some custom ROMs. As the other thread you posted in mentioned "blame AT&T".
Running an AT&T base 4.4.4 ROM is your best bet for trouble-free use on AT&T's network. WNC's ROM might fit the bill for what you want (debloated) and is often where I send folks that want a bug-free experience on AT&T (while retaining some AT&T specific features). The 3.28 version ROM is what you should try: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
There are other ROMs that might work for you. But the above is my suggestion, at least as a start.
redpoint73 said:
I can't tell what ROM your are talking about based on that description. Possibly GPE stock rooted?
What I can tell you, is that most any Lollipop Sense ROM will have issues when used alongside 4.4.4 firmware.
Sense 4.4.4 ROMs will play well with your firmware, as will a number of 4.4.4 and 5.0 GPE and AOSP ROMs (that specifically state they support 4.4.4 firmware). However, when it comes to AT&T, there is more at play then whether the ROM corresponds to the firmware. That other complication is that AT&T does some annoyingly unique things with their network. In the past, this has included changes to build.prop and even the signal icons, which sometimes caused "international" custom ROMs to have some issues. And now you see that their HD Voice (Voice over LTE) is messing with some custom ROMs. As the other thread you posted in mentioned "blame AT&T".
Running an AT&T base 4.4.4 ROM is your best bet for trouble-free use on AT&T's network. WNC's ROM might fit the bill for what you want (debloated) and is often where I send folks that want a bug-free experience on AT&T (while retaining some AT&T specific features). The 3.28 version ROM is what you should try: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
There are other ROMs that might work for you. But the above is my suggestion, at least as a start.
Click to expand...
Click to collapse
You are correct. It is a GPE stock rooted Lollipop ROM. It works just fine as long as I have 3G selected as my network, but it is just not as much flash as I wanted.
I am going to give the one you sited here a look and maybe give it a try. I appreciate your taking the time to reply. It was helpful and informative.
Erring on the Side of Caution
I'm in a similar quandry as the OP. I have lots of experience flashing ROMS on my older phones but trying to keep up with all the changes since getting my M8 has me confused.
Here's my current setup. I'm running Skydragon after trying the last 4.4 milestone of Liquidsmooth. I like both, but am interested in keeping up with the Lollipop guild.
I have Sunshine installed but when I ran it I found out I need to remove or disable Xposed Installer to continue. I'll deal with that by disabling it.
UPDATE: Well, that didn't work. Xposed was installed with the ROM and there's no option to uninstall it.
My biggest concern is updating the firmware. From my bootloader info, I'm assuming that I'm way behind on the latest firmware, but after reading so many threads about updating, my head is swimming.
If I need to update, I just want to make sure that I don't brick my phone.
CanuckinPA said:
I have Sunshine installed but when I ran it I found out I need to remove or disable Xposed Installer to continue. I'll deal with that by disabling it.
UPDATE: Well, that didn't work. Xposed was installed with the ROM and there's no option to uninstall it.
Click to expand...
Click to collapse
Return to stock ROM and stock recovery, for optimal configuration for sunshine to work. RUU is probably the easiest way to get back to stock. Backup your personal data, than relock bootloader to run RUU.
CanuckinPA said:
My biggest concern is updating the firmware. From my bootloader info, I'm assuming that I'm way behind on the latest firmware, but after reading so many threads about updating, my head is swimming.
Click to expand...
Click to collapse
Yes, based on your hboot number, your firmware is about as old as it gets (Android 4.4.2).
You can RUU to 4.4.4 firmware without s-off; and Lollipop Skydragon GPE should work fine with 4.4.4 firmware.
You can of course still s-off and update to Lollipop firmware. But you need to use some other firmware besides AT&T (such as Dev Edition, Euro, etc.), since they haven't released a Lollipop update (and therefore no firmware).
I ended up with a Verizon S4 through eBay (for a good price at least), and have managed to get on 5.0.1 and root it (via the PC version of Kingroot). Being that it's the OC1 baseband version, my options seem to be quite - no, very limited, when it comes to flashing non-touchwiz based ROMs. Is there any conceivable way I can get a custom recovery on here that will allow me to flash AOSP ROMs? I can wait, it doesn't have to be right now... I just need to know if my particular S4 is permanently crippled in this regard, or if it's just a matter of waiting until someone cracks it. Ideally I'd like to have an unofficial Android M ROM on here when the time comes. What are my options?
Also, I just came from the development sub forum (I can't comment there yet) and saw a new 5.1.1 ROM (Gamer Rom?) that claims to work for the Verizon S4. I'm skeptical that it wouldn't actually brick my device so I wanted to check of anyone else here has found a way to flash it. As far as I know, we can't even flash CWM so I just wanted to double check of I was missing anything obvious. Cheers
First I'd describe myself as a PC power user, but android Noob, I have no issues with actually doing things, and find the instructions provided, are all I need
My only previous android knowledge was Rooting and installing Custom ROM on a standard S3 Mini.
That allowed me full control, to remove 95% of the apps, (unwanted by me). It was a very easy process and I was happy with all, except screen size.
I'm a PC user, on my high end system 12 to 16 hours a day and know how that environment works, mobile has no great appeal for me. I simply want phone and browser, and apart from a few utilities and a basic notepad, need very little else.
I only use my mobile to read/write on forums like this, mostly concerned with modding PC Games, that's what eats all those hours on PC.
I'm not the typical mobile user, I just want full control of any device I use.
I bought a second hand S5 advertised as Stock and unlocked, which turned out locked to Vodafone, so I demanded it was unlocked. That wasn't possible, (sure it was, but at what price?).
I wasn't paying more for it, than the original price and was offered a brand new unlocked model, but it would be a contract phone unlocked. That for the price of the second hand model, seemed OK.
Then I find it's a T-Mobile and not the standard S5, which makes this process a lot more complicated. I've successfully Rooted the phone, but it's a stock ROM, now I'm looking for a Custom ROM, to allow me full control of the device.
All the T-Mobile/Google/Samsung Bloatware (95% of stock) is still there and uninstallable. A few other strange issues are present. Like Titanium Backup cant Write to my External SD, yet it's writable, FileManagerHD works fine.
So I want a basic custom ROM that gives me full control, I don't need to ask these basic questions on PC, I simply RTFM, but I'm unused to fighting for full control, I didn't even know that custom provider hardware was an issue, before this happened, I need some pointers as to where to look.
Any restrictions that I can't change, pretty basic stuff, but knowing what applies to the model i have, isn't so apparent, and I'm not 100% sure I even know all the specs to check, a link to where to find out is all I need, I can then RTFM and get on with making this device do what I want
The details I know make a difference are these
Current SIM = GiffGaff PAYG (Basic with no mobile data allowed, I will not even enter the required details)
Android version = 5.1.1
Baseband version = G900TUVU1FOG6
Root and StockROM = [ROOT/KERNEL] Root Method for FOG6 / 5.1.1 by ShinySide
Warranty and KNOX already voided, I don't care.
Thanks for reading to here, Let me know if more specs are required.
@Uhuru N'Uru I would highly recommend CyanogenMod 13, specifically, this version: http://forum.xda-developers.com/gal...t/4-4-4-cm11-rom-temaseks-unofficial-t2907450
In case you're confused by all the different S5 variants and development codenames, this device is klte
I just flashed Cyanogenmod 13 a couple days ago on my T-Mobile S5, and I am thrilled with it, so far it is working perfectly after 2 days of very heavy use and I have not found anything wrong with it. I have free wifi tethering now!
I downloaded it from here but I went with the latest tested release (cm-13.0-20151227-UNOFFICIAL-klte.zip), instead of a nightly build:
forum.xda-developers.com/galaxy-s5/unified-development/rom-cyanogenmod-13-0-android-6-0-t3237502
I'm not sure how it is different from the Temasek MM versions... Can someone explain whats the difference?
I spent hours deciding whether to stay with a custom 5.1.1 Lolipop or upgrade to 6.0.1 Marshmallow. I'm extremely happy with MM. My phone is awesome now, I had some bad lagging problems and was annoyed with all of the bloatware on the stock firmware.
Oh yeah and I have FOL1 baseband version. No idea what that means...
jkq1996 said:
I just flashed Cyanogenmod 13 a couple days ago on my T-Mobile S5, and I am thrilled with it, so far it is working perfectly after 2 days of very heavy use and I have not found anything wrong with it. I have free wifi tethering now!
I downloaded it from here but I went with the latest tested release (cm-13.0-20151227-UNOFFICIAL-klte.zip), instead of a nightly build:
forum.xda-developers.com/galaxy-s5/unified-development/rom-cyanogenmod-13-0-android-6-0-t3237502
I'm not sure how it is different from the Temasek MM versions... Can someone explain whats the difference?
I spent hours deciding whether to stay with a custom 5.1.1 Lolipop or upgrade to 6.0.1 Marshmallow. I'm extremely happy with MM. My phone is awesome now, I had some bad lagging problems and was annoyed with all of the bloatware on the stock firmware.
Oh yeah and I have FOL1 baseband version. No idea what that means...
Click to expand...
Click to collapse
Temasek version has more options (mostly but not all theming) in system settings (I also think it has better battery life but that could be me). FOL1 baseband just means you have the most recent modem and bootloader installed on your phone, it's a good thing
Ok actually after more days of heavy use, I have found a couple of things that aren't working right in CM13. GPS doesn't work correctly in Google Maps, and I can't get text suggestions to work (predicting the next word I will type). I guess I should start reading the 6920 posts in the CM13 thread and see if there are fixes...