Develop Bugs

[Q] will arc get root with zergrush?

will the arc get root with zergrush oneclick have tried it but doesnt work, is it possible to get this to work with arc?

I'm interested too!

I followed the guide for the play, it worked flawlessly.
Sent via subspace beacon from my Arc.

Hi!
This works for ARC!!! 4.0.1.A.0.283 at least. Was able to remove bloat through adb. Wohoooo....no more worries of getting the 0% battery(if you don't need permanent root).

Works flawlessly on 4.0.2.A.0.42 Xperia Arc here. Just use the pdf guide, you can't go wrong

Works for Xperia Pro (MK16i) on 4.0.1.A.0.283 as well

Does it work with 4.0.A.2.368 ?

maciek51 said:
Does it work with 4.0.A.2.368 ?
Click to expand...
Click to collapse
It should do, seems to be fairly universal.

Thank you Lord Takyon
The pdf file is way detailled but as I'm not an expert of such commands, is there any risk of doing something wrong ?
As the root is temporary, I don't think so... right ?

maciek51 said:
Thank you Lord Takyon
The pdf file is way detailled but as I'm not an expert of such commands, is there any risk of doing something wrong ?
As the root is temporary, I don't think so... right ?
Click to expand...
Click to collapse
I think the danger of doing something harmful is quite minimal. if you do it wrong you just can't get rooted. The exploit itself is temporary(until reboot) and gives you
root over adb shell, but you can make it "permanent" by pushing the su binary and Superuser.apk to the phone. But I actually like that you have the option to just root until next reboot - so you can remove bloat via adb or modify system files and if you don't want to run any root apps that is exactly what you need.

thank you m2kk
Pushing su binary and superuser makes it permanent, you mean permanent until the next reboot, right ?
In any case, I reboot my phone very rarely (airplane, etc.) otherwise, neally never and the procedure seems to be short enough to be reproduce time to time.
I will try it in the evening and I will report

maciek51 said:
Pushing su binary and superuser makes it permanent, you mean permanent until the next reboot, right ?
Click to expand...
Click to collapse
Nope, if you do it by the book you will have a fully rooted phone and the root survives reboot.

[Tutorial] Xperia Z2 Tablet Bootloader Unlocking/Relocking

Quick tutorial for unlocking & relocking the bootloader of the Xperia Z2 Tablet
this is the official way to unlock bootloader
WARNING!
MAKE TA BACKUP BEFORE UNLOCKING BOOTLOADER!
​
if you want to backup the TA or keep ur DRM keys,first root the device and then check this out
Warning!
This procedure will wipe the /data partition of your tablet, so you will loss all ur stored data, settings. SDCARD will BE WIPED!!!
For Xperia™ devices released 2013 or later (for example Xperia™ Z and Xperia™ ZL), the SD card of your device will be formatted and you will lose all content (for example photos, music, videos) when you unlock the boot loader.
Click to expand...
Click to collapse
DRM keys WILL be lost forever
schaggo said:
I'd add what losing DRM keys means, e.g. no more Music ID/Gracenote within the Walkman app plus probably most importantly, as asked all the time and all over the place in the T/mint forums: loss of Bravia Engine.
Click to expand...
Click to collapse
older Xperia devices sometimes got issues after unlock of bootloader (BRICK after FOTA update) - you have been warned
why to unlock bootloader?
u can flash custom ROMs/Kernels
u dont need to worry if the new firmware can be rooted or not as with unlocked bootloader u can always ROOT ur device
Sony gives sneak-peaks/preview builds of latest OS which requires unlocked bootloaders, as they did with Xperia 2011/2012 line, so who knows may be Sony may give early builds of next android OS
Most of this is taken from lollylost100's his tutorial from ARC thread (all credits for that concise tutorial go to him, i have elaborated on a few things and added device specific changes)
btw i dont have this device, most of this testing was done remotely on a users phone... so thanks a lot to him for helping out!!!
[ before we begin unlocking bootloader ]
download the fastboot package
IMPORTANT: if you are using Windows 8 you will need to enable few things to allow driver installation
download the latest FlashTool Xperia Driver Pack and install fastboot drivers (common) & adb drivers for this device from the list!
make sure u have a windows PC with USB cable to connect the phone
power down ur tablet and keeping the Volume Up button pressed connect the USB cable to PC this will trigger FASTBOOT mode and windows will start driver installation, which should be automatically done
once drivers are installed just disconnect cable and power on device
[ how to unlock ] (official way)
Go to: http://unlockbootloader.sonymobile.com/ and read everything!
At the bottom click 'Start Unlocking the Bootloader'
First, you should confirm that it is possible to unlock the boot loader of your tablet by checking the service menu. On your tablet, open the dialler and enter *#*#7378423#*#* to access the service menu.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
after u have verified that u can unlock bootloader, scroll to the bottom of the page and click "Continue"
you will get numerous prompts, read all info and if u agree click on "Accept"/"OK"/"Proceed"
finally u will get a "Create Unlock request" page, enter your IMEI (sometimes the last digit needs to be removed for this to work), name and email address
You should now receive your unique unlock key via EMAIL, SAVE THIS KEY SAFELY
Extract fastboot_with_Android_USB_file.rar and open fastboot folder
Hold SHIFT and right click on the background of the folder
Select 'Open command window here'
Connect your tablet in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above)
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned (it will return 0.5), it means the tablet is correctly connected
Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
You're device should now be bootloader unlocked
If this tutorial is too much for you then itskapil wrote a step-by-step guide (and recorded a video also):
-Instructions: http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
-Video: http://www.youtube.com/watch?v=LRH3pC7MhEA
(the above videos and some steps are for Xperia 2011 devices, but most the steps are same for Xperia Z)
Relock procedure is posted here
regards,
DooMLoRD

Relocking bootloader
With the latest release of Flashtool it is now possible to relock bootloader.
Download the latest flashtool from:
http://forum.xda-developers.com/showthread.php?t=920746
Important
DO NOT USE ANY FTF TO RELOCK BOOTLOADER! THOSE OLD FTFs DO NOT WORK FOR THE 2013 DEVICES!!!
before u relock bootloader u have to be on pure stock kernel (flash only the kernel.sin using flashtool), else the device WILL NOT BOOT after relock
Steps:
now start Flashtool and click on BLU button
u will be asked to connect device in flashmode
once u connect the device u will get a prompt to "Relock"
click on it and when prompted disconnect the device
Want to UNLOCK again after relocking? read this!

Obviously since we must unlock to root, no TA backup can bedone...

Diomorgan said:
Obviously since we must unlock to root, no TA backup can bedone...
Click to expand...
Click to collapse
Asking or telling..........either way, correct. TA needs root, to get root you need to unlock lol

Mikey said:
Asking or telling..........either way, correct. TA needs root, to get root you need to unlock lol
Click to expand...
Click to collapse
I'm confused now.....

Pondy said:
I'm confused now.....
Click to expand...
Click to collapse
No TA backup can be done, the guide is the same of Z1 that can be rooted withouth unlock.

Pondy said:
I'm confused now.....
Click to expand...
Click to collapse
It is very confusing indeed. In other words it actually says, do not unlock yet. Wait for an exploid to be found and released so you can root without unlocking the bootloader. Then you can safely make an TA backup, and then safely unlock the bootloader. If you unlock now, your warranty is void.
Sent from my SGP511 using XDA Free mobile app

When a root exploit is found, unlocking the bootloader or backing up TA is not necessary anymore. (Except if one wants to install a custom ROM or custom kernel.)

Yes, but that's why we here. To install custom roms and kernels I mean..
Sent from my LT26i using XDA Free mobile app

dumbl3 said:
Yes, but that's why we here. To install custom roms and kernels I mean..
Sent from my LT26i using XDA Free mobile app
Click to expand...
Click to collapse
OK thanks for clarifying that! I figured that was the case. And yes thats why I'm here, custom rom! This thing would rock with Slimkat or something similar (if it ever gets ported).

For all those who worry about unlocking I would like to cite Doomlord from the Z2 phone CWM recovery thread:
Dont worry I have been on unlocked Bootloader on all my Xperia phones and honestly there is no functionality that I missed.
Click to expand...
Click to collapse
This!
(Yes, I know, the warranty, blah... )

dumbl3 said:
Yes, but that's why we here. To install custom roms and kernels I mean..
Sent from my LT26i using XDA Free mobile app
Click to expand...
Click to collapse
Actually I have customs on all my device, but on z1 (same for z2) never needed one, just root and exposed framework+adaway.
About unlocking, as far as I know the only "useful feature" you will disable should be the bravia engine.

Bravia Engine (or X-Reality) is not "useful", it's just oversaturating and exaggerating colors in an unnatural way. A feature for noobs, just like "Beats Audio" is a bass-booster for music-unsensible juvenile oomph-oomph listeners.
So it can easily be discarded without ever looking back.

hasenbein1966 said:
Bravia Engine (or X-Reality) is not "useful", it's just oversaturating and exaggerating colors in an unnatural way. A feature for noobs, just like "Beats Audio" is a bass-booster for music-unsensible juvenile oomph-oomph listeners.
So it can easily be discarded without ever looking back.
Click to expand...
Click to collapse
i agree on that but it voids your warranty.
Im not saying we should all wait till your warranty is over, but at least fully test your device before making a irrational decision, dead pixels, speakers, loose corners (have had 2 devices with that problem), waterproof test, etc...

LitoNi said:
i agree on that but it voids your warranty.
Im not saying we should all wait till your warranty is over, but at least fully test your device before making a irrational decision, dead pixels, speakers, loose corners (have had 2 devices with that problem), waterproof test, etc...
Click to expand...
Click to collapse
True, last thing you want is to void the warranty and find out something covered by it goes bad. I can wait. This baby is running nice so far. Dont need custom rom, but im missing that root!!

SD card write
Is anyone else having issue to write to external sdcard ?

nizammoidu said:
Is anyone else having issue to write to external sdcard ?
Click to expand...
Click to collapse
That's the new rule implemented in kit kat, not Sony's fault.
This problem can be solved if root is available
Sent from my C6603 using XDA Premium 4 mobile app

what s that rule? I have been using kitkat with omni since it released in note 2 nd hammerhead. initially it had issues with selinux, then i wrote a patch to omni source as well. but here selinux is not the bad guy I suspect something to QUCOMSEC nd drm keys. l have root, can u give me pointer to fixes. This s my first sony device so I have idea, Thank u

nizammoidu said:
what s that rule? I have been using kitkat with omni since it released in note 2 nd hammerhead. initially it had issues with selinux, then i wrote a patch to omni source as well. but here selinux is not the bad guy I suspect something to QUCOMSEC nd drm keys. l have root, can u give me pointer to fixes. This s my first sony device so I have idea, Thank u
Click to expand...
Click to collapse
custom roms probably already coded it, thats why you didnt encounter the problem. Explanation of the problem can be found here provided by the OP.
If you have root already you can try both of the following,
*please note that Ive tried the xposed module on my Xperia Z running stock kit kat not Z2.
**please note, back up your stuff before proceeding, just incase something goes wrong and wipes your files.
[XPOSED] HandleExternalStorage requires Xposed framework installed. I am currently running this module and working fine.
[Playstore] SDFix: KitKat Writable MicroSD this was suggested by kingvortex in another thread, havent tried it yet, but the reviews seem to suggest it works.

hasenbein1966 said:
Bravia Engine (or X-Reality) is not "useful", it's just oversaturating and exaggerating colors in an unnatural way. A feature for noobs, just like "Beats Audio" is a bass-booster for music-unsensible juvenile oomph-oomph listeners.
So it can easily be discarded without ever looking back.
Click to expand...
Click to collapse
Sorry - but I just have to add my own experience as a "noob".
First: I gave that X-Reality thing a deeper check; I had two Z2 tablets for simultaneously checking how HD videos look with and without that X-Reality feature.
I usually dislike all kinds of "enhancers", whether for audio or video enhancement. First things to switch off.
But I have to admit: X-Reality really works. The Z2 with the feature on produced a far more lively, absorbing experience. It's hard to tell what exactly makes the difference, it's just there. Among other videos, I used the famous Samsung "build-a-helicopter" video for comparison. Contrasts were better, details improved a bit, colors got slightly accentuated, became deeper. The slightly oversaturated color reproduction of the Z2 of course is there - but with and without X-Reality.
In short: Videos were just more fun and pleasant to the eye.
Best of all: You can switch it off; but you don't want to.
To be honest: X-Reality is THE feature preventing me from rooting the Z2 now. I don't care for DRM keys, I don't care for a true-to-life color rendition. But I care for pictures and videos looking simply better.
Quite lenghty explanation - but I guess this is an issue to consider prior to unlocking your bootloader and waving X-Reality goodbye forever.
Second: Beats Audio is a bit more than a "bass-booster for music-unsensible juvenile oomph-oomph listeners".
I seem to be a 45 years old "music-unsensible" listener. In fact, I am a former professional musician, knowing just a bit about sound.
I don't see anything wrong with utilizing software techologies to overcome some of the acoustic issues tiny smartphone or tablet loudspeakers suffer of. It's not just about creating that "oomph-oomph" redneck sound; it's about compensating the shortcomings of problematic speaker setups.
That's what devices like HTCs One clearly demonstrated.
I'd be quite happy if our Z2 had anything similar to offer. :/
So please try to be a bit more reluctant if it comes to demonizing modern features not everybody may like, but which will be gone forever if you go the hasty way.

Unlock Bootloader

How to unlock bootloader on Sony Xperia M5.
How to unlock bootloader
1.In http://developer.sonymobile.com/unlockbootloader/ choose Sony Xperia M2.
2.Submit Email
3.Submit IMEI
4.And unlock bootloader with intruction.
You get the code? Then we continue.
Download the latest version here or Flashtool http://www.flashtool.net/downloads.php
After installation, go the path C: \ Users \ username \ .flashTool \ registeredDevices here and create a folder with the code-name of your machine (you can find out if flashtool click on BLU and see where in the log are in line «Current device» for example, in line 09/045/2015 23:45:08 - INFO - Current device: C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17 code machine will AB100C2DE3. Code which will write your name and location).
Later in this folder, create a text file and name it «ulcode» (without the quotes). Open, and in it write your unlock code, that you have on the site Sony. Save. Write code very carefully.
Now open flashtool and press the BLU. If everything is correct, in line you should write your code, pressing unlock. All should be ready to unlock.
Working on:E5633
I am not responsible for the broken device. Whatever you do, you do at your own risk
After unlocking bootloader will void the warranty

I forgot write. I get unlock code with my IMEI.

Interesting, I checked my Rooting Info as per the guide and it does say allowed.
I think giving Sony my IMEI will potentially void my warranty claims? Let me think about it.

ykphuah said:
Interesting, I checked my Rooting Info as per the guide and it does say allowed.
I think giving Sony my IMEI will potentially void my warranty claims? Let me think about it.
Click to expand...
Click to collapse
I think, in service centre check bootloader. If bootloader not unlocked, warranty is valid.

This method is working also on M5 dual, 6533
But the next step should be how to gain the root =)
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
ykphuah said:
Interesting, I checked my Rooting Info as per the guide and it does say allowed.
I think giving Sony my IMEI will potentially void my warranty claims? Let me think about it.
Click to expand...
Click to collapse
Probably no.
You could reLock your device from flashtool simply, before visiting the service center.

vsm778 said:
This method is working also on M5 dual, 6533
But the next step should be how to gain the root =)
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
Probably no.
You could reLock your device from flashtool simply, before visiting the service center.
Click to expand...
Click to collapse
Maybe 5633 ?

DukeMcWood said:
Maybe 5633 ?
Click to expand...
Click to collapse
yep, you're right, thanks

hello guys. when you unlock bootloader, can you than record 4k video in H.264 not H.265 and upload it to youtube?

vsm778 said:
This method is working also on M5 dual, 6533
Probably no.
You could reLock your device from flashtool simply, before visiting the service center.
Click to expand...
Click to collapse
Yes, you can relock your bootloader with Flash Tool but your DRM keys are gone forever, proprietary Sony features won't work even after relocking...
Also, it's veeeeeery unlikely, but they may check if your DRM keys still exist in Sony Service Center, in case they don't find them they'll know you've unlocked your bootloader...

How about port TWRP or CWM on Xperia M5 ? If we port recovery, we can get root.

mbc07 said:
Yes, you can relock your bootloader with Flash Tool but your DRM keys are gone forever, proprietary Sony features won't work even after relocking...
Also, it's veeeeeery unlikely, but they may check if your DRM keys still exist in Sony Service Center, in case they don't find them they'll know you've unlocked your bootloader...
Click to expand...
Click to collapse
I think there's a way to do it by backing up the TA partition. That's how Sony Xperia Z1 started. We root, unlock bootloader, backup TA and when we relock, we can actually restore the TA and DRM key

firdyRAY said:
I think there's a way to do it by backing up the TA partition. That's how Sony Xperia Z1 started. We root, unlock bootloader, backup TA and when we relock, we can actually restore the TA and DRM key
Click to expand...
Click to collapse
Err, no. To preserve your DRM keys you need a way to root without unlocking the bootloader (e.g. using an exploit), then you make a backup of your TA partition which will contain your DRM keys. If you unlocked your bootloader without a taking a TA backup first, your DRM keys are gone forever, even if you root your device afterwards and make a backup of your TA partition you won't have any keys at all because they already were wiped when you unlocked the bootloader, this applies to any Sony device.
In other words, currently there's no way of unlocking M5 bootloader and keeping your DRM keys, the hope is Xperia Z5 series or other flagship devices, they draw attention of many developers and like what happened with Z2 and Z3, for example, locked bootloader users probably gonna start a bounty or some kind of incentive for a way to root the locked variant of those flagships, eventually they'll find an exploit that probably can be ported to other devices with less development activity, like Xperia M4/M5.
It's the cat-and-mouse game, new flagships are released, devs will research possible exploits to those new flagship devices and when one is found it's very likely to work with most devices released at the same time (and that probably are unpatched too). Also, in Sony devices, if you have root in one firmware version, you'll automatically have root in any new firmware too (using tools like PRFCreator or dd Flasher)...
(as record, towelroot, developed originally for Galaxy S5, could be used in a lot of Xperia devices from that time, and the Xperia Z3 exploit was successfully ported to Xperia E3 as well and could probably be used in similar devices released around the same time like Xperia C3 and others)

Thank you! What's the chance of the M5 properly supported by custom rom, like FreeXperia and CyanogenMod?

optionalmgrr.la said:
Thank you! What's the chance of the M5 properly supported by custom rom, like FreeXperia and CyanogenMod?
Click to expand...
Click to collapse
I dont know. But, I want port flyme os from meizu devices.

camping here to get notified of root asap..

DukeMcWood said:
How to unlock bootloader on Sony Xperia M5.
How to unlock bootloader
Click to expand...
Click to collapse
Hello Duke,
On Sonymobile page for M5 it is showing that it is due to update to Android 6.0 Marshmellow which is coming soon.
So what do you think? I heard root isnt possible on Android 6.0 , and if rooted they will make it hard for the users.
Is it going to be well? or Rooting is history?
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.

Ketansa said:
Hello Duke,
On Sonymobile page for M5 it is showing that it is due to update to Android 6.0 Marshmellow which is coming soon.
So what do you think? I heard root isnt possible on Android 6.0 , and if rooted they will make it hard for the users.
Is it going to be well? or Rooting is history?
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Click to expand...
Click to collapse
I dont know about 6.0, because i dont have 6.0. In the near future i maybe port recovery. But i dont have original recovery.img from Xperia M5 for port.

mbc07 said:
Err, no. To preserve your DRM keys you need a way to root without unlocking the bootloader (e.g. using an exploit), then you make a backup of your TA partition which will contain your DRM keys. If you unlocked your bootloader without a taking a TA backup first, your DRM keys are gone forever, even if you root your device afterwards and make a backup of your TA partition you won't have any keys at all because they already were wiped when you unlocked the bootloader, this applies to any Sony device.
In other words, currently there's no way of unlocking M5 bootloader and keeping your DRM keys, the hope is Xperia Z5 series or other flagship devices, they draw attention of many developers and like what happened with Z2 and Z3, for example, locked bootloader users probably gonna start a bounty or some kind of incentive for a way to root the locked variant of those flagships, eventually they'll find an exploit that probably can be ported to other devices with less development activity, like Xperia M4/M5.
It's the cat-and-mouse game, new flagships are released, devs will research possible exploits to those new flagship devices and when one is found it's very likely to work with most devices released at the same time (and that probably are unpatched too). Also, in Sony devices, if you have root in one firmware version, you'll automatically have root in any new firmware too (using tools like PRFCreator or dd Flasher)...
(as record, towelroot, developed originally for Galaxy S5, could be used in a lot of Xperia devices from that time, and the Xperia Z3 exploit was successfully ported to Xperia E3 as well and could probably be used in similar devices released around the same time like Xperia C3 and others)
Click to expand...
Click to collapse
That's very lengthy but good to know. Thank you!
Ketansa said:
Hello Duke,
On Sonymobile page for M5 it is showing that it is due to update to Android 6.0 Marshmellow which is coming soon.
So what do you think? I heard root isnt possible on Android 6.0 , and if rooted they will make it hard for the users.
Is it going to be well? or Rooting is history?
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Click to expand...
Click to collapse
Well i personally don't trust any advice from any other source except for XDA just to be safe because we the internet have too many smart alecks who know nothing and try to act smart by being sarcastic. So i guess the safest thing to do is to check on XDA for root methods and go through the forum to see if it works for others

Ketansa said:
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Click to expand...
Click to collapse
I don't think he have a rooted M5. Before we get root, we must unlock the bootloader first, and this is the part that is not done yet.

firdyRAY said:
That's very lengthy but good to know. Thank you!
Well i personally don't trust any advice from any other source except for XDA just to be safe because we the internet have too many smart alecks who know nothing and try to act smart by being sarcastic. So i guess the safest thing to do is to check on XDA for root methods and go through the forum to see if it works for others
Click to expand...
Click to collapse
Hello Thank you,
Yes you are right, may be he is being Sarcastic or some kind of adware developer for corporates.
Looking in XDA forums.

Changing dpi and warranty

I'm tempted to change dpi to take advantage of 4k screen but wanted confirmation if doing so would void warranty. Also how do you change dpi and do you need to be rooted?
Thanks

Any modifacation voids your warrenty
And to edit your DPI you need to edit /system/build.prop and look for a line that says
"ro.sf.lcd_density=480"
(480 part may differ per user or device)
( i believe 4k dpi is 820)

Hi, how you can do that if there is no rooting for that device?

sev7en said:
Hi, how you can do that if there is no rooting for that device?
Click to expand...
Click to collapse
Flash recovery
Flash su binary
Rooted
Alternatively you can push it through adb

Envious_Data said:
Flash recovery
Flash su binary
Rooted
Alternatively you can push it through adb
Click to expand...
Click to collapse
how can I push it through adb?

Envious_Data said:
Flash recovery
Flash su binary
Rooted
Alternatively you can push it through adb
Click to expand...
Click to collapse
As first thanks for your reply, where did you get the Recovery? Did you the same of Z5?
Thanks,

tonylcc said:
how can I push it through adb?
Click to expand...
Click to collapse
sev7en said:
As first thanks for your reply, where did you get the Recovery? Did you the same of Z5?
Thanks,
Click to expand...
Click to collapse
I dont have a Z5 but Sony Xperia devices typically get a working Recovery shortly after release
I have tried pushing superUser through ADB many times logged in as sudo or root and it has been fine.
You can look up guides on "how to install ADB" and how to push "superSu through Adb"
It may be that my Z2's bootloader is unlocked hence why im able to root it so easily but i havent the time to test the fact.

Envious_Data said:
I dont have a Z5 but Sony Xperia devices typically get a working Recovery shortly after release
I have tried pushing superUser through ADB many times logged in as sudo or root and it has been fine.
You can look up guides on "how to install ADB" and how to push "superSu through Adb"
It may be that my Z2's bootloader is unlocked hence why im able to root it so easily but i havent the time to test the fact.
Click to expand...
Click to collapse
Thanks but you are reporting that without to have checked it with the device? I am curious to try the 4K in the whole system...

ZohabK said:
I used this guide, and it worked perfectly!
Let me know if you have problems with it...
http://android.wonderhowto.com/how-...creen-resolution-without-root-access-0160439/
Click to expand...
Click to collapse
This guy seems to have done it without root using the linked method.

Craleb said:
This guy seems to have done it without root using the linked method.
Click to expand...
Click to collapse
And here's the proof...
http://forum.xda-developers.com/showthread.php?p=63858899

ZohabK said:
And here's the proof...
http://forum.xda-developers.com/showthread.php?p=63858899
Click to expand...
Click to collapse
Thanks for posting that. I was curious as to what DPI you went with.

Envious_Data said:
I dont have a Z5 but Sony Xperia devices typically get a working Recovery shortly after release
I have tried pushing superUser through ADB many times logged in as sudo or root and it has been fine.
You can look up guides on "how to install ADB" and how to push "superSu through Adb"
It may be that my Z2's bootloader is unlocked hence why im able to root it so easily but i havent the time to test the fact.
Click to expand...
Click to collapse
People are reporting that the camera's features stop working once you unlock the bootloader... Can you confirm this? I believe it was reported that two major camera functions stop...don't know if there is a workaround yet.

gparmar76 said:
People are reporting that the camera's features stop working once you unlock the bootloader... Can you confirm this? I believe it was reported that two major camera functions stop...don't know if there is a workaround yet.
Click to expand...
Click to collapse
Im not sure about how it is with the Z5P
But with my Z2 2 things stopped, post processing and xreality which in my opinion both are a waste of time

You can change you DPI by running
adb shell wm density 400
and reset it by running
adb shell wm density reset
You don't have to root or unlock your bootloader to change screen density.

CLShortFuse said:
You can change you DPI by running
adb shell wm density 400
and reset it by running
adb shell wm density reset
You don't have to root or unlock your bootloader to change screen density.
Click to expand...
Click to collapse
Would doing so void your warranty?

riz157 said:
Would doing so void your warranty?
Click to expand...
Click to collapse
Ask a lawyer who specialises in consumer law in the country you live in. They would definitely know.
Sent from my SGP311 using XDA Free mobile app

riz157 said:
Would doing so void your warranty?
Click to expand...
Click to collapse
Any customization voids your warranty. But you can always change back the DPI to factory...
Sorry for my weak english

I need a little help. I changed my dpi to 400 using adb and now the icons don't fill the screen

kamalaggi said:
I need a little help. I changed my dpi to 400 using adb and now the icons don't fill the screen
Click to expand...
Click to collapse
Yeah the stock launcher won't adapt to the DPI the way you'd think. You could try Nova with the 400 DPI.

what is the consensus what is the best dpi?

[GUIDE] How to root Xperia XZ1 Compact

Hello together,
WARNING!!! Unlocking the bootloader stops stock Sony camera from working (takes green pics after) and possibly other things.
There are workarounds for camera but the quality is worse than stock sony. (see step 11)
I finally was able to root my Xperia XZ1 Compact and I wanted to share my experience.
It was a bit complicated, because Magisk did not work at all (older versions did not do anything and recent versions ended up in bootloops) and flashing SuperSU did not flash because missing unzip in recovery.
So I decided to do a little research about the unzip problem. I analysed the install script of SuperSU and came to the conclusion that the installation error was caused by a missing unzip binary (or symlink) in /sbin/ of the recovery. So I unpacked the recovery done by modpunk (many thanks for creating the recovery, I am not yet able to do so myself...) and compared it to other twrp versions. There were two differences in sbin: our version did not have an unzip symlink and modpunk did include something named toybox instead of busybox. I decided to try to temporary add busybox and a unzip symlink to the recovery and it worked.
So here a step by step guide (Basic knowledge of adb and fastboot is required):
1. Install the firmware you want to root with newflasher and boot it once to ensure that encryption is initialized and working. (rooting is confirmed working with version 47.1.A.2.374 and 47.1.A.5.51)
2. You obviously have to unlock your bootloader if not done yet.
3. Install the twrp from modpunk matching your firmware Version.
https://xor.cryptomilk.org/android/...3.1.1-0-lilac-stock-patchlevel-2017-10-01.img for version 47.1.A.2.374​https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img for version 47.1.A.5.51​4. Boot to twrp.
and now comes the trick
5. Connect your device to a pc and adb push the attached busybox to sbin (took it from twrp from another arm64 device cannot remember which).
adb push pathtobusybox\busybox /sbin/ (replace pathtobusybox with the loacation of the unziped busybox for example C:\ )​6. Open adb shell
adb shell​7. Give busybox the required rights
chmod 750 /sbin/busybox​8. Create unzip symlink
ln -s /sbin/busybox /sbin/unzip​
Remember these modifications are only temporary so do not reboot before flashing SuperSU
9. Now you should be able to flash SuperSU. I used the following Version : https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
10. Reboot to your fresh rooted device.
11. If looking for a workaround for camera taking green pics look here (it is for xz premium but works with our phone too): https://forum.xda-developers.com/xz-premium/how-to/tip-camera-fix-unlocked-rooted-sony-t3647333
If you restart twrp busybox and unzip are gone, this is only a temporary modification.
I hope this helps the ones of you that do not mind unlocking bootloader without working drm fix.
Many thanks to:
modpunk for twrp
sToRm// for camera workaround

Thanks for the guide. Having gone without it for so long though I'm still in no rush, might have felt differently if we didn't have no-root theming, but we do so I don't.

OMG!
Dude!
Finally ROOT!
Thanks!
I can confirm, that this method is also working with 47.1.A.5.51.
So let's have a look at the camera fix from //strom ^^

Does this method work on the full size xz1?

I Do not know if there is a recovery for the full size xz1...

I thought the full size and compact had the same hardware, similar to the way iPhone and Samsung does it?

I habe no idea if recovery for xz1 compact might work on xz1 because they have different displays.

Good point. Would different displays make a huge difference do you think?

blindman666 said:
11. If looking for a workaround for camera taking green pics look here (it is for xz premium but works with our phone too): https://forum.xda-developers.com/xz-premium/how-to/tip-camera-fix-unlocked-rooted-sony-t3647333
If you restart twrp busybox and unzip are gone, this is only a temporary modification.
I hope this helps the ones of you that do not mind unlocking bootloader without working drm fix.
Many thanks to:
modpunk for twrp
sToRm// for camera workaround
Click to expand...
Click to collapse
Please DON'T flash the DRM patch for XZP! The secd is different to other devices. It maybe will brick your device, because the TA is different! I'm actually working on the new version of XperiFIX which includes the DRM patch for XZ1 Compact.

I did Not link your drm patch, the link is for the working camera apps without a drm patch...

sToRm// said:
Please DON'T flash the DRM patch for XZP! The secd is different to other devices. It maybe will brick your device, because the TA is different! I'm actually working on the new version of XperiFIX which includes the DRM patch for XZ1 Compact.
Click to expand...
Click to collapse
Any chance you are gonna throw the full size xz1 in the program as well as the xz1 compact?

blindman666 said:
I did Not link your drm patch, the link is for the working camera apps without a drm patch...
Click to expand...
Click to collapse
I just wanted to warn other users before they try some thing without knowledge. There are a lot of users that would try this.
It's just a warning - not related to your link. Only a safety first thing.

Has anyone gotten Magisk to work on their device without running in debug mode, just running it on normal mode?

Nope, magisk does not work, i was able to get supersu to work but not magisk.

I saw this on another post, and tried :
I can do photos with only one app : Footej Camera (actual version : 2.1.9)
Xperia XZ1 Compact, 47.1.A.5.51, bootloader unlocked, rooted

lemassykoi said:
I saw this on another post, and tried :
I can do photos with only one app : Footej Camera (actual version : 2.1.9)
Xperia XZ1 Compact, 47.1.A.5.51, bootloader unlocked, rooted
Click to expand...
Click to collapse
Can you please post a full resolution image taken at the highest resolution using that camera app?

N1ghtr08d said:
Can you please post a full resolution image taken at the highest resolution using that camera app?
Click to expand...
Click to collapse
attached

Hi, reading all of your isssues about rooting the phone, perhaps may not be yet time to try to root.
Then, I must wait a few time to buy my new phone (XZ1 Compact) and keep my Z3 Compact alive.

lemassykoi said:
I saw this on another post, and tried :
I can do photos with only one app : Footej Camera (actual version : 2.1.9)
Xperia XZ1 Compact, 47.1.A.5.51, bootloader unlocked, rooted
Click to expand...
Click to collapse
Was able to get this working with the current version. Your tip made this phone usable for me again!

Can someone with ulbl test if aptx hd is working or if it's also effected by loss of drm keys?