yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 Edge Q&A, Help & Troubleshooting] croash:
See this thread for lots of details on 9250 variant.

http://xdaforums.com/showthread.php?p=60170560
[Mogul, XV6800 General] whipped99:
Hi all, I was wondering if anyone else is having the same issues as I am with my new 6800. I have noticed that on occasion the screen will change to a very light greenish hue when I press on the screen with the stylus. The screen immediately changes back to normal once I pull off the screen. This seems to happens several times throughout the day. Is this normal? Any possible fix? or return it? Thanks for your help!

Great forum BTW...
[Mogul, XV6800 General] leetsauce:
Yes, sometimes I do notice the hue change, but it doesn't happen very often. I don't believe it's a defect since I've seen it in more than one Mougls (though one had it worse than the other; the hue alternates with every tap or key press). Some expert opinion on this would be nice.
[Mogul, XV6800 General] SINNN:
Not normal~! The first batch of Moguls did not have this issue and they came with a harder screen to the touch. the HTC replaced the screen to a inferior quality resulting to this issue. I am a witness to this. We have to live with it or nag enough about it. I personally made Sprint and HTC replace my Mogul4 time for this and every replacement had this issue. So to prevent myself from being dropped from, the service I will just suck it up. Sad indeed. But i least I gave them hell for it. :eek:
[Mogul, XV6800 General] leetsauce:
If what you're saying is true, then perhaps the three bright spots on my screen (from pressure against the carrying case) is also a result of this inferior screen. Curse HTC for their cheap antics!
[Mogul, XV6800 General] whipped99:
I guess I'm going to go ahead and just live with it. I really don't want to go through the hassle of returning it just to get another that has the same issue or possibly something worse. Thanks all for your input.
[Mogul, XV6800 General] Dishe:
WRONG.

not a hardware issue, really.

You'll notice the scroll wheel also sometimes causes it.

Its a driver issue... when any input is received (screen tap, hardware button, etc...), the screen hue shifts every so slightly. Most don't notice it.

Some people on ppcgeeks have reported that depending on the rom you use, sometimes it goes away.
[Mogul, XV6800 General] SINNN:
Sorry, But I already went thru issue with HTC and SPrint. Neither both know why but they call it a defective unit. Reason why I state that the screen is different because I am furtunate to have bought 2 Mogul on the first day it was released. One for me and one for my GF. Then my Mogul ended up breaking its Stylus clip form the housing of the phone so like a moron I went over to have it replaced my Sprint thru the manufacture warranty. Spring decided to give me a onetime replacement thru the warranty. So when the phone got here first thing I noticed was a yellow color hue to the backlight and the screen kept changing from somewhat bluish tint to yellowish tint using any buttons including the scroll wheel and taping the screen. Immidietly I called Sprint and explained y frustration with this new usnit. They concluded that it was a defect. So the next mogul shipped had the same issue exept this one had a back backlight that kept shutting off. Again I sent it back and the forth mogul that I received had AGAIn a yellow look to it and dimmer backlight. I called Sprint and they said again that it was defective and to send it back. Now i finally got my 5th Mogul and this time the backlight was not yellow but more of a cold bluish color but more acceptable. It was not as brite as my first mogul but I just gave up on getting mogul after mogul and just decided to keep this one because I am sure If I send it back then Sprint will send me another yellow colored hue backlight again. How do I know that all my backlight on all those Moguls were kinda funny? Because I had my GF mogul in which was one of the first moguls sold. And comparing all the moguls to hers you can definately tell they are different. Also I must note that her screen is harder than all the new Moguls that i got. ALl my replacements including my current Mogul have a softer screen. Very noticable. That why I know for a fact that they changed screens to a inferior quality to cut cost. I must recommend everyone with this same issue to have them call Sprint and have them replace your unit. This way they can force HTS from replacing screens int he near future. Here is a pic of a mogul with a yellow hue backlight that flikers different colors when tapped or using the scroll wheel. You can see how the Mogul on the right is soo much whiter like it should be, this is my GF mogul. Her manufacture date is May 3 2007. One of the first batch of good moguls. Now you can see that my story is real and I am not lying or making up anything about the screen being different. So its not a driver issue. Its a DIFFERENT SCREEN all together. Remember when you break you mogul and have it replace.. compare both screen before you decide to stay with your replacement.

PS. My GF screen is very White and Bright and never flickers different colors when tapped. Its rock solid. And also if I tap it normaly I can really feel a different in how much harder her screen feel. Im 100% this is a very superior screen ALL moguls should come with. But we are not HTC and cant forced them to switch back :(
[Mogul, XV6800 General] borealcool:
Wow from reading people's comments I didn't think it was that bad. After seeing your picture though, that is completely unacceptable. Send a letter to HTC along with the photo and

demand

they send a replacement!
[Mogul, XV6800 General] SINNN:
You know... im sick of having to wait a week for replacement AFTER REPLACEMENT from sprint and the same bad screen i get. But i will emal HTC and see what they say.
[Galaxy S 5 Q&A, Help & Troubleshooting] vexsilver:
So I had to finally use my warranty for my S5 with Tmobile. I have the replacement but it came with Lollipop 5.1.1 and not Kitkat. I've started using Lollipop and it's a nightmare. I absolutely hate it and many of my apps are incompatible. I am a bit new to this but am well aware Samsung has pretty lousy performance with S5 and lollipop.

Knowing this, is there an efficient and safe way to downgrade without tripping knox? I did some googling but find more information on 5.0 Lollipop than 5.1.1. I'm surprised S5's got that update.
[Galaxy S 5 Q&A, Help & Troubleshooting] popmpopm:
you can with no problem ( right now no one have problem with imei )
[Galaxy S 5 Q&A, Help & Troubleshooting] vexsilver:
Thanks for the reply. What is the best way to get started reading up on that? I am a bit new to the rooting scene etc. I don't want anyone to spoonfeed me an answer--just kind of a general "where can I get started" thing so I can understand what firmware I need etc.
[Galaxy S 5 Q&A, Help & Troubleshooting] DuncaneD:
1. Go to sammobile website and click Firmware button.

2. Enter your device model in the search box

3. Select your country and the android version you want (in your case select 4.4.2)

4. Click Download button to download the firmware (you need to register to be able to download, don't worry it's free).

5. Download Odin and use it to flash the firmware you've downloaded (Google how to use it if you don't know how).

By the way, your phone doesn't need to be rooted to do all this. In the contrary, if it is already rooted, it will lose the root after doing these steps.

Hope that helps
[Xperia Z4 Tablet General] najoor:
Reserved

For FAQ, etc.
[Xperia Z4 Tablet General] Stevethegreat:
Thanks for this great guide.

My question is this. Since it would be easier to avoid all this, can this tool help us do it without having to downgrade?

http://www.xda-developers.com/chainfires-flashfire-can-now-create-fastboot-flashable-backups/

I mean would it also backup the DRM keys? Has anyone tried (preferably with a TA backup already in place so that he may not lose the keys in case that this won't work)...
[Xperia Z4 Tablet General] najoor:
No. This tool cannot help you and trust me there is no shortcut to avoid all of this.

Flashfire (the tool you mentioned) only works if you already have root access. There is no root available for this tablet without unlocking the bootloader, and unlocking the bootloader means you lose the TA partition immediately. So by the time you get this tool to work your TA partition will have been long erased.
[Xperia Z4 Tablet General] alex009988:
Hi. Does this solution suit only for people who have not erased drm keys yet and are be able to backup it? For those who lost, no up-to-date solution except for that http://xdaforums.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383 ?
[Xperia Z4 Tablet General] najoor:
Correct.
[Xperia Z4 Tablet General] mrdarek:
Not understand step:

1.1- Start by clean flashing any 28.0.A.8.260 firmware

without this step temporary root not work...

But how flash firmware if device has still locked bootloader? What tool using for this step?
[Xperia Z4 Tablet General] najoor:
You can download a tool called flashtool from http://www.flashtool.net/index.php and flash an unmodified ftf firmware. Because the firmware is unmodified the bootloader doesn't have to be unlocked. Many tutorials are available on xda and elsewhere about using this tool, which you can find by doing a Google search. As I said in the prerequisite section, "You should be able to flash an ftf file using flashtool. "
[Xperia Z4 Tablet General] ajamils:
anybody successfully tried this guide?
[Xperia Z4 Tablet General] mrdarek:
I learned how flash and succesfully do my first flash.

Currently I have problem with iovyroot

It always say

Error: Device not supported

rm: /data/local/tmp/tabackup/TA-*.img: No such file or directory

My current software is:

SGP771_28.0.A.8.251_R15A_UK Generic_1295-4697

and it earlier then december 2015 like need iovyroot

I can't find software *.260 like in guide, I don't know if this created that problem...

Maybe najoor version work because it was "customized" - it mean - with patched kernel. But if locked bootloader allow me flash customized firmware?
[Xperia Z4 Tablet General] najoor:
As you said it, the problem was that you didn't flash the 260 version, not that it wasn't customized.

If you can't find the right version I upload it and post a link in the OP. It takes a little time so check this thread again in about 5 hours.
[Xperia Z4 Tablet General] mrdarek:
I found "260" firmware and magically all start work :). I finished all job and have now root and recovery :).

It worth add tips about fastboot - you can check connection by command but also you can see - if LED on device is blue - connection in fastboot work (if not - try again)

My last question is about how check that DRM emulation work - under security after phone code is still errors. I 100% patched kernel and flash it properly.

Thanks for tutorial and support

Something just not work... Someone can check sizes ?:

boot.img - original kernel androplus 2.5: 17 756 160

andropatched.img - patched with my drm keys: 17 760 256

keys: 2 097 152
[Xperia Z4 Tablet General] najoor:
The sizes sound about right. What errors are you getting?

You can try to relock the bootloader using the instructions and see if your TA backup works. If that works then we can see why the kernel is patched correctly.
[Xperia Z4 Tablet General] mrdarek:
Hi - I succesfully restored bootloader (=locked it, and no errors in service) - so I'm sure - my keys are OK. It was very hard - 3x flash, 3 x try use restore (still was errors), and at last success!!!

Now all procedure again, almost from start - but I also more try if need - I send info tomorrow :)

---------------------------------------

Hmmm not work... Tested original marsmallow germany kernel and androkernel 2.4. Image test described in step 2.6 fail

Under security is: Blobs : generic error!

HUK: generic error!

Flashed kernels names are properly recognized under settings. root work. I not have idea where is bug. It must be during creating andropatched image - but no errors here:

C:\rootkit>drmonly boot.img andropatched.img TA-07102015.img

- Unpacking kernel

Found android boot image

Kernel version: 3.10.84

- Detected vendor: somc (Sony), device: karin, variant: row

- Unpacking initramfs

- Detected platform: 64-bit

- Detected Android version: 6.0

- Skipping drmfix. Unsuppported/untested for model karin

- Creating new initramfs

- Creating boot image

- Cleaning up

Done

C:\rootkit>

--------------------Maybe that line is wrong!!!!!!!!

Skipping drmfix. Unsuppported/untested for model karin

but how fix it?
[Xperia Z4 Tablet General] najoor:
You need to follow the instructions to the letter:

1- flash the esaxt same firmware that you made the TA backup with.

2- Restore TA backup.

I guarantee you it will work or l will help you debug it.
[Xperia Z4 Tablet General] mrdarek:
Not very understand. It was done. TA backup was done with "260" firmware. I'm able lock that firmware again, so it work. but it only lollipop, can't go into marshmallow from it.

Goal is: marshmallow with root twrp and drm. How achieve it?

I see - I have new device version (karin) so (hopefully) temporary this solution not work for me. I can have only marshmallow with root and twrp (no DRM) or marshmallow with DRM (no root and twrp). I must wait as developers support my device, and keep my keys in safe place to that time.
[Xperia Z4 Tablet General] najoor:
OK, I see what is going on.

When I use drmonly script version 4.24 I get the following:

C:\Users\najoor\Desktop\rootkernel_v4.24_Windows_Linux>drmonly.cmd boot.img test.img TA-07102015.img
- Unpacking kernel
Found android boot image
- Unpacking initramfs
- 64-bit platfrom detected
- Configuring secd
- Configuring wvkbd
- Configuring drmserver
- Creating new initramfs
- Creating boot image
- Cleaning up
Done

But if I use version 4.31:

C:\Users\shervin\Desktop\working\Download\rootkernel_v4.31_Windows_Linux>drmonly
.cmd boot.img x.img TA-07102015.img
- Unpacking kernel
Found android boot image
Kernel version: 3.10.84
- Detected vendor: somc (Sony), device: karin, variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 6.0
- Skipping drmfix. Unsuppported/untested for model karin
- Creating new initramfs
- Creating boot image
- Cleaning up
Done

I have no idea why [MENTION=357342]tobias.waldvogel[/MENTION] decided to remove the support for Tablet Z4 in the latest version of the drmonly script, but I can see that the DRM works fine with the old version.

I do not have persmission from [MENTION=357342]tobias.waldvogel[/MENTION] to post the older version of his script here so you have to ask him to either add support in the new version or give you the older version.
[Xperia Z4 Tablet General] mrdarek:
Thanks - so now I see where is problem. I try contact with author.

Heh - I send PM him but it was my fault :( [added: it not totally fault - Tobias work on new version and soon we should have new working utility for all :) ]

I'm enough clever to modify script in 5 minutes (it txt :P ), and enough stupid to flash it immediately. Now I have....

rooted marshmallow with DRM KEY and TWRP - job finished :)

To finish job I disabled in settings auto-update, because now it start possible :P
[Xperia Z4 Tablet General] Hybel1507:
FAILED <remote dtb not found>

Unlocked the bootloader and successfully retrieved TA partion with SGP771_28.0.A.8.260 , installed stock 32.1.A.1.185, tablet runs fine without problems.

Retrieving the boot.img from Z4T_SGP771_AndroPlusKernel_v27 for my SGP771 device and running

fastboot boot boot.img

gives

This happens even with the 32.1.A.1.185 stock boot.img. Tried on Kubuntu 16.04 and WIN7. Same result. When I flash

the AndroPlusKernel_v27 boot.img,

fastboot flash boot boot.img

finishes without errors and tablet does not boot any more but -thanks God- fastboot mode still functioning.

I am lost. Can not root my tablet :( . Any clues?

---------- Post added at 04:14 PM ---------- Previous post was at 03:41 PM ----------

Sorry, correction:

first retrieved TA partion, then unlocked bootloader.
[Xperia Z4 Tablet General] najoor:
Please follow the following steps exactly and let me know in what step things fail. If you do not provide detailed information I will not be able to help you.

1- Clean flash a 185 ftf and make sure system boots fine.

2- extract the kernel.elf from the ftf and I use fastboot to see if you can boot using fastboot with this kernel.

3- extract boot.img from AndroPlusKernel_v27 and see if you can use fastboot to boot with this image.

4- use the procedure in the OP to patch AndroPlus kernel and see if you can use fastboot to boot with this image.

5- flash this image using fastboot to see if the system boots fine.
[Xperia Z4 Tablet General] Kenshiro7:
Thank you very much for this great guide, I was able to back up my DRM keys before rooting my tablet.
[Xperia Z4 Tablet General] Hybel1507:
Thank you for your fast reply. Started out with factory reset, following steps of your guide.

Result: Full success!!!! :D

Everything works! Root, DRM emulation.

Thanks to all the developers and this guide. Now I love my Z4 Tablet even more. I do not like not to be in full charge of my devices, i.e., life without ROOT is incomplete.
[Xperia Z4 Tablet General] ShiraiwaRiku:
I've tried to flash SGP712_28.0.A.8.260_R3A_Latin America Generic_1295-9724.ftf (the only one i can find)

when I finished and boot into home screen, there are two error messages: unfortunately, the android.process.acore and android.process.media has stopped and the device just restarts by itself over and over again...

I tried to tabackup in iovyroot, but the device always restarts on the step of Removing JOP

I've been trying to do this for 6 hours now, and this is as far as I got..

do I need another 28.0.A.8.260 firmware?

or am I doing something wrong?

Please help me
[Xperia Z4 Tablet General] najoor:
You did not succeed likely because you did not do a clean flash of the firmware. A clean flash means that you should wipe everything including the data on your tablet. I am guessing that you have downgraded from Marshmallow to 260. The app data in marshmallow is incompatible with Lollipop and therefore you will get force closes all over the place, more prominently with android core process (android.process.acore).

If you can, reset your tablet using the settings menu. A better option is to re-flash the ROM but this time make sure the tablet data is wiped. For example, if you are using Flashtool version 0.9.20.0, under the "wipe" section make sure all the items (APP_LOG, B2B, DIAG, SSD USERDATA) are selected.
[Xperia Z4 Tablet General] ShiraiwaRiku:
thanks for the reply..

I tried to get into the setting and do factory reset

but the device just keeps on restarting on its own

is there any way to do that without turning the device on? (like recovery mode etc??)
[Xperia Z4 Tablet General] najoor:
Please read the answer I gave you before asking the exact same question:
[Xperia Z4 Tablet General] ShiraiwaRiku:
hey... sorry if I annoyed you in any way...

It's just that I'm really new to this, so half of the time I don't understand what you are saying, and when I was trying to do this, I ran into series of problems...

eg. I'm using SGP712 so I can't dial *#*#7378423#*#*, and cant use the firmware you provided, googled a hidden trick in contact setting to solve that issue

adb devices: shows up empty, when I finally got it to show, its status was offline

how to create FTF file from downloaded files from XperiFirm

how to open command line in folder

have to put boot-patch file in device

etc etc...

I'm sure most of problems were due to lack of knowledge on this field... (of course the problem I ran into now is no exception)

but everything seems to working fine now... (although it took me literally 11 hours)

Thanks for everything! You are wonderful!
[Xperia Z4 Tablet General] Hybel1507:
I fully subscribe to your comment. This was acztually my fault, that I forgot to make a factory reset after flashing the 28 firmware. After a full wipe, your guide worked like a charm.
[Xperia Z4 Tablet General] MM365:
device not rebooting

Hi!

I tried rooting my sony xperia z4 tablet SGP771, but now it's not rebooting -.-

I thought I did all steps according to the guide.

- I enabled USB Debugging

- installed all Sony drivers

- unlocked bootloader

- ran fastboot flash boot -> which reported success.

sending 'boot' <17056 KB>...
OKAY [ 0.460s]
writing 'boot'....
OKAY [ 0.110s]
finished. total time: 0.580s

but after I told the device to reboot, it won't - just the red led is blinking ( I guess signalling that the device is charging)

Can you please help me?
[Xperia Z4 Tablet General] najoor:
This happens when a) your boot image is corrupted or b) the image your are trying to flash doesn't match the firmware version currently installed on your system or c) the boot image is a valid Sony image but something else (for example in /system) has been modified and when the kernel tries to verify the integrity of the system it fails.

The systematic method to debug this is to first flash a full factory image using flashtool (under wipe select all the options) and make sure the system boots fine. Then, before flashing any kernel test it out first by running this command in fastboot mode:

fastboot boot kernel.img

This boots the system without actually flashing the kernel. If this step fails then something is wrong with your kernel image.
[Xperia Z4 Tablet General] MM365:
Thank you for your help. Unfortunately the flashtool is not starting on my PC.

I followed the installation steps from the official guide

and when I run the flashtool Emma, it shows up as a process in the task manager, but not as a program & it's not starting.

I saw in the forum that others are experiencing similar problems with Emma, and I have not found a suggested solution there -.-

Do you have any idea what's going wrong? Disabling the Firewall did not work either.

Thanks in advance.
[Xperia Z4 Tablet General] najoor:
I don't know about Emma cus I never use it. But when my flashtool doesn't start it because there are old copies of it dormant in memory and I should kill them in task manager. Also try rebooting and finally uninstalling and reinstalling flashtool. Once you get that working go to my previous post and start Debugging.
[Xperia Z4 Tablet General] MM365:
Which flashtool do you use instead?

I just found the Sony Mobile Flasher by Androxyde, which starts and also recognizes that a device is connected.

- can you post me a link for the full factory image I need to flash?
[Xperia Z4 Tablet General] najoor:
Yes, androxyde flashtool is what you should be using to flash an ftf image (the equivalent of a factory image for xperia phones).

If you decide to use the said flashtool I strongly urge you to read or watch a tutorial on how to use it.

If you have an LTE model the link to a lollipop firmware to flash is posted in the original OP. If your have a WiFi model unfortunately I don't have a link to give you. Just use Google and find an ftf.

Or do you need a link for marshmallow firmware?
[Xperia Z4 Tablet General] MM365:
Thanks. The link you provided was the right one for my tablet.

I just flashed the ftf image and it's finally booting. I'm so happy :) thank you very much!!!!!!

I think I will have a break now, before I try again rooting my device.

You made my day!

- - Edit - -

I now also understand what I did wrong - I did not read the steps as thoroughly as I thought.

As you suggested from your first reply I did try to flash a kernel which did not match the firmware.

Everything is now working like a charm
[Xperia Z4 Tablet General] kuroneko007:
Great guide, although us SGP712 Wifi owners are left to do a lot of extra work to fill in the missing steps.

Perhaps you could add the following info to the first post?

28.0.A.8.260 for SGP712 (Wi-Fi only model):

https://mega.nz/#!wlIl0JDa!DR0lRL6dDn5Y-K_4768oJnLGWQyrxNV0xLHgKVVesFw

How to access service menu on SGP712 (Wi-Fi only model) - needed as we have no dialer app:

http://xdaforums.com/showpost.php?p=66164176&postcount=5

Thanks, & much appreciation for the hard work to put together the guide.