Database Develop

[Q] Change SKU from CN to US or WW, how?

Hi kids, as per title, my issue is quite simple: I (unfortunately) live in China, and my pad came with CN firmware. I realized that it also came with no gapps installed, and that's a bummer. I'm about to root it, so I'll be able to install gapps as system apps manually one by one, but that's a huge waste of time and it's not an elegant solution, too.
This said, how can I -SAFELY- change my SKU version from CN to WW or US? After rooting, can I do the manual update procedure and put the unzipped FW from Asus in the microsd card etc etc? Or is there some other way?
P.S. I'm not planning to install any recovery at the moment: I actually received my pad last week, and I hard-bricked it in 30 minutes following the recovery install guide in the dedicated thread (too lazy to link it now, but it's just out there in the other forum - I didn't follow the now locked one, I followed the other one, where so many people seemed so happy with the result -__-). Luckily either the seller of my tab or the asus service desk he sent the tablet too were too dumb to realize I dabbled with it... and they restored the system for free although you could see UNLOCKED on the screen at boot anyhow that's why I'm NOT installing recovery now, not until there's a tested "official" version I can just slap in with ROM Manager. So, do I need a recovery to change my CN to WW or US? Or it can be done some other way?
Cheers!

UoMoTaLpA said:
Hi kids, as per title, my issue is quite simple: I (unfortunately) live in China, and my pad came with CN firmware. I realized that it also came with no gapps installed, and that's a bummer. I'm about to root it, so I'll be able to install gapps as system apps manually one by one, but that's a huge waste of time and it's not an elegant solution, too.
This said, how can I -SAFELY- change my SKU version from CN to WW or US? After rooting, can I do the manual update procedure and put the unzipped FW from Asus in the microsd card etc etc? Or is there some other way?
P.S. I'm not planning to install any recovery at the moment: I actually received my pad last week, and I hard-bricked it in 30 minutes following the recovery install guide in the dedicated thread (too lazy to link it now, but it's just out there in the other forum - I didn't follow the now locked one, I followed the other one, where so many people seemed so happy with the result -__-). Luckily either the seller of my tab or the asus service desk he sent the tablet too were too dumb to realize I dabbled with it... and they restored the system for free although you could see UNLOCKED on the screen at boot anyhow that's why I'm NOT installing recovery now, not until there's a tested "official" version I can just slap in with ROM Manager. So, do I need a recovery to change my CN to WW or US? Or it can be done some other way?
Cheers!
Click to expand...
Click to collapse
Not sure if you can, but if you could i think the only way would be to an offical Asus ROM with a different SKU manually via fastboot. But since you already had problems installing a custom recovery this might not be for you.
I think remembering when i owned the TF300 and Jelly Bean (or was TF101 with ICS?) came out that the only way at first was to flash the US-version of the ROM (since WW wasn't out yet). Which is what i did and i hadn't any problem. A week or so later when the WW version came out I went back to WW.
But i'm really not certain anymore. Maybe someone else knows if it's possible or not.

Not possible
Sent from my SGH-T889 using XDA Premium 4 mobile app

actually it is if rooted and have cwm or something.
it will let you flash any firmware. though there are risks of bricking.
I did the same on my old acer was an AU now it`s ww because ww had less bloat ware and the 4.1 had been out for 2 months and au didn`t get it and i was impatient

malos1984 said:
actually it is if rooted and have cwm or something.
it will let you flash any firmware. though there are risks of bricking.
I did the same on my old acer was an AU now it`s ww because ww had less bloat ware and the 4.1 had been out for 2 months and au didn`t get it and i was impatient
Click to expand...
Click to collapse
flashing official firmware for a different SKU will cause issues

AngryDinosaur said:
flashing official firmware for a different SKU will cause issues
Click to expand...
Click to collapse
only if the hardware is different i.e. dock jpn has diff buttons. some brands have diff wifi hardware depending on region etc.
however in the case of au and ww acer the tab is the same besides pre-loaded bloatware.
as is the case for most of the versions of tf701. cn jp and TW would probably not be wise to go to ww or us due to the dock but i can`t be certain.
It might just mean the language ime buttons won`t function but it might also mean the dock won`t function at all.

malos1984 said:
only if the hardware is different i.e. dock jpn has diff buttons. some brands have diff wifi hardware depending on region etc.
however in the case of au and ww acer the tab is the same besides pre-loaded bloatware.
as is the case for most of the versions of tf701. cn jp and TW would probably not be wise to go to ww or us due to the dock but i can`t be certain.
It might just mean the language ime buttons won`t function but it might also mean the dock won`t function at all.
Click to expand...
Click to collapse
I'm pretty sure i did it, but i didn't have a dock, so it was the tablet only. Didn't run it that long either, like 3-4 days, so maybe it was too short to see what didn't work anymore...
I was trying to find back the post here on XDA, but i think it has been rewritten when the WW-version came out.

What's beneficial to flash a different sku Rom?
Sent from my SGH-T889 using XDA Premium 4 mobile app

Benefit is that on CN SKU I got no gapps and in return I got a boatload of chinese crapware. No google play. No maps. No gmail.
I'm actually struggling with the vendor to take it back, since as it is now, it's actually nothing more than a paperweight:
-Bootloader can't be unlocked, since the unlock software calls home to Asus, and my SN is not recognized.
-Since bootloader is locked, I can't root.
-Since I can't root, I can't install Gapps, I can't do basically anything.
Would a working nvflash let me fix all this? Or with a locked bootloader I'm definitely screwed? Would it be worth the wait?

if ur sn is not recognised then its a knock off or stolen from asus factory imo
i would force a refund

malos1984 said:
if ur sn is not recognised then its a knock off or stolen from asus factory imo
i would force a refund
Click to expand...
Click to collapse
...and in the end that's what I did. I loved the concept, but the actual thing was crippled. I leveraged the double-SN-thingy and the hardware connector issue, and after some discussion I got my refund. Bought a note 10.1 2014, not what I wanted, due to lack of keyboard and battery life, but it seems it's the second best tablet around (in my opinion).
I would have been happier with a working Asus, but problems were too many. At least the note does what it promises, even though it promises "less", and I never even used the S-pen once since I unboxed it.

Need some help regarding Custom-ROMs and their consequences!

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!

[Q] Need help unlocking S3 on 4.3

Hi xda
I have referred to this site many times for help but never became a member until now - I seriously need some help!
I recently bought a second hand S3 LTE which I knew was locked but as I had unlocked a few phones in the past I thought it wouldn't be a problem... until I encountered Android 4.3 and its bodyguard Knox. Searching on forums I found many other people experiencing similar problems but nothing conclusive that didn't involve using a Z3X box which costs about as much as I paid for the phone.
Apologies if this has already been covered in some form in another thread but I have done a lot of searching and a lot of hair pulling before coming to this stage.
So to cut a long story short I managed to successfully root the phone using CF through Odin and installed the version of SuperSU capable of bypassing it (downloaded .apk as opposed to play store which some people had said worked).
Next stage was to remove Knox, I installed NoBloat Free as suggested by someone in another forum and I basically removed anything with the word Knox in it and that seems to have done the job.
Now I just need to unlock the damn thing! While I have had some experience with rooting / unlocking a few android phones etc I really don't have much knowledge on the subject and pretty much forget it all in between phones :silly:
For the record I don't care about warranty, flags etc and am more than happy to downgrade if it means getting the phone working.
Any help would be greatly appreciated!

[A] Need help unlocking S3 on 4.3
Hi. The only way I know is via 4.1.1 ROM as explained here: http://forum.xda-developers.com/galaxy-s3/help-i9305/sim-card-unlock-samsung-galaxy-s3-gt-t2185866 (no root needed, just install the 4.1.1 using Odin)
I recently unlocked a stock 4.3 I9305 downgrading it to 4.1.1 first. It worked fine and then I restored a Cyanogenmod 4.4.4 ROM I had from another I9305 of mine. And then on CM I "lost" the IMEI (it happens), but I easily recovered it.
bouipoz said:
Hi xda
I have referred to this site many times for help but never became a member until now - I seriously need some help!
I recently bought a second hand S3 LTE which I knew was locked but as I had unlocked a few phones in the past I thought it wouldn't be a problem... until I encountered Android 4.3 and its bodyguard Knox. Searching on forums I found many other people experiencing similar problems but nothing conclusive that didn't involve using a Z3X box which costs about as much as I paid for the phone.
Apologies if this has already been covered in some form in another thread but I have done a lot of searching and a lot of hair pulling before coming to this stage.
So to cut a long story short I managed to successfully root the phone using CF through Odin and installed the version of SuperSU capable of bypassing it (downloaded .apk as opposed to play store which some people had said worked).
Next stage was to remove Knox, I installed NoBloat Free as suggested by someone in another forum and I basically removed anything with the word Knox in it and that seems to have done the job.
Now I just need to unlock the damn thing! While I have had some experience with rooting / unlocking a few android phones etc I really don't have much knowledge on the subject and pretty much forget it all in between phones :silly:
For the record I don't care about warranty, flags etc and am more than happy to downgrade if it means getting the phone working.
Any help would be greatly appreciated!
Click to expand...
Click to collapse

[Q] Questions about the Z3+/Z4 when bootloader unlocked

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.

What's the easiest way if you only want root access, nothing else?

First of all, I have been using custom kernels and later rooting since Pocket PC 2002/Merlin, and I now have bought my first Sony (after just about every other brand of Android phone, no particular reason why I never had a Sony since the SE T68) because it's the only phone I can use with salt water spray on the screen and wet fingers. I do a lot of lobster, crayfish and crab fishing with traps and use an app called Fishing Poins to keep track of my pots and what I get where. Coming from Samsung (S5 was the latest I had) the rooting of a Sony seems rather cumbersome, but I have a few apps that need root access. LIke Air Audio to play music through an Airplay system. DLNA is useless to me, I want to stream the audio that I'm using on the phone directly to the whole house systen.
So can somebody please tell me what I do to get root access on Nougat (which my phone upgraded to before I saw that's what was happening, and no, I'm not big on reading long explanation screens, if it's a new phone and an official upgrade I am used to just doing it before I root on Samsung phones, since I have to unroot to install them later) and nothing else? For now I don't want to use any custom kernels or recovery, if I can avoid it. Just stock, rooted, like I could on my S5 (and Note 2, S4 Active and so on), please!
I did attempt the KingRoot app, but it didn't work. Also I have read a bit about that app that doesn't seem to good (Chinese spy fator app), so I did a full reset after the failed attempt. But if there's something similar that would be the perfect way of doing this. Of course I'm no stranger to ADB, so hooking it up to my pc is not a problem either.

1. Downgrade to any version of stock Marshmallow firmware with Xperifirm and Flashtool. Wipe everything and Exclude nothing (but *.ta - if any). Do not use FSC script! << FSC is now mandatory!
2. Backup your device's TA partition with Universal TA Backup tool.
3. Flash Nougat firmware (again with Xperifirm and Flashtool). Wipe everything and Exclude nothing (but *.ta - if any).
4. Unlock your device's bootloader
5. Follow this instructions to create/flash a custom kernel with root, and also DK.ftf (to fully reactivate sony's drm keys, which is wiped when bootloader is unlocked).
Anyway, try it at your own risk!

Thanks! So that's the method, which of course means deleting everything I've set up on the phone. Is there a chance there may be an easier, less destructive way during the next month or so? I can do without root access for that long.

oh, btw, by "custom kernel" do you mean that it will not be the original setup for the phone? I've been betatesting kernels on many devices, but nowadays I only want a phone that works without any hitches, and I want access to the official updates. That was easy on the Samsung phones, but maybe Sony is more different than I thought?
Oh, btw, maybe it is explained in the long post you directed me to, but I recently had an eye operation, and I would appreciate a shorter answer, before I get to the "how to", which takes me a while to read right now...

NEVER MIND THIS MESSAGE! Now I understand what Xperfirm is...
Also where would be a safe place to download ROMs from? Both the downgrade ROM and the Nougat ROM? I now really wish I hadn't let the thing upgrade before I took the TB backup (I'm still a bit unsure as to why I need that, I don't use any media with any form for DRM, but I guess better safe than sorry).

Mastiff said:
NEVER MIND THIS MESSAGE! Now I understand what Xperfirm is...
Also where would be a safe place to download ROMs from? Both the downgrade ROM and the Nougat ROM? I now really wish I hadn't let the thing upgrade before I took the TB backup (I'm still a bit unsure as to why I need that, I don't use any media with any form for DRM, but I guess better safe than sorry).
Click to expand...
Click to collapse
As far as I know there's no danger to download through Xperifirm, you need TA for guarantee reasons (if your phone need repair, not everywhere but for safety)

THanks, yeah. I have managed to read a bit and found out that Xperifirm downloads from the official Sony servers. Pain in the ass downloading, it breaks the download every couple of minutes. But that's probably Sony's servers, not the program. As for warranty, that's no problem in Norway since we have very strong consumer rights here. If an error can not be prooven to stem from rooting or other software stuff, it will be fixed. If I remember correctly Apple tried really hard to battle with the consumer rights officials about jailbreaking, but they had a very bloody defeat.

Seems like I have a problem. The Telenor Nougat ROM doesn't have a loader, according to Flashtool. Neither do the two other ROMs I have downloaded so far, but I'm trying again with a third, which doesn't have the "customised" moniker. So I hope that has a loader. But how do I upgrade again to Nougat, with the Norwegian version, when the Telenor ROM doesn't have a loader?

Mastiff said:
Seems like I have a problem. The Telenor Nougat ROM doesn't have a loader, according to Flashtool. Neither do the two other ROMs I have downloaded so far, but I'm trying again with a third, which doesn't have the "customised" moniker. So I hope that has a loader. But how do I upgrade again to Nougat, with the Norwegian version, when the Telenor ROM doesn't have a loader?
Click to expand...
Click to collapse
if your phone is locked(Bootloader),fix it using Xperia Companion..that way it upgrades automatically to Nougat.
if not,lock it using Flashtool first.

Well, the message was kind of badly worded, because I need to downgrade first of all. So I'm at the moment trying to get it to MM without messing up the TA partition. So anyway, this thread has been followed by others, I think this can be considered solved since there is only one way to get root on these phones.

What would be the best approach to rooting if you unlock your bootloader before learning about TA backup? I have since downgraded, done TA backup, upgraded, flashed TWRP, flashed SU/Magisk/phhSu, and saw two green checks in Magisk. Tried to continue to get the three checks by installing Sony framework v1 through Magisk and then Andros plus kernel, but got stuck on Sony screen on boot up. So I repeated steps and stopped after I got two checks, however after long use and simple phone restart, I lost root. Please HELP!