Database Users

[4.4.4] for [SGP521]

Is this Android 4.4.4 to SGP521?
Link

Exciting!

Yes, it is 4.4.4, and it will bring us the new Z3 UI, and some Z3 features.

Bird40 said:
Is this Android 4.4.4 to SGP521?
Link
Click to expand...
Click to collapse
Sure you are not being a bit previous? My Z2 is SGP512, not SGP521! Hope you are right though
UPDATE: Doh! Just realized that both are valid

Very good news

Finally!
Sent from my SGP521 using Tapatalk

The rumour-mill has gone scarily quiet.. I don't understand why, having subscribed to a "premium" product, we don't get "premium" service. Anyone prepared to stir the pot and get the rumours going again?

pdes said:
The rumour-mill has gone scarily quiet.. I don't understand why, having subscribed to a "premium" product, we don't get "premium" service. Anyone prepared to stir the pot and get the rumours going again?
Click to expand...
Click to collapse
Ok, try this one. They're not going to push the 4.4.4 and will go straight to 5L next year

New version
New version
Link

Has anyone been able to update? Mine just failes
Sent fra min D6503 via Tapatalk

Installed and working properly, we only need to root :good:

Bird40 said:
Is this Android 4.4.4 to SGP521?
Link
Click to expand...
Click to collapse
yes, i already got it, any one has recovery?

I managed to install it with dual recovery but I am having issues on mounting the system. Does anyone know how to?

chesterr said:
I managed to install it with dual recovery but I am having issues on mounting the system. Does anyone know how to?
Click to expand...
Click to collapse
But it is compatible? Now try but could

So, what do you guys think about this update? Is it really worth it? Curious to know.

The biggest reason for me to change was to get Remote Play to link with my PS4. Also, the applications button is now shifted to the middle of the bottom edge. Other than that, I haven't noticed any huge changes that blew me away.
Remote Play is pretty cool though, tried it out for a little bit last night and it was good enough to play Call of Duty campaign mode.

chesterr said:
I managed to install it with dual recovery but I am having issues on mounting the system. Does anyone know how to?
Click to expand...
Click to collapse
Need to modify the kernel ramdisk to make it insecure.

Moscow Desire said:
Need to modify the kernel ramdisk to make it insecure.
Click to expand...
Click to collapse
Yea it did ask me about ramdisk btw, guess I'm just gonna wait till PRF Creator tool to be updated,

chesterr said:
Yea it did ask me about ramdisk btw, guess I'm just gonna wait till PRF Creator tool to be updated,
Click to expand...
Click to collapse
Well, technically, it's not such a big deal, to swap kernels/ramdisk with an unlocked bootloader. It's a simple edit. But, at this point, it would mean unlocking bootloader, and losing DRM keys (still not sure what functions besides some lost advanced camera functions, not that anybody uses the camera anyhow except for skype).
Under the old rooting, it used an exploit to modify ramdisk, (and install the necessary apps), without unlocking bootloader via an exploit.
As for me, I will wait a couple weeks and see if there's a new exploit. If not, well, I will do the above method.

Moscow Desire said:
Well, technically, it's not such a big deal, to swap kernels/ramdisk with an unlocked bootloader. It's a simple edit. But, at this point, it would mean unlocking bootloader, and losing DRM keys (still not sure what functions besides some lost advanced camera functions, not that anybody uses the camera anyhow except for skype).
Under the old rooting, it used an exploit to modify ramdisk, (and install the necessary apps), without unlocking bootloader via an exploit.
As for me, I will wait a couple weeks and see if there's a new exploit. If not, well, I will do the above method.
Click to expand...
Click to collapse
Basically DRM keys are used to see if you have unlocked the device (in the past). So mainly for Sony to check if your warranty is still valid.
There is a tool that will backup your DRM keys though, and can restore it too. You just need root for that (just downgrade, root, backup keys and upgrade again) Just Google Xperia DRM backup and you're bound to find out

root and lollipop

UPDATED:
Please jump to the following thread for information on root/lollipop:
http://forum.xda-developers.com/shield-tablet/help/qa-root-shield-tablet-2-0-lollipop-t2945163

garyd9 said:
There's some misinformation going around concerning lollipop (android 5.0), root, and the SHIELD tablet. I'm posting this (redundant) information to (hopefully) clear things up and prevent someone from causing themselves a headache after the tablet updates...
nvidia has stuck very close to AOSP in their tablet firmware updates, so it's a reasonable assumption (at this point) that the new firmware will also be very close to AOSP.
If that comes to be, then "rooting" the tablet will be more difficult than in previous firmware updates. Most of the gory details can be found in this G+ article by @Chainfire : https://plus.google.com/113517319477420052449/posts/VxjfYJnZAXP
(BTW, as always, a huge thanks to Chainfire for his efforts. If you haven't already, paying for the upgrade to "SuperSU Pro" is well worth the price if for no other reason than to encourage Chainfire to continue work on that project.)
If you don't understand the details of that post from chainfire, I'll try to summarize it: Even if you manage to get a copy of the "su" binary on your system partition (which is essentially the goal of all the older root exploits), it won't matter much in Android 5.0. In Android 5.0, we'll ALSO need a part of the kernel image changed (the ramdisk) so that a part of "superSU" can run at a more permissive context.
Updating the kernel ramdisk shouldn't be too difficult (if its compressed with the kernel in a normal way) once we have the image to play with. As well, in order to put the newly modified kernel image in place, a person would have to unlock their bootloader (which can void your warranty.)
Actually, it's possible (once the image is released by nvidia) that @Chainfire will stick the image on his server in one of his very easy to use "CF-Auto-Root" bundles. (Hopefully, all the @ references I've made will get him to look at this thread and confirm what I've said. The honest truth is that I'm NOT familiar with SELinux, so I'd have to do a bit of experimenting to get this working.)
Take care
Gary
Click to expand...
Click to collapse
Have you found any specifics on what will need to be modified in the ramdisk? I haven't really done anything with the boot.img itself but I'd be interested to see what is going on with this.

Keithn said:
Have you found any specifics on what will need to be modified in the ramdisk? I haven't really done anything with the boot.img itself but I'd be interested to see what is going on with this.
Click to expand...
Click to collapse
That Google plus post I linked to describes the needed change.
Sent from my SHIELD Tablet using Tapatalk

Okay, thanks. I guess I didn't catch that.
Sent from my One M8

Root successful!
I just successfully got root. If I can make it permanent I will post the necessary files/instructions in the update thread.

SuperPichu said:
I just successfully got root. If I can make it permanent I will post the necessary files/instructions in the update thread.
Click to expand...
Click to collapse
With a modified recovery or stock ?

matyas69 said:
With a modified recovery or stock ?
Click to expand...
Click to collapse
CWM. The instructions are up in the lollipop update thread

SuperPichu said:
CWM. The instructions are up in the lollipop update thread
Click to expand...
Click to collapse
Is this root sticking?

whoamanwtf said:
Is this root sticking?
Click to expand...
Click to collapse
It seems to be. Only problem I have run into is that FX file explorer root mode doesn't seem to work, but ES does so I think it's an app compatibility with 5.0 thing rather than a problem with root.

SuperPichu said:
CWM. The instructions are up in the lollipop update thread
Click to expand...
Click to collapse
I'll wait root without custom recovery

SuperPichu said:
It seems to be. Only problem I have run into is that FX file explorer root mode doesn't seem to work, but ES does so I think it's an app compatibility with 5.0 thing rather than a problem with root.
Click to expand...
Click to collapse
Are you able to use FolderMount with it? and Titanium? Those are the reason I need root, and if those both work then I will wipe and unlock to get LP rooted

whoamanwtf said:
Are you able to use FolderMount with it? and Titanium? Those are the reason I need root, and if those both work then I will wipe and unlock to get LP rooted
Click to expand...
Click to collapse
Testing right now. How should I test these? i.e. What do you use them for?

SuperPichu said:
Testing right now. How should I test these? i.e. What do you use them for?
Click to expand...
Click to collapse
Awesome, I use FolderMount to link my obb files from the sd card to the main so that my largest game files are all on my sd card. I actually have the premium version so I just link my whole obb folder and data folder but I would guess linking any obb and then seeing if the game would load would test it. As for Titanium a backup/delete/restore of any app would test all of the features. Thanks for checking that out

whoamanwtf said:
Awesome, I use FolderMount to link my obb files from the sd card to the main so that my largest game files are all on my sd card. I actually have the premium version so I just link my whole obb folder and data folder but I would guess linking any obb and then seeing if the game would load would test it. As for Titanium a backup/delete/restore of any app would test all of the features. Thanks for checking that out
Click to expand...
Click to collapse
No problem.
Results
Folder Mount - Made a link from internal to external and the link seemed to be working correctly (files put in one showed up in the other)
Titanium - Backed-up, uninstalled, and restored Netflix successfully with no errors

Here's a link to the root instructions. http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
Please post any questions there.
Works for both locked and unlocked bootloaders now.

SuperPichu said:
Here's a link to the root instructions. http://forum.xda-developers.com/showpost.php?p=56854633&postcount=77
Works for both locked and unlocked bootloaders now.
Click to expand...
Click to collapse
You beat me too it lol. I just got home pulled the ota and modified the boot.img before I saw this.

Keithn said:
You beat me too it lol. I just got home pulled the ota and modified the boot.img before I saw this.
Click to expand...
Click to collapse
I was starting to wonder how I was the only person (or at least the first) to have that idea.

So I already installed the update for lollipop. Although I was rooted using towelroot, I never installed CWM or unlocked my bootloader. Is it too late to follow the instructions to unlock my bootloader at this point? Do I need to just wait for another root method?

onduck said:
So I already installed the update for lollipop. Although I was rooted using towelroot, I never installed CWM or unlocked my bootloader. Is it too late to follow the instructions to unlock my bootloader at this point? Do I need to just wait for another root method?
Click to expand...
Click to collapse
No if you unlock your bootloader you can follow my unlocked instruuctions.

onduck said:
Is it too late to follow the instructions to unlock my bootloader at this point?
Click to expand...
Click to collapse
no. Not too late.
Sent from my HTC One_M8

[FAQ][ROOT]Answers to Questions about Root

All Your Root Questions Answered:​
This thread is a work in progress. Ask your root questions, and I'll answer them in the OP. This way we can clean up the other thread.
Thank you @DmdStar, @somberfox, @CrashXXL, and everyone else I missed (which I will add to the OP)
Q: I followed all the directions and after I finished the root procedure, my device is stuck at the M logo? HALP.
A: You didn't follow all the directions, and now you're going to have to start over from step one. Flash SU6-7 in RSD Lite as mentioned in the directions, and follow the directions word-for-word. You're only wasting your own time, not ours.
Q: My phone is stuck at the black green and the root script isn't detecting my phone?
A: You're probably using a USB3.0 port which isn't supported. Move your phone to a USB2.0 port and install the Qualcomm drivers provided in the download.
Q: Why is it taking so long, I think it froze.
A: Just leave your phone alone and get a coffee. Make that three. It's a long process.
Q: Can I install blah-blah ROM?
A: NO! While this is a perma-root, you are unable to disable write-protection, therefore you can't use Safestrap.
Q: Now that I'm rooted, can I unlock my bootloader?
A: SU4-21 was the last system update that worked with Sunshine. Unless you can get in contact with the Chinese middleman, you're out of luck. Sorry.
Q: Why won't my changes to /system persist after a reboot?
A: Unfortunately, no one has managed to circumvent write protection on the device, therefore you can't do anything to /system and expect it to persist unless you do soft-reboots. Sorry.
Q: Can I delete system apps?
A: No, unless you edit the system.mbn and split it into 16mb chunk files. There's no way around this, sorry.
Q: Can I install your Busybox image?
A: I mean if you want a brick, go right ahead. No one's stopping you.
Q: Viper4Android?
A: Which needs Busybox. Again, feel free to proceed at your own risk.
Q: Can I downgrade to SU6-7 if I took the upgrade to SU6-7.2?
A: Yes, you can. There's no magic trick to downgrading to SU6-7, just flash it in RSD Lite.
Q: Can i have only root with SU6-7 and locked bootloader?
A: You can not unlock your bootloader past SU4-21.
Q: Wait, if we can downgrade to SU6-7, why not just downgrade to SU4-21 and unlock our bootloaders?
A: Because you can't. Debating about it on the forums won't magically make it work neither. Nor will complaining about Motorola locking down the devices. You bought an on-contract device that you knew was going to be locked and stock. They also had a developer edition MAXX for sale. If you didn't get it, blame yourself, not Motorola/Verizon.
Q: Can we take the OTA update without losing root?
A: Yes, but you will lose Xposed if you do.(Answered by @DmdStar)

Thanks for the faq @thenameisnigel
Sent from my XT1080 using Tapatalk

yeah thx

Nice one ! Thanks for Viper4Android information. What preset did you choose (battery saving, high/super quality) ?
Actually I don't see what stops you from deleting an app, although it's faster "frozing" it via Titanium for example (paid solution). I removed some files successfully (I should try with apps). Also, did you try installing another ROM ? I didn't take the time to try it but it might work with the python script. You just would have to replace almost all memory blocks, which would take 16+ hours (!!).
I've another question : did someone succeed in installing CF.Lumen ?
Thanks again for the faq
PS : agree with Artimunor just below my post, change colors please !

thenameisnigel said:
Q: Can I delete system apps?
A: No.
Click to expand...
Click to collapse
Wait... here you say it's impossible....
however in the other thread you replied to my post with this:
thenameisnigel said:
Yes
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
My original post:
Artimunor said:
Thats the reason i would like to know how to safely alter the image we upload to the phone, to add/remove apps from it.
Is it save to just mount the image on a linux system as a HD and alter the /system directory?
Click to expand...
Click to collapse
Whats the deal here?
I already started creating a linux environment for this, just did not had the time to complete it yet with my dayjob (already pretty sleep depraved)
P.S. that azure blue really hurts the eyes.

Artimunor said:
Wait... here you say it's impossible....
however in the other thread you replied to my post with this:
My original post:
Whats the deal here?
I already started creating a linux environment for this, just did not had the time to complete it yet with my dayjob (already pretty sleep depraved)
P.S. that azure blue really hurts the eyes.
Click to expand...
Click to collapse
It's possible if you edit the image like what you're doing. That answer was meant more for people who want to edit /system directly from the device. I'll clarify it.
Sent from my XT1080 using Tapatalk

can i have only root with SU7-6 and locked bootloader?

Deleted.

danger2u said:
can i have only root with SU7-6 and locked bootloader?
Click to expand...
Click to collapse
thenameisnigel said:
Q: Can i have only root with SU6-7 and locked bootloader?
A: You can not unlock your bootloader past SU4-21.
Click to expand...
Click to collapse
Sent from my XT1080 using Tapatalk

thenameisnigel said:
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
ok.
but can i have root with locked bootloader with the method that bricks the phone?

danger2u said:
ok.
but can i have root with locked bootloader with the method that bricks the phone?
Click to expand...
Click to collapse
Yes.
Sent from my XT1080 using Tapatalk

if i restart the phone,the root will remain ?
Busybox can be installed?

danger2u said:
if i restart the phone,the root will remain ?
Busybox can be installed?
Click to expand...
Click to collapse
Only if you put it in the image before you flash it to the phone it seems, if you do it afterwards it does not persist.

another question
can we take the OTA update without losing root?

danger2u said:
another question
can we take the OTA update without losing root?
Click to expand...
Click to collapse
Yes. But you will lose xposed if you installed it.
Sent from my XT1080 using Tapatalk

danger2u said:
another question
can we take the OTA update without losing root?
Click to expand...
Click to collapse
Didnt try it myself but from what ive gathered if you used the crashxxl method you will not loose root if you take the su6-7.2 OTA update.

Artimunor said:
Didnt try it myself but from what ive gathered if you used the crashxxl method you will not loose root if you take the su6-7.2 OTA update.
Click to expand...
Click to collapse
i updated
the root it s still here.
will see with Lollipop if ever will be out for Droid maxx
ps: don t update if u want xposed.

danger2u said:
take it the update
the root it s still here.
will see with Lollipop if ever will be out for Droid maxx
Click to expand...
Click to collapse
Dude why are you telling people to take the update when we already know that it'll break Xposed? If you're not here to help, don't post. Simple as that.
Sent from my XT1080 using Tapatalk

thenameisnigel said:
Dude why are you telling people to take the update when we already know that it'll break Xposed? If you're not here to help, don't post. Simple as that.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I take it the update
i don t tell anyone to update the Droid maxx.

are you referring to losing functionality of a baked in exposed? I am running the crash exploit, with non-baked exposed, on SU6-7.2

Post MHC19l update camera does not work at all

So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.

None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.

Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?

Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!

Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.

Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.

Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys

So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk

and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk

and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?

Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.

naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.

did it flash the vendor?

Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk

and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.

Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk

Searching For Root..

I've had this phone a little while now and I'm itching to root it. There's nothing wrong with it, I just really want to get into the code and do some modding. But there doesn't seem to be any root solution available right now.
So I thought I'd start this thread so we could discuss any rooting tips and ideas you all might have.
First I should probably mention all the potentially dodgy rooting solutions out there. Google "root xa1" and you get many results that offer methods to gain root access on our phone.
I confess I haven't tried any of them but that's because they all look suspicious. Some were written before the phone launched, some require you to download unknown software (I'll keep my PC virus-free, thanks), some even go so far as to feature a fake comment section with people saying it works.
I have no desire to stick malware on either my PC or my phone so I'm steering well clear of those.
The XZs launched at the same time as the XA1 and there seems to be a solution available for that. This is a thread by @zlRampageSlz with details: https://forum.xda-developers.com/xzs/how-to/tutorial-step-step-guide-to-gain-root-t3612624
It looks like the best solution is to unlock the bootloader (making sure to back up your TA partition first!), flash a modified kernel (otherwise the camera takes green pictures), flash a recovery image and then flash Magisk.
Where do we get this modified kernel? Where do we get the recovery image?
I have no idea, sadly. This is all way beyond my area of expertise. I'm a themer, not a developer.
But if anybody knows better than me, please post here.
This is a great phone, let's work together so we can get it modded!

Ticklefish said:
I've had this phone a little while now and I'm itching to root it. There's nothing wrong with it, I just really want to get into the code and do some modding. But there doesn't seem to be any root solution available right now.
So I thought I'd start this thread so we could discuss any rooting tips and ideas you all might have.
First I should probably mention all the potentially dodgy rooting solutions out there. Google "root xa1" and you get many results that offer methods to gain root access on our phone.
I confess I haven't tried any of them but that's because they all look suspicious. Some were written before the phone launched, some require you to download unknown software (I'll keep my PC virus-free, thanks), some even go so far as to feature a fake comment section with people saying it works.
I have no desire to stick malware on either my PC or my phone so I'm steering well clear of those.
The XZs launched at the same time as the XA1 and there seems to be a solution available for that. This is a thread by @zlRampageSlz with details: https://forum.xda-developers.com/xzs/how-to/tutorial-step-step-guide-to-gain-root-t3612624
It looks like the best solution is to unlock the bootloader (making sure to back up your TA partition first!), flash a modified kernel (otherwise the camera takes green pictures), flash a recovery image and then flash Magisk.
Where do we get this modified kernel? Where do we get the recovery image?
I have no idea, sadly. This is all way beyond my area of expertise. I'm a themer, not a developer.
But if anybody knows better than me, please post here.
This is a great phone, let's work together so we can get it modded!
Click to expand...
Click to collapse
First of all thank you so much for your awesome tool "Tickle My Android" which i really like it (Y).
i'm about to get XA1 Ultra so sure i'm so curious about root also but i'll try to make it clear,
simply, don't waste your time searching for a root tool because it's impossible to have root without modifying kernel, so, 100% all of these tools are just malware !
in the new devices there's something calls DM-Verity which is a check tool and that means any modification to /system will leads to bootloop,
so DM-Verity must be disabled ( through kernel of course ) & any mess with kernel means you have to unlock bootloader.
another thing, Sony ric which is prevent mounting system, so, any modification must be through recovery or it will leads to bootloop also, so we must also disable it.
fortunately on my xperia z2 there is no DM-Verity and there's a module to disable sony ric through recovery so root was possible without unlocking bootloader but starting from xperia z3+ DM-Verity appeared !
so now root is impossible without unlocking bootloader ( which means losing drm keys forever if you didn't back it up ).
i downloaded the firmware for xa1 ultra through xperiafirm and i unpacked the kernel and tried with these tools to see how its going on:
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
&
https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
the first one was hanging and i didn't get any information & the second one to be able to use it then you must put your ta.img ( your ta backup ) inside the folder,
i used my z2 ta.img as a test to see the process and the result was pretty good !
i successful disabled DM-Verity and there's no sony ric !!!!! but it's also still not safe and needs to be confirmed because maybe there's a bad surprise which is not clear yet, maybe something like sony ric but new !
so, if it's only the ****ty DM-Verity it's easy to disable it even away from this tool because we can't use it without ta.img, maybe by any script or unpacking kernel and modify it then repacking it this is not a problem at all & after that MAYBE we can flash supersu or magisk via ADB since there's no recovery yet ( completely not sure about this so it needs to be confirmed ) & in this case the choice is between root or drm features but at least root has been achieved.
so now, we need something like this to be able to backup ta without root and after that no problem of unlocking bootloader:
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
or
https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
or if it's not possible at this moment to backup ta without root then at least we need something like this to be able to to reactivate drm features such as camera denoise and x-reality...etc:
https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
or
https://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
or the worst choice...root without drm & waiting for a fix like those above !
anyway, root is not easy like before but it's still possible after all, i tried to clarify everything as much as i can and i hope there's a solution soon !
@munjeni we need your help bro, please if you have free time have a look, i uploaded the kernel for xa1 ultra so try to tell us how it's going on & what is new !
https://www.mediafire.com/?bc63fgjw99r785d
good luck for everyone .

As my Z5 compact was broken, I bought the XA1. I didn't remember, how awful an unrooted phone is - So I am also waiting and would be very interested to be informed.
BR
Sopur

Did anyone tried this?
https://www.oneclickroot.com/sony/sony-xperia-xa1/

chauhanjayc said:
Did anyone tried this?
https://www.oneclickroot.com/sony/sony-xperia-xa1/
Click to expand...
Click to collapse
I haven't, personally. Every mention of it I can find just looks like an advert. And I'm not paying for something that might not work and might do something horrible to my phone.
Sent from my Sony Xperia XA1 using XDA Labs

Ticklefish said:
I haven't, personally. Every mention of it I can find just looks like an advert. And I'm not paying for something that might not work and might do something horrible to my phone.
Click to expand...
Click to collapse
Its free

chauhanjayc said:
Its free
Click to expand...
Click to collapse
One Click Root does not work at the moment :crying:

kpfreak said:
One Click Root does not work at the moment :crying:
Click to expand...
Click to collapse
Uffffd
Let wait till next exploit.

chauhanjayc said:
Uffffd
Let wait till next exploit.
Click to expand...
Click to collapse
I'm sure it's only a matter of time.
Sent from my Sony Xperia XA1 using XDA Labs

bought this phone to replace my oppo. i can't wait for root abilities to be made

Bought this phone to replace my old Xiaomi. It's a good, powerful phone. Hope to see root appear for it soon. Personally for me, I'm one of those people who will only root a phone once it gets slow (the warranty expires). So as much as I'm reluctant to root my phone now, I'll hold out and see what wonderful developments appear on this thread.
Given the XA1 (I have the XA1 not the XA1 Ultra, I believe they are different) runs a Mediatek processor, I'm inclined to see something along the lines of a MT Flash Tool being used. Correct me if I'm wrong but I've only had successful flashes and roots with Qualcomm processors. The last device I had with a Mediatek processor (Lenovo A8-50 A5500H, MT8382) bricked on me horribly and I had to throw it away :crying:.
Meh. Hope we'll see awesomeness come soon from here. I'm still pretty new to XDA, looks like an awesome community

MINGXXIE said:
Bought this phone to replace my old Xiaomi. It's a good, powerful phone. Hope to see root appear for it soon. Personally for me, I'm one of those people who will only root a phone once it gets slow (the warranty expires). So as much as I'm reluctant to root my phone now, I'll hold out and see what wonderful developments appear on this thread.
Given the XA1 (I have the XA1 not the XA1 Ultra, I believe they are different) runs a Mediatek processor, I'm inclined to see something along the lines of a MT Flash Tool being used. Correct me if I'm wrong but I've only had successful flashes and roots with Qualcomm processors. The last device I had with a Mediatek processor (Lenovo A8-50 A5500H, MT8382) bricked on me horribly and I had to throw it away :crying:.
Meh. Hope we'll see awesomeness come soon from here. I'm still pretty new to XDA, looks like an awesome community
Click to expand...
Click to collapse
from what i've seen on sony's support page, they've made their own flash tool to flash stock roms to your phone with in case of events like bricking

diosdetiempo said:
from what i've seen on sony's support page, they've made their own flash tool to flash stock roms to your phone with in case of events like bricking
Click to expand...
Click to collapse
Is it? That's wonderful, shall go check it out

Seems like the ultra version has gotten it.
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886

diosdetiempo said:
Seems like the ultra version has gotten it.
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
Click to expand...
Click to collapse
Cool. I wonder if they can help with our device..
Sent from my Sony Xperia XA1 using XDA Labs

Hi. Wondered if I could ask advice. When trying to unlock bootloader using Sony website via a code. After entering the command with the code it says command not allowed, any ideas?

arienwalsall72 said:
Hi. Wondered if I could ask advice. When trying to unlock bootloader using Sony website via a code. After entering the command with the code it says command not allowed, any ideas?
Click to expand...
Click to collapse
I don't know, sorry. Did you definitely enter the right code?
Sent from my Sony Xperia XA1 using XDA Labs

Ticklefish said:
I don't know, sorry. Did you definitely enter the right code?
Click to expand...
Click to collapse
Yes. It gives the full command with the code on the Sony website. So I copied and pasted it from there. It does say on the phone in the service menu under bootloader unlock able = no. But says yes on the Sony website so not sure

arienwalsall72 said:
Yes. It gives the full command with the code on the Sony website. So I copied and pasted it from there. It does say on the phone in the service menu under bootloader unlock able = no. But says yes on the Sony website so not sure
Click to expand...
Click to collapse
if it says no on your phone then you're not able to

arienwalsall72 said:
Yes. It gives the full command with the code on the Sony website. So I copied and pasted it from there. It does say on the phone in the service menu under bootloader unlock able = no. But says yes on the Sony website so not sure
Click to expand...
Click to collapse
Go to Settings > About Phone.
Tap on Build Number until you get a toast notification that says you're a developer.
You should now be able to access Developer Options in Settings.
Go inside Developer Options then toggle OEM unlocking. Make sure it's on.
The code you get from the website should work now.