Related
Hello, iam a Xperia-Z (C6603) User for a week or two and am now looking forward to a
Nice and clean custom-Rom without any bloatware which I hate(ultimate music Sony select,sonysocialfoo and Facebook and alike)
and I guess cm11nightly would fulfill my needs, as i would also really love a smartphone without gapps.
FIrst I thought it would basically be a decision between the to be flashed ROM but now
I read about the bravia-engine getting lost forever which would really suck, is this still
State-of-the-art? Or is there an Option to get it back, as far as I know the BE is basically still there but licensed over a key like the mpeg2-codec on the raspberry-Pi isn't there a possibility to back it up and still be able to use it when you revert back to stock for example?
You're in charge now, what do you suggest me? Iam still on 4.2.2 and would like to get everything up-to-date soon. Btw. I would want a Rom that is of the same color as stock 4.2.2 so basically black, a white theme would be hard to look at in dark conditions even when turned down to lowest brightness.
So to sum it up: NO bloatware (must), NO gapps(nicetohave), black theme like 4.2.2(must), still BEngine(nicetohave)
Btw. How's the image-quality with custom-Roms? It shouldn't get worse than it is in 4.2.2 stock if possible!
Thanks! :good::highfive:
luluchambler said:
Hello, iam a Xperia-Z (C6603) User for a week or two and am now looking forward to a
Nice and clean custom-Rom without any bloatware which I hate(ultimate music Sony select,sonysocialfoo and Facebook and alike)
and I guess cm11nightly would fulfill my needs, as i would also really love a smartphone without gapps.
FIrst I thought it would basically be a decision between the to be flashed ROM but now
I read about the bravia-engine getting lost forever which would really suck, is this still
State-of-the-art? Or is there an Option to get it back, as far as I know the BE is basically still there but licensed over a key like the mpeg2-codec on the raspberry-Pi isn't there a possibility to back it up and still be able to use it when you revert back to stock for example?
You're in charge now, what do you suggest me? Iam still on 4.2.2 and would like to get everything up-to-date soon. Btw. I would want a Rom that is of the same color as stock 4.2.2 so basically black, a white theme would be hard to look at in dark conditions even when turned down to lowest brightness.
So to sum it up: NO bloatware (must), NO gapps(nicetohave), black theme like 4.2.2(must), still BEngine(nicetohave)
Btw. How's the image-quality with custom-Roms? It shouldn't get worse than it is in 4.2.2 stock if possible!
Thanks! :good::highfive:
Click to expand...
Click to collapse
I would recommend Cyanogen Mod to most people. Honestly I can't live without the features these days!
Regarding the consequences.. Well there aren't really any.. Kinda.. You may or may not lose your warranty based on how stingy Sony are feeling at the time. Most of the BRICK warnings are just to cover developers if someone does something wrong or if your phone just so happens to die of something completely unrelated while installing the rom.
I would recommend trawling this forum for at least and hour or two just reading the various guides; How to backup your phone, How to unlock the bootloader and, most importantly, how to backup your TA partition.
It's quite a pain free process. It's just better to be aware of what could go wrong, so you are prepared and can easily apply the fix before panicking and messing something up
Good luck and happy trawling!
You only have to learn these things once. Once your rooted, unlocked and running a custom rom updating is easier than sonys
Hi, thank you for your reply.
I just looked up what exactly the "TA-Partition" is and i guess the only thing that was worrying me (loosing Bravia) is not up-to-date anymore
So lets get started, i looked up what i need to backup the "TA-Partition" and if i understood everything its basically having a rooted Xperia-Z and a double-click on a .bat-file?
So i guess the best would to not upgrade any of the shown OTA-Updates by Sony, and root the 4.2.2-Stock ROM that is on the device right now?
As far as i know rooting 4.2.2 isn't really a problem right now, agreed?
So after sucessfully rooting the Sony Xperia-Z its just backing up the "TA-Par tition" with "TA-Backup"-Script?
After that, its unlocking the Boot-loader over the Sony-Website (IMEI, Name, Email....) so that they send you the Unlock-Code, after that you'll have to use fastboot to finally unlock it?
(If i check the Service Menu "Rooting Status": there is nothing behind it, but the bootloader-unlock allowed: says yes, so no problem right?)
After that you most likely are done for the moment, until you decide if it should be CM10.1Stable or CM11Nightly, rig
How's the status of CM11 right now, any known major bugs?
Thank you already for your help :good:
luluchambler said:
Hi, thank you for your reply.
I just looked up what exactly the "TA-Partition" is and i guess the only thing that was worrying me (loosing Bravia) is not up-to-date anymore
So lets get started, i looked up what i need to backup the "TA-Partition" and if i understood everything its basically having a rooted Xperia-Z and a double-click on a .bat-file?
So i guess the best would to not upgrade any of the shown OTA-Updates by Sony, and root the 4.2.2-Stock ROM that is on the device right now?
As far as i know rooting 4.2.2 isn't really a problem right now, agreed?
So after sucessfully rooting the Sony Xperia-Z its just backing up the "TA-Par tition" with "TA-Backup"-Script?
After that, its unlocking the Boot-loader over the Sony-Website (IMEI, Name, Email....) so that they send you the Unlock-Code, after that you'll have to use fastboot to finally unlock it?
(If i check the Service Menu "Rooting Status": there is nothing behind it, but the bootloader-unlock allowed: says yes, so no problem right?)
After that you most likely are done for the moment, until you decide if it should be CM10.1Stable or CM11Nightly, rig
How's the status of CM11 right now, any known major bugs?
Thank you already for your help :good:
Click to expand...
Click to collapse
I've been using Cyanogenmod 11 nighties for months now, no obvious bugs
Some features aren't implemented yet and the occasional feature is broken.. Nothing really integral to the phone though
You've pretty much got the method down! Just ensure you use a root method for your sony firmware version (Android version). It should use some form of "Exploit" to avoid deleting the TA-Partition. Honestly I backed mine up and haven't ever wanted to restore it, the features are more of a gimmick than anything useful
Enjoy
A few more questions! (Iam sorry )
So as far as i can see, my smartphone is running "10.3.1.A.0.244" which is regarding to the post by DooMLord not exploitable.
I therefore have to flash the "10.3.A.0.423"-Kernel-Only so that the previously used exploit works again.
After that i'll have to restore the Kernel that was previously on the Smartphone therefore "10.3.1.A.0.244"
After that root should stay in intact, but what about the TA-Partion? Is it somehow affected by this?
Secound Question, is it crucial to have an micro-sdhc inserted to sucessfully flash CM11 onto the Xperia Z after backing up TA, or is it possible without?
And the Image-Quality (taking Pictures) should be kinda worse on CM11 than it is with Sony's Stock Firmware, is it possible to include(myself) the propritary firmware.blobs for the Camera as we do it with gapps, or will i have to live with the reduced image Quality?
Thanks!
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
dont mess with itttt leave it until someone replies we need to extract your firmware, hold onto it if you not messing around, im not experinced enough but someone will pm you im sure
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=54642044
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
Apparently there are many different circumstances under which the splash screen says custom, which have nothing to do with the bootloader being locked or unlocked. I seem to recall it showing up for people when they just switched to ART runtime, and in some cases it didn't even go back when they switched back to Dalvik. Many of the methods for making this not appear just involve cosmetically hiding it, not actually cleaning up whatever it is that is being detected.
What I wouldn't give to have this bootloader unlocked
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
If there is a dev that wants a s5 to experiment with to get the bootloader unlocked I'll be happy to donate my s5 if I can get it back after finding an exploit . But the dev needs to come with unanimous recommendation by the devs. Let me know I can still use my s3.
Sent from my SAMSUNG-SM-T537A using XDA Free mobile app
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
MGArcher007 said:
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
Click to expand...
Click to collapse
Sadly. ...We may never see the bootloader unlocked without a factory method...
It's encryption prevents us from even being able to open it into a usable state...
We need either an encryption key....or a new bootloader entirely...
Not happening any time soon....g
I have been reading this forum as long as I have had my phone (over 2 years) and I have finally decided it's time to move past the concept rom.
I am unfortunately inexperienced w/ flashing roms on the z3 compact (I last loaded custom roms on my moto defy, but only flashed .sbf files on my razr m) and I just want to clear up a few questions.
I hope that 7.1 will make it to z3 compact in a stable rom eventually, so that is my end goal, but for now i am considering going with one of the stock roms out there (slimm, etc.) First question is about UL bootloader, drm and the camera. If I back up the DRM does that mean i can relock the bootloader, transfer the drm keys back to the phone and the camera will be useable? will i be able to use an aosp if i relock the bootlaoder after flashing the rom? It's unclear if custom roms need ul bootloader all the time or just for install.
Also, custom kernels need ul bootloader to run correct? i cannot load a custom kernel, and custom rom, and then re lock the bootloader?
I love this phone (will probably get a second just in case) and don't see anything out there to replace it. That's why I requesta bit of help from the xda community for this. If there is no xz compact in the works, i'd be happy w/ z3 compact for a while (assuming i can get newer roms plus a working camera)
Thank you
1. The Camera is usable regardless of whether or not you have DRM keys. However, certain features such as noise reduction during the night do not work without DRM keys.
2. "If I back up the DRM does that mean i can relock the bootloader, transfer the drm keys back to the phone and the camera will be useable?" - Yes.
3. You need unlocked bootloader for all AOSP ROMs since the kernel is different.
4. "I cannot load a custom kernel, and custom rom, and then re lock the bootloader?" - Nooo, your phone will just stop booting up. Unless you're fully stock don't bother relocking. There's a "DRM Restoration" patch for unlocked bootloaders anyway http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
When you go back to stock, you'll probably feel how slow and bad it performs compared to Concept haha. I went right back after I flashed stock for a day.
Also, camera on AOSP ROMs have a fish eye effect for now.
Thanks. I wasn't sure if the DRM fix would fix the fisheye problem in AOSP Roms. I guess my best bet is to see what happens now that they've released the concept kernel source? Meaning I'll be on concept for a while longer.
Hopefully there will eventually be a 7.1 ROM stable with for use on my primary phone? I just don't want to lose camera functionality (since it's not that great to begin with)
The thing is people hope hope hope and never actually help with development, so it's a little slow.
Camera is limited to 15 fps for reasons which I think will stay that way and fish eye can be corrected by anyone who can be bothered. Also DRM fix doesn't matter in AOSP since AOSP doesn't use DRM stuff.
And so what if they released kernel source ? There's really not too much to do on it and I don't see any demand for a custom kernel so I haven't released mine here.
You're right. I wish had the know how to help out here. Also, I guess my ignorance is clear to you real devs out there, since I thought that having the kernel source might make it easier for the devs to work with the concept ROM
Hi
My first post here and wondered if any of you would have a neat answer for me.
I am considering getting a Z3 Compact, and have been reading about it and it seems there may have been some issues with Android updates affecting thing slike battery life, etc. I know it can be taken as far as MARSHMALLOW, but some people say it is better to stay at LOLLIPOP, and I have found still other owners saying that they have flashed their phones back to KITKAT, and that this is the best match for the phone.
I am wondering if there is a best answer for what is the best version of Android to be using with this phone?
Thanks!
Robert
It's a very difficult question since it depends on what you mean what best is since the term is very subjective. IIf battery life is all you care about then I heard Kitkat is the best because they crippled the Stamina mode in later versions. But that means you will have a hopelessly outdated software when it comes to security updates, which I would think is more important than battery life. But if you want to software thats up to date then you cant be using stock ROM but which means you have to unlock the bootloader which leads to degradation in camera quality. So there are lots of factors to consider.
BrotherZero said:
It's a very difficult question since it depends on what you mean what best is since the term is very subjective. IIf battery life is all you care about then I heard Kitkat is the best because they crippled the Stamina mode in later versions. But that means you will have a hopelessly outdated software when it comes to security updates, which I would think is more important than battery life. But if you want to software thats up to date then you cant be using stock ROM but which means you have to unlock the bootloader which leads to degradation in camera quality. So there are lots of factors to consider.
Click to expand...
Click to collapse
Thanks BrotherZero
That's useful to hear. My preference would be to have the most recent OS available, which looks like MARSHMALLOW (I don't want to change bootloader and good camera is important)
My concern was just that battery life would be really poor with that. If it's still good I have no issue.
Worry has arisen because I had one for a couple of days that I sent back because the battery was draining very quickly indeed, and I am trying to work out if it is an OS issue before buying again (I really liked the phone)
If its just "not quite as good battery life on Marshmallow, but still very decent" then that's fine.
Thanks
R
rdpxi said:
Thanks BrotherZero
That's useful to hear. My preference would be to have the most recent OS available, which looks like MARSHMALLOW (I don't want to change bootloader and good camera is important)
My concern was just that battery life would be really poor with that. If it's still good I have no issue.
Worry has arisen because I had one for a couple of days that I sent back because the battery was draining very quickly indeed, and I am trying to work out if it is an OS issue before buying again (I really liked the phone)
If its just "not quite as good battery life on Marshmallow, but still very decent" then that's fine.
Thanks
R
Click to expand...
Click to collapse
I have flashed Kitkat, but I never used it for an extensive period (my phone was delivered with LP). I heard from numerous sources that battery life was exceptional on Kitkat, but it was really good on LP too for mer, so It wasn't like I needed better batterylife and add that Kitkat looked really outdated. With Marshmallow I thought I could slightly worse batterylife, but it wasnt a huge degradation either. So I think you will be fine on that.
About the camera, I don't know how good the quality is now on either LIneage OS or OmniROM (these are the ROMs I'm looking to flash my Z3c with now, they have the most up to date software right now and are also open source, Jaguar looks very interesting too, but the dev just dropped the project a month or so ago) but i felt the camera wasn't that good to begin with on Z3c any way. My LG phones (G2 and G4) always blew it out of the water and I don't think I ever seen a sony phone with a really good camera (which is weird since they make the sensor for everybody else). That's why I dont have any qualms abuot unlocking bootloader anymore.
BrotherZero said:
I have flashed Kitkat, but I never used it for an extensive period (my phone was delivered with LP). I heard from numerous sources that battery life was exceptional on Kitkat, but it was really good on LP too for mer, so It wasn't like I needed better batterylife and add that Kitkat looked really outdated. With Marshmallow I thought I could slightly worse batterylife, but it wasnt a huge degradation either. So I think you will be fine on that.
About the camera, I don't know how good the quality is now on either LIneage OS or OmniROM (these are the ROMs I'm looking to flash my Z3c with now, they have the most up to date software right now and are also open source, Jaguar looks very interesting too, but the dev just dropped the project a month or so ago) but i felt the camera wasn't that good to begin with on Z3c any way. My LG phones (G2 and G4) always blew it out of the water and I don't think I ever seen a sony phone with a really good camera (which is weird since they make the sensor for everybody else). That's why I dont have any qualms abuot unlocking bootloader anymore.
Click to expand...
Click to collapse
Thanks again
What I am hearing is that if I buy one, I can upgrade it to MMallow and all will be fine, which is kind of what I was hoping to hear.
I've spent three years with an S4 Mini, so I think the camera will be a huge step up whatever I do to it!!
R
After the last marshmallow update the battery life seems the same if not better with lollipop also the Phone is faster. Just Do a full repair to be sure after updating it to the last Version from sonys tool.
I would unlock the bootloader and install new LineageOS,I am running it and it is amazing,camera is rock solid and performance is amazing
rdpxi said:
Thanks again
What I am hearing is that if I buy one, I can upgrade it to MMallow and all will be fine, which is kind of what I was hoping to hear.
I've spent three years with an S4 Mini, so I think the camera will be a huge step up whatever I do to it!!
R
Click to expand...
Click to collapse
S4 mini's camera is really cool ( had that phone before my z3 compact too! )
For months, I've been using the 4.4 version for my Z3 Compact, cause I sipmly find the camera tons better than Marshmallow! ( Haven't tried Lollipop, I bought the phone with Marshmallow installed! )
On Marshmallow , while you're on the viewfinder, the touch to focus function doesn't work for me! ( I have to tap on the screen to choose where I want to focus, and then use the camera dedicated button, so that the camera starts focusing, while on Kitkat, I just tap , and it focuses immidiately)
Auto focus while video recording is horrible as well, while on Kitkat the autofocus is really fast.
I even found playing GTA San Andreas smoother at 4.4.
What I want to say is that staying at old versions isn't always bad. Sometimes old is gold.
Thanks to all of you responding.
Couple of things:
1 . what do you mean by "do a full repair" after updating?
2. how difficult is doing something like fiddling wth bootloader and installing Lineage? (I probably wouldn't go that far TBH)
On the second question, and also because you're concerned about the camera, if you unlock the bootloader the phone wipes DRM keys that are needed for integration with various functionns. The camera quality will be greatly reduced, audio effects will be reduced, and some other stuff that I was never concerned with and thus don't know what they are. You can backup the DRM keys and restore them after relocking the bootloader for use on a stock ROM, which is a process you'de need to search and find out how to do and isn't too complicated at the moment, however running anything that isn't stock, Lineage, Jaguar, Cyanogenmod, etc, requires an unlocked bootloader and camera quality is going to suffer on these ROMs. Also, if you don't back up the DRM keys properly and unlock the bootloader, you're screwed when it comes to getting them back; they will be deleted forever.
As for fiddling with the bootloader and installing a ROM goes, you need to go to a Sony webpage to unlock it. This voids your warranty. You then use fastboot to install a custom recovery, TWRP usually, and flash the ROM. You can relock it using a tool called Flashtool, which is found in the Z3 compact section somewhere, but you can't use a custom ROM while the bootloader is locked nor use the full features that are included with the stock ROM and will have reduced camera quality and a sligtly distorted image; relocking the bootloader is for the purpose of using Flashtool to put a stock ROM back and restore the (hopefully backed up) DRM keys.
Keep in mind that there are stock ROMs that have been modified to have a locked bootloader, root, implement TWRP where it isn't detected by the phone (so DRM keys still work), xposed can be flashed, etc, etc.
All of this would be a little daunting for someone swithing to the phone right now because the frustrations and progress have been incremental and there isn't a really clear thread I know of that lays it all out, like Backup DRM keys like this, Unlock the Bootloader like this, Install TWRP like this, Download Flashtool here, Relock the bootloader like this, Install a Stock ROM like this, Restore DRM keys like this, Install a rooted stock ROM like this, etc. That said, if you've been on the forum for any length of time it should go okay, the main concern is backing up your DRM keys and once that is done the only concern is, like any other phone, bricking it. If you don't need root and want a good camera, then the question is if you're content with Marshmallow and the fact that there aren't any future updates, or more acurately, you can have root on Marshmallow and a good camera (the current method on the latest stock Marshmallow is the easiest its ever been to get root), but there aren't any future updates.
Hi PantsDownJedi, could you pls share the link to the safest method to get root on Marshmallow, leaving the locked bootloader untouched? Thanks!
---------- Post added at 11:04 PM ---------- Previous post was at 10:17 PM ----------
PantsDownJedi said:
On the second question, and also because you're concerned about the camera, if you unlock the bootloader the phone wipes DRM keys that are needed for integration with various functionns. The camera quality will be greatly reduced, audio effects will be reduced, and some other stuff that I was never concerned with and thus don't know what they are. You can backup the DRM keys and restore them after relocking the bootloader for use on a stock ROM, which is a process you'de need to search and find out how to do and isn't too complicated at the moment, however running anything that isn't stock, Lineage, Jaguar, Cyanogenmod, etc, requires an unlocked bootloader and camera quality is going to suffer on these ROMs. Also, if you don't back up the DRM keys properly and unlock the bootloader, you're screwed when it comes to getting them back; they will be deleted forever.
As for fiddling with the bootloader and installing a ROM goes, you need to go to a Sony webpage to unlock it. This voids your warranty. You then use fastboot to install a custom recovery, TWRP usually, and flash the ROM. You can relock it using a tool called Flashtool, which is found in the Z3 compact section somewhere, but you can't use a custom ROM while the bootloader is locked nor use the full features that are included with the stock ROM and will have reduced camera quality and a sligtly distorted image; relocking the bootloader is for the purpose of using Flashtool to put a stock ROM back and restore the (hopefully backed up) DRM keys.
Keep in mind that there are stock ROMs that have been modified to have a locked bootloader, root, implement TWRP where it isn't detected by the phone (so DRM keys still work), xposed can be flashed, etc, etc.
All of this would be a little daunting for someone swithing to the phone right now because the frustrations and progress have been incremental and there isn't a really clear thread I know of that lays it all out, like Backup DRM keys like this, Unlock the Bootloader like this, Install TWRP like this, Download Flashtool here, Relock the bootloader like this, Install a Stock ROM like this, Restore DRM keys like this, Install a rooted stock ROM like this, etc. That said, if you've been on the forum for any length of time it should go okay, the main concern is backing up your DRM keys and once that is done the only concern is, like any other phone, bricking it. If you don't need root and want a good camera, then the question is if you're content with Marshmallow and the fact that there aren't any future updates, or more acurately, you can have root on Marshmallow and a good camera (the current method on the latest stock Marshmallow is the easiest its ever been to get root), but there aren't any future updates.
Click to expand...
Click to collapse
Hi PantsDownJedi, could you pls share the link to the safest method to get root on Marshmallow, leaving the locked bootloader untouched? Thanks!
liviugi said:
Hi PantsDownJedi, could you pls share the link to the safest method to get root on Marshmallow, leaving the locked bootloader untouched? Thanks!
---------- Post added at 11:04 PM ---------- Previous post was at 10:17 PM ----------
Hi PantsDownJedi, could you pls share the link to the safest method to get root on Marshmallow, leaving the locked bootloader untouched? Thanks!
Click to expand...
Click to collapse
Recovery & Root for MM .575 & .291 LB
https://forum.xda-developers.com/showthread.php?t=3418714
Gesendet von meinem D5803 mit Tapatalk
Hi there !
So for the first time in years of ownership, I am interested in Rooting.
Naturally I searched around here, but could only find 2017 and 2018 threads with many problems and various bugs.
For an April 2020 guy, rooting is stock latest ROM, and interested in keeping stock but go rooted (mostly to block some Android trash) - What is the easiest way, can I have a link that is updated, or a paid tool I can buy and not mess with anything ?
Thanks a lot !
baboon23 said:
What is the easiest way, can I have a link that is updated
Click to expand...
Click to collapse
Crack on - https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
SXUsr said:
Crack on - https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Click to expand...
Click to collapse
Too much mess for my blood !
How much would It be to hire your service via screenshare ?
PM me please
Keep in mind I only want a root so I can disable some stock google trash with F-Droid apps.... I don't really need a new ROM, or do I ?
I rooted mine on stock just a few weeks ago.
All I did was unlock the bootloader, flash TWRP, then flash the latest magisk. I then used Titanium Backup to remove the bloat. It was quick and painless.
Thanks !
Which thread did you use as guide/link glossary ?
I didn't use a guide, just did it based on experience rooting my Sony devices from before. But I can write up something brief. How much knowledge do you have rooting devices?
baboon23 said:
Too much mess for my blood !
How much would It be to hire your service via screenshare ?
Click to expand...
Click to collapse
I wouldn't want to do it that way, and if you do it yourself you'll gain a little experience which makes restoring or further modding easier.
baboon23 said:
Keep in mind I only want a root so I can disable some stock google trash with F-Droid apps.... I don't really need a new ROM, or do I ?
Click to expand...
Click to collapse
If you want to root you need to unlock the bootloader, if you're unlocking your BL then it's advised to backup your DRM keys and restore them after unlocking your BL which is a one time process. Everything you need is in the thread I've linked to above.
Thanks SX. I have seen a lot of your work around here doing searches, and I'm honored that you reply to my question
I will have a crack at it, I have done those things before but I remember not leaving the house for a few days, so it scarred me a bit
Haha
One last question if I may.... Do you believe that installing Lineage with no google on the xz1c is worth it? I guess it's a general question, but what I'm really asking is, should I even bother with rooting for privacy if my end goal isn't to flash Lineage ?
OK, after some more research, I have decided that what I really want to do is just install the 17v LineageOS version for the XZ1C.... It is my understanding it is possible without a root. ?
For sure the bootloader needs unlocking and TWRP to backup/flash correct ?
Super SU, does that make my procedure easier in any way ?
It is my understanding that if I flash a Lineage OS after unlocking via code and flashing TWRP, then the camera and all will still work.
Considering I don't mind binning that phone if I get sick of Lineage (I have like four of those in a box) - Can I skip the TA backup and restore ?
Apologies for the newb questioning, just trying to "get the hang" of it so I actually understand what i'm doing rather than just follow guides.
I'm a bit older than all you guys so forgive me
I'm running lineage 16.1 on root with unlocked bootloader without restoring TA. But I didn't care about preserving the keys. Yes camera works great and everything is super stable.
You don't have to root lineage so if you need help best to narrow down what exactly you want to do as there are many possibilities.
betacrypt said:
I'm running lineage 16.1 on root with unlocked bootloader without restoring TA. But I didn't care about preserving the keys. Yes camera works great and everything is super stable.
You don't have to root lineage so if you need help best to narrow down what exactly you want to do as there are many possibilities.
Click to expand...
Click to collapse
Absolutely, you're right !
I will be as specific as I can:
Sony abandoned the XZ1C, so I want to swap to Lineage OS with a full heart with no Gapps (i'll manage).
Here is what I understand tell me if I am correct:
1. Unlock bootloader via sony website
2. Flash latest TWRP
3. Use it to flash 17.1 Lineage OS from the genius dude (mod punk?)
4. Happy days
5. If modpunk updates it, will I be able to update with no reformatting ?
baboon23 said:
Absolutely, you're right !
I will be as specific as I can:
Sony abandoned the XZ1C, so I want to swap to Lineage OS with a full heart with no Gapps (i'll manage).
Here is what I understand tell me if I am correct:
1. Unlock bootloader via sony website
2. Flash latest TWRP
3. Use it to flash 17.1 Lineage OS from the genius dude (mod punk?)
4. Happy days
5. If modpunk updates it, will I be able to update with no reformatting ?
Click to expand...
Click to collapse
Yep that's about right. Unlock bootloader with Flash Tool by getting unlock code from Sony. Flash TWRP in fastboot mode. Boot to TWRP and flash lineage 17.1. If you don't need gapps you're good to go.
As for lineage updates probably best to check with the thread. Usually you can dirty flash, i. e. flash new version over the old and it should be ok. Lastly check to see if they're are any major bugs with 17.1. Since it's so new there could be issues. 16.1 is smooth fast and stable if you ever need to go back to it.
betacrypt said:
Yep that's about right. Unlock bootloader with Flash Tool by getting unlock code from Sony. Flash TWRP in fastboot mode. Boot to TWRP and flash lineage 17.1. If you don't need gapps you're good to go.
As for lineage updates probably best to check with the thread. Usually you can dirty flash, i. e. flash new version over the old and it should be ok. Lastly check to see if they're are any major bugs with 17.1. Since it's so new there could be issues. 16.1 is smooth fast and stable if you ever need to go back to it.
Click to expand...
Click to collapse
Superb, thank you so much ! What a wonderful community. I feel like im stealing. I will be sure to donate !
One question, may I use adb tools for the bootloader ?
No problem. That one I'm not sure about. I've only used flash tool myself but adb tools should work with the right commands.
Yay for me !
Bootloader unlocked, onto recovery and LOS
I did it !
Thanks yall
I get this horrible " please lock the bootloader" greeting when I turn on the device, for 5 seconds.
Is that normal for everyone ?
baboon23 said:
Considering I don't mind binning that phone if I get sick of Lineage (I have like four of those in a box) - Can I skip the TA backup and restore ?
Click to expand...
Click to collapse
You've got 4 XZ1Cs in a box?
baboon23 said:
I get this horrible " please lock the bootloader" greeting when I turn on the device, for 5 seconds.
Is that normal for everyone ?
Click to expand...
Click to collapse
It is yes, you'll have to live with that unfortunately. In regards to the TA, I would have taken the time to back them up, that'll matter should you wish to return to stock. It's better to have it and not need it than to need it and not have it. But you've achieved what you wanted to which is all that matters. :good:
Thank you sir !
You're probably right, I just couldn't be bothered... Sometimes 20 minutes more is like a life long more
Well, now that all is installed....
So when modpunk stopps working on the project (like sony stopped working on the xz1) - Will it be safe to just continue using the phone without updates at all ?
Or is the eventual doom of all ROM Flashers is to come back to stock (but then, it doesn't get updates anymore also...)
So does it matter in which platform I remain outdates ?
Re the XZ1's, I knew that this was going to be the last proper small phone so I made sure to stock. I plan to carry these into 2022 …….
Problem is, I think even in box without, the batteries will die out. So I'm not sure how smart I was when I got several.
All in all, for all phones I paid less than one iPhone so I'm pretty happy, but hopefully a lab can change the batteries on them.
baboon23 said:
Thank you sir !
You're probably right, I just couldn't be bothered... Sometimes 20 minutes more is like a life long more
Well, now that all is installed....
So when modpunk stopps working on the project (like sony stopped working on the xz1) - Will it be safe to just continue using the phone without updates at all ?
Or is the eventual doom of all ROM Flashers is to come back to stock (but then, it doesn't get updates anymore also...)
So does it matter in which platform I remain outdates ?
Re the XZ1's, I knew that this was going to be the last proper small phone so I made sure to stock. I plan to carry these into 2022 …….
Problem is, I think even in box without, the batteries will die out. So I'm not sure how smart I was when I got several.
All in all, for all phones I paid less than one iPhone so I'm pretty happy, but hopefully a lab can change the batteries on them.
Click to expand...
Click to collapse
I believe it is recommended to charge lithium-ion batteries fully every other month or so to keep it healthy.
If you are rooted I recommend checking out the ACC magisk module and controller app. This allows the phone to stop charging when the battery level has reached a certain level. In the long run keeping your device charged between I think 80% - 20% will increase your battery longevity by 200% (sorry I don't remember the exact study this was from).
And I agree the XZ1c is the last proper small phone. I've rebuilt mine from one sold for parts from eBay and now it feels like new.
About the security:
If you want to you can keep a look out for specific vulnerabilities in Android after the last security patch released for the custom rom.
https://source.android.com/security/bulletin
But in general by not connecting to sketchy WiFi hotspots, being un-rooted, having se-linux on enforcing, and running af-wall (requires root permissions) or another firewall you should be good for a while.
I think it really depends on what security issues get discovered in the future and what vulnerabilities your specific use case opens you up to.
Hi guys !
What about DRM key backup ?
I need help if you have a solution
https://forum.xda-developers.com/xp...de-to-install-lineageos-17-1-scratch-t4136195
Thanks you !