Database Info

Help a Xperia noob out with some questions please :L

So this is my first xperia device since the Xperia Arc was released way back when, and I have been using HTC phones. Which are WAY different in terms of Rooting / Unlocking / Etc.
So long story short, What I want to know is what Can I currently do to the Xperia Z5? I see there's no custom ROM's yet which is expected , but I see mixed results about unlocked BootLoader & Root , the main thread says that a bootloader hasn't been achieved, yet there's a few root methods which have been successfully completed , requiring an unlocked bootloader, so naturally you could see the confusion..... Can someone point a SONY noob towards the right direction in terms of bootloader unlock / rooting? Running the E6653 ( not sure if there's variants )

Basically you currently need to unlock the bootloader to to get root. And doing so loses some features which u may possibly never get back. So most people are currently waiting for another way around to be figured out
Sent from my Xperia z5 using Tapatalk

well ****...
Ben36 said:
Basically you currently need to unlock the bootloader to to get root. And doing so loses some features which u may possibly never get back. So most people are currently waiting for another way around to be figured out
Sent from my Xperia z5 using Tapatalk
Click to expand...
Click to collapse
My heart literally dropped as I read this..... Because I already unlocked the bootloader. I'm assuming it's the bootloader unlocking that destroys some features? If so , which ones?
And how can I tell if they were actually destroyed / bootloader unlock actually worked

Unlocking the bootloader on Xperias will delete the device's DRM keys. These keys are unique per device and once gone are gone forever. They're needed for Image enhancements like X-Reality/Bravia/Super-Vivid and some camera features too - low light and noise reduction algorithms I think. Sound improvements (ClearAudio+...) too.

ricodredd said:
Unlocking the bootloader on Xperias will delete the device's DRM keys. These keys are unique per device and once gone are gone forever. They're needed for Image enhancements like X-Reality/Bravia/Super-Vivid and some camera features too - low light and noise reduction algorithms I think. Sound improvements (ClearAudio+...) too.
Click to expand...
Click to collapse
Well crap lol, is there any way to actually make sure that the DRM's were deleted or if the bootloader unlock was actually successful? I still have a few days to swap the phone out if anything goes wrong ( Bell wouldn't be able to tell a bootloader unlock ) , I haven't had enough play time with the phone before the process to actually see a difference with the camera, I read somewhere that if TrackID works, than it's not unlocked, is that true?

Looking to buy the Galaxy S7; couple questions

Hello,
I'm planning to buy this (Exynos) variant of the Galaxy S7. It has great specs and the availability of custom ROMs pleasantly surprised me. Therefore, I have some questions:
1. How do you go from full stock to being able to flash custom ROMs? Is it difficult to unlock the bootloader? I'm used to Nexus devices where you'd reboot to bootloader, fastboot oem/flashing unlock and that's it, but the procedure is certainly different on the Galaxy S7.
2. Are there any things I should be aware of? e.g. Can I brick my phone with flashing something or doing something that wouldn't brick some other phones?
3. Is it possible to return from custom ROMs to full stock? I guess I won't have KNOX back since that's a physical detail AFAIK, but I can live with it, I guess. Modded stock ROMs can also be flashed from TWRP, right?
4. I was really surprised that the Exynos variant got so much dev support. Normally I would expect that from a Snapdragon device, but the Snapdragon variant's BL is locked. How come Exynos got so much dev support and ROMs with practically no issues on this device (and some other like the Galaxy S6)? From what I've heard in the past, the Exynos phones aren't exactly the most dev-friendly ones. What has changed since? I may be completely wrong though
That's all for now.
Thanks in advance!

Fobos531 said:
Hello,
I'm planning to buy this (Exynos) variant of the Galaxy S7. It has great specs and the availability of custom ROMs pleasantly surprised me. Therefore, I have some questions:
1. How do you go from full stock to being able to flash custom ROMs? Is it difficult to unlock the bootloader? I'm used to Nexus devices where you'd reboot to bootloader, fastboot oem/flashing unlock and that's it, but the procedure is certainly different on the Galaxy S7.
Click to expand...
Click to collapse
You need to flash TWRP custom recovery (Instructions in the TWRP thread)
Unlocking the bootloader is a simple toggle switch in developer options
Fobos531 said:
2. Are there any things I should be aware of? e.g. Can I brick my phone with flashing something or doing something that wouldn't brick some other phones?
Click to expand...
Click to collapse
Always a risk, make sure to read up thoroughly before flashing anything
Fobos531 said:
3. Is it possible to return from custom ROMs to full stock? I guess I won't have KNOX back since that's a physical detail AFAIK, but I can live with it, I guess. Modded stock ROMs can also be flashed from TWRP, right?
Click to expand...
Click to collapse
Once KNOX is tripped that's permanent, but you can return to stock using ODIN and a stock ROM from sammobile or other sources scattered around the forum

*Detection* said:
You need to flash TWRP custom recovery (Instructions in the TWRP thread)
Unlocking the bootloader is a simple toggle switch in developer options
Click to expand...
Click to collapse
So, to unlock the bootloader, I literally have to toggle "Enable OEM unlock" in developer options? That's it? I'll have this switch regardless if I'm on Marshmallow or Nougat, right?

Fobos531 said:
So, to unlock the bootloader, I literally have to toggle "Enable OEM unlock" in developer options? That's it? I'll have this switch regardless if I'm on Marshmallow or Nougat, right?
Click to expand...
Click to collapse
Correct
Don't make the same mistake a few members have, and disabled it once they had TWRP installed, you need to leave it unlocked while you are running custom

*Detection* said:
Correct
Don't make the same mistake a few members have, and disabled it once they had TWRP installed, you need to leave it unlocked while you are running custom
Click to expand...
Click to collapse
I've never wanted to try this, but I'm curious. What happens if you toggle it back? Bricks the phone?

Beanvee7 said:
I've never wanted to try this, but I'm curious. What happens if you toggle it back? Bricks the phone?
Click to expand...
Click to collapse
It gets stuck trying to boot with custom binary blocked errors iirc
Then you need to spend time working out how to bypass the lock and reflash stock etc

If i was you then i would keep the s7 with the stock rom because this stock rom is pretty awesome and i like having the secure folder functions etc.

Question [Q] Why do we need to unlock the bootloader before rooting?

hi! so i just bought my rog phone 5, coming from xperia z (yeah i know). so based on my experience using xperia phone, rooting doesnt require unlocked bootloader, right? or did i just forget it coz im using custom roms?
im just not ready to unlock the bootloader and I WANT ROOT. theres so many ads

kal27 said:
hi! so i just bought my rog phone 5, coming from xperia z (yeah i know). so based on my experience using xperia phone, rooting doesnt require unlocked bootloader, right? or did i just forget it coz im using custom roms?
im just not ready to unlock the bootloader and I WANT ROOT. theres so many ads
Click to expand...
Click to collapse
AFAIK, unlocking bl is a prerequisite for rooting. Or else, the device wouldn't be able to execute 'fastboot flash' or 'fastboot boot' adb commands.
As for the ad issue, try 'dns.adguard.com' w/o quotes as private dns address (dns over tls).

because you need to modify the boot partition by flashing the patched boot. hence it has to be unlocked. otherwise you will not be able to flash the patched boot.
as simple as this.

By default, the bootloader only supports official signed images from the manufacturer. Since no engineering bootloader is available and we don't have the signing tools, the next best thing is to disable the restriction.

thanks everyone! this sure cleared things up. anyway is there a available custom rom? like cyanogenmod for phone 5?

kal27 said:
thanks everyone! this sure cleared things up. anyway is there a available custom rom? like cyanogenmod for phone 5?
Click to expand...
Click to collapse
Still needs a proper device profile for that stuff

How To Guide Rooting the SM-F711B (on Version F711BXXU2AUI4) working

First of all:
I'm no Dev...just someone who likes to play lego.
From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.
I've read a good startup here.
Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.
(https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
(1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)
Anyways...here are maybe small hints to avoid a few traps.
a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
There appears a possibility of choice.
Press VolUp short: get the mobile on standby to flash the rom via odin.
Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
Of course this can possibly be done via adb/fastboot commands.
Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.
b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
Flashing the tar back to the mobile via odin was little bit tricky.
It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
I had to patch it to BL too.
Cheers
MikGx

When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.

@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2

MikGx said:
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
Click to expand...
Click to collapse
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.

naldotech.com, the link you provide is pretty clear about the process. What it doesnt say is what to do at the end. When you untick "reboot" in odin, and you finish flashing, your phone will stay in download mode. Then what to do?. Press power and volume down to leave and restart the phone? or, power and volume down, screen goes black imediately power and volume up, enter recovery and restart from there.? please someone ?

Press the power and volume down buttons for about 7 seconds and it will reboot

beanbean50 said:
Press the power and volume down buttons for about 7 seconds and it will reboot
Click to expand...
Click to collapse
I did as you mention but it didnt work. It made me reset the system. But I Fallowed the naldotech.com guide. At the end, being in dawnload mode, I pressed power and volume down, when the screen got black I pressed power and volumen up, I entered recovery mod, cleared cache and re- started the system: Voila my phone is rooted

Hello.
Can someone pleas provide a working link for frija download? The one referring from naldotech seems to be broken (https://www.naldotech.com/download-samsung-galaxy-stock-firmware-frija-tool/)
Update: Found a link via google -> https://technastic.com/odin-download-samsung-latest-all-versions/

twistedumbrella said:
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
Click to expand...
Click to collapse
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.

d0x360 said:
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
Click to expand...
Click to collapse
twistedumbrella said:
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
Click to expand...
Click to collapse
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.

twistedumbrella said:
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
Click to expand...
Click to collapse
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.

d0x360 said:
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
Click to expand...
Click to collapse
You got where I said "I guess the disclaimer is misleading" right?

twistedumbrella said:
You got where I said "I guess the disclaimer is misleading" right?
Click to expand...
Click to collapse
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons

d0x360 said:
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
Click to expand...
Click to collapse
Lucky? I dunno. Had I known it would cause this much trolling, I wouldn't have bothered to mention it.

I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?

david.siebauer said:
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
Click to expand...
Click to collapse
Partially. I just did that: I have AfWall running on my old phone, tried to unlock the Flip with this manual here in order to use the firewall there, did something wrong - and stumbled upon Netguard while searching what might have happened and decided to give it a try first. (Unless there is a custom ROM for the phone available, I have no other need for root or an unlocked bootloader.)
From what I could find on my Flip 3, you can unlock and relock the bootloader as you like - but as soon as you install a non-genuine bootloader (i.e. one chnaged by Magisk) you will trip Knox - and this cannot be reverted.
In such a case you can still re-lock your bootloader and unlock it later (on my phone, that "7-day-no-switch-indeveloper-options" routine kicked in, but you can circumvent that) - but Knox will stay in its state. From what I read this means some things will not work such as Samsung Pay, but I do not know the details (yet) apart from that it does not bother me ;-), and the nag screen during boot is gone.

Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now

david.siebauer said:
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
Click to expand...
Click to collapse
Well, it's better than my Sony - there it is "once unlocked, always unlocked" with no way back at all
But I have to admit I understand the logic why the manufacturers do that, at least to the degree that they trip a fuse as Samsung does.
By rooting the phone, you shift the responsibility for the software state of the phone from the manufacturer to the user, so I think it is okay to implement something to make it clear to possible future buyers that it is or has been in that state.
(This does not include however all the other stones they put in the way of people wanting to develop or use custom ROMs!)

I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features. Guess u shouldn't have bought a Samsung lol.

david.siebauer said:
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features.
Click to expand...
Click to collapse
Oh, trust me - as soon as I hear there is a custom ROM that works as a daily driver I will root mine as well. I really hope that there will be one for this phone
david.siebauer said:
Guess u shouldn't have bought a Samsung lol.
Click to expand...
Click to collapse
Sadly there is no Fairphone mini or Fairphone Flip - or would it be Fairfliphone? ... Flipfairphone?... - yet (if ever), so the only current alternative would be Motorola. And the price tag for the Razr is simply too much, even if I personally think it looks better than the Samsung. Additionally, I do not know if they are in any way better when it comes to rooting or loading custom ROMs.

BL unlocking/custom ROM Question: What is permanently lost if I do that?

Hi,
Just grabbed an Xperia 5 II on a great deal and I'm loving this device. It's an A002SO. I have noticed in other threads that there is some loss with original functionality of the phone (maybe Dolby or some other features are broken even if phone is restored to stock). Is it true? And if so what features are broken.
I noticed that Xperia camera software are available for other roms too which is great but what about device fingerprint and BL unlock sensing protection for banking apps? (I am not interested in rooting the phone after flashing lineage/AOSP roms but more concerned about the broken safety net in-case I go custom ROM route)
Also, is there a risk of losing IMEI with all this process? Not talking about crossflashing here but would love an AIO guide about BL unlock > recovery > ROM and the Back to stock locked bootloader guides if there are any.
Thank you!

dark_prince said:
Hi,
Just grabbed an Xperia 5 II on a great deal and I'm loving this device. It's an A002SO. I have noticed in other threads that there is some loss with original functionality of the phone (maybe Dolby or some other features are broken even if phone is restored to stock). Is it true? And if so what features are broken.
I noticed that Xperia camera software are available for other roms too which is great but what about device fingerprint and BL unlock sensing protection for banking apps? (I am not interested in rooting the phone after flashing lineage/AOSP roms but more concerned about the broken safety net in-case I go custom ROM route)
Also, is there a risk of losing IMEI with all this process? Not talking about crossflashing here but would love an AIO guide about BL unlock > recovery > ROM and the Back to stock locked bootloader guides if there are any.
Thank you!
Click to expand...
Click to collapse
I have a different model, but I recently went from stock to Lineage OS, then back to stock. I haven't had any issues. Dolby works, my data/LTE works, and I can still use my banking app just fine. Fingerprint detection was a bit more finnicky with Lineage OS, though.
I should also note, I'm currently rooted with my bootloader unlocked, and still no issues.

SomeRandomGuy212 said:
I have a different model, but I recently went from stock to Lineage OS, then back to stock. I haven't had any issues. Dolby works, my data/LTE works, and I can still use my banking app just fine. Fingerprint detection was a bit more finnicky with Lineage OS, though.
I should also note, I'm currently rooted with my bootloader unlocked, and still no issues.
Click to expand...
Click to collapse
I gave up in the end because my device is Japan Softbank with bootloader unlocking not allowed. Crossflashing instructions have alot of "you can", "I think" but no definite root-to-fruit guide so I may convert it to global model and BL unlock without losing imei / 4G. Thank you for taking time to write the clarification.

dark_prince said:
I gave up in the end because my device is Japan Softbank with bootloader unlocking not allowed. Crossflashing instructions have alot of "you can", "I think" but no definite root-to-fruit guide so I may convert it to global model and BL unlock without losing imei / 4G. Thank you for taking time to write the clarification.
Click to expand...
Click to collapse
I don't actually know if that would work... I don't mean to give you another indefinite answer, but I tried that once on a Japanese Xperia 10 II. I know it's a different device, but it may still apply in your situation. I would still try it, though. Worse case scenario, you have to use Sony's repair tool to get back to stock.
(Also, if you're interested in a non Japanese model, I am currently selling my 5 II.)

SomeRandomGuy212 said:
I don't actually know if that would work... I don't mean to give you another indefinite answer, but I tried that once on a Japanese Xperia 10 II. I know it's a different device, but it may still apply in your situation. I would still try it, though. Worse case scenario, you have to use Sony's repair tool to get back to stock.
(Also, if you're interested in a non Japanese model, I am currently selling my 5 II.)
Click to expand...
Click to collapse
I am from Pakistan so it's gonna cost me double the actual price to pay customs taxes and get it cleared for use in-country. Our country has a rule about only the devices which are approved after paying hefty taxes, are permitted on Pakistan's cellular operators.

This was discussed before, in short you seem to lose out certain manufacturer keys and your phone remembers you have unlocked its bootloader before. As for functionality, iirc they seem to come back after relocking.
More info: https://forum.xda-developers.com/t/closed-delete.4177209/post-87242833