Z2 root and unlocked bootloader - Xperia Z2 Tablet Q&A, Help & Troubleshooting

Is it possible to unlock the bootloader + root and keep the original rom? I can't find a stock rom for the 32gb wifi tablet
Sent from my SGP512 using Tapatalk

---

Anyone?
Sent from my SGP512 using Tapatalk

---

SnowManWales said:
Is it possible to unlock the bootloader + root and keep the original rom? I can't find a stock rom for the 32gb wifi tablet
Sent from my SGP512 using Tapatalk
Click to expand...
Click to collapse
Wrong thread but yes it is possible. And here are link to latest stock rom for SGP512:
http://forum.xda-developers.com/showthread.php?p=54755457

---

Thanks for the info, but I do think it's a general question, so not the wrong thread
Sent from my SGP512 using Tapatalk

---

SnowManWales said:
Thanks for the info, but I do think it's a general question, so not the wrong thread
Sent from my SGP512 using Tapatalk
Click to expand...
Click to collapse
Hey there,
Lets see if I can sort this out, as remember, we have a multi national group of users, and not always do we understand the question.
Now, being a new Z2 owner, but not new to android development, here is the deal as I see it.
You keep the original "stock" rom, but only in a sense. Yes, the core components are still in place, but more than likely a few things have changed.
1) most likely the boot.img, as in the case of an insecure kernel. Although this change is mostly done in ramdisk and not the kernel itself.
2) unlocked bootloader (depending on which root method you use)
3) addition of superuser or superSu
4) possibly some exploit files, most which may be cleaned up on rooting.
Bear in mind a couple other things might be changed, but in the end, it's still basically a stock OS as far as the core files go.
If you want to know if there is an easy way to go back to a totally "factory condition, well, you will need to flash a factory ROM (ftf image). Generally this takes care of things except for the DRM files (if you unlock bootloader, then you should back them up first)
Hope this is a little more inline with what you were requesting.
Personally, I rooted the latest version without doing the bootloader unlock. I believe by unloking bootloader, you only lose the DRM keys, and your /Data (downloaded apps). Somebody correct me if I'm wrong.

---

Well I unlocked the bootloader, rooted the device, tried to install busybox but no luck
BusyBox file was not found in the system declared path.
A popular method of installing BusyBox is to use this BusyBox app by Stericson in Google Play.
Results provided on your SGP512 device by Root Checker Pro version 1.3.4 from joeykrim in the Android Market - http://goo.gl/NcnHn
And root checker tells me this
Congratulations! You have root access!
Super User Application Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 121260 2014-10-23 16:16 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGP512 device by Root Checker Pro version 1.3.4 from joeykrim in the Android Market - http://goo.gl/NcnHn
Sent from my SGP512 using Tapatalk

---

SnowManWales said:
Well I unlocked the bootloader, rooted the device, tried to install busybox but no luck
********
BusyBox file was not found in the system declared path.
A popular method of installing BusyBox is to use this BusyBox app by Stericson in Google Play.
********
Super User Application Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 121260 2014-10-23 16:16 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Click to expand...
Click to collapse
Probably what's going on, is exactly what the error logs are telling you. You have root access, to look at files, but you have no /system RW access. Understand Root and /System RW are 2 different things (although most rooting methods generally give you both).
The "SU" file it refers to, is the superuser binary file. Without it being installed, nothing is going to work right. I might suggest you do one of the following.
a) Use the original root program, and run it 2 or three times and verify it installs the SU binary.
or
b) Use the root method that installs the custom recovery, and flash install the superuser package. (unfortunately this involves unlocking the bootloader)
Regardless of which method, you will still probably need to use your file explorer to set /system to RW after the rooting process.

---

Good afternoon guys, when root for the new version 4.4.4??
Thankss