I recently made a terrible mistake in toying with downgrading back to Marshmallow from Nougat which resulted in the sad hard-bricking of my device. The Nougat bootloader somehow allowed stock Marshmallow to boot and when I decided to accept a security OTA, it must have patched the bootloader and didn't notice that the bootloader was the incorrect version. The second that OTA had applied, my poor MXP had died and it never turned back on. So now I'm here to present a couple of things I feel that I should drop off before I leave this device forever because I had a couple of projects in the works that might be cool for you all to check out.
I have one build of Lineage 15 that I slapped together using HashBang173's kernel and device config and the other sources provided by the Android Oreo WIP page. The last time I was able to get it to boot, it had some serious Bluetooth force closing problems, but there were a ton of changes since I last made a new build. I was never able to see any sort of improvement since I couldn't flash and test the build so if you're looking to try out this build, be my guest. Just flash at your own risk as usual and if you do, you will have to erase userdata before you will be able to wipe anything in TWRP again due to some bug that crashes TWRP.
My second build is for a Nougat build of PureNexus. I was getting really antsy while waiting for a build to come in from HashBang that he mentioned that he'd make a while ago, but since that never ended up coming, (as far as I know) I made one myself. I slapped this build together with the PureNexusProject-Mod sources, I haphazardly put together my own device config, and the build succeeded. However, with the same sad result, I was never able to run this build myself and I have it here abandoned. Again, try it at your own risk because I have put no testing into this at all.
I'm very saddened to leave this device because I really loved everything about it, (minus some of the motorola inconveniences along the way) and I put so much into my little device over the past two years. I guess it's about time to move on anyways :crying:
BUT WAIT, there's more. I have been able to revive my Moto X Pure using this thread over here: https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
I'm constantly checking the thread to help people who are running into problems. It was a godsend to me so I'm more than willing to help others
Download
I just installed your Lineage 15 build. Bluetooth keeps crashing, and camera doesn't work. I managed to stop bluetooth crash by deleting it from system files. Thanks for your work and I hope to see more from you.
Related
I have been on a plain rooted 4.1.2 rom for years. I now need to update for a couple apps I use to work. Can someone give me some brief feedback and point me in the right direction so I can update my phone without locking the bootloader?
I like the plain set up I have now, so maybe I just need to update to the highest version without locking BL. Thanks.
I thought about trying this---> File: cm-10.1-20130315-NIGHTLY-d2vzw.zip, but all links that I've found are dead. Anyone know where I might find this file? Thanks
CM is dead. The leftovers rose from the ashes as Lineage OS.
Look them up. Pretty stable.
Jump straight into Marshmallow or Nougat. I'm still on CM12.1 Lollipop, but the newer stuff should work fine. There are threads for all of it, so do good reading before you start.
Thanks for answering my thread. I haven't messed around with my phone in years. I guess what you're saying is since I've never took the OTA 4.3, I can load an advanced CM without locking my bootloader.
phonetool....thanks for the input. I tried Nougat but I had issues with my 3G data and a couple other little things.
I decided to go with 12.1 Lollypop and it is great. All my apps work and 3G fires right up.
Hi All,
I have a two Relays that have served me well, and I enjoyed having them, but the time has come to pass them on to someone else. Before I do that, I'd like to update them to the most recent versions of stable-release software that is available for them.
For Cyanogen, I have:
cm-11-20150831 (this is stable)
cm-11-20160523 (this is a nightly build)
For recovery I have:
philz touch 6.48.4
I'd like to replace Philz with a newer TWRP, but the Relay is no longer listed on the TWRP website. I'm also wondering if there was ever a stable CM release newer than the one I have.
Does anyone have sources for the above?
Thanks.
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
mrigancb said:
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
Click to expand...
Click to collapse
Although I'm not a developer I have been working on my SGH T699 from T Mobile. You may already know of the JellyBean and before. Recently I've noticed new builds for the samsung Galaxy S Relay 4G like the Validus 5.0.2 or the Fat Toad. I haven't tried those yet I was trying for a higher version. With 8.0 Oreo it requires partitioning and I need to brush up on that. So I went lower to the 7.0 or the 7.1 Nougat. I started noticing a lot of broken or old links so I had to resort to fishing the internet for most of the packages apparently lost in XDA. I pretty much have all of them and was just starting to try a few out when I ran into problems like I want to keep using the keyboard and Wifi calling or a related Wifi issue. It also crashed, went into bootloop or even soft bricked within a few days. The Roms and packages I've found are highly unstable and I see many had flashing issues. So far I've been tricking my device into taking the flash and even then it doesn't hold long. I'd like 6.0 MarshMallow if I can, maybe 7.1 if they ever get stabler that'd be great. But so far the ROMs for the Galaxy S (relay) are fairly horrible to say the least. I get the impression these so-called developers aren't testing their ROM creations more than 5 minutes and then handing them off to noobs who may be very likely to brick their device trying to get it in and running, only to have it crash repetedly! Or worse, hard-bricked.
I like this device. I think I'll keep working on it.
Casper Young.
As we all know there is a point during setup where you put in your google account and it asks to restore from a phone or start fresh. When I got to that part, there were no backups to restore from. I confirmed that my Essential Phone and my Pixel XL backup were still present on my drive. Then after the setup was complete, I noticed that there wasn't Android 8.1 on the Premium, despite having the April security update. Being impatient, I looked it up and I saw that 8.1 was available and out for OTA. Since I don't have a carrier-locked device, theoretically I could receive all updates as they roll out from Sony. I thought since my backups were from an 8.1 device, they were incompatible to downgrade to 8.0. Still being impatient, I looked over XDA and found that Unlocking the bootloader and loading a custom ROM would be fine, but that's where I ran into issues.
Half of the threads that supported G8412 (Dual Sim) were either edited to "working" or out-of-date or closed by a moderator (I downloaded the Turbo mod before it was deleted, and I only discovered it was deleted when I logged on to thank him).
TL;DR:
-Unlocked my bootloader, which turned out to be a terrible mistake on my part
-Cant seem to find a stable ROM (the flash-and-forget kind) that supports my model
-Apparently now the camera is broken and unusable on most ROMs?
-Can't migrate any of my data due to a (theoretical) Android 8.1/8.0 clash
Anything I am missing on the forum would be appreciated. I've looked at Storm's thread (closed), Turbo's thread (closed), Snappatch (DRM Fix required). It seems like a lot of ROMs that are still active require the DRM fix by Storm except for the Carbon ROM. So, any suggestions as to what to do going forward? Is there something I am missing?
(Edit: upon reading, this looked more like a blog post so I cut it down)
I'm personally using the official CarbonROM 8.1 on my G8142. Been running it for a few weeks and it's pretty stable.
Thunder_47 said:
As we all know there is a point during setup where you put in your google account and it asks to restore from a phone or start fresh. When I got to that part, there were no backups to restore from. I confirmed that my Essential Phone and my Pixel XL backup were still present on my drive. Then after the setup was complete, I noticed that there wasn't Android 8.1 on the Premium, despite having the April security update. Being impatient, I looked it up and I saw that 8.1 was available and out for OTA. Since I don't have a carrier-locked device, theoretically I could receive all updates as they roll out from Sony. I thought since my backups were from an 8.1 device, they were incompatible to downgrade to 8.0. Still being impatient, I looked over XDA and found that Unlocking the bootloader and loading a custom ROM would be fine, but that's where I ran into issues.
Half of the threads that supported G8412 (Dual Sim) were either edited to "working" or out-of-date or closed by a moderator (I downloaded the Turbo mod before it was deleted, and I only discovered it was deleted when I logged on to thank him).
TL;DR:
-Unlocked my bootloader, which turned out to be a terrible mistake on my part
-Cant seem to find a stable ROM (the flash-and-forget kind) that supports my model
-Apparently now the camera is broken and unusable on most ROMs?
-Can't migrate any of my data due to a (theoretical) Android 8.1/8.0 clash
Anything I am missing on the forum would be appreciated. I've looked at Storm's thread (closed), Turbo's thread (closed), Snappatch (DRM Fix required). It seems like a lot of ROMs that are still active require the DRM fix by Storm except for the Carbon ROM. So, any suggestions as to what to do going forward? Is there something I am missing?
(Edit: upon reading, this looked more like a blog post so I cut it down)
Click to expand...
Click to collapse
i think turbo said he might bring it back he is just away right now(work)
also for camera you can go here https://forum.xda-developers.com/xz-premium/how-to/xz-premium-145-twrp-root-fix-t3783036 and download the drm fix.
blweldon2 said:
I'm personally using the official CarbonROM 8.1 on my G8142. Been running it for a few weeks and it's pretty stable.
Click to expand...
Click to collapse
Does the CarbonROM require any upkeep? I see it says "Weeklys" in it's title, so for the uneducated, does that mean it is updated Weekly with new features/fixes?
raven213 said:
i think turbo said he might bring it back he is just away right now(work)
also for camera you can go here https://forum.xda-developers.com/xz-premium/how-to/xz-premium-145-twrp-root-fix-t3783036 and download the drm fix.
Click to expand...
Click to collapse
I did get the firmware that is .145, and I do have a DRM fix currently, however I do not remember where I got it from. I wish Turbo the best of luck in bringing back his work and collab with that other guy.
Update
After a bit of research, I did find that getting the 8.1 Carbon Rom with the AOSP upgrade below would be best. As seems like the current trend where some users report successes and others report failures and there really isn't an "in-between" of a particular combination, this one seems to have the most credibility as of May 8. Carbon Rom's thread hasn't been active for about a month, however and the author behind the Snappatch upgrades seems to have left XDA..
Any other users that have Android 8.1 have anything else to say/suggest?
Carbon Rom:
https://forum.xda-developers.com/xz-premium/development/8-1-x-carbonrom-cr-6-1-t3771540
AOSP Upgrade (Snappatch)
https://forum.xda-developers.com/crossdevice-dev/sony/pom-snappatch-xperia-aosp-t3777322
blweldon2 said:
I'm personally using the official CarbonROM 8.1 on my G8142. Been running it for a few weeks and it's pretty stable.
Click to expand...
Click to collapse
How did you do to flash it when I do it it's stock at Sony logo
SilverGamer_YT said:
How did you do to flash it when I do it it's stock at Sony logo
Click to expand...
Click to collapse
Make sure you flash the AOSP userdata image. Can obtain it by compiling from source or grabbing it from one of the AOSP roms compiled from source. Just flash it in fastboot and then flash the rom in TWRP. Only need to flash userdata once.
By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.
I recently ran into the issue during custom rom work. I reflash the stock android ZIP, it starts booting, then I hard reset it with the power button and try to reach bootloader again. This, as it turns out, is terrible to do if you want a fast setup. The moment it starts and you reboot it, the boot image is corrupted (that's my guess) because escaping the boot screen during a clean flash bricks your phone. If you're reading this, it happened to you as well.
The answer is so flipping obvious and it took me an hour to figure it out - nowhere on the internet is there a "solution" for this problem, no matter how frequent it is. But there are lots of people who deal with this, whether still on their factory images (like the Pixel 3 EDL issue) or like me bouncing from custom to stock. So here's the answer:
ALL YOU HAVE TO DO IS SIDELOAD THE CURRENT SOFTWARE OTA OR A BETA OTA FROM ANOTHER FUTURE VERSION.
It doesn't recognize timestamps before your current software, so you'll need to assume you're on the latest of whatever you're on and do that. Future versions work as well, so if you wanted to reach 12 in one shot, your phone's bootloader would fully accept it as long as the file isn't corrupted. If you need a sideloading or flashing guide, here you go.
For me, I flashed the latest build of Android 11 (August patch) and rebooted during the boot up. What I did was download the OTA of the same exact file to my laptop, and entered adb sideload coral.xxx.x.zip. (The name of the file) It ran all the way through and it started up perfectly normal.
I hope this helps someone!
P.S. I don't have any pictures or tutorials, I only wrote this to help others understand what happened and how to fix it. Probably wouldn't have needed to say it if the forum for it existed.