Ok, so I have this nearly new Z3+/Z4 (E6553 single SIM) and I'm looking to do some experimentation. I'm not quite that familiar with Sony smartphones (this is my first) while I come from a background of owning dozens of Samsung, LG, Motorola, and other brands. My main question is this:
I've already requested the bootloader unlock code and got it (haven't actually used it yet so the phone is still "clean" at the moment), but I did use the Sony software to do a full flash of the clean latest firmware (185, Android 6.) and it works great but I'm itching to do some playing around with it and see what's possible.
If I unlock the bootloader does that mean - on this particular device - that I can (if I can locate the firmware) roll it all the way back to the shipping firmware which I believe is Android 5.0.2 with build number 28.0.A.6.8) without any hassles or major issues or, is there something going on with the bootloader (like other devices) that once upgraded to a specific version of bootloader you're blocked from that kind of a rollback?
Also, while I've never compiled firmware or a ROM myself over the past two decades, I'm thinking about giving it a go with this Xperia device because Sony provides all the info needed, at least I think they do. It would be an interesting use of my time to learn something new but the question about that is mainly this:
It says it's AOSP which should be the pure untouched Android experience but then I see Sony has some binaries they have posted so I'm wondering if those are "the bloatware" and can they be dismissed and not used or are those binary files necessary because they're what allows AOSP to run properly with hardware support on the Z3+/Z4 as one might expect?
And of course last question: knowing I can relock the bootloader (fastboot oem lock, probably, will have to look into that) I presume I'd be able to use that Sony tool to get it back to the latest build doing the repair option if necessary, right?
If anyone can offer any suggestions or feedback it would be greatly appreciated, thanks.
Have fun, always...
br0adband said:
Ok, so I have this nearly new Z3+/Z4 (E6553 single SIM) and I'm looking to do some experimentation. I'm not quite that familiar with Sony smartphones (this is my first) while I come from a background of owning dozens of Samsung, LG, Motorola, and other brands. My main question is this:
I've already requested the bootloader unlock code and got it (haven't actually used it yet so the phone is still "clean" at the moment), but I did use the Sony software to do a full flash of the clean latest firmware (185, Android 6.) and it works great but I'm itching to do some playing around with it and see what's possible.
If I unlock the bootloader does that mean - on this particular device - that I can (if I can locate the firmware) roll it all the way back to the shipping firmware which I believe is Android 5.0.2 with build number 28.0.A.6.8) without any hassles or major issues or, is there something going on with the bootloader (like other devices) that once upgraded to a specific version of bootloader you're blocked from that kind of a rollback?
Also, while I've never compiled firmware or a ROM myself over the past two decades, I'm thinking about giving it a go with this Xperia device because Sony provides all the info needed, at least I think they do. It would be an interesting use of my time to learn something new but the question about that is mainly this:
It says it's AOSP which should be the pure untouched Android experience but then I see Sony has some binaries they have posted so I'm wondering if those are "the bloatware" and can they be dismissed and not used or are those binary files necessary because they're what allows AOSP to run properly with hardware support on the Z3+/Z4 as one might expect?
And of course last question: knowing I can relock the bootloader (fastboot oem lock, probably, will have to look into that) I presume I'd be able to use that Sony tool to get it back to the latest build doing the repair option if necessary, right?
If anyone can offer any suggestions or feedback it would be greatly appreciated, thanks.
Have fun, always...
Click to expand...
Click to collapse
1- In 99% percent of cases, which includes this phone, Sony does not have a mechanism that blocks a roll back of the firmware. Of course Sony would officially tell you that once you upgrade you cannot downgrade but they (and everyone else) knows that is not true. You just need to find what's known as an ftf file for your firmware of choice and use the unofficial flashtool (not Sony's) to flash it on your device. It is important for you to know that the bootloader DOES NOT have to be unlocked for flashing Sony's unmodified stock firmware.
2- Xperia firmware is not fully AOSP but it is as close as you can get to it. There is no bloat in Sony's code and even if you consider some of it bloat they are normally removable. There are certain hardware and software provisions specific to Sony (which honestly a lot of people, myself included, find useful) such as the stamina mode, which you do not have in AOSP. So if you want to do your own ROM, start with Sony's code.
3- Unlocking bootloader is irreversible in some sense. If you decide to do it, I suggest you read this post carefully in advance: http://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
najoor said:
1- In 99% percent of cases, which includes this phone, Sony does not have a mechanism that blocks a roll back of the firmware. Of course Sony would officially tell you that once you upgrade you cannot downgrade but they (and everyone else) knows that is not true. You just need to find what's known as an ftf file for your firmware of choice and use the unofficial flashtool (not Sony's) to flash it on your device. It is important for you to know that the bootloader DOES NOT have to be unlocked for flashing Sony's unmodified stock firmware.
2- Xperia firmware is not fully AOSP but it is as close as you can get to it. There is no bloat in Sony's code and even if you consider some of it bloat they are normally removable. There are certain hardware and software provisions specific to Sony (which honestly a lot of people, myself included, find useful) such as the stamina mode, which you do not have in AOSP. So if you want to do your own ROM, start with Sony's code.
3- Unlocking bootloader is irreversible in some sense. If you decide to do it, I suggest you read this post carefully in advance: http://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
Click to expand...
Click to collapse
Nice Reply + very good.
Thanks for the reply, the information could prove useful to another member in the future, but I sold the Z3+ pretty much the next day, honestly.
Hello everyone,
I have to say I am completely lost regarding the whole rooting process for the XZ1C. I usually manage to get where I want just by carefully reading the forums, but with this device, I feel overwhelmed by information. And I sometimes feel like what I am reading contradicts what I though I understood from previous reads...
I will try to sum up what I know so far.
First of all, I have a just-out-of-the-box Sony model G8441 with firmware 47.1.A.12.179 / Oreo 8.0.0 (never been connected to the outside world yet), and I want to properly root the device and install TWRP with no loss of feature.
What I think I understand:
To root, I first need to unlock the bootloader, which seems to be a trivial operation. However, this will break some functionalities due to DRM keys being erased. Once it is done, there is no way, ever, to get them back. There are however ways to "trick" DRM-related functionalities into believing DRM keys are still there.
Alternatively, there seems to be a way to backup the DRM keys prior to unlocking the BL, and this backup can somehow be reused and injected back into the unlocked device. If true, then this would certainly be a preferable method than the previous one, which would then be obsolete. However, it obviously doesn't look obsolete when I read the related topics, so I must be missing something...
Another thing I noted (but do not quite understand): There are ROMs for this device that "include" a DRM fix.
Last important thing I read: there is a paid "do-it-all" tool which takes my locked device and, with one click, makes it unlocked - rooted - DRM-fixed - TWRP-enabled. Now that sounds really good! Maybe too good?
As far as i know (but I learn new stuff every day on this topic) this DRM stuff is the main difficulty here. I understand that the rest of the process (root + TWRP) will be much simpler (although I'm old-school and completly missed all this magisk trend...!)
What I don't understand:
I read that some people downgrade to Oreo to be able to root properly, and at the same time, I read that Pie removed the restrictions on unlocked bootloader. So I still have no idea if I should connect and receive Sony updates, or avoid them.
Another thing I don't get, is how many ways do we have to root this thing? In the past, I was used to see, for a specific device, always one major and widly used rooting method. Here I fail to identify it...
What I think I will do:
1. Backup TA partition with j4nn's tool. This will probably imply flashing an older firmware right? Is there any link that could help me with this flashing process? (I only know Odin - did I mention old-school?) I saw this page for generic sony Z devices, but the thread is from 2013 and now closed. Is it still up-to-date or is there a newer thread?
2. Unlock bootloader and restore TA partition.
3. Wait for Sony updates? Or should I first hide unlock status?
3bis. Alternaltively to waiting for updates, maybe I can just flash the latest build? (47.2.A.8.24 if I am not mistaken)
4. Flash modpunk's TWRP.
5. Flash janjan's Boot.img to get root functionalities?
Alternaltively to all the above (except maybe step 1 that I will probably do in any case), buy the paid all-in-one tool (Xperifix), plug, click and wait... But will I really end up the same as with the manual way?
I saw a few other methods in the forums but it seems my brain is currently refusing to bring them back...
That's all I have right now. I would really appreciate if you guys could share some insight and tell me what you think about this, whether there are missing steps, useless steps, incorrectly ordered steps, silly steps, or if I'm just completely wrong about the whole thing.
Feel free also to correct me on the assumptions I made at the beginning.
Thank you very much for reading this repulsive piece of text.
SunJu22 said:
I would really appreciate if you guys could share some insight and tell me what you think about this
Click to expand...
Click to collapse
By the looks of it you have done a great deal of research on the project.
Yes, go down the route of backing up your TA partition first, but that is not a small step in itself, it's pretty complicated and if you get that working then the rest of the project will be a breeze.
You don't say what version of firmware you want to end up on. If you want to end up on Pie then forget the DRMfix . But if you're staying on Oreo and can't be bothered with lots of files & flashing, then this is the easy way out, I bought the paid version and can verify it works.
More recently I ended up janjan's kernel (Oreo build). Hidden root (Google Pay works), lots of performance tweaks, DRM completely working.
It's unlikely that anyone will bother making a DRM fix for Pie as the camera works and there are only a couple of other features that get disabled.
It sounds like you're not the sort of person who's only going to read the first couple of pages of a thread (or the last) flash the xxxxxx and then complain when it's broken.
The people on the forum here are very helpful and if you go into any of the threads you mentioned in your post with a question, you'll get a reply.
Good luck.
I agree, there is a lot of information out there and different methods of achieving what you want - very confusing if you have not been following the threads since the beginning.
In my opinion, the preferred method is j4nn's method outlined here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Use that post as your main guide (the final step in that guide, #13, is how you will achieve root). You will use Newflasher to flash the various firmwares along the way (this is linked from j4nn's procedure in step #2). User munted made a very detailed pdf file that fills in some of the details on j4nn's procedure - see the following post and download the pdf attached: https://forum.xda-developers.com/showpost.php?p=78255334&postcount=382
Most of the other methods out there came before j4nn's work - they didn't include DRM backup/restore.
If you follow j4nn's procedure, you won't need to use the janjan kernel as you assumed - janjan method is different and does not overlap with j4nn.
SunJu22 said:
Feel free also to correct me on the assumptions I made at the beginning.
Click to expand...
Click to collapse
Sorry, I didn't point out that I was one of the early 'jumpers' who unlocked their bootloader without any backups, so I have been forced into always using fixes and all the information I have is based on having to fix your phone for it to work, but that's all changed now. I'm so out of date :-/
@camaro322hp is right, if you follow j4nn's method correctly you'll be rooted with no DRM loss. All of the other stuff is not required.
Thank you Digesteve and camaro322hp for your help.
From what I understand the XZ1C didn't get as much love as other devices, thus there was a long period of tinkering before a "do-it-all guide" could be considered "the" solution. That could explain all these different approaches that are proposed. Like you said camaro322hp it's rather difficult to jump on this train, and I can only guess how interesting this ride has been.
Anyway, I didn't see that the TA backup thread from j4nn also encompassed all the information I needed; I am glad to finally know that there is indeed a centralized "do-it-all guide" . To make it easier for XZ1C newcomers, I think j4nn should update his opening post to make this clearer.
Since I managed to grab the attention of 2 XZ1C power users, I would like to ask you: Did you keep stock? Did you try alternative ROMs? Do you like some of them? Do you prefer Oreo or Pie?
For information, the most up-to-date experience I have on a Android phone is my LG90 with CyanogenMod 11 (KitKat 4.4.4! Yes sir!). I heard that it's becoming less and less useful to flash a custom ROM due to major OS improvements, but I would still enjoy the simplest and lightest Android possible.
SunJu22 said:
Did you keep stock? Did you try alternative ROMs?
Click to expand...
Click to collapse
I've always been on stock, the camera is an important part of what I want from my phone and although there's lots of alternative camera apps, there's no competition to the stock camera app. Then I theme it black with swift installer and just uninstall or freeze any apps I don't want with Titanium Backup. I have stuck with Oreo, everything works perfect and I remember seeing so many people jumping to 9 then wanting to go back to 8 because they didn't like it. Something about changing the way the drop down menu works, among other things, but having never installed it, I'm not the person to comment on if it's any good or not.
I have been watching the XZ1c thread and Lineage is gaining ground, it even has a stock camera now. I would have thought something like that with miniGapps is going to be pretty lightweight and very similar to your carbon rom of before. At the moment this is based on 8, but is working well. Depends how keen you are to move to Pie.
Thank you Digesteve.
One thing I still don't understand. Part of the process is to hide unlock status. If I do this, FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
@SunJu22 I've stuck with the Sony ROM. A rooted stock ROM meets all my needs, so I've never felt the need to experiment with custom ROMs. There are some custom options out there that people seem fairly happy with, so if that's your thing, I'd encourage it.
Without going into too much detail, I'm still on Oreo for the moment, for a variety of reasons, but I don't know of anything that would keep me from recommending Pie.
One thing you should note is that once you unlock, there is no going back. AFAIK there is no known or working method to relock the bootloader.
SunJu22 said:
FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
Click to expand...
Click to collapse
Yes, I'm not entirely sure why having your rooted phone try and update itself is an advantage, but something I'd recomend avoiding.
Stock camera is the Sony camera, yes.
Thank you everyone, I believe I now have enough information to jump into this with confidence. The adventure begins, and will be reported in this thread for future reference, in the hope that it will help others like me!
Well, I am a bit sad... I wanted to report my "adventure" here in detail, but I'm afraid I have nothing to say.
Indeed, following the procedure from j4nn with a printed copy of munted's awesome guide, I managed to do all I wanted on the first attempt.
I don't have anything to add to this guide, everyone wanting to root their XZ1C can do it just by reading the opening post from j4nn and the mentioned guide. It takes a bit of time but nothing complicated thanks to the clear and detailed explanations.
I now have a fully functional rooted XZ1C (including camera) on Pie with Magisk root and TWRP.
Thank you all again from pointing me to the right direction.
I however have a slight disappointment. I wanted to start with Oreo and make an Nandroid backup before moving to Pie, but I didn't find Oreo builds on Xperifirm. So I jumped straight to Pie.
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea?
Last but not least: I looked for the latest Oreo build version number but couldn't find it. Do you guys know what it is and where I can download it?
I guess this will be all for this thread after this. Although it is very convenient to have my own thread to ask questions rather than finding the relevant page for each one, I don't want to annoy you too much...
EDIT: Please ignore the last question. I found out last Oreo build is 47.1.A.16.20, and I found the files via the download link in the opening post of the Lineage thread.
SunJu22 said:
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea? Lineage thread.
Click to expand...
Click to collapse
There is an easy solution to downgrade:
Newflasher
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
mEREHAIGE said:
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
Click to expand...
Click to collapse
No, you can flash a kernel to hide the bootloader unlock flag, this will mean that you will receive OTA updates, although depending on how you're rooted an update will most likely break your phone, so not that useful.
*made a thread*
Thanks--rooted withOUT adventure too
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
kirkzp said:
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
Click to expand...
Click to collapse
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
kernel with hide-unlock
T_Tank said:
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
Click to expand...
Click to collapse
Full disclosure: I don't use Google pay or too many banking apps, so YMMV. But, I am using j4nn's kernel with unlock hidden. (See link in my note 6.) You can flash this, or you can leave in your stock kernel and merely fastboot to this. From what I have seen, it hides most - if not all -- indicators that the phone is rooted and the BL in unlocked.
Does somebody has :
G8441_1310-7123_47.1.A.16.20-R7B_Customized_CE1.ftf ?
Only backup i did not make, and its gone from XperiFirm.
Still have the feeling battery life was better in Oreo, and would be nice for experimenting.
Would be nice.
Thanks in advance.
Is it possible to unlock?
At this moment, no.
You will know as it'll be reported here very early. There are some third party companies that do it. Some are cheaper than others.
For the moment, there is nothing..
Sucks I know
I asked this before on another similar thread and didn't get a response. Is it possible to dump the bootloader from either an unlocked or locked phone to analyse it for potential vulnerabilities either in how it handles the unlock code, or more generally that would allow a user to soft-mod unlock the phone? I know for the 5th, 7th, and 9th gen Fire 7 tablets exploits were found in the LK part of the bootloader which eventually allowed for a customised version of TWRP to be flashed onto the devices, and later LineageOS. If we could dump the current Huawei bootloader surely we could try to find if there are any similar exploits?
I am found metod but it needs mrt dongle((
Tbh custom roms aren't really important anymore. Google is already ruining android everytime a new update comes around, like the overlay feature that was introduced in oreo but then removed for no reason.
Besides EMUI is already optimised for the chip so, again, no reason for custom roms and/or rooting (unless you want to remove bloatware but that can be solved via ADB)
The Restless Soul said:
Tbh custom roms aren't really important anymore. Google is already ruining android everytime a new update comes around, like the overlay feature that was introduced in oreo but then removed for no reason.
Besides EMUI is already optimised for the chip so, again, no reason for custom roms and/or rooting (unless you want to remove bloatware but that can be solved via ADB)
Click to expand...
Click to collapse
I am need it for root and lineage os
Is it possible to downgrade from 13 to 12? I think the upgrade messed up my camera. Or maybe a way to reflash the camera firmware?
If the bootloader wasn't updated you can roll it back.
How can I find out if it was updated? I have a US unlocked phone. Its updated from 11 to 12 and now to 13.
See this thread, different models but the same information applies.
blackhawk said:
See this thread, different models but the same information applies.
Click to expand...
Click to collapse
This is the build I'm on now:
RedCrane3 said:
This is the build I'm on now:
Click to expand...
Click to collapse
Hello good morning
Of course, it can be downgraded, as long as the binary number is the same... example in the image.
The bootloader version is 9 so for you to roll back that build number's 5th digit from the end needs to be the same or higher.
With stock Snapdragon's locked bootloader it's easy to get locked into an OTA upgrade you don't want if it updates the bootloader too. I have two N10+'s, one running on 9, the other 10 (can't be rolled back to 9). That's what they were loaded when bought new. They will likely remain on those versions for their service lives as they are running well. I prefer Pie though.
I could be running Android 11 or 12 but I blew them off mostly because of the scoped storage bs.
The first thing I disable is OTA updates, once bitten twice shy. Had a S4+ that got screwed up by a OTA update that couldn't be rolled back... it sucks.
Thank you guys for helping me with all of this information. I guess I have a decision to make.
I can try to rollback to Android 12 in the hopes that will fix my camera issue, or I can sit tight and hope that a future update will resolve it.
Either way, I'm beginning to regret allowing OTA updates.
I really love the hardware of this phone, especially the screen, but its not important to me to have the latest Android (security updates are important though).
I originnaly submitted the problem to Samsung through their members app and the tech who looked at it said he *thought* it was a hardware issue, but come on, what are the chances that the one camera stops working right after the update to 13 and OneUI 5? I take very good care of my phone and never drop it (certainly didn't recently, after the update), there's not a scratch on it.
I suppose its possible, but it would be an incredible coincidence...
The tech suggested I visit a service center (which for me would be a Best Buy, yikes) or call their support 800 number, but what are they going to be able to do that the tech couldn't?
I just don't know if I can trust their initial assessment - no one knows everything, and plenty of people give up on a problem and pass it off the first trouble they run into. Maybe the tech just wasn't interested in digging deeper? A quote from their answer:
"Chi request is getting timed out. Read wide camera sensor seems to be not responding to requests [...]"
I guess my question is: can a downgrade to 12 even fix the issue?
Should I wait for another update?
Or should i just heave Samsung over the side and try to install a custom ROM?
Thanks again for all your help.
You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.
blackhawk said:
You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.
Click to expand...
Click to collapse
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.
RedCrane3 said:
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.
Click to expand...
Click to collapse
That refers to the carrier not bootloader I think. Not sure about your specific model's bootloader.