Database Users

Sony's developer policy! RANT

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.

Temporary unofficial builds for h815

See: https://forum.xda-developers.com/g4/development/lineageos-unofficial-builds-h815-t3726177

So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?

Wuddelchen said:
So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?
Click to expand...
Click to collapse
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs

Bleuzen said:
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs
Click to expand...
Click to collapse
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...

Wuddelchen said:
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...
Click to expand...
Click to collapse
Nobody knows. The bug exists since 2017-04-30, but nothing happens. And until the bug is not fixed, we don't get new official builds.
If you want to take the time to wipe and (re)setup your device is your decision.
But if you have the time, I would recommend it, mainly because of the security updates.

Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.

tulen_kobi said:
Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.
Click to expand...
Click to collapse
No, I didn't know that
Uh, there is work going on? This is great! I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Great to her that there is still developing going on
Well, I help where I can. But I'm new to Android.
I have experience with Linux, use it every day, and now I know how to build LineageOS. I also can do Java programming.
But I never developed something with Android already. So I don't know how much I can help.

Bleuzen said:
I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Click to expand...
Click to collapse
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.

Exabyter said:
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.
Click to expand...
Click to collapse
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.

Bleuzen said:
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.
Click to expand...
Click to collapse
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102

Exabyter said:
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
Click to expand...
Click to collapse
Yep, looks good. I already tryed Oreo but it isn't complete already. But I'm looking forward to use and recommend it as new daily driver when it's ready

Debloated & rooted stock ROM ?

Hi everyone,
I'm currently using the S7 edge under superman v2.4.1 (ROm from early 2017) and never uptated it since.
As the battery drain is important now (whereas the battery life is still good) i'd like to install a stockbased ROM under 8.0 version. Are there some ?
By the way, i'd like to know (especially in terms of battery life) it's better to get android 8.0 or ported NFE 9.0 ROM ?
Thanks in advance for the answer :good:

I am an experienced person. those who see me can call me a cow. Or you could say what you're doing here.
Do not use custom rom. It could be information theft or data sale. Not safe. It also damages and exhausts the device. Also the battery runs out faster.
Dont login any bank account in any custom rom.
I know this is the developer platform. But people are bad. The good thing about this place is that you can make your own rom by learning something. Just do it to yourself.
Or;
Always use stock rom.
If you need it, root it, debloat it.
Be conscious. Know what you're doing.
Be aware.

riro56 said:
Hi everyone,
I'm currently using the S7 edge under superman v2.4.1 (ROm from early 2017) and never uptated it since.
As the battery drain is important now (whereas the battery life is still good) i'd like to install a stockbased ROM under 8.0 version. Are there some ?
By the way, i'd like to know (especially in terms of battery life) it's better to get android 8.0 or ported NFE 9.0 ROM ?
Thanks in advance for the answer :good:
Click to expand...
Click to collapse
first... you need to update your bootloader and módem.... so flash thru odin a stock firmware then use the latest twrp to hack the recovery and flash any rom avalaible on the development thread...
do that way and it will be fine

luckstar53 said:
I am an experienced person. those who see me can call me a cow. Or you could say what you're doing here.
Do not use custom rom. It could be information theft or data sale. Not safe. It also damages and exhausts the device. Also the battery runs out faster.
Dont login any bank account in any custom rom.
I know this is the developer platform. But people are bad. The good thing about this place is that you can make your own rom by learning something. Just do it to yourself.
Or;
Always use stock rom.
If you need it, root it, debloat it.
Be conscious. Know what you're doing.
Be aware.
Click to expand...
Click to collapse
I agree that rooting and debloating is the best option due to stability reasons .. but your accusation to the developer community here is totally out of sense ..
Rooting a stock rom or even debloating it requires a custom recovery .. a flashable zip for gaining root access like magix/super su and others WHICH are also coded by the great developers here on xda..
So going with your theory.. EVEN flashing a custom recovery or rooting with a zip will hijack the phone because its also a custom coded program not made by samsung .. and so we should not use them too and use full stock so only samsung and google can spy on us.. lol.. Its hillarious man .. you just contradicted your own statement..
And the amount of spying google and OEMs did and are doing.. outpaces any spying a developer here would put in his rom just to see how your face looks like xD like seriously dude this is xda not pi***e b*y.. devs here are the best people and not some low life hijackers .. if they were .. our phones/data and bank accounts would have been hacked a long time ago because of using their roms/programs ..
Again, this is xda.. no one is allowed to do data stealing here unlike oems and google.. if anyone did they would have got banned already.
And you think only a developer can hack the phone by using/flashing his rom/program ?
Whatsapp hacked phones of millions of users which were on STOCK oem roms due to a critical android OS glitch.. android OS itself needs fixing and devs try to implement more security in this unsecure OS if not much.. if they do anything it is extending the life of a device ditched by the oem a long time ago, providing it with latest android OSes, bugs and security fixes/updates and giving it a new life basically..
BUT yes if you or anyone has the skill to modify a rom or make custom one on their own using the sources, I totally agree with that but accusing the ones who did that much hassle and providing an already cooked rom to general people who don't know a bit about coding is the worst type of offence imo, they need to be appreciated highly for their contributions instead of these old pathetic accusations..
Don't misguide other users here on xda ! If you feel still like your data could be hacked .. stop using internet, phones and computers, don't use android, stop using gps too and build an underground bunker to be most 'secure' in life.. but don't misguide others or accuse developers !
I wouldn't have bothered to write such a long reply if your post wasn't that much misguiding and based on false theories.
Also being 'secure' in 21st century is a hillarious joke really and an eternal illusion to people ; )
Sent from my S7 Edge using XDA Labs

Is it worth upgrading from 7.1.1?

I spent a good few years rooting my Android phones, installing ROMs, etc. Quite a while ago I stopped, due to being pretty happy with the performance of this phone, and lack of time/interest in doing it any more. Consquently my phone is running 7.1.1 and ony has a security patch date of September 2017
I realise this is not a good state of affairs. I'm not a coder or anything like that, and I've forgotten most of what I learned about the specifics of this phone a long time ago. If I want to install a new ROM, it's going to mean a lot of reading to bring myself back up to date.
So, aside from my dire security situation, is there actually anything that is going to make my life better by installing an Android 9 or 10 ROM, over and above 7.1.1? Or is it just window-dressing? I'm looking to keep this phone for a while longer yet, and have just ordered a new battery for it, so I thought a software refresh might also be nice. I just wondered whether anyone wanted to offer an opinion on whether it's worthwhile, given it will involve a lot of work for me since I'm so rusty!

Why not just upgrade to stock pie and wait for the Android 10 update coming next year. You don't need to root to get more up to date software.
I've decided it's not worth rooting anymore because I want working Google pay, no bugs, etc. There isn't really anything I need root for and the stock oxygen os is perfect in my opinion.

350Rocket said:
Why not just upgrade to stock pie and wait for the Android 10 update coming next year. You don't need to root to get more up to date software.
I've decided it's not worth rooting anymore because I want working Google pay, no bugs, etc. There isn't really anything I need root for and the stock oxygen os is perfect in my opinion.
Click to expand...
Click to collapse
Just re-read my initial post and I wasn't clear. My phone is rooted/ROMd already. This is why I'm so far behind with software updates, because I got sick of flashing updates all the time. I have a couple of apps that require root, such as an ad-free Youtube with background play (which I'd really like to keep), and Titanium Backup. Aside from those, my phone doesn't really need to be rooted I guess.

I pay a monthly fee to have those features on YouTube. I couldn't go without background play anymore. I would almost root just for that.
As far as if it's worth it, security updates are probably a good idea. I don't recall any major things that Android 9 has that 7.1.1 didn't when I first got the phone a couple of years ago.
I have my banking info to worry about though so I stay stock and keep updated (over the air updates the easy way).

setspeed, I don't know what ROM you are rocking there but for me, on official, pure Oxygen OS I don't find it at all hard to update:
- I download the ROM, Magisk uninstaller, latest Magisk, latest TWRP (I noticed that some blu spark version works best with decryption).
- boot into TWRP
- flash ROM, magisk uninstaller, Makist, TWRP
- boot into sys and re-download whatever Magisk modules I had installed
OxygenOS is only updated every month or so, this procedure takes 10 - 20 minutes at most, so this is not really too much for me to do.
I cannot pin point you the exact big improvements being introduced since 7.1.1, but you can trace the important ones on Wikipedia.
On another note, not having security updates since September 2017 is like walking in front of the shooting range and expecting not to get shot.

setspeed said:
I spent a good few years rooting my Android phones, installing ROMs, etc. Quite a while ago I stopped, due to being pretty happy with the performance of this phone, and lack of time/interest in doing it any more. Consquently my phone is running 7.1.1 and ony has a security patch date of September 2017
I realise this is not a good state of affairs. I'm not a coder or anything like that, and I've forgotten most of what I learned about the specifics of this phone a long time ago. If I want to install a new ROM, it's going to mean a lot of reading to bring myself back up to date.
So, aside from my dire security situation, is there actually anything that is going to make my life better by installing an Android 9 or 10 ROM, over and above 7.1.1? Or is it just window-dressing? I'm looking to keep this phone for a while longer yet, and have just ordered a new battery for it, so I thought a software refresh might also be nice. I just wondered whether anyone wanted to offer an opinion on whether it's worthwhile, given it will involve a lot of work for me since I'm so rusty!
Click to expand...
Click to collapse
Man, i'm basically in the same situation and i make a post just today for the same reason. I want to update and unroot. What can i do? i'm at oreo 8.1.0 and os 5.1.1. Maybe is better first lock the bootloader and then make the OTA? but even if all go smooth which i doubt, how can i restore my backup without titanium without the root? is a f...ing mess

Just dirty flash the latest Oxygen OS (full zip). Then wipe the cache and you should be good to go. That's basically what I've been doing for quite some time with every update (plus Magisk).

daniel_loft said:
Just dirty flash the latest Oxygen OS (full zip). Then wipe the cache and you should be good to go. That's basically what I've been doing for quite some time with every update (plus Magisk).
Click to expand...
Click to collapse
that's probably the worst suggestion i've ever heard. You suggest to dirty flash from nougat/oreo to pie and do it straigh away...maybe even with a twrp 2 years old. Sounds good man..then i good to go..to a store and buy a new phone

Any way to remain on stock, but get the security updates?

I've use ROMs in the past, but never with the Essential phone. In fact my phone has run so well, I've never even factory reset it a single time, let alone put a ROM on it. But with Essential gone, I need a way to keep my phone secure.
I'm wondering what the best way to keep stock android (nothing wrong with stock) but allow myself to get the latest android updates as they come out. In looking at the ROMs there still seems to be some issues with bugs, and since this phone is my daily driver, I'd like it to be as stable as possible.
So is there:
1) A way to get the PH-1 on stock, but still get the important security updates somehow?
2) A rom available (even if android 9) that works for PH-1 that would be super stable but also get all new security updates?
Thanks in advance for any help.

holodude said:
I've use ROMs in the past, but never with the Essential phone. In fact my phone has run so well, I've never even factory reset it a single time, let alone put a ROM on it. But with Essential gone, I need a way to keep my phone secure.
I'm wondering what the best way to keep stock android (nothing wrong with stock) but allow myself to get the latest android updates as they come out. In looking at the ROMs there still seems to be some issues with bugs, and since this phone is my daily driver, I'd like it to be as stable as possible.
So is there:
1) A way to get the PH-1 on stock, but still get the important security updates somehow?
2) A rom available (even if android 9) that works for PH-1 that would be super stable but also get all new security updates?
Thanks in advance for any help.
Click to expand...
Click to collapse
Don't want to be rude, but here's the answer:
1. None
2. None

chanh2018 said:
Don't want to be rude, but here's the answer:
1. None
2. None
Click to expand...
Click to collapse
I could have sworn I saw something that basically said you can download the latest stock version (that includes security updates) and flash it every time there is a new update. But I guess I could have misunderstood?

holodude said:
I could have sworn I saw something that basically said you can download the latest stock version (that includes security updates) and flash it every time there is a new update. But I guess I could have misunderstood?
Click to expand...
Click to collapse
That was the case until Essential went out of business - you could do OTA updates, or download and flash yourself. The stock security updates were only provided by Essential, and the Feb 2020 update was the last one for this phone...

holodude said:
I could have sworn I saw something that basically said you can download the latest stock version (that includes security updates) and flash it every time there is a new update. But I guess I could have misunderstood?
Click to expand...
Click to collapse
You are correct: Android GSI. Info >here<

aleph23 said:
Android GSI
Click to expand...
Click to collapse
And how would that be "remaining on stock", as per the OP?

holodude said:
I could have sworn I saw something that basically said you can download the latest stock version (that includes security updates) and flash it every time there is a new update. But I guess I could have misunderstood?
Click to expand...
Click to collapse
No way to stay on stock & get security updates (well you will get some direct from Google ie the Google Play System Update, the last one shown lower down this page
https://source.android.com/security/bulletin/2020-03-01
and can be found in your settings under security, but its only a fraction of patches)
That means your best option is probably the Android 11 GSI when it's out of Developer Preview in a July (?) and hope it's bug free, else Lineage etc .... not that you want custom roms, sorry.

IronRoo said:
No way to stay on stock & get security updates (well you will get some direct from Google ie the Google Play System Update, the last one shown lower down this page
https://source.android.com/security/bulletin/2020-03-01
and can be found in your settings under security, but its only a fraction of patches)
That means your best option is probably the Android 11 GSI when it's out of Developer Preview in a July (?) and hope it's bug free, else Lineage etc .... not that you want custom roms, sorry.
Click to expand...
Click to collapse
Basically I'm looking for something safe and stable, whether it is ROM or otherwise. Right now I'm stable, but not safe. So you think my best bet is move to Lineage (to become safe) and then switch to the GSI when it is out of developer preview (and stable)?

From what I have read and asked here: https://forum.xda-developers.com/essential-phone/development/rom-evolution-x-4-1-69-t4073153
This ROM will give you what you are asking for as far as regular security updates are concerned. I have been waiting for Lineage to release an "OFFICIAL" version of Android 10 for our PH-1's but so far nothing. Also I would not mind going on Android 11 but then I do not think that will get monthly security updates either so I am thinking about trying this Evolution ROM out.... I have never worked with a phone with A/B slots so that is my only concern but after reading all the threads I am starting to understand how that works.
Hope this info helps you out.

holodude said:
Right now I'm stable, but not safe.
Click to expand...
Click to collapse
Security updates are overrated. ?

SirDigitalKnight said:
From what I have read and asked here: https://forum.xda-developers.com/essential-phone/development/rom-evolution-x-4-1-69-t4073153
This ROM will give you what you are asking for as far as regular security updates are concerned. I have been waiting for Lineage to release an "OFFICIAL" version of Android 10 for our PH-1's but so far nothing. Also I would not mind going on Android 11 but then I do not think that will get monthly security updates either so I am thinking about trying this Evolution ROM out.... I have never worked with a phone with A/B slots so that is my only concern but after reading all the threads I am starting to understand how that works.
Hope this info helps you out.
Click to expand...
Click to collapse
You & your big mouth! ?
https://download.lineageos.org/mata
(actually its been out a while, by the looks of it, but no mention here)
I'm the same boat as you, had hoped to flash LineageOS 17 months ago then move to Android 11 in few months time, guess it's decision time now.
---------- Post added at 03:31 AM ---------- Previous post was at 03:23 AM ----------
holodude said:
Basically I'm looking for something safe and stable, whether it is ROM or otherwise. Right now I'm stable, but not safe. So you think my best bet is move to Lineage (to become safe) and then switch to the GSI when it is out of developer preview (and stable)?
Click to expand...
Click to collapse
Guess for stability & functionality it would have to be LineageOS.
Looks like May version is ver 17.1 (Android 10), not sure how this compares to previous version re bugs/working functions, but that means previous ver is already a month out of date on security )
edit: see this post also
https://forum.xda-developers.com/es...7-1-essential-ph-1-mata-t4066163/post82606687
Also DO NOT use the Essential USB cable & DO NOT relock boot loader!

SirDigitalKnight said:
From what I have read and asked here: https://forum.xda-developers.com/essential-phone/development/rom-evolution-x-4-1-69-t4073153
This ROM will give you what you are asking for as far as regular security updates are concerned. I have been waiting for Lineage to release an "OFFICIAL" version of Android 10 for our PH-1's but so far nothing. Also I would not mind going on Android 11 but then I do not think that will get monthly security updates either so I am thinking about trying this Evolution ROM out.... I have never worked with a phone with A/B slots so that is my only concern but after reading all the threads I am starting to understand how that works.
Hope this info helps you out.
Click to expand...
Click to collapse
I'm on EvoX the only thing tht is not t working very well, is tht if u fast forward or rewind on Netflix ur phone reboots, hopefully fixed next update, but I'm happy with this ROM, the touch lag is almost non existence for some reason, glad they managed to fix tht. Also L1 certification is still there. The 360 camera workes better in this Rom for some reason. The best part is the customization though, so much

IronRoo said:
You & your big mouth!
https://download.lineageos.org/mata
(actually its been out a while, by the looks of it, but no mention here)
I'm the same boat as you, had hoped to flash LineageOS 17 months ago then move to Android 11 in few months time, guess it's decision time now.
---------- Post added at 03:31 AM ---------- Previous post was at 03:23 AM ----------
Guess for stability & functionality it would have to be LineageOS.
Looks like May version is ver 17.1 (Android 10), not sure how this compares to previous version re bugs/working functions, but that means previous ver is already a month out of date on security )
edit: see this post also
https://forum.xda-developers.com/es...7-1-essential-ph-1-mata-t4066163/post82606687
Also DO NOT use the Essential USB cable & DO NOT relock boot loader!
Click to expand...
Click to collapse
Very strange that no one has started a new thread in the Custom ROM section about this... (This being an official release version of Lineageos 17.1) you would think it would be bigger news? There is still only an Unofficial thread... strange..
Anyway IronRoo let me know what you decide to do and how it goes... I am still on the fence as my PH-1 is currently working perfect on stock 10 but it is of course on the Feb 29th security patch... plus I haven't done a custom ROM install since my LG G5 but I hear it is like riding a bike... lol :silly::fingers-crossed:

SirDigitalKnight said:
Very strange that no one has started a new thread in the Custom ROM section about this... (This being an official release version of Lineageos 17.1) you would think it would be bigger news? There is still only an Unofficial thread... strange..
Anyway IronRoo let me know what you decide to do and how it goes... I am still on the fence as my PH-1 is currently working perfect on stock 10 but it is of course on the Feb 29th security patch... plus I haven't done a custom ROM install since my LG G5 but I hear it is like riding a bike... lol :silly::fingers-crossed:
Click to expand...
Click to collapse
For LOS, I think we should wait until their server is back, and few more releases come out.
LineageOS 17.1 for Essential is so new, only couple releases, and still in updating state.

chanh2018 said:
For LOS, I think we should wait until their server is back, and few more releases come out.
LineageOS 17.1 for Essential is so new, only couple releases, and still in updating state.
Click to expand...
Click to collapse
Yes, many will agree, though I'm OK with giving it a go but I need to buy a new high quality USB cable as kid damaged my Samsung one and have only a cheap 6" one which I'm not sure I trust to flash without bricking phone.

SirDigitalKnight said:
Very strange that no one has started a new thread in the Custom ROM section about this... (This being an official release version of Lineageos 17.1) you would think it would be bigger news? There is still only an Unofficial thread... strange..
Anyway IronRoo let me know what you decide to do and how it goes... I am still on the fence as my PH-1 is currently working perfect on stock 10 but it is of course on the Feb 29th security patch... plus I haven't done a custom ROM install since my LG G5 but I hear it is like riding a bike... lol :silly::fingers-crossed:
Click to expand...
Click to collapse
Just did a quick websearch and a few have tried flashing it reddit and here on the 16 thread, and it's suggested wait for next release (first recovery had issue, but now fixed, but next release of ROM should have a few fixes & Lineage build servers are down so not sure when new release will drop)