I just picked up a refurbished Moto E2 (Surnia) for ATT/Cricket, and I rather like it aside from the limited internal storage. Would love to flash a ROM that allows adoptable storage via SD card, but read some things about Nougat roms having issues with bluetooth and other little nagging bugs on some ported devices. Would love to stick with Marshmallow or anything stable enough for a trouble-free experience. I'm not necessarily looking for latest-and-greatest, if this phone shipped with Marshmallow, that'd be good enough for me honestly. Just need to move past Android 5.1 here.
Should I try to dig up an antiquated CM13 rom image? Seems like official links have been pulled in honor of lineage OS. Is LineageOS stable enough? Should I try that first?
Basically you have an AT&T device, which is unauthorized for bootloader unlocking, therefore flashing any custom ROMs is impossible. You're pretty much stuck with stock 5.1 firmware.
Oh well that just stinks. I already had a VZ Moto E2 that I've been using in GSM thanks to the tweaks for that, but was annoyed that I'm stuck on 5.1. Had an opportunity to grab the xt1527 for 99cents refurbished at Cricket, and figured I could replace it with this one and flash Marshmallow.
Fantastic. Now I have two Moto E2's with locked bootloaders.
Wasn't there an official 6.0 ROM that Moto released in markets other than US? Would I be able to flash that on my Xt1527 with a locked bootloader since it is an offically signed ROM, or will it reject?
Short answer, I presume it's not possible to flash the firmware released for a different phone variant, the phone's CID must correspond with its designated firmware.
I'm not 100% sure though, never had a phone with a carrier locked bootloader.
Related
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).
Hi,
I currently have a Samsung Galaxy S4 i545 (Verizon) that has the locked bootloader, and therefore has limited ROMs available. I am considering picking up a used LG G3 and would like to know if there are any "gotchas" to be aware of? Has Verizon & AT&T locked the bootloaders to the G3 as well, or is root and custom recovery a go for all versions?
Appreciate your feedback!
Short answer: You can root and "Bump" the boot-loader;
Longer answer (obviously there is a MUCH longer and complete answer, but this should get you started): Depending on who you talk to, the Boot-loader is quasi/unlocked. You may need to restore an older firmware in order to root and Bump though. I am still not 100% clear on the specifics, but I believe there was a work-around for the boot-loader to get a custom recovery installed - this is the Bump. From there, all kernel's and Rom's need to be "Bumped" in order to flash. Every kernel/ROM I've seen on XDA is already Bumped, so you shouldn't have any issues flashing anything.
Hope that makes sense. For more info on which firmware will allow you to do what, http://forum.xda-developers.com/verizon-lg-g3/general/verizon-lg-g3-one-toolkit-vs985-root-t3124846
In order to be able to install and get into TWRP or any custom recovery, you have to use the 12B (KitKat) bootloader or below (10C KitKat, 11C KitKat). It's easiest to root on 10B with the Stump app. You can downgrade from every official stock version, although from 35B and higher, the only way to downgrade is to flash the 10B TOT file from Windows using the .DLL that's extracted from the 35B KDZ (even if you're downgrading from 46A or 47A).
Rooting gets more complicated after 10B, and putting TWRP on gets more complicated after 12B.
Thanks guys! Since I'd be buying used it would be a crap-shoot which boot-loader I get...but it still seems more promising than my current S4.
I'm in no hurry but I'll start looking for a deal.
mn1968 said:
Thanks guys! Since I'd be buying used it would be a crap-shoot which boot-loader I get...but it still seems more promising than my current S4.
I'm in no hurry but I'll start looking for a deal.
Click to expand...
Click to collapse
You're welcome, good luck!
Just got a refub.ed G3 VS985 off ebay for $109 last week (saw a $99 deal a few days ago). It came with 35B version ... easy to downgraded back to 10B, then rooted (stump apk) , then added TWRP 3.0.0.0 (TWRP apk), then flashed 35B bootstack + stock47A.
Had quite a bit of issues (going back to 10B) due to a corrupted TOT file causing "Failed Previous Load" for LGFlashTool.
@ hyperxguy - So despite your troubles everything worked out OK? Have you flashed any ROMs yet? I'm a bit eager to jump in sooner than later at thought of being able to use different ROMs.
mn1968 said:
@ hyperxguy - So despite your troubles everything worked out OK? Have you flashed any ROMs yet? I'm a bit eager to jump in sooner than later at thought of being able to use different ROMs.
Click to expand...
Click to collapse
It took me awhile to realize the corrupted TOT file was causing the downgrade problem ... otherwise, the process was painless. I'm having no issue with the stock-rooted47A. Will start playing with other ROMs soon.
This G3 is about the same as my old G2, regarding root & ROMs. So I'm feeling pretty comfortable.
Note: I've been using the G4 for the last year ... but it has no root solution ... so I'm getting the G3 just to have some fun (kinda miss my old G2).
Hey fellows, I too am thinking of getting a G3 to replace my S3 that died a while back. I'm using an old moto x2 now. After posting in another thread elsewhere and describing what I'm looking for in a New(used) phone, someone recommended the G3 and after some reading I see that it fits the bill perfectly. (Ext SD, Replaceable battery, 5" or larger display) I had been thinking about a new moto or a note but root and ext sd are a must. I also need a phone with decent reception. My S3 was terrible compared to my old Droid X and X2, and since signal at home is hit or miss (95db/m on my dx2 now) I want a phone that pulls in signal well.
What do those of you who own this phone think about signal / reception compared to other devices?
I think I can get any Verizon version downgraded to install root and TWRP correct?
Without me reading through all the custom rom posts, do all features of the phone work as good or better on a custom rom as on a stock rom? What I'm mean here is for example, on my DX, DX2, and S3, some features do not work on custom roms due to the closed source of the original software / drivers I believe. On the DX and X2 for example the HDMI out port won't work on AOSP roms because the driver isn't available. Performance suffers on AOSP roms on the X2 past GB because of the closed nature of the Nvidia Tegra 2 drivers I think. I think I'm explaining this correctly.
I'm pretty sure that's everything I can find out how to do everything once I acquire the device. The link in the first reply above is most helpful.
Would anyone recommend any other device for the price range between 100-200 US dollars? Again, I've been considering a note, nexus 6 (because I know I'll have beaucoup kernels and roms to choose from)
griz.droidx said:
Hey fellows, I too am thinking of getting a G3 to replace my S3 that died a while back.
Click to expand...
Click to collapse
Hi! I too, came from the S3, albeit the Sprint version. I loved that phone, by the way. I think overall I was most satisfied on the S3 but the G3 definitely has some great specifications in comparison.
What do those of you who own this phone think about signal / reception compared to other devices?
Click to expand...
Click to collapse
I can't comment regarding this. I've moved too many times in the past 6 years and had four different Android phones in that time.
I think I can get any Verizon version downgraded to install root and TWRP correct?
Click to expand...
Click to collapse
Yes. The overall wisest way is to flash the 10B (KitKat) TOT using the .DLL that's extracted from the 35B (Lollipop 5.1.1) KDZ from a Windows PC, then use the Stump app to root it using the brute force method.
Google for:
Code:
XDA Stump
and then use TWRP Manager from the Play Store to install TWRP. Rooting gets more complicated after 10B and installing TWRP gets more complicated after 12B.
To flash a ROM - the order you flash things in matters if you end up dealing with JasmineROM 9.x or SkyDragon 6.x. After flashing either of those two ROMs, flash either the 24B or 35B Bootstack that you can find in @xdabbeb 's VS985 v2.0 ROM thread in the Development section. Depending on which Bootstack you flashed, if you flashed it before flashing either of those two ROMs, you'll brick your phone. Recoverable but no sense doing it if you can avoid it.
I recommend just getting used to flashing the appropriate Bootstack after flashing any ROM, that way you don't have to remember that with those two ROMs you can brick if you flash the Bootstack first. There's more details and exceptions but there's no use overloading you. If you always flash the Bootstack after, there's nothing else to worry about.
Without me reading through all the custom rom posts, do all features of the phone work as good or better on a custom rom as on a stock rom? What I'm mean here is for example, on my DX, DX2, and S3, some features do not work on custom roms due to the closed source of the original software / drivers I believe. On the DX and X2 for example the HDMI out port won't work on AOSP roms because the driver isn't available. Performance suffers on AOSP roms on the X2 past GB because of the closed nature of the Nvidia Tegra 2 drivers I think. I think I'm explaining this correctly.
Click to expand...
Click to collapse
No. For what it's worth in my opinion, I don't bother fooling with non-stock Verizon LG ROMs any more. CyanogenMod/AOSP and ports of international stock ROMs often end up not working quite 100%, and you won't get all the features you will on stock. You can't use laser focus on CyanogenMod no matter what camera app you use, there are workarounds that at least used to work to get QuickRemote working on non-stock ROMs, but I haven't fooled with them in over a year so I have no idea if the same way works on newer ROMs.
I can get the most important to me features of non-stock ROMs by using Xposed and modules like G3TweaksBox.
All too often, after a user has flashed a handful of non-stock ROMs, sometimes they end up not being able to get Mobile Data working, even if they flash a stock rooted ROM. Only flashing the TOT or a KDZ will fix such a situation. TOT is recommended, it flashes more partitions than KDZs and can fix issues KDZs can't.
Would anyone recommend any other device for the price range between 100-200 US dollars? Again, I've been considering a note, nexus 6 (because I know I'll have beaucoup kernels and roms to choose from)
Click to expand...
Click to collapse
I can't really speak to this either. Every time I'm tempted to go Nexus the price and/or the no MicroSD card or lack of as good a camera etc sways me away. I'm going to keep my eye on the HTC 10 in half a year when I may be in the market again, but it won't be that cheap that soon.
Congratulations, you just absorbed 1 1/2 years of experience with LG devices that I got by reading nearly every post in nearly every thread in the G3 sections since that time, and flashing both my VS985s and my VK810 many dozens of times.
P.S. If you go with the VS985, although I've been on @xdabbeb 's as pure stock while rooted 47A Marshmallow (although heavily debloated) for several months now, his custom ROM based on 35B is my overall favorite. You probably won't go wrong with either one of those, in my opinion.
Edit: By the way, it's a common enough occurence on the G3 that when flashing TOTs or KDZs, and maybe other situations, some people have gotten their IMEI wiped and have to go through some headache to put it back in, and you need to know what it was to begin with.
So if you flash back to 10B, root and install TWRP, the first thing you should back up in TWRP is "EFS" which includes your IMEI. Then save that somewhere like on Google Drive. It'll save you a lot of headache if you lose your IMEI. That said, I haven't lost mine once in several dozen flashes on my wife's and my G3s.
If you're still thinking of getting a G3, I was looking at Ebay last night and noticed they are selling refurbished G3's for $100.00 - I think with free shipping.
Just FYI
It's me again.
I've been seeing the development community of the Moto Z starting to pick up after the release of the Nougat source code, evident by the release of an unofficial build of LineageOS 14.1 and the rather quick pace of updates.
However, that ROM was built on the Nougat source code and while it was stated that it might work on Marshmallow bootloaders, it's not expected to be as stable.
You might know by now that my Moto Z is running the RETMX Nougat firmware but on the Marshmallow bootloader (this is done so that if anything goes wrong, I can easily go back to Marshmallow) with TWRP and systemless root via Superuser. However, with this new development, I am considering going back to full-stock and having the Nougat bootloader before flashing LnOS. I have no plans to flash it anytime soon, but I may do so after 1.5 years when official support for the Z will wind down.
So my questions for you guys now are as follows;
1) If an update comes out, would it make sense to just flash the entire factory image since I want to return to full stock?
2) What's the best way to do it? ADB or RSDLite? I used both and didn't have an issue with both, but I do prefer RSD's easier method, although I didn't use that to flash the N image as it would also update the bootloader (something I did not want at the time).
3) Would you recommend flashing the newest version of the software or simply flashing the oldest supported version by the bootloader and then accepting the OTA?
4) Would doing any of the specified methods relock the bootloader? (Hopefully not)
Thanks and I hope to get a good reply soon.
Planning to get a new moto z from a carrier since theybare having a sale and not charging anything for the phone. Fiancé is planning to switch to that carrier anyway since her workplace and is switching all phones to it.
I liked the idea of the moto mod and was thinking of getting the new turbopower pack by Motorola instead of the incipio one. I read that the turbopower requires the moto mod platform to be at 1.6 for it to work. I believe the nougat update brings the platform to 1.6 right?
At the same time, I want to use custom roms on this phone and I read that going to official stock nougat updates the bootloader and brings problems to custom roms. So my question is, can custom roms update the mod platform to the latest while keeping the bootloader on marshmallow? Can we flash nougat custom roms while on marshmallow bootloader with no problems?